1837117 Members
2368 Online
110112 Solutions
New Discussion

package swithcing query

 
SOLVED
Go to solution
TMcB
Super Advisor

package swithcing query

Hi everyone

My package starts OK on both nodes on our 2 node cluster.
In mainly runs on node1, but when I switch run it on the 2nd node, it starts OK, but only remains up for a few seconds before it returns back to the first node.

I turned off package switching, and it remained up on the 2nd node for a period of time. As soon as I enabled package switching it automatically failed back over to node 1.

What do I need to set so that it will not immediately fail back to node 1 as soon as I switch it to run on node 2.

The entries in the cntl log file are :
Aug 29 08:13:01 - Node "bfsm02": Starting service sgm_ser using
"/etc/cmcluster/pkg/ pkg.sh monitor"
*** /etc/cmcluster/pkg/ pkg.sh called with monitor argument. ***

########### Node "bfsm02": Package start completed at Wed Aug 29 08:13
:01 BST 2007 ###########
Monitored process = oninit, pid = 21601

########### Node "bfsm02": Halting package at Wed Aug 29 08:28:37 BST
2007 ###########
Aug 29 08:28:37 - Node "bfsm02": Halting service sgm_service

*** /etc/cmcluster/pkg/pkg.sh called with halt argument. ***

Thanks
3 REPLIES 3
Wim Rombauts
Honored Contributor
Solution

Re: package swithcing query

Maybe you have auto-failback enabled ? This will bring th epackage to the preferred node immediately when SG detects the preferred node is available.
Marcin O.
Frequent Advisor

Re: package swithcing query

Hi
Check parameter:
FAILOVER_POLICY CONFIGURED_NODE
FAILBACK_POLICY MANUAL
Failback should be like in ex. manual if you don't want automatic failback.

Rgrds
Marcin
TMcB
Super Advisor

Re: package swithcing query

thanks for the quick responses.
checked the settings :
FAILBACK_POLICY AUTOMATIC
and changed it as required