---
** [tickets:#894] Incorrect error log when unloading of tipc module has failed**
**Status:** unassigned
**Milestone:** future
**Created:** Fri May 09, 2014 10:17 AM UTC by Sirisha Alla
**Last Updated:** Fri May 09, 2014 10:17 AM UTC
**Owner:** nobody
This issue is seen on 4.3.2 cs 5143.
The cluster is configure to come up with tipc. An non-amf saf application is
running on the node and is using the tipc link.
Now when opensaf is restarted on that node following is the log message:
May 9 15:28:00 SLES-64BIT-SLOT4 osafamfnd[2338]: NO Shutdown completed, exiting
May 9 15:28:01 SLES-64BIT-SLOT4 opensafd: warning: TIPC module unloading failed
May 9 15:28:01 SLES-64BIT-SLOT4 opensafd: OpenSAF services successfully stopped
May 9 15:28:01 SLES-64BIT-SLOT4 opensafd: Starting OpenSAF Services
May 9 15:28:01 SLES-64BIT-SLOT4 opensafd: warning: TIPC module unloading failed
May 9 15:28:01 SLES-64BIT-SLOT4 osafimmnd[3077]: Started
May 9 15:28:01 SLES-64BIT-SLOT4 osafimmnd[3077]: NO Persistent Back-End
capability configured, Pbe file:imm.db
May 9 15:28:01 SLES-64BIT-SLOT4 osafimmnd[3077]: NO SERVER STATE:
IMM_SERVER_ANONYMOUS --> IMM_SERVER_CLUSTER_WAITING
May 9 15:28:01 SLES-64BIT-SLOT4 osafimmnd[3077]: NO SERVER STATE:
IMM_SERVER_CLUSTER_WAITING --> IMM_SERVER_LOADING_PENDING
May 9 15:28:01 SLES-64BIT-SLOT4 osafimmnd[3077]: NO SERVER STATE:
IMM_SERVER_LOADING_PENDING --> IMM_SERVER_SYNC_PENDING
May 9 15:28:01 SLES-64BIT-SLOT4 osafimmnd[3077]: NO NODE STATE->
IMM_NODE_ISOLATED
May 9 15:28:02 SLES-64BIT-SLOT4 osafimmnd[3077]: NO NODE STATE->
IMM_NODE_W_AVAILABLE
May 9 15:28:02 SLES-64BIT-SLOT4 osafimmnd[3077]: NO SERVER STATE:
IMM_SERVER_SYNC_PENDING --> IMM_SERVER_SYNC_CLIENT
May 9 15:28:06 SLES-64BIT-SLOT4 sudo: tet : TTY=unknown ;
PWD=/tmp/02860aa ; USER=root ; COMMAND=/usr/bin/pgrep osafckptd
May 9 15:28:10 SLES-64BIT-SLOT4 sshd[3083]: Accepted keyboard-interactive/pam
for root from 192.168.56.1 port 42768 ssh2
May 9 15:28:16 SLES-64BIT-SLOT4 osafimmnd[3077]: NO NODE STATE->
IMM_NODE_FULLY_AVAILABLE 2147
May 9 15:28:16 SLES-64BIT-SLOT4 osafimmnd[3077]: NO RepositoryInitModeT is
SA_IMM_KEEP_REPOSITORY
May 9 15:28:16 SLES-64BIT-SLOT4 osafimmnd[3077]: NO Epoch set to 461 in
ImmModel
May 9 15:28:16 SLES-64BIT-SLOT4 cpsv_app: IN Received PROC_STALE_CLIENTS
May 9 15:28:16 SLES-64BIT-SLOT4 osafimmnd[3077]: NO SERVER STATE:
IMM_SERVER_SYNC_CLIENT --> IMM SERVER READY
May 9 15:28:16 SLES-64BIT-SLOT4 osafclmna[3122]: Started
May 9 15:28:16 SLES-64BIT-SLOT4 osafclmna[3122]: ER
safNode=PL-4,safCluster=myClmCluster is already up. Specify a unique name
in/etc/opensaf/node_name
May 9 15:28:16 SLES-64BIT-SLOT4 opensafd[3044]: ER Failed DESC:CLMNA
May 9 15:28:16 SLES-64BIT-SLOT4 opensafd[3044]: ER Going for recovery
May 9 15:28:16 SLES-64BIT-SLOT4 opensafd[3044]: ER Trying To RESPAWN
/usr/lib64/opensaf/clc-cli/osaf-noded attempt #1
May 9 15:28:16 SLES-64BIT-SLOT4 opensafd[3044]: ER Sending SIGKILL to CLMNA,
pid=3117
May 9 15:28:20 SLES-64BIT-SLOT4 osafimmnd[3077]: NO Implementer connected: 18
(MsgQueueService132111) <0, 2010f>
May 9 15:28:20 SLES-64BIT-SLOT4 osafimmnd[3077]: NO Implementer disconnected
18 <0, 2010f> (MsgQueueService132111)
May 9 15:28:31 SLES-64BIT-SLOT4 osafclmna[3154]: Started
May 9 15:28:31 SLES-64BIT-SLOT4 osafclmna[3154]: ER
safNode=PL-4,safCluster=myClmCluster is already up. Specify a unique name
in/etc/opensaf/node_name
May 9 15:28:31 SLES-64BIT-SLOT4 opensafd[3044]: ER Could Not RESPAWN CLMNA
May 9 15:28:31 SLES-64BIT-SLOT4 opensafd[3044]: ER Failed DESC:CLMNA
May 9 15:28:31 SLES-64BIT-SLOT4 opensafd[3044]: ER Trying To RESPAWN
/usr/lib64/opensaf/clc-cli/osaf-noded attempt #2
May 9 15:28:31 SLES-64BIT-SLOT4 opensafd[3044]: ER Sending SIGKILL to CLMNA,
pid=3149
May 9 15:28:46 SLES-64BIT-SLOT4 osafclmna[3173]: Started
May 9 15:28:46 SLES-64BIT-SLOT4 osafclmna[3173]: ER
safNode=PL-4,safCluster=myClmCluster is already up. Specify a unique name
in/etc/opensaf/node_name
May 9 15:28:46 SLES-64BIT-SLOT4 opensafd[3044]: ER Could Not RESPAWN CLMNA
May 9 15:28:46 SLES-64BIT-SLOT4 opensafd[3044]: ER Failed DESC:CLMNA
May 9 15:28:46 SLES-64BIT-SLOT4 opensafd[3044]: ER FAILED TO RESPAWN
May 9 15:28:47 SLES-64BIT-SLOT4 opensafd: warning: TIPC module unloading failed
May 9 15:28:47 SLES-64BIT-SLOT4 opensafd: Starting OpenSAF failed
Different behavior is observed in 4.4RC2 tag codebase.
If the tipc id matches then the cluster is brought up. If there is a mismatch
in the tipc id between restarts it logs an error message:
Apr 3 12:45:29 SLES-64BIT-SLOT3 opensafd: Starting OpenSAF Services
Apr 3 12:45:29 SLES-64BIT-SLOT3 opensafd: warning: TIPC module unloading failed
Apr 3 12:45:29 SLES-64BIT-SLOT3 opensaf: TIPC network ID not configured to
OpenSAF requirements, exiting...
Apr 3 12:45:29 SLES-64BIT-SLOT3 opensafd[16905]: ER Failed DESC:TRANSPORT
Apr 3 12:45:29 SLES-64BIT-SLOT3 opensafd[16905]: ER Going for recovery
In both the cases the error is not clear and instead should fail with "TIPC
Module in use".
---
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.
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
