#671 imm.db process came up on Standby controller.

[manu]

Changeset:- 4733

Initially imm.db process came up on the Active controller.
Restarted the cluster and with due to lack of permission imm.db trying to re spawn on controller 2.
Once permission has been given to imm.db directory as on both the nodes "chmod 777 /home/immpbe -R"
Process "/usr/lib64/opensaf/osafimmpbed --pbe /home/immpbe/imm.db" spawned on the Standby controller.

SC-1 is active controller:-

SLES_NEW1:/opt/goahead/tetware/opensaffire # /etc/init.d/opensafd status
safSISU=safSu=SC-1\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed2,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SC-1\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SC-2\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed1,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SC-2\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=PL-3\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed4,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=PL-4\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed3,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
SLES_NEW1:/opt/goahead/tetware/opensaffire #

[Anders Bjornerstedt]

I think you mean the osafimmpbed process when you say 'imm.db process'.
The PBE process (persistent back end) can execute on either the active SC
or the standby SC. It is not related/started/owned by the IMMD but by
the IMMND coord. The IMMNDs are totally replicated and the IMMND coord
is elected by the IMMD to be on either the active or standby SC according
to what is available at the time the election is made.