- **status**: fixed --> unassigned
- **Comment**:
Getting IMMND-Unknown event while bringing up the SC-2 (32bit) controller.
changeset : 5942 ( branch opensaf-4.5.x)
Sep 30 18:21:34 OpenSAF-SLOT2 kernel: [ 52.390051] TIPC: Started in single
node mode
Sep 30 18:21:34 OpenSAF-SLOT2 kernel: [ 52.405023] TIPC: Started in network
mode
Sep 30 18:21:34 OpenSAF-SLOT2 kernel: [ 52.405038] TIPC: Own node address
<1.1.2>, network identity 7234
Sep 30 18:21:34 OpenSAF-SLOT2 kernel: [ 52.410942] TIPC: Enabled bearer
<eth:eth0>, discovery domain <1.1.0>, priority 10
Sep 30 18:21:34 OpenSAF-SLOT2 kernel: [ 52.411540] TIPC: Established link
<1.1.2:eth0-1.1.1:eth0> on network plane A
Sep 30 18:21:34 OpenSAF-SLOT2 osafrded[3015]: Started
Sep 30 18:21:34 OpenSAF-SLOT2 osafrded[3015]: NO Peer rde@2010f has active
state => Assigning Standby role to this node
Sep 30 18:21:34 OpenSAF-SLOT2 osaffmd[3025]: Started
Sep 30 18:21:34 OpenSAF-SLOT2 osafimmd[3035]: Started
Sep 30 18:21:34 OpenSAF-SLOT2 osafimmnd[3045]: Started
Sep 30 18:21:34 OpenSAF-SLOT2 osafimmnd[3045]: NO SERVER STATE:
IMM_SERVER_ANONYMOUS --> IMM_SERVER_CLUSTER_WAITING
Sep 30 18:21:35 OpenSAF-SLOT2 osafimmnd[3045]: NO SERVER STATE:
IMM_SERVER_CLUSTER_WAITING --> IMM_SERVER_LOADING_PENDING
Sep 30 18:21:35 OpenSAF-SLOT2 osafimmnd[3045]: NO SERVER STATE:
IMM_SERVER_LOADING_PENDING --> IMM_SERVER_SYNC_PENDING
Sep 30 18:21:35 OpenSAF-SLOT2 osafimmnd[3045]: NO NODE STATE-> IMM_NODE_ISOLATED
Sep 30 18:21:35 OpenSAF-SLOT2 osafimmd[3035]: NO SBY: Ruling epoch noted as:16
Sep 30 18:21:35 OpenSAF-SLOT2 osafimmd[3035]: NO IMMND coord at 2010f
Sep 30 18:21:35 OpenSAF-SLOT2 osafimmnd[3045]: ER IMMND - Unknown Event
Sep 30 18:21:35 OpenSAF-SLOT2 osafimmnd[3045]: ER IMMND - Unknown Event
Sep 30 18:21:35 OpenSAF-SLOT2 osafimmnd[3045]: ER IMMND - Unknown Event
Sep 30 18:21:35 OpenSAF-SLOT2 osafimmnd[3045]: ER IMMND - Unknown Event
Sep 30 18:21:35 OpenSAF-SLOT2 osafimmnd[3045]: ER IMMND - Unknown Event
Sep 30 18:21:35 OpenSAF-SLOT2 osafimmnd[3045]: ER IMMND - Unknown Event
Sep 30 18:21:35 OpenSAF-SLOT2 osafimmnd[3045]: ER IMMND - Unknown Event
Sep 30 18:21:35 OpenSAF-SLOT2 osafimmnd[3045]: ER IMMND - Unknown Event
Sep 30 18:21:35 OpenSAF-SLOT2 osafimmnd[3045]: ER IMMND - Unknown Event
Sep 30 18:21:35 OpenSAF-SLOT2 osafimmnd[3045]: ER IMMND - Unknown Event
---
** [tickets:#1043] immnd crashes (segfault) while bringing up the SC-1
controller .**
**Status:** unassigned
**Milestone:** 4.5.FC
**Created:** Thu Sep 04, 2014 05:22 AM UTC by manu
**Last Updated:** Wed Sep 10, 2014 10:23 AM UTC
**Owner:** A V Mahesh (AVM)
Changeset : 5608
Scenario:- SC-2 is already up and running ,tring to bring up the SC-1
controller on the node 1.
Rarely reproducible.
Syslog:-
Sep 3 17:09:32 OpenSAF-SLOT1 opensafd: Starting OpenSAF Services
Starting OpenSAF Services: Sep 3 17:09:32 OpenSAF-SLOT1 kernel: [ 9769.989840]
TIPC: Activated (version 2.0.0)
Sep 3 17:09:32 OpenSAF-SLOT1 kernel: [ 9769.989994] NET: Registered protocol
family 30
Sep 3 17:09:32 OpenSAF-SLOT1 kernel: [ 9769.989995] TIPC: Started in single
node mode
Sep 3 17:09:32 OpenSAF-SLOT1 kernel: [ 9769.993128] TIPC: Started in network
mode
Sep 3 17:09:32 OpenSAF-SLOT1 kernel: [ 9769.993132] TIPC: Own node address
<1.1.1>, network identity 1234
Sep 3 17:09:32 OpenSAF-SLOT1 kernel: [ 9769.995619] TIPC: Enabled bearer
<eth:eth0>, discovery domain <1.1.0>, priority 10
Sep 3 17:09:32 OpenSAF-SLOT1 kernel: [ 9769.996695] TIPC: Established link
<1.1.1:eth0-1.1.2:eth0> on network plane A
Sep 3 17:09:33 OpenSAF-SLOT1 osafrded[10151]: Started
Sep 3 17:09:33 OpenSAF-SLOT1 osafrded[10151]: NO Peer rde@2020f has active
state => Assigning Standby role to this node
Sep 3 17:09:33 OpenSAF-SLOT1 osaffmd[10160]: Started
Sep 3 17:09:33 OpenSAF-SLOT1 osafimmd[10170]: Started
Sep 3 17:09:33 OpenSAF-SLOT1 osafimmnd[10180]: Started
Sep 3 17:09:33 OpenSAF-SLOT1 osafimmnd[10180]: NO Persistent Back-End
capability configured, Pbe file:imm.db (suffix may get added)
Sep 3 17:09:33 OpenSAF-SLOT1 osafimmnd[10180]: NO SERVER STATE:
IMM_SERVER_ANONYMOUS --> IMM_SERVER_CLUSTER_WAITING
Sep 3 17:09:33 OpenSAF-SLOT1 osafimmnd[10180]: NO SERVER STATE:
IMM_SERVER_CLUSTER_WAITING --> IMM_SERVER_LOADING_PENDING
Sep 3 17:09:33 OpenSAF-SLOT1 osafimmnd[10180]: NO SERVER STATE:
IMM_SERVER_LOADING_PENDING --> IMM_SERVER_SYNC_PENDING
Sep 3 17:09:33 OpenSAF-SLOT1 osafimmnd[10180]: NO NODE STATE->
IMM_NODE_ISOLATED
Sep 3 17:09:33 OpenSAF-SLOT1 osafimmd[10170]: NO SBY: Ruling epoch noted as:742
Sep 3 17:09:33 OpenSAF-SLOT1 osafimmd[10170]: NO IMMND coord at 2020f
Sep 3 17:09:33 OpenSAF-SLOT1 osafimmd[10170]: NO SBY: SaImmRepositoryInitModeT
changed and noted as 'SA_IMM_KEEP_REPOSITORY'
Sep 3 17:09:33 OpenSAF-SLOT1 kernel: [ 9770.652257] osafimmnd[10183]: segfault
at 0 ip 00007f7e7a9f2472 sp 00007f7e7c11eea8 error 4 in
libc-2.11.3.so[7f7e7a96f000+16b000]
^C
OpenSAF-SLOT1:/home/opensaf_FC_5697 # Sep 3 17:09:45 OpenSAF-SLOT1
osafimmd[10170]: NO SBY: New Epoch for IMMND process at node 2020f old epoch:
741 new epoch:742
Sep 3 17:09:45 OpenSAF-SLOT1 osafimmd[10170]: NO IMMND coord at 2020f
=============================================================================
gdb output has been attached.
---
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.
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
