---
** [tickets:#1133] Payload Middleware SU is not instantiated after
unlock-in/unlock operation.**
**Status:** unassigned
**Milestone:** 4.5.0
**Created:** Wed Sep 24, 2014 10:05 AM UTC by manu
**Last Updated:** Wed Sep 24, 2014 10:05 AM UTC
**Owner:** nobody
changeset : 5697
setup : 4-node cluster
PL-4 su is not intantiated as part unlock-in/unlock.
Reproducible steps
1) bring up 4 nodes sc-1,sc-2,pl-3,pl-4
2) lock/lock-in pl-4 middle ware su
3) stop opensaf on pl-4 as /etc/init.d/opensafd stop
4) start opensaf on pl-4 as /etc/init.d/opensafd start
5) unlock-in/unlock the middleware PL-4 su
After doing stop and start on PL-4 and unlock-in and UNlock on PL-4 Su, still
pl-4 Su is in DISABLED and UNINSTANTIATED state.
safSu=PL-4,safSg=NoRed,safApp=OpenSAF
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=DISABLED(2)
saAmfSUPresenceState=UNINSTANTIATED(1)
saAmfSUReadinessState=IN-SERVICE(2)
After starting opensaf on PL-4 only few processes spawned ,
SLES4:~ # ps -ef|grep saf
root 7100 1 0 12:00 ? 00:00:00 /bin/sh
/usr/lib64/opensaf/clc-cli/osaf-transport-monitor
opensaf 7112 1 0 12:00 ? 00:00:00 /usr/lib64/opensaf/osafimmnd
opensaf 7122 1 0 12:00 ? 00:00:00 /usr/lib64/opensaf/osafclmna
root 7131 1 0 12:00 ? 00:00:00 /usr/lib64/opensaf/osafamfnd
--tracemask=0xffffffff
root 7522 2531 0 12:19 pts/0 00:00:00 grep saf
Please find the amfnd traces.
syslog pl-4
ep 24 12:00:07 SLES4 osafimmnd[7112]: Started
Sep 24 12:00:07 SLES4 osafimmnd[7112]: NO Persistent Back-End capability
configured, Pbe file:imm.db (suffix may get added)
Sep 24 12:00:07 SLES4 osafimmnd[7112]: NO SERVER STATE: IMM_SERVER_ANONYMOUS
--> IMM_SERVER_CLUSTER_WAITING
Sep 24 12:00:07 SLES4 osafimmnd[7112]: NO SERVER STATE:
IMM_SERVER_CLUSTER_WAITING --> IMM_SERVER_LOADING_PENDING
Sep 24 12:00:07 SLES4 osafimmnd[7112]: NO SERVER STATE:
IMM_SERVER_LOADING_PENDING --> IMM_SERVER_SYNC_PENDING
Sep 24 12:00:07 SLES4 osafimmnd[7112]: NO NODE STATE-> IMM_NODE_ISOLATED
Sep 24 12:00:08 SLES4 osafimmnd[7112]: NO NODE STATE-> IMM_NODE_W_AVAILABLE
Sep 24 12:00:08 SLES4 osafimmnd[7112]: NO SERVER STATE: IMM_SERVER_SYNC_PENDING
--> IMM_SERVER_SYNC_CLIENT
Sep 24 12:00:10 SLES4 osafimmnd[7112]: NO NODE STATE-> IMM_NODE_FULLY_AVAILABLE
2460
Sep 24 12:00:10 SLES4 osafimmnd[7112]: NO RepositoryInitModeT is
SA_IMM_INIT_FROM_FILE
Sep 24 12:00:10 SLES4 osafimmnd[7112]: WA IMM Access Control mode is DISABLED!
Sep 24 12:00:10 SLES4 osafimmnd[7112]: NO Epoch set to 5 in ImmModel
Sep 24 12:00:10 SLES4 osafimmnd[7112]: NO SERVER STATE: IMM_SERVER_SYNC_CLIENT
--> IMM SERVER READY
Sep 24 12:00:10 SLES4 osafclmna[7122]: Started
Sep 24 12:00:10 SLES4 osafclmna[7122]: NO safNode=PL-4,safCluster=myClmCluster
Joined cluster, nodeid=2040f
Sep 24 12:00:10 SLES4 osafamfnd[7131]: Started
Sep 24 12:00:56 SLES4 osafamfnd[7131]: NO Assigning
'safSi=NoRed3,safApp=OpenSAF' ACTIVE to 'safSu=PL-4,safSg=NoRed,safApp=OpenSAF'
Sep 24 12:00:56 SLES4 osafamfnd[7131]: NO Assigned
'safSi=NoRed3,safApp=OpenSAF' ACTIVE to 'safSu=PL-4,safSg=NoRed,safApp=OpenSAF'
Sep 24 12:00:56 SLES4 opensafd: OpenSAF(4.5.FC - ) services successfully started
---
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
