OS : Suse 64bit
Changeset : 8634 ( 5.2.FC)
Setup : 4 nodes ( 2 controllers and 2 payloads & PBE enabled)
similar issue observed again while running switchover scenarios.
Mar 1 14:50:58 TestBed-R2 osafsmfd[487]: NO Verify Timeout = 100000000000
Mar 1 14:50:58 TestBed-R2 osafsmfd[487]: NO smfKeepDuState = 0
Mar 1 14:50:50 TestBed-R2 osaflcknd[403]: ER GLND agent node not found:
2020f5754c046
Mar 1 14:50:49 TestBed-R2 osafntfimcnd[3041]: WA ntfimcn_imm_init
saImmOiInitialize_2() returned SA_AIS_ERR_TIMEOUT (5)
Mar 1 14:50:48 TestBed-R2 osafimmnd[32765]: NO Implementer connected: 23
(safLckService) <135, 2020f>
Mar 1 14:50:57 TestBed-R2 osafevtd[388]: ER saImmOiImplementerSet failed with
error: 5
Mar 1 14:50:57 TestBed-R2 osaflckd[421]: ER saImmOiImplementerSet FAILED, rc =
5
Mar 1 14:50:58 TestBed-R2 osafamfnd[349]: NO
'safComp=EDS,safSu=SC-2,safSg=2N,safApp=OpenSAF' faulted due to 'avaDown' :
Recovery is 'nodeFailfast'
Mar 1 14:50:58 TestBed-R2 osafamfnd[349]: ER
safComp=EDS,safSu=SC-2,safSg=2N,safApp=OpenSAF Faulted due to:avaDown Recovery
is:nodeFailfast
Mar 1 14:50:58 TestBed-R2 osafamfnd[349]: Rebooting OpenSAF NodeId = 131599 EE
Name = , Reason: Component faulted: recovery is node failfast, OwnNodeId =
131599, SupervisionTime = 60
Mar 1 14:50:57 TestBed-R2 osafclmd[329]: ER saImmOiImplementerSet failed, rc =
5
Mar 1 14:50:58 TestBed-R2 osaflogd[309]: WA saImmOiClassImplementerSet
returned SA_AIS_ERR_TIMEOUT (5)
Mar 1 14:50:58 TestBed-R2 osafimmnd[32765]: NO Implementer connected: 24
(safEvtService) <123, 2020f>
Mar 1 14:50:58 TestBed-R2 opensaf_reboot: Rebooting local node; timeout=60
Mar 1 14:50:59 TestBed-R2 osafntfimcnd[3041]: WA ntfimcn_imm_init
saImmOiInitialize_2() returned SA_AIS_ERR_TIMEOUT (5)
Mar 1 14:50:59 TestBed-R2 osafimmnd[32765]: WA MDS Send Failed
Mar 1 14:50:59 TestBed-R2 osafimmnd[32765]: WA Failed to send response to
agent/client over MDS
---
** [tickets:#2116] EDS faulted on new Active controller after being promoted
from QUIESCED to ACTIVE**
**Status:** unassigned
**Milestone:** 5.0.2
**Created:** Thu Oct 13, 2016 09:49 AM UTC by Ritu Raj
**Last Updated:** Thu Nov 24, 2016 05:26 AM UTC
**Owner:** nobody
**Attachments:**
-
[messages](https://sourceforge.net/p/opensaf/tickets/2116/attachment/messages)
(2.9 MB; application/octet-stream)
-
[osafevtd](https://sourceforge.net/p/opensaf/tickets/2116/attachment/osafevtd)
(102.4 kB; application/octet-stream)
# Environment details
OS : Suse 64bit
Changeset : 8190 ( 5.1.GA)
Setup : 3 nodes ( 3 controllers with headless feature enabled & PBE disabled)
# Summary
EDS faulted on new Active controller after being promoted from QUIESCED to
ACTIVE
# Steps followed & Observed behaviour
1. Initially started OpenSAF on 3 controller with HEADLESS feature enabled
(SC-1 ACTIVE, SC-2 Standby, SC-3 QUIESCED)
2. Stop OpenSAF on both the controller(Active/Standby) simultaneously
3. QUIESCED controller become Active as clmna Starting to promote this node to
a system controller
........
Oct 13 14:29:05 SCALE_SLOT-73 osafclmna[3434]: NO Starting to promote this node
to a system controller
Oct 13 14:29:05 SCALE_SLOT-73 osafrded[3443]: NO Requesting ACTIVE role
........
Oct 13 14:29:10 SCALE_SLOT-73 osafimmd[3462]: IN AMF HA ACTIVE request
Oct 13 14:29:10 SCALE_SLOT-73 osaffmd[3452]: NO Stopped activation supervision
due to new AMF state 1
Oct 13 14:29:10 SCALE_SLOT-73 osafamfd[3513]: NO Received node_up from 2030f:
msg_id 1
Oct 13 14:29:10 SCALE_SLOT-73 osafamfd[3513]: NO Node 'SC-3' joined the cluster
3. After few second EDS faulted and node went for reboot
........
Oct 13 14:30:11 SCALE_SLOT-73 osafamfnd[3523]: NO
'safComp=EDS,safSu=SC-3,safSg=2N,safApp=OpenSAF' faulted due to 'avaDown' :
Recovery is 'nodeFailfast'
Oct 13 14:30:11 SCALE_SLOT-73 osafamfnd[3523]: ER
safComp=EDS,safSu=SC-3,safSg=2N,safApp=OpenSAF Faulted due to:avaDown Recovery
is:nodeFailfast
Oct 13 14:30:11 SCALE_SLOT-73 osafamfnd[3523]: Rebooting OpenSAF NodeId =
131855 EE Name = , Reason: Component faulted: recovery is node failfast,
OwnNodeId = 131855, SupervisionTime = 60
** Notes
1. Syslog attached
2. osafevtd trace attached
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
