can't lock file '/var/lock/qemu-server/lock-100.conf' - got timeout

vitalijs-saro

New Member
Jan 20, 2021
6
0
1
39
Hi,

Virtual Environment 6.2-4

I am investigating issue about the reboot VM from Proxmox. Issue that on reboot it is loading and loading and nothing happens. In logs I can see:

....
Sep 16 21:52:01 pr3 systemd[1]: Started Proxmox VE replication runner.
Sep 16 21:53:00 pr3 systemd[1]: Starting Proxmox VE replication runner...
Sep 16 21:53:01 pr3 systemd[1]: pvesr.service: Succeeded.
Sep 16 21:53:01 pr3 systemd[1]: Started Proxmox VE replication runner.
Sep 16 21:53:59 pr3 pveproxy[20516]: worker exit
Sep 16 21:53:59 pr3 pveproxy[1955]: worker 20516 finished
Sep 16 21:53:59 pr3 pveproxy[1955]: starting 1 worker(s)
Sep 16 21:53:59 pr3 pveproxy[1955]: worker 7616 started
.....

If I click stop - I received:

trying to acquire lock...
can't lock file '/var/lock/qemu-server/lock-100.conf' - got timeout

For sure remove file and Stop - Start will work fine, but not reboot.

Could You, please, tell me what can be the cause?

Thanks,
 
nothing interesting in the above log.

try the qm unlock 100 command, if that not helps please provide us with the output of
Bash:
pveversion -v
qm config 100

you could also run journalctl -f before restarting the VM for more details of the Syslog
 
nothing interesting in the above log.

try the qm unlock 100 command, if that not helps please provide us with the output of
Bash:
pveversion -v
qm config 100

you could also run journalctl -f before restarting the VM for more details of the Syslog
Hi,

Yes forgot to mentioned qm unlock 100 - I tried didn't help. I did it - tried to restart the same.

Log yes, also payed attention to it - nothing there: "worker exit worker started." It is not good,cause without error - really hard to investigate.

Code:
root@proxmox:~# pveversion -v
proxmox-ve: 6.2-1 (running kernel: 5.4.34-1-pve)
pve-manager: 6.2-4 (running version: 6.2-4/9824574a)
pve-kernel-5.4: 6.2-1
pve-kernel-helper: 6.2-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libproxmox-acme-perl: 1.0.3
libpve-access-control: 6.1-1
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-2
libpve-guest-common-perl: 3.0-10
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-7
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.2-1
lxcfs: 4.0.3-pve2
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-1
pve-cluster: 6.1-8
pve-container: 3.1-5
pve-docs: 6.2-4
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.1-2
pve-firmware: 3.1-1
pve-ha-manager: 3.0-9
pve-i18n: 2.1-2
pve-qemu-kvm: 5.0.0-2
pve-xtermjs: 4.3.0-1
qemu-server: 6.2-2
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1
root@proxmox:~#
[code]

[code]
root@proxmox:~# qm config 100
agent: 1
boot: cdn
bootdisk: scsi0
cores: 8
ide2: none,media=cdrom
memory: 10240
name: IEM2020
net0: e1000=22:7C:85:07:94:B9,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: other
scsi0: local-zfs:vm-100-disk-1,size=10G,ssd=1
scsi1: local-zfs:vm-100-disk-0,size=20G,ssd=1
scsi2: local-zfs:vm-100-disk-2,size=150G,ssd=1
scsihw: virtio-scsi-pci
smbios1: uuid=f3daf50b-d6bb-4331-abf4-64fd29acecef
sockets: 1
vmgenid: 281b7848-941e-4ea1-9c7f-a98d5d6c2ccc
root@proxmox:~#
[code]

Maybe it will help You ( Actually I thought this is exact error, but no ):

It was my first Proxmox server ( with others I was more attentive ) - I called server pr3, but then re called it to proxmox, so finally in /etc/hosts were pr3 and proxmox -> became two nodes pr3 and proxmox . Yes, pr3 never used, all in proxmox in GUI only proxmox ---- maybe it will help You.

P.S. /etc/hosts corrected, but on restart VM the same
 
Ok, please post the cat /etc/hosts and the output of the hostname

you could also provide us with the Syslog since you restart the VM by using: journalctl -f and just restart the VM
 
Hi
Code:
root@proxmox:~# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost

10.9.12.126 proxmox.smartmedical.eu proxmox

# The following lines are desirable for IPv6 capable hosts

::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
root@proxmox:~#

root@proxmox:~# hostname
proxmox

It is production server, so I can't restart it - I will request maintenance window for today at this moment I will attach syslog from last week, when I tried to do 3 restart - all 3 were unsuccessful, so Start - Stop were done. Maybe it will give You more info
( 1st restart started: Sep 16 21:39:17 pr3 systemd[1]: Starting User Manager for UID 0...)

Thanks,
 

Attachments

  • syslog.txt
    314.6 KB · Views: 8

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!