- **status**: review --> fixed
- **assigned_to**: Vu Minh Nguyen --> nobody
- **Comment**:
changeset: 8357:2f1901bd5e3f
tag: tip
parent: 8354:288991466a47
user: Vu Minh Nguyen <[email protected]>
date: Thu Nov 17 13:10:24 2016 +0700
summary: ntf: handle error code TRY_AGAIN of saClmInitialize() [#2191]
changeset: 8356:898ed6baeb2f
branch: opensaf-5.1.x
parent: 8352:15416dce3e2d
user: Vu Minh Nguyen <[email protected]>
date: Thu Nov 17 13:10:24 2016 +0700
summary: ntf: handle error code TRY_AGAIN of saClmInitialize() [#2191]
changeset: 8355:6833e9b1d421
branch: opensaf-5.0.x
parent: 8351:4eb1ebe62d35
user: Vu Minh Nguyen <[email protected]>
date: Thu Nov 17 13:10:24 2016 +0700
summary: ntf: handle error code TRY_AGAIN of saClmInitialize() [#2191]
---
** [tickets:#2191] ntf: not handle TRY_AGAIN of saClmInitialize_4()**
**Status:** fixed
**Milestone:** 5.0.2
**Created:** Thu Nov 17, 2016 03:12 AM UTC by Vu Minh Nguyen
**Last Updated:** Thu Nov 17, 2016 06:31 AM UTC
**Owner:** nobody
In current implementation, ntfsv does not deal with `SA_AIS_ERR_TRY_AGAIN` when
calling `saClmInitialize`. If that is the case, ntfsv will be exited, and in
consequence, the node will be reboot.
Below is the trace log, happened when testing roaming SC:
> 2016-11-15 18:13:25 SC-3 osafntfd[458]: ER saClmInitialize failed with error:
> 6
> 2016-11-15 18:13:25 SC-3 osafrded[412]: NO Peer down on node 0x2020f
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
