Good day time! I have upgraded OpenSAF up to 1.0-4 and met the following problem:
I have two host cluster where controller and application share the same host. After rebooting a host with active component standby component does not become active: Nov 15 19:31:51 host5 solid_amf_adapter: starting Solid AMF Adapter (pid:5514, cmd: /opt/aissolid/bin/solid_amf_adapter).. Nov 15 19:31:51 host5 solid_amf_adapter: loading configuration file (/opt/aissolid/bin/solid.ini).. Nov 15 19:31:52 host5 solid_amf_adapter: MDS_LOG:0 Nov 15 19:31:52 host5 solid_amf_adapter: select result: 1 Nov 15 19:31:52 host5 solid_amf_adapter: result code: 0 Nov 15 19:31:52 host5 solid_amf_adapter: requesting the safComp=CompT_SAA,safSu=SU_SAA,safNode=SC_2_1 component to assume the SA_AMF_HA_STANDB Y state for the safCsi=CSI_SAA,safSi=SI_SAA.. Nov 15 19:31:52 host5 solid_amf_adapter: adapter->m_amf_driver->saAmfHealthcheckStop(adapter-> m_handle, compName, healthcheckKey): SA_AIS_ERR _NOT_EXIST () Nov 15 19:31:52 host5 solid_amf_adapter: healthchecking the safComp=CompT_SAA,safSu=SU_SAA,safNode=SC_2_1 component, the 6B6579 key.. Nov 15 19:31:52 host5 solid_amf_adapter: protection group notificationfor csi: safCsi=CSI_SAA,safSi=SI_SAA: Nov 15 19:31:52 host5 solid_amf_adapter: name: safComp=CompT_SAA,safSu=SU_SAA,safNode=SC_2_1, state: SA_AMF_HA_STANDBY, change: STATE CHANGED Nov 15 19:31:57 host5 solid_amf_adapter: healthchecking the safComp=CompT_SAA,safSu=SU_SAA,safNode=SC_2_1 component, the 6B6579 key.. Nov 15 19:32:28 host5 last message repeated 6 times Nov 15 19:32:38 host5 last message repeated 2 times Nov 15 19:32:42 host5 kernel: TIPC: Resetting link <1.1.31:eth0-1.1.47:eth0>, peer not responding Nov 15 19:32:42 host5 kernel: TIPC: Lost link <1.1.31:eth0-1.1.47:eth0> on network plane A Nov 15 19:32:42 host5 kernel: TIPC: Lost contact with <1.1.47> Nov 15 19:32:43 host5 solid_amf_adapter: healthchecking the safComp=CompT_SAA,safSu=SU_SAA,safNode=SC_2_1 component, the 6B6579 key.. Nov 15 19:33:19 host5 last message repeated 7 times Nov 15 19:34:20 host5 last message repeated 12 times Nov 15 19:35:21 host5 last message repeated 12 times Nov 15 19:35:41 host5 last message repeated 4 times Nov 15 19:35:45 host5 kernel: TIPC: Established link <1.1.31:eth0-1.1.47:eth0> on network plane A Nov 15 19:35:46 host5 solid_amf_adapter: healthchecking the safComp=CompT_SAA,safSu=SU_SAA,safNode=SC_2_1 component, the 6B6579 key.. Nov 15 19:36:17 host5 last message repeated 6 times Nov 15 19:37:18 host5 last message repeated 12 times Nov 15 19:38:19 host5 last message repeated 12 times Nov 15 19:39:21 host5 last message repeated 12 times State of active component before rebooting: Nov 15 19:28:49 host6 solid_amf_adapter: protection group notificationfor csi: safCsi=CSI_SAA,safSi=SI_SAA: Nov 15 19:28:49 host6 solid_amf_adapter: name: safComp=CompT_SAA,safSu=SU_SAA,safNode=SC_2_1, state: SA_AMF_HA_QUIESCED, change: STATE CHANGED Nov 15 19:28:49 host6 solid_amf_adapter: requesting the safComp=CompT_SAA,safSu=SU_SAA,safNode=SC_2_2 component to assume the SA_AMF_HA_ACTIVE state for the .. Nov 15 19:28:49 host6 solid_amf_adapter: healthchecking the safComp=CompT_SAA,safSu=SU_SAA,safNode=SC_2_2 component, the 6B6579 key.. Nov 15 19:28:49 host6 solid_amf_adapter: protection group notificationfor csi: safCsi=CSI_SAA,safSi=SI_SAA: Nov 15 19:28:49 host6 solid_amf_adapter: name: safComp=CompT_SAA,safSu=SU_SAA,safNode=SC_2_2, state: SA_AMF_HA_ACTIVE, change: STATE CHANGED Nov 15 19:28:49 host6 solid_amf_adapter: protection group notificationfor csi: safCsi=CSI_SAA,safSi=SI_SAA: Nov 15 19:28:49 host6 solid_amf_adapter: name: safComp=CompT_SAA,safSu=SU_SAA,safNode=SC_2_1, state: SA_AMF_UNKNOW, change: REMOVED Nov 15 19:28:50 host6 solid_amf_adapter: protection group notificationfor csi: safCsi=CSI_SAA,safSi=SI_SAA: Nov 15 19:28:50 host6 solid_amf_adapter: name: safComp=CompT_SAA,safSu=SU_SAA,safNode=SC_2_1, state: SA_AMF_HA_STANDBY, change: ADDED Nov 15 19:28:54 host6 solid_amf_adapter: healthchecking the safComp=CompT_SAA,safSu=SU_SAA,safNode=SC_2_2 component, the 6B6579 key.. Nov 15 19:29:25 host6 last message repeated 6 times Nov 15 19:30:11 host6 last message repeated 9 times Nov 15 19:30:11 host6 solid_amf_adapter: protection group notificationfor csi: safCsi=CSI_SAA,safSi=SI_SAA: Nov 15 19:30:11 host6 solid_amf_adapter: name: safComp=CompT_SAA,safSu=SU_SAA,safNode=SC_2_1, state: SA_AMF_UNKNOW, change: REMOVED Nov 15 19:30:12 host6 solid_amf_adapter: protection group notificationfor csi: safCsi=CSI_SAA,safSi=SI_SAA: Nov 15 19:30:12 host6 solid_amf_adapter: name: safComp=CompT_SAA,safSu=SU_SAA,safNode=SC_2_1, state: SA_AMF_HA_STANDBY, change: ADDED Nov 15 19:30:16 host6 solid_amf_adapter: healthchecking the safComp=CompT_SAA,safSu=SU_SAA,safNode=SC_2_2 component, the 6B6579 key.. Nov 15 19:30:51 host6 last message repeated 7 times Nov 15 19:30:57 host6 solid_amf_adapter: healthchecking the safComp=CompT_SAA,safSu=SU_SAA,safNode=SC_2_2 component, the 6B6579 key.. Nov 15 19:31:00 host6 kernel: md: stopping all md devices. Nov 15 19:31:00 host6 kernel: md: md0 switched to read-only mode. After that the rebooted host cannot bring up OpenSAF: Nov 15 18:56:05 host6 NID: Starting OpenSAF Services... Nov 15 18:56:05 host6 NID: TIPC Service has been set a priority value of 0 Nov 15 18:56:05 host6 kernel: TIPC: Activated (version 1.5.12 compiled Oct 5 2007 18:00:38) Nov 15 18:56:05 host6 kernel: NET: Registered protocol family 30 Nov 15 18:56:05 host6 kernel: TIPC: Started in single node mode Nov 15 18:56:05 host6 kernel: TIPC: Started in network mode Nov 15 18:56:05 host6 kernel: TIPC: Own node address <1.1.47>, network identity 1234 Nov 15 18:56:05 host6 kernel: TIPC: Enabled bearer <eth:eth0>, discovery domain <1.1.0> Nov 15 18:56:05 host6 NID: RDF Service has been set a priority value of 0 Nov 15 18:56:05 host6 kernel: TIPC: Established link <1.1.47:eth0-1.1.31:eth0> on network plane A Nov 15 18:56:11 host6 NID: Interrupted system call, Error: 4 Nov 15 18:56:11 host6 ncs_rde: MDS_LOG:0 Nov 15 18:56:14 host6 NID: RDF-ROLE for this System Controller is: 1, STANDBY Nov 15 18:56:14 host6 NID: DTSV Service has been set a priority value of 0 Nov 15 18:56:14 host6 ncs_dts: MDS_LOG:0 Nov 15 18:56:14 host6 ncs_dts: NODE_ID=0x0002020F PID 3627 Nov 15 18:56:17 host6 NID: MASV Service has been set a priority value of 0 Nov 15 18:56:17 host6 ncs_mas: MDS_LOG:0 Nov 15 18:56:17 host6 ncs_mas: NODE_ID=0x0002020F PID 3634 Nov 15 18:56:20 host6 NID: PSSV Service has been set a priority value of 0 Nov 15 18:56:20 host6 ncs_psr: MDS_LOG:0 Nov 15 18:56:20 host6 ncs_psr: NODE_ID=0x0002020F PID 3643 Nov 15 18:56:23 host6 NID: EDSV Service has been set a priority value of 0 Nov 15 18:56:23 host6 ncs_eds: MDS_LOG:0 Nov 15 18:56:23 host6 ncs_eds: NODE_ID=0x0002020F PID 3651 Nov 15 18:56:26 host6 NID: SUBAGT Service has been set a priority value of 0 Nov 15 18:56:26 host6 ncs_snmp_subagt: MDS_LOG:0 Nov 15 18:56:26 host6 ncs_snmp_subagt: NODE_ID=0x0002020F PID 3658 Nov 15 18:56:29 host6 NID: SCAP Service has been set a priority value of 0 Nov 15 18:56:30 host6 ncs_scap: MDS_LOG:0 Nov 15 18:56:30 host6 ncs_scap: NODE_ID=0x0002020F PID 3665 Any comments? Thanks in advance. _______________________________________________ Users mailing list [email protected] http://list.opensaf.org/maillist/listinfo/users
