Looks like 2PBE is enabled.
and the other SC-2 is down. In this case the CCB will not be allowed.
An admin operation is required to enable 1safe2PBE.
For more information see the osaf/services/saf/immsv/README.2PBE
From the README:
------------------------
The 1safe2PBE mechanism allows a 2PBE OpenSAF cluster to open up for
persistent
writes using only one of the two PBEs - temporarily. This is only
intended to be
used as a temporary state when one SC is long term unavailable. As soon
as the
other SC returns, then the IMM will automatically re-enter normal
2-safe2PBE and
will reject persistent writes and attempts to enter 1safe2PBE until the
slave PBE
has synced (regenerated its file) and rejoined the cluster.
The 1safe2PBE state is entered by the administrative opeation:
immadm -o 1 -a safImmService -p opensafImmNostdFlags:SA_UINT32_T:8 \
opensafImm=opensafImm,safApp=safImmService
/Neel.
On Thursday 08 October 2015 11:03 PM, Chad Lingrell wrote:
> The command and associated logs are below. The same command works when the
> peer SC is up and enabled.
>
> Command:
>
> immcfg -c SaAmfSU safSu=saf-SU3,safSg=saf-Np1,safApp=safApp -a
> saAmfSUType=safVersion=1,safSuType=safSuTypeNp1 -a saAmfSUFailover=1 -a
> saAmfSUHostNodeOrNodeGroup=safAmfNode=PL-3,safAmfCluster=amfCluster -a
> saAmfSURank=1 -a saAmfSUAdminState=3
>
> Log:
>
> Oct 8 17:29:51 q50-s1 osafimmnd[6298]: IN GOING FROM IMM_CCB_PREPARE to
> IMM_CCB_CRITICAL Ccb:2
> Oct 8 17:29:51 q50-s1 osafimmpbed: IN Starting distributed PBE commit for
> Ccb:2/2
> Oct 8 17:29:52 q50-s1 osafimmpbed: NO Slave PBE 12 or Immsv (4294901760)
> replied with transient error on prepare for ccb:2/2
> Oct 8 17:29:54 q50-s1 osafimmpbed: Last message 'NO Slave PBE 12 or I'
> repeated 5 times, suppressed by syslog-ng on q50-s1
> Oct 8 17:29:54 q50-s1 osafimmpbed: WA Start prepare for ccb: 2/2 towards
> slave PBE returned: '12' from Immsv
> Oct 8 17:29:54 q50-s1 osafimmpbed: WA PBE-A failed to prepare Ccb:2/2
> towards PBE-B
> Oct 8 17:29:54 q50-s1 osafimmnd[6298]: NO Validation error (BAD_OPERATION)
> reported by implementer 'OpenSafImmPBE', Ccb 2 will be aborted
> Oct 8 17:29:54 q50-s1 osafimmnd[6298]: NO Ccb 2 ABORTED (immcfg_q50-s1_7465)
> Oct 8 17:29:54 q50-s1 osafimmpbed: WA Failed to find CCB object for 2/2
>
> -----Original Message-----
> From: Mathivanan Naickan Palanivelu [mailto:[email protected]]
> Sent: Thursday, October 08, 2015 1:09 PM
> To: [email protected]; [email protected]; Chad
> Lingrell
> Subject: RE: [users] immcfg
>
> Is it a command on AMF object or (log, clm?) The reason for failure should be
> logged in the syslog, what's the command and the error seen?
>
> Mathi
>
> -----Original Message-----
>
> From: Chad Lingrell [[email protected]]
> Received: Thursday, 08 Oct 2015, 20:52
> To: Zoran Milinkovic [[email protected]];
> [email protected] [[email protected]]
> Subject: Re: [users] immcfg
>
> Hi Zoran,
>
> I did have a running controller. It was just the peer that was not available.
>
> Chad
>
> -----Original Message-----
> From: Zoran Milinkovic [mailto:[email protected]]
> Sent: Thursday, October 08, 2015 11:20 AM
> To: Chad Lingrell; [email protected]
> Subject: RE: immcfg
>
> Hi Chad,
>
> You must have running OpenSAF to be able to use immcfg.
> It means, at least one controller.
>
> When IMM is unavailable (example: sync data due to a new node joined the
> cluster), you are not able to do any CCB operation.
>
> Thanks,
> Zoran
>
> -----Original Message-----
> From: Chad Lingrell [mailto:[email protected]]
> Sent: Thursday, October 08, 2015 4:56 PM
> To: [email protected]
> Subject: [users] immcfg
>
> Hello,
>
> I am in the process of getting familiar with the immcfg tool and the dynamic
> configuration of OpenSAF. One thing I noticed, so far, is that I cannot add
> seem to configuration unless the peer system controller is available. I
> would expect to be able to change the configuration regardless of the peer
> being available and that when the peer came back up it would perform a sync
> with the master. Is what I am seeing correct behavior or am I missing
> something?
>
> Thanks,
>
> Chad
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Opensaf-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/opensaf-users
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Opensaf-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/opensaf-users
> ------------------------------------------------------------------------------
> _______________________________________________
> Opensaf-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/opensaf-users
------------------------------------------------------------------------------
_______________________________________________
Opensaf-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-users
