---
** [tickets:#1290] AMF: node rebooted when immnd is killed twice in succession**
**Status:** unassigned
**Milestone:** 4.6.RC1
**Created:** Mon Mar 30, 2015 07:07 AM UTC by Sirisha Alla
**Last Updated:** Mon Mar 30, 2015 07:07 AM UTC
**Owner:** nobody
The issue is observed in 4.6 FC Tag changeset 6377.
IMM Application is running on standby controller. When the application killed
IMMND twice, the standby controller went for reboot. Following is the syslog on
SC-2:
Mar 26 14:56:44 SLES-64BIT-SLOT2 sudo: tet : TTY=unknown ;
PWD=/tmp/10199aa ; USER=root ; COMMAND=/bin/kill -9 9282
Mar 26 14:56:44 SLES-64BIT-SLOT2 osafamfnd[9368]: NO
'safSu=SC-2,safSg=NoRed,safApp=OpenSAF' component restart probation timer
started (timeout: 60000000000 ns)
Mar 26 14:56:44 SLES-64BIT-SLOT2 osafamfnd[9368]: NO Restarting a component of
'safSu=SC-2,safSg=NoRed,safApp=OpenSAF' (comp restart count: 1)
Mar 26 14:56:44 SLES-64BIT-SLOT2 osafamfnd[9368]: NO
'safComp=IMMND,safSu=SC-2,safSg=NoRed,safApp=OpenSAF' faulted due to 'avaDown'
: Recovery is 'componentRestart'
Mar 26 14:56:44 SLES-64BIT-SLOT2 osafntfimcnd[9328]: NO saImmOiDispatch() Fail
SA_AIS_ERR_BAD_HANDLE (9)
Mar 26 14:56:44 SLES-64BIT-SLOT2 osafamfd[9358]: NO Re-initializing with IMM
Mar 26 14:56:44 SLES-64BIT-SLOT2 osafimmnd[10260]: Started
Mar 26 14:56:44 SLES-64BIT-SLOT2 osafimmnd[10260]: NO Persistent Back-End
capability configured, Pbe file:imm.db (suffix may get added)
Mar 26 14:56:44 SLES-64BIT-SLOT2 osafimmnd[10260]: NO Fevs count adjusted to
52406 preLoadPid: 0
Mar 26 14:56:44 SLES-64BIT-SLOT2 osafimmnd[10260]: NO SERVER STATE:
IMM_SERVER_ANONYMOUS --> IMM_SERVER_CLUSTER_WAITING
Mar 26 14:56:44 SLES-64BIT-SLOT2 osafimmnd[10260]: NO SERVER STATE:
IMM_SERVER_CLUSTER_WAITING --> IMM_SERVER_LOADING_PENDING
Mar 26 14:56:44 SLES-64BIT-SLOT2 osafimmnd[10260]: NO SERVER STATE:
IMM_SERVER_LOADING_PENDING --> IMM_SERVER_SYNC_PENDING
Mar 26 14:56:44 SLES-64BIT-SLOT2 osafimmnd[10260]: NO NODE STATE->
IMM_NODE_ISOLATED
Mar 26 14:56:45 SLES-64BIT-SLOT2 osafimmd[9272]: NO SBY: Ruling epoch noted
as:11
Mar 26 14:56:45 SLES-64BIT-SLOT2 osafimmd[9272]: NO IMMND coord at 2010f
Mar 26 14:56:45 SLES-64BIT-SLOT2 osafimmnd[10260]: NO NODE STATE->
IMM_NODE_W_AVAILABLE
Mar 26 14:56:45 SLES-64BIT-SLOT2 osafimmnd[10260]: NO SERVER STATE:
IMM_SERVER_SYNC_PENDING --> IMM_SERVER_SYNC_CLIENT
Mar 26 14:56:58 SLES-64BIT-SLOT2 osafimmd[9272]: NO SBY: New Epoch for IMMND
process at node 2030f old epoch: 10 new epoch:11
Mar 26 14:56:58 SLES-64BIT-SLOT2 osafimmd[9272]: NO SBY: New Epoch for IMMND
process at node 2040f old epoch: 10 new epoch:11
Mar 26 14:56:58 SLES-64BIT-SLOT2 osafimmd[9272]: NO SBY: New Epoch for IMMND
process at node 2010f old epoch: 10 new epoch:11
Mar 26 14:56:58 SLES-64BIT-SLOT2 osafimmd[9272]: NO IMMND coord at 2010f
Mar 26 14:56:58 SLES-64BIT-SLOT2 osafimmnd[10260]: NO NODE STATE->
IMM_NODE_FULLY_AVAILABLE 2588
Mar 26 14:56:58 SLES-64BIT-SLOT2 osafimmnd[10260]: NO RepositoryInitModeT is
SA_IMM_KEEP_REPOSITORY
Mar 26 14:56:58 SLES-64BIT-SLOT2 osafimmnd[10260]: WA IMM Access Control mode
is DISABLED!
Mar 26 14:56:58 SLES-64BIT-SLOT2 osafimmnd[10260]: NO Epoch set to 11 in
ImmModel
Mar 26 14:56:58 SLES-64BIT-SLOT2 osafimmd[9272]: NO SBY: New Epoch for IMMND
process at node 2020f old epoch: 0 new epoch:11
Mar 26 14:56:58 SLES-64BIT-SLOT2 python2.5: IN Received PROC_STALE_CLIENTS
Mar 26 14:56:58 SLES-64BIT-SLOT2 python2.5: IN Received PROC_STALE_CLIENTS
Mar 26 14:56:58 SLES-64BIT-SLOT2 osafimmnd[10260]: NO Implementer connected:
141 (MsgQueueService131599) <308, 2020f>
Mar 26 14:56:58 SLES-64BIT-SLOT2 osafimmnd[10260]: NO SERVER STATE:
IMM_SERVER_SYNC_CLIENT --> IMM SERVER READY
Mar 26 14:56:58 SLES-64BIT-SLOT2 osafimmnd[10260]: NO PBE-OI established on
other SC. Dumping incrementally to file imm.db
Mar 26 14:56:58 SLES-64BIT-SLOT2 osafimmnd[10260]: NO Implementer (applier)
connected: 142 (@safAmfService2020f) <457, 2020f>
Mar 26 14:56:58 SLES-64BIT-SLOT2 sudo: tet : TTY=unknown ;
PWD=/tmp/10199aa ; USER=root ; COMMAND=/bin/kill -9 10260
Mar 26 14:56:58 SLES-64BIT-SLOT2 osafamfnd[9368]: NO Restarting a component of
'safSu=SC-2,safSg=NoRed,safApp=OpenSAF' (comp restart count: 2)
Mar 26 14:56:58 SLES-64BIT-SLOT2 osafamfnd[9368]: NO
'safComp=IMMND,safSu=SC-2,safSg=NoRed,safApp=OpenSAF' faulted due to 'avaDown'
: Recovery is 'componentRestart'
Mar 26 14:56:58 SLES-64BIT-SLOT2 osafamfd[9358]: NO Re-initializing with IMM
Mar 26 14:56:58 SLES-64BIT-SLOT2 osafimmnd[10346]: Started
Mar 26 14:56:58 SLES-64BIT-SLOT2 osafimmnd[10346]: NO Persistent Back-End
capability configured, Pbe file:imm.db (suffix may get added)
Mar 26 14:56:58 SLES-64BIT-SLOT2 osafimmnd[10346]: NO SERVER STATE:
IMM_SERVER_ANONYMOUS --> IMM_SERVER_CLUSTER_WAITING
Mar 26 14:56:58 SLES-64BIT-SLOT2 osafimmnd[10346]: NO SERVER STATE:
IMM_SERVER_CLUSTER_WAITING --> IMM_SERVER_LOADING_PENDING
Mar 26 14:56:58 SLES-64BIT-SLOT2 osafimmnd[10346]: NO SERVER STATE:
IMM_SERVER_LOADING_PENDING --> IMM_SERVER_SYNC_PENDING
Mar 26 14:56:58 SLES-64BIT-SLOT2 osafimmnd[10346]: NO NODE STATE->
IMM_NODE_ISOLATED
Mar 26 14:57:02 SLES-64BIT-SLOT2 osafimmd[9272]: NO SBY: Ruling epoch noted
as:12
Mar 26 14:57:02 SLES-64BIT-SLOT2 osafimmd[9272]: NO IMMND coord at 2010f
Mar 26 14:57:02 SLES-64BIT-SLOT2 osafimmnd[10346]: NO NODE STATE->
IMM_NODE_W_AVAILABLE
Mar 26 14:57:02 SLES-64BIT-SLOT2 osafimmnd[10346]: NO SERVER STATE:
IMM_SERVER_SYNC_PENDING --> IMM_SERVER_SYNC_CLIENT
Mar 26 14:57:08 SLES-64BIT-SLOT2 osafamfd[9358]: ER Impl Set Failed for
SaAmfHealthcheckType, returned 9
Mar 26 14:57:08 SLES-64BIT-SLOT2 osafamfd[9358]: ER exiting since
avd_imm_applier_set failed
Mar 26 14:57:08 SLES-64BIT-SLOT2 osafamfnd[9368]: ER AMF director unexpectedly
crashed
Mar 26 14:57:08 SLES-64BIT-SLOT2 osafamfnd[9368]: Rebooting OpenSAF NodeId =
131599 EE Name = , Reason: local AVD down(Adest) or both AVD down(Vdest)
received, OwnNodeId = 131599, SupervisionTime = 60
Mar 26 14:57:08 SLES-64BIT-SLOT2 opensaf_reboot: Rebooting local node;
timeout=60
syslog and amfd traces of SC-2 are 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.
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
