Data Protector Package will not start on main node after switching

[Chad Brindley]

Hi,

We run a two node cluster; covsapp (main node) and covsapq (alternate node)

I have noticed this morning that our data protector package has switched to our alternate node. I halted the package on the alternate node and tried to run on our main node but I get this message;

Running package paDP on node covsapp.
cmrunpkg : Node covsapp is currently unable to run package paDP.
Check the syslog on node covsapp and pkg log files for more detailed information

I will attach the package.cntl log file and the syslog.log file.

I need to get this package running on the main node but I cannot restart the cluster during the day which might fix it.

I think this happened due to some network issues but I am not sure.

Regards,

Chad

[Steven E. Protter]

Shalom Chad,

Seems like a simple SG package configuration issue. The package does not appear to be permitted to run on both nodes.

I recommend you schedule some downtime where you can reconfigure the package and cluster and do some QA testing.

SEP

[Chad Brindley]

Hi,

But before the switch yesterday to the alternate node the package has always ran on the main node so I dont understand.

Chad

[Saeid Ghanei_1]

Hi,

I think that the standby node can not run the package because the external disk is set. you have to deactivate the volume group on standby node:
vgchange -a n /dev/pv../lvol1

You can let the package running on the other node and reboot the standby node, then the system will initialize and you can switch over.

Cheers
SG

[John Waller · Accepted solution]

Hi,
I presume you've checked that your primary server is enabled to run the package:

cmviewcl -v -p paDP. if it says disabled:

cmmodpkg -e -n covsapp paDP

[Chad Brindley]

The last reply has resolved my problem;

From John Waller;

Hi,
I presume you've checked that your primary server is enabled to run the package:

cmviewcl -v -p paDP. if it says disabled:

cmmodpkg -e -n covsapp paDP

It would not start becuase the package was not enabled on covsapp so it would not switch back. After doing this command cmmodpkg -e -n covsapp paDP I could then run the cmrunpkg -v -v covsapp paDP command on the main node.

Thanks all.

Chad

[Senthil Kumar .A_1]

Hi Chad,

These are the erros in syslog file that indicates your failure to start the package in the primary node. Meaning, the primary node was disable to start the package when the package was halted...

Apr 20 09:31:08 covsapp CM-CMD[14550]: cmrunpkg -v paDP
Apr 20 09:31:08 covsapp cmcld: Unable to start package paDP. Node covsapp not enabled to run it.
Apr 20 09:47:39 covsapp CM-CMD[16601]: cmrunpkg -v paDP
Apr 20 09:47:39 covsapp cmcld: Unable to start package paDP. Node covsapp not enabled to run it.

To fix this issue, when you find the downtime do the following...

cmhaltpkg -v -n covsapq paDP
cmmodpkg -e -n covsapp paDP
cmrunpkg -v -n covsapp paDP

regards,
Senthil Kumar .A

[Chad Brindley]

please see my last post for answer that fixed the problem.

Chad

thread closed.