ARSERVTCD process donB4t come up

[Starrynight_1]

Hello everyone

I really need urgent help!
I have a cluster with 2 nodes, one is the fail over of the other and if the package switches he doesn??t return to the primary node automatically (it has to be done manually).
So, during the night someone follows a backup procedure. That includes halting the package on primary node, so that he doesn??t switch during reboot.
Then, after reboot, the package is activated again. The split is made an the backup begins.

Everything went fine during a lot of years, but now when the package is brought up after reboot he switch automatically after awhile because he detects that a process is not running (ARSERVTCD).
In the morning, when I switch the package back to the primary node manually everything works fine.
So, the conclusion:
- Switching from the alternative node (WORKS)
- Halting and then running in the primary node (DOES NOT WORK).
Can anyone help? Why does the process don??t come up when in the cluster logs you can see that the package did?

Thanks in advance.

SN

[Jeff Machols]

Try to add nohup on the command line to start the processes, maybe the process is comming up, then getting killed when the control script exists, so if you have

/usr/local/bin/start_proc args

change it to

nohup /usr/local/bin/start_proc args