- Description has changed:
Diff:
~~~~
--- old
+++ new
@@ -9,7 +9,7 @@
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 PL-4 su
+5) unlock-in/unlock the middleware PL-4 su
console output on PL-4:
~~~~
---
** [tickets:#863] payload middleware su is not instantiated as part of
unlock-in/unlock**
**Status:** review
**Milestone:** future
**Created:** Fri Apr 18, 2014 10:00 AM UTC by surender khetavath
**Last Updated:** Tue May 06, 2014 11:57 AM UTC
**Owner:** Nagendra Kumar
changeset : 5143
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
console output on PL-4:
safSu=PL-4,safSg=NoRed,safApp=OpenSAF
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=DISABLED(2)
saAmfSUPresenceState=UNINSTANTIATED(1)
saAmfSUReadinessState=OUT-OF-SERVICE(1)
ps -ef| grep saf
root 14348 3641 0 15:10 pts/0 00:00:00 /bin/sh /etc/init.d/opensafd
start
root 14380 14348 0 15:10 pts/0 00:00:00 /usr/lib64/opensaf/opensafd
root 14381 14380 0 15:10 ? 00:00:00 /bin/bash
/usr/lib64/opensaf/nid_tipc start eth2 7676
root 14397 14380 0 15:10 ? 00:00:00 [osaf-immnd] <defunct>
root 14406 1 0 15:10 ? 00:00:00 /usr/lib64/opensaf/osafimmnd
--tracemask=0xffffffff
root 14410 14380 0 15:10 ? 00:00:00 [osaf-noded] <defunct>
root 14419 14380 0 15:10 ? 00:00:00 [osaf-amfnd] <defunct>
root 14424 1 0 15:10 ? 00:00:00 /usr/lib64/opensaf/osafamfnd
--tracemask=0xffffffff
root 15208 3641 0 15:24 pts/0 00:00:00 grep saf
time : 15:10:09
---
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