- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Cluster lock was denied. Lock was obtained by anot...
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
01-19-2008 05:48 AM
01-19-2008 05:48 AM
Cluster lock was denied. Lock was obtained by another node
I have two node cluster with EVA shared storage. Cluster and package are configured for failover.
When I’m halting node1 package is moving and running on node 2 without any problems.
But : If I physically disconnect all networks cables ( I have 4 LAN cards on each node) from node1 –package is trying to be run on node2 and after couple of minutes node2 restarts. Syslog on node2 give this error:
“
Jan 19 11:32:42 db2 cmcld[13896]: Timed out node db1. It may have failed.
Jan 19 11:32:42 db2 cmcld[13896]: Attempting to form a new cluster
Jan 19 11:32:42 db2 cmcld[13896]: Beginning standard election
Jan 19 11:32:43 db2 cmfileassistd[14084]: Updated file /var/adm/cmcluster/frdump.cmcld.7 (length = 251602).
Jan 19 11:32:49 db2 cmcld[13896]: Obtaining Cluster Lock
Jan 19 11:32:50 db2 cmcld[13896]: Cluster lock was denied. Lock was obtained by another node.
Jan 19 11:32:50 db2 cmcld[13896]: Attempting to form a new cluster
Jan 19 11:32:50 db2 cmcld[13896]: Beginning standard election
Jan 19 11:32:58 db2 cmcld[13896]: Cluster lock has been denied
Jan 19 11:33:43 db2 cmcld[13896]: Service cmfileassistd terminated due to an exit(0)”
After I disconnect network cables on node1 I still can access shared volumes. This could be a reason why package cannot start on node2.
Is there any way to configure cluster to run HALT_Script when all network interfaces are down???
Has anyone met this problem???
Thanks in advance,
Farid.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-19-2008 11:24 AM
01-19-2008 11:24 AM
Re: Cluster lock was denied. Lock was obtained by another node
That's not a problem - that's expected behaviour in a 2-node cluster when one node can't communicate with the other. You might 'know' that node 2 still has LAN connections and could run the package and that node 1 has no LAN connections and can't run the package, but as there is no LAN interconnect between the 2 nodes, neither can know the state of the other and therefore have to use some tie-break mechanism - in this case a race for the cluster lock, which unfortunately node 2 lost. To do anything else would be to risk the integrity of your data by causing a split-brain scenario (both nodes think they are the remaining cluster and both access the data on disk concurrently causing corruption).
Serviceguard protects against single points of failure - removing all the LAN connections is multiple points of failure, so you can't assume the cluster will recover from this automatically. In these situations Serviceguard considers protecting the integrity of your data to be more important than keeping the package up.
One alternative to get different behaviour in this scenario is to use a Serviceguard quorum server rather than a cluster lock disk. If you had used a quorum server then in this scenario I think node 2 would have remained running the cluster - of course quorum servers place more emphasis on the resilience of your network, so consider carefully.
Read this paper here to get a full understanding of this cluster behaviour:
http://docs.hp.com/en/B3936-90078/B3936-90078.pdf
HTH
Duncan
I am an HPE Employee

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-21-2008 04:42 AM
01-21-2008 04:42 AM
Re: Cluster lock was denied. Lock was obtained by another node
But if node1 does not have network connection is there any way to configure node1 to halt node in this case.????????
let say halt node1 when all interfaces or heardbeat interfaces are down.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-21-2008 05:23 AM
01-21-2008 05:23 AM
Re: Cluster lock was denied. Lock was obtained by another node
If a quorum server were used, a complete network failure on one node would also prevent access to the quorum server, guaranteeing that node would be ejected from the cluster.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-21-2008 12:14 PM
01-21-2008 12:14 PM
Re: Cluster lock was denied. Lock was obtained by another node
HTH
Duncan
I am an HPE Employee
