HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Starting of package on node hp02
Operating System - HP-UX
1834217
Members
3491
Online
110066
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2004 08:16 PM
04-12-2004 08:16 PM
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.
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2004 08:27 PM
04-12-2004 08:27 PM
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.
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!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2004 08:36 PM
04-12-2004 08:36 PM
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.
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
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP