1.
ER saClmClusterNodeGet failed, rc=SA_AIS_ERR_NOT_EXIST (12):
This is because SMF gets a NCSMDS_UP for a SMF ND but when checking if this is
a CLM node
CLM answer that the node does not exist. There are AMF logs indicating that
this problem is
detected by AMF as well but AMF does not log this as an ER. Ticket #1969 is for
making SMF
more robust and tunable for handling nodes that does not start immediately.
2.
ER node id [2030f] not found for state update DOWN:
This is because SMF gets a NCSMDS_UP for a SMF ND but a node director with this
Id cannot be found in the SMF node director list. This problem is probably
because SMF fail to register the node director when it is started because of
problem 1.
---
** [tickets:#1872] smf: ER messages when handling smfnd node up**
**Status:** accepted
**Milestone:** 5.0.2
**Created:** Fri Jun 10, 2016 08:41 AM UTC by elunlen
**Last Updated:** Fri Dec 09, 2016 03:35 PM UTC
**Owner:** elunlen
The following error messages is written in syslog:
2016-05-09 21:47:01 SC-2 osafsmfd[595]: ER saClmClusterNodeGet failed,
rc=SA_AIS_ERR_NOT_EXIST (12)
2016-05-09 21:47:01 SC-2 osafsmfd[595]: ER node id [2030f] not found for state
update DOWN
This happen when MDS detects node up but when SMF asks CLM for node information
for the node it is down again resuling in a NOT EXIST answer from CLM
---
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.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
