- **status**: unassigned --> not-reproducible
- **Milestone**: future --> never
- **Comment**:
Since no logs are attached and it says random, so please reopen with logs if it
occurs again.
---
** [tickets:#381] Opensafd on payload is not coming up during controller
switchover (random)**
**Status:** not-reproducible
**Milestone:** never
**Created:** Fri May 31, 2013 04:10 AM UTC by Nagendra Kumar
**Last Updated:** Fri May 31, 2013 04:10 AM UTC
**Owner:** nobody
Migrated from http://devel.opensaf.org/ticket/2393
Changeset: 3102
Setup: SLES 11 32bit VirtualBox?
OpenSAF is up on two controllers SC-1 (Active) and SC-2 (Standby) with TCP as
MDS transport and UNIX as intra-node transport
On the third node (PL-3) Opensafd is started and switchover is triggered from
SC-1 simultaneously.
The Active controller SC-1 went down due to AMFD crash (ticket #2318)
The payload got struck and came out after the timeout for response from AMFND.
The following is the syslog of PL-3:
Dec 2 14:47:27 SLES11-CONN-PC opensafd: Starting OpenSAF Services
Dec 2 14:47:27 SLES11-CONN-PC osafdtmd[8608]: Started
Dec 2 14:47:27 SLES11-CONN-PC osafimmnd[8623]: Started
Dec 2 14:47:27 SLES11-CONN-PC osafimmnd[8623]: Director Service is up
Dec 2 14:47:27 SLES11-CONN-PC osafimmnd[8623]: SERVER STATE:
IMM_SERVER_ANONYMOUS —> IMM_SERVER_CLUSTER_WAITING
Dec 2 14:47:27 SLES11-CONN-PC osafimmnd[8623]: SERVER STATE:
IMM_SERVER_CLUSTER_WAITING —> IMM_SERVER_LOADING_PENDING
Dec 2 14:47:27 SLES11-CONN-PC osafimmnd[8623]: SERVER STATE:
IMM_SERVER_LOADING_PENDING —> IMM_SERVER_SYNC_PENDING
Dec 2 14:47:27 SLES11-CONN-PC osafimmnd[8623]: NODE STATE-> IMM_NODE_ISOLATED
Dec 2 14:47:28 SLES11-CONN-PC osafimmnd[8623]: NODE STATE-> IMM_NODE_W_AVAILABLE
Dec 2 14:47:28 SLES11-CONN-PC osafimmnd[8623]: SERVER STATE:
IMM_SERVER_SYNC_PENDING —> IMM_SERVER_SYNC_CLIENT
Dec 2 14:47:34 SLES11-CONN-PC osafimmnd[8623]: NODE STATE->
IMM_NODE_FULLY_AVAILABLE 1892
Dec 2 14:47:34 SLES11-CONN-PC osafimmnd[8623]: RepositoryInitModeT is
SA_IMM_INIT_FROM_FILE
Dec 2 14:47:34 SLES11-CONN-PC osafimmnd[8623]: Epoch set to 7 in ImmModel?
Dec 2 14:47:34 SLES11-CONN-PC osafimmnd[8623]: SERVER STATE:
IMM_SERVER_SYNC_CLIENT —> IMM SERVER READY
Dec 2 14:47:34 SLES11-CONN-PC osafclmna[8639]: Started
Dec 2 14:47:34 SLES11-CONN-PC osafclmna[8639]:
safNode=PL-3,safCluster=myClmCluster Joined cluster, nodeid=20300
Dec 2 14:47:34 SLES11-CONN-PC osafamfnd[8648]: Started
Dec 2 14:47:34 SLES11-CONN-PC osafimmnd[8623]: Implementer disconnected 65 <0,
20100> (safLogService)
Dec 2 14:47:34 SLES11-CONN-PC osafimmnd[8623]: Implementer disconnected 68 <0,
20100> (safMsgGrpService)
Dec 2 14:47:34 SLES11-CONN-PC osafimmnd[8623]: Implementer disconnected 66 <0,
20100> (safEvtService)
Dec 2 14:47:34 SLES11-CONN-PC osafamfnd[8648]: Failed to start cluster
tracking: 6
Dec 2 14:47:34 SLES11-CONN-PC osafamfnd[8648]: Failed to stop cluster tracking 6
Dec 2 14:47:34 SLES11-CONN-PC osafamfnd[8648]: avnd_create failed
Dec 2 14:47:34 SLES11-CONN-PC osafamfnd[8648]: exiting
Dec 2 14:47:34 SLES11-CONN-PC osafimmnd[8623]: Implementer disconnected 70 <0,
20100> (safSmfService)
Dec 2 14:47:35 SLES11-CONN-PC osafimmnd[8623]: Implementer disconnected 69 <0,
20100> (safLckService)
Dec 2 14:47:35 SLES11-CONN-PC osafimmnd[8623]: Implementer disconnected 67 <0,
20100> (safCheckPointService)
Dec 2 14:47:35 SLES11-CONN-PC osafimmnd[8623]: Implementer disconnected 64 <0,
20100> (safClmService)
Dec 2 14:47:35 SLES11-CONN-PC osafimmnd[8623]: Director Service in NOACTIVE
state
Dec 2 14:47:36 SLES11-CONN-PC osafimmnd[8623]: Director Service Is NEWACTIVE
state
Dec 2 14:47:36 SLES11-CONN-PC osafimmnd[8623]: Implementer connected: 78
(safLogService) <0, 20200>
Dec 2 14:47:36 SLES11-CONN-PC osafimmnd[8623]: Implementer connected: 79
(safClmService) <0, 20200>
Dec 2 14:47:36 SLES11-CONN-PC osafimmnd[8623]: Implementer connected: 80
(safLckService) <0, 20200>
Dec 2 14:47:36 SLES11-CONN-PC osafimmnd[8623]: Implementer connected: 81
(safEvtService) <0, 20200>
Dec 2 14:47:36 SLES11-CONN-PC osafimmnd[8623]: Implementer connected: 82
(safCheckPointService) <0, 20200>
Dec 2 14:47:36 SLES11-CONN-PC osafimmnd[8623]: Implementer connected: 83
(safMsgGrpService) <0, 20200>
Dec 2 14:47:36 SLES11-CONN-PC osafimmnd[8623]: Implementer connected: 84
(safSmfService) <0, 20200>
Dec 2 14:47:38 SLES11-CONN-PC osafimmnd[8623]: Implementer disconnected 74 <0,
20100> (safAmfService)
Dec 2 14:47:38 SLES11-CONN-PC osafimmnd[8623]: Implementer (applier) connected:
85 (@safAmfService20100) <0, 20100>
Dec 2 14:47:38 SLES11-CONN-PC osafimmnd[8623]: Implementer disconnected 76 <0,
20200> (@safAmfService20200)
Dec 2 14:47:38 SLES11-CONN-PC osafimmnd[8623]: Implementer connected: 86
(safAmfService) <0, 20200>
Dec 2 14:47:41 SLES11-CONN-PC osafimmnd[8623]: Global discard node received for
nodeId:20100 pid:3705
Dec 2 14:47:41 SLES11-CONN-PC osafimmnd[8623]: Implementer disconnected 85 <0,
20100(down)> (@safAmfService20100)
Dec 2 14:47:41 SLES11-CONN-PC osafimmnd[8623]: Implementer disconnected 5 <0,
20100(down)> (MsgQueueService?131328)
Dec 2 14:47:46 SLES11-CONN-PC osafdtmd[8608]: DTM:dtm_comm_socket_recv() failed
rc : 19
Dec 2 14:47:46 SLES11-CONN-PC osafimmnd[8623]: Implementer connected: 87
(MsgQueueService?131328) <0, 20200>
Dec 2 14:47:46 SLES11-CONN-PC osafimmnd[8623]: Implementer disconnected 87 <0,
20200> (MsgQueueService?131328)
Dec 2 14:48:11 SLES11-CONN-PC osafimmnd[8623]: NODE STATE-> IMM_NODE_R_AVAILABLE
Dec 2 14:48:17 SLES11-CONN-PC osafimmnd[8623]: NODE STATE->
IMM_NODE_FULLY_AVAILABLE 12105
Dec 2 14:48:17 SLES11-CONN-PC osafimmnd[8623]: Epoch set to 8 in ImmModel?
Dec 2 14:48:19 SLES11-CONN-PC osafimmnd[8623]: Implementer (applier) connected:
88 (@safAmfService20100) <0, 20100>
Dec 2 14:48:20 SLES11-CONN-PC osafimmnd[8623]: Implementer connected: 89
(MsgQueueService?131328) <0, 20100>
Dec 2 15:04:04 SLES11-CONN-PC opensafd[8598]: Timed-out for response from AMFND
Dec 2 15:04:04 SLES11-CONN-PC opensafd[8598]:
Dec 2 15:04:04 SLES11-CONN-PC opensafd[8598]: Going for recovery
Dec 2 15:04:04 SLES11-CONN-PC osafimmnd[8623]: MDTM:socket_recv() = 0, conn
lost with dh server, exiting library
Dec 2 15:04:04 SLES11-CONN-PC opensafd: Starting OpenSAF failed
---
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.
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
