Error: Acquire running lock failed: 512

Asset ID:	1-72-1625095.1
Update Date:	2017-10-20
Keywords:

Solution Type Problem Resolution Sure

Solution 1625095.1 : Error: Acquire running lock failed: 512

Applies to:

Oracle VM - Version 3.1.1 and later
Exalogic Elastic Cloud X4-2 Hardware
Linux x86-64

Symptoms

When try to start or migrate a virtual machine ( guest/domU ), the ovs-agent.log on the Oracle VM server ( dom0 ) shows the following error:

[2014-02-16 04:53:02 26866] DEBUG (service:74) async call start: start_vm('0004fb00000300005a77c160355563fb', '0004fb00000600004a128ef0b90b93a0')
[2014-02-16 04:53:02 26871] ERROR (base:259) async call exception
Traceback (most recent call last):
File "/usr/lib64/python2.4/site-packages/agent/api/host/base.py", line 257, in ovs_async_proc
    output = function(*args)
File "/usr/lib64/python2.4/site-packages/agent/lib/service.py", line 109, in wrapper
    return func(*args)
File "/usr/lib64/python2.4/site-packages/agent/api/hypervisor/xenxm.py", line 120, in start_vm
    create_vm(path)
File "/usr/lib64/python2.4/site-packages/agent/lib/xenxm.py", line 148, in create_vm
    run_cmd(['xm', 'create', path])
File "/usr/lib64/python2.4/site-packages/agent/lib/linux.py", line 49, in run_cmd
    raise RuntimeError('Command: %s failed (%s): stderr: %s stdout: %s'
RuntimeError: Command: ['xm', 'create', '/OVS/Repositories/0004fb00000300005a77c160355563fb/VirtualMachines/0004fb00000600004a128ef0b90b93a0/vm.cfg'] failed (1): stderr: Error: Acquire running lock failed: 512
stdout: Using config file "/OVS/Repositories/0004fb00000300005a77c160355563fb/VirtualMachines/0004fb00000600004a128ef0b90b93a0/vm.cfg".

[2014-02-16 04:53:02 26871] DEBUG (base:269) async call complete: func: start_vm pid: 26871 status: 1 output: Command: ['xm', 'create', '/OVS/Repositories/0004fb00000300005a77c160355563fb/VirtualMachines/0004fb00000600004a128ef0b90b93a0/vm.cfg'] failed (1): stderr: Error: Acquire running lock failed: 512
stdout: Using config file "/OVS/Repositories/0004fb00000300005a77c160355563fb/VirtualMachines/0004fb00000600004a128ef0b90b93a0/vm.cfg".

Cause

The cause is a stale lock file in /var/run/ovs-agent/

[root@ca-support9 ~]# ls -ltr /var/run/ovs-agent/
total 28
-rw------- 1 root root 5 Feb 4 06:26 log.pid
-rw------- 1 root root 5 Feb 4 06:26 xmlrpc.pid
-rw------- 1 root root 5 Feb 4 06:26 stats.pid
-rw------- 1 root root 5 Feb 4 06:26 remaster.pid
-rw------- 1 root root 5 Feb 4 06:26 notification.pid
-rw------- 1 root root 5 Feb 4 06:26 monitor.pid
-rw------- 1 root root 5 Feb 4 06:26 ha.pid
srwx------ 1 root root 0 Feb 10 09:53 notification-server.sock
-rw------- 1 root root 0 Feb 4 06:26 vm-0004fb00000600004a128ef0b90b93a0.lock

Solution

Delete the stale lock ( ensure that the domU is NOT running on any dom0's in the whole cluster ):

# cd /var/run/ovs-agent/
# rm vm-0004fb00000600004a128ef0b90b93a0.lock

Afterwards try to start your domU again.

References

<NOTE:1380333.1> - Oracle VM 3.0: Error: Acquire running lock failed: 256
<BUG:16922439> - XENDERROR: ACQUIRE RUNNING LOCK FAILED: 512 STILL SEEN ON OVM 3.2
<NOTE:1474565.1> - Acquire running lock failed: 256 Error When Start VM From Non-clustered Server Pool

Attachments

This solution has no attachment