HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: vgchange: Failed to get vg ownership, 251 clos...
Operating System - HP-UX
1838598
Members
3884
Online
110128
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
11-02-2004 07:24 AM
11-02-2004 07:24 AM
vgchange: Failed to get vg ownership, 251 closing conn.
Hi,
I'm having this issue with a cluster configuration basically.
I run the following commands to respectively enable and activate a vg in shared mode
vgchange -c y -S y vgora
vgchange -a s vgora
Second comand returns the following error
vgchange: Failed to get vg ownership, 251 closing conn.
vgchange: failed to get volume group ownership -Function is not available (251)
Initially when I formed the cluster the vg was visible on both nodes of the cluster. After the systems have been rebooted and the cluster reactivated, I can only seem to activate the volume group in exclusive mode.
Really appreciate any assistance with this. Haven't found much info on the reported error.
Thanks and Regards,
-Alvi
I'm having this issue with a cluster configuration basically.
I run the following commands to respectively enable and activate a vg in shared mode
vgchange -c y -S y vgora
vgchange -a s vgora
Second comand returns the following error
vgchange: Failed to get vg ownership, 251 closing conn.
vgchange: failed to get volume group ownership -Function is not available (251)
Initially when I formed the cluster the vg was visible on both nodes of the cluster. After the systems have been rebooted and the cluster reactivated, I can only seem to activate the volume group in exclusive mode.
Really appreciate any assistance with this. Haven't found much info on the reported error.
Thanks and Regards,
-Alvi
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-02-2004 07:29 AM
11-02-2004 07:29 AM
Re: vgchange: Failed to get vg ownership, 251 closing conn.
Hi Alvi,
Was the cluster up when you did the -S y ?
Did you do it on both nodes? Should only be done on one.
If you did it on both do a -S n & bounce the cluster & start again.
Rgds,
Jeff
Was the cluster up when you did the -S y ?
Did you do it on both nodes? Should only be done on one.
If you did it on both do a -S n & bounce the cluster & start again.
Rgds,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-02-2004 07:35 AM
11-02-2004 07:35 AM
Re: vgchange: Failed to get vg ownership, 251 closing conn.
Hi Omar,
Was the vg deactivated before you ran the "vgchange -c y -S y vgora" command.
the vg should be deavtivated on all nodes, vgchange -a n vgora and then the share should be enabled,
vgchange -c y -S y vgora
If required i would suggest doing to export / import on the other nodes using a map file after the share is enabled.
Hope this helps.
Regds
Was the vg deactivated before you ran the "vgchange -c y -S y vgora" command.
the vg should be deavtivated on all nodes, vgchange -a n vgora and then the share should be enabled,
vgchange -c y -S y vgora
If required i would suggest doing to export / import on the other nodes using a map file after the share is enabled.
Hope this helps.
Regds
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-02-2004 10:05 AM
11-02-2004 10:05 AM
Re: vgchange: Failed to get vg ownership, 251 closing conn.
Thanks Jeff and Sanjay,
I issued the shared mode enabling command only on one of the nodes, the primary, and also I issued it while the vg was deactivated.
And, as I mentioned before, when I first activated the cluster I could see the vg on both nodes, indicating that tis command ha worked before.
Thanks and Regards,
-Alvi
I issued the shared mode enabling command only on one of the nodes, the primary, and also I issued it while the vg was deactivated.
And, as I mentioned before, when I first activated the cluster I could see the vg on both nodes, indicating that tis command ha worked before.
Thanks and Regards,
-Alvi
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