Operating System - HP-UX
1834217 Members
3491 Online
110066 Solutions
New Discussion

Starting of package on node hp02

 
jamshed
Frequent Advisor

Starting of package on node hp02

When i try to start my package on node2, next message appeared.
What does it mean?
########### Node "hp02": Starting package at Mon Apr 12 19:31:35 gmt 2004 ###########
Apr 12 19:31:35 - "hp02": Activating volume group vgu00 with exclusive option.
vgchange: Activation of volume group "/dev/vgu00" denied by another node in the cluster.
Request on this system conflicts with Activation Mode on remote system.
ERROR: Function activate_volume_group
ERROR: Failed to activate vgu00
Apr 12 19:31:35 - Node "hp02": Deactivating volume group vgu00
vgchange: Volume group "vgu00" has been successfully changed.
Apr 12 19:31:35 - Node "hp02": Deactivating volume group vgu01
vgchange: Volume group "vgu01" has been successfully changed.
Apr 12 19:31:35 - Node "hp02": Deactivating volume group vgu02
vgchange: Volume group "vgu02" has been successfully changed.
Apr 12 19:31:35 - Node "hp02": Deactivating volume group vgu03
vgchange: Volume group "vgu03" has been successfully changed.
Apr 12 19:31:35 - Node "hp02": Deactivating volume group vgu04
vgchange: Volume group "vgu04" has been successfully changed.
2 REPLIES 2
melvyn burnard
Honored Contributor

Re: Starting of package on node hp02

As per the log message, another node has the vg activated, and as this is a cluster aware vg, it can only be activated one one node at a time.
De-activate it on the other node, but more importantly check the package log on the other node to see why it did not get deactivated automatically, or if someone manualy activated the vg while the package was down.
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!
Sanjiv Sharma_1
Honored Contributor

Re: Starting of package on node hp02

Hi Jamshed,

The error indicates that the vgu00 was already activated in hp01 (another node).

Unmounted the filesystem of vgu00 on hp01.
Deactivated the vgu00
# vgchange -a n /dev/vgu00

Now start the package in hp02.

You should also check the cluster log/syslog.log in hp01 why it didn't unmount/deactivate the vgu00.
Everything is possible