I want to add this one too:
So, if we start second node SC-2, it will failed to join the cluster
And both node will go for reboot
 **and finally after reboot when node join back:
 
 >>SC-2 will join with "ACTIVE" role and first node(PL-3) will join as 
 >>"QUIESCED"


Syslog of SC-2:
Sep 20 17:27:18 TestBed-R2 osafimmd[27361]: ER Failed to find candidate for new 
IMMND coordinator (ScAbsenceAllowed:0 RulingEpoch:0
Sep 20 17:27:18 TestBed-R2 osafimmd[27361]: ER Active IMMD has to restart the 
IMMSv. All IMMNDs will restart
Sep 20 17:27:18 TestBed-R2 osafimmd[27361]: NO Cluster failed to load => IMMDs 
will not exit.
Sep 20 17:27:18 TestBed-R2 osafimmd[27361]: NO MDS event from svc_id 25 
(change:4, dest:564114851160080)
Sep 20 17:27:18 TestBed-R2 osafimmd[27361]: IN Added IMMND node with dest 
564114851160080
Sep 20 17:27:18 TestBed-R2 osafimmd[27361]: IN Added IMMND node with dest 
565216431636496
Sep 20 17:27:18 TestBed-R2 osafimmd[27361]: WA Error returned from processing 
message err:0 msg-type:14
Sep 20 17:27:18 TestBed-R2 osafimmnd[27372]: ER IMMND forced to restart on 
order from IMMD, exiting
Sep 20 17:27:18 TestBed-R2 osafimmd[27361]: NO MDS event from svc_id 25 
(change:4, dest:565216431636496)
Sep 20 17:27:18 TestBed-R2 osafamfnd[27422]: NO 
'safSu=SC-2,safSg=NoRed,safApp=OpenSAF' component restart probation timer 
started (timeout: 60000000000 ns)
Sep 20 17:27:18 TestBed-R2 osafamfnd[27422]: NO Restarting a component of 
'safSu=SC-2,safSg=NoRed,safApp=OpenSAF' (comp restart count: 1)
Sep 20 17:27:18 TestBed-R2 osafamfnd[27422]: NO 
'safComp=IMMND,safSu=SC-2,safSg=NoRed,safApp=OpenSAF' faulted due to 'avaDown' 
: Recovery is 'componentRestart

.............

Sep 20 17:27:23 TestBed-R2 osafclmd[27402]: NO ERR_INVALID_PARAM: Implementer 
safClmService already set for this handle when trying to set safClmService
Sep 20 17:27:23 TestBed-R2 osafclmd[27402]: ER saImmOiImplementerSet failed, rc 
= 7
Sep 20 17:27:23 TestBed-R2 osafamfnd[27422]: NO 
'safComp=CLM,safSu=SC-2,safSg=2N,safApp=OpenSAF' faulted due to 'avaDown' : 
Recovery is 'nodeFailfast'
Sep 20 17:27:23 TestBed-R2 osafamfnd[27422]: ER 
safComp=CLM,safSu=SC-2,safSg=2N,safApp=OpenSAF Faulted due to:avaDown Recovery 
is:nodeFailfast
Sep 20 17:27:23 TestBed-R2 osafamfnd[27422]: Rebooting OpenSAF NodeId = 131599 
EE Name = , Reason: Component faulted: recovery is node failfast, OwnNodeId = 
131599, SupervisionTime = 60
Sep 20 17:27:23 TestBed-R2 opensaf_reboot: Rebooting local node; timeout=60



Syslog of firstnode:
Sep 20 17:28:10 TestBed-R1 osafimmnd[31481]: ER No IMMD service => cluster 
restart, exiting
Sep 20 17:28:10 TestBed-R1 osafamfnd[30949]: NO Restarting a component of 
'safSu=PL-3,safSg=NoRed,safApp=OpenSAF' (comp restart count: 2)
Sep 20 17:28:10 TestBed-R1 osafamfnd[30949]: NO 
'safComp=IMMND,safSu=PL-3,safSg=NoRed,safApp=OpenSAF' faulted due to 'avaDown' 
: Recovery is 'componentRestart'
Sep 20 17:28:10 TestBed-R1 osafntfimcnd[31487]: NO saImmOiDispatch() Fail 
SA_AIS_ERR_BAD_HANDLE (9)
Sep 20 17:28:10 TestBed-R1 osafamfd[30935]: NO Node 'SC-2' left the cluster
Sep 20 17:28:10 TestBed-R1 osafamfd[30935]: safSu=SC-2,safSg=2N,safApp=OpenSAF 
OperState ENABLED => DISABLED
Sep 20 17:28:10 TestBed-R1 opensaf_reboot: Rebooting local node; timeout=60
Sep 20 17:28:10 TestBed-R1 osafamfd[30935]: ER sendStateChangeNotificationAvd: 
saNtfNotificationSend Failed (6)
Sep 20 17:28:10 TestBed-R1 osafamfd[30935]: safSu=SC-2,safSg=2N,safApp=OpenSAF 
PresenceState INSTANTIATED => UNINSTANTIATED
Sep 20 17:28:10 TestBed-R1 osafamfd[30935]: ER sendStateChangeNotificationAvd: 
saNtfNotificationSend Failed (6)
Sep 20 17:28:10 TestBed-R1 osafamfd[30935]: safSu=SC-2,safSg=2N,safApp=OpenSAF 
ReadinessState IN_SERVICE => OUT_OF_SERVICE



---

** [tickets:#2052] immtools: SC/PL field in nodes.cfg is not used**

**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Tue Sep 20, 2016 09:41 AM UTC by Ritu Raj
**Last Updated:** Tue Sep 20, 2016 11:58 AM UTC
**Owner:** nobody


# Environment details
OS : Suse 64bit
Changeset : 7997 ( 5.1.FC)

# Summary
Controller able to join with invalid node_name

# Steps followed & Observed behaviour
1. Mistakenly configured controller node_name with PL-3 and the remaining 
configuration files are properly installed and updated apart from 
/etc/opensaf/node_name.
2. Bringup OpenSAF, OpneSAF still able to comeup with misconfigured node_name

Opensaf status:
fos1:/opt/goahead/tetware/opensaffire/suites/avsv/api/suites # 
/etc/init.d/opensafd status
safSISU=safSu=PL-3\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed1,safApp=OpenSAF
        saAmfSISUHAState=ACTIVE(1)
    
#  Expected
OpenSAF should come up with only SC-1 / SC-2, as immxml generated with :
 ./immxml-clustersize -s 2 -p 2
 ./immxml-configure




---

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.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to