VM restarting every 3 minutes

[mihaib]

Hi all,

I have a Truenas core vm that is restarting every 3 minutes. I have no clue why, but this is how the loogs look like:
root@Bespin:~# cat /var/log/pve/tasks/active
UPID:Bespin:0006504E:003B101C:670E5C79:vncshell::root@pam: 0
UPID:Bespin:0006BC8E:003F2F59:670E6706:vncshell::root@pam: 0
UPID:Bespin:000B28B0:006A2D7C:670ED516:vncproxy:100:root@pam: 0
UPID:Bespin:000B2826:006A2CC5:670ED514:qmstart:100:root@pam: 1 670ED516 OK
UPID:Bespin:000B27B9:006A2A33:670ED50E:qmstop:100:root@pam: 1 670ED50F OK
UPID:Bespin:000B21C5:0069F14B:670ED47C:vncproxy:100:root@pam: 1 670ED50F OK
UPID:Bespin:000B19CA:00699C45:670ED3A2:qmstart:100:root@pam: 1 670ED3AC can't lock file '/var/lock/qemu-server/lock-100.conf' - got timeout
UPID:Bespin:000B1936:0069960C:670ED393:qmstop:100:root@pam: 1 670ED39D can't lock file '/var/lock/qemu-server/lock-100.conf' - got timeout
UPID:Bespin:000B0BB8:00690D9A:670ED235:vncproxy:100:root@pam: 1 670ED3EE OK
UPID:Bespin:000B0B06:00690808:670ED227:qmstart:100:root@pam: 1 670ED231 can't lock file '/var/lock/qemu-server/lock-100.conf' - got timeout
UPID:Bespin:000B0A99:006901D6:670ED217:qmstop:100:root@pam: 1 670ED221 can't lock file '/var/lock/qemu-server/lock-100.conf' - got timeout
UPID:Bespin:000B0A5C:006900AE:670ED214:qmshutdown:100:root@pam: 1 670ED46C VM quit/powerdown failed
UPID:Bespin:000AFBEE:00687717:670ED0B4:qmstart:100:root@pam: 1 670ED0B6 OK
UPID:Bespin:000AFB9A:0068748A:670ED0AD:qmstop:100:root@pam: 1 670ED0AE OK
UPID:Bespin:000AED92:0067EADC:670ECF4D:qmstart:100:root@pam: 1 670ECF4F OK
UPID:Bespin:000AED2B:0067E847:670ECF46:qmstop:100:root@pam: 1 670ECF47 OK
UPID:Bespin:000ADF0B:00675EA7:670ECDE6:qmstart:100:root@pam: 1 670ECDE8 OK
UPID:Bespin:000ADE96:00675C0C:670ECDDF:qmstop:100:root@pam: 1 670ECDE0 OK
UPID:Bespin:000AD536:0066FC49:670ECCEA:vncproxy:100:root@pam: 1 670ECD66 OK
UPID:Bespin:000AD0C7:0066D276:670ECC7F:qmstart:100:root@pam: 1 670ECC81 OK
UPID:Bespin:000AD063:0066CFE5:670ECC79:qmstop:100:root@pam: 1 670ECC79 OK
UPID:Bespin:000AC279:0066464B:670ECB18:qmstart:100:root@pam: 1 670ECB1A OK
UPID:Bespin:000AC209:006643BE:670ECB12:qmstop:100:root@pam: 1 670ECB12 OK
UPID:Bespin:000AB418:0065BA3D:670EC9B2:qmstart:100:root@pam: 1 670EC9B3 OK
UPID:Bespin:000AB3A1:0065B7A9:670EC9AB:qmstop:100:root@pam: 1 670EC9AC OK
looks like root is executing a qmstop command.




Any idea why this happens?

 

[fireon]

According to the log, the commands are executed deliberately. Please send the output of the following files:

cat /etc/pve/jobs.cfg

cat /etc/crontab

crontab -l

ls /etc/cron*

 

[leesteken]

Usually these things are caused by "Proxmox helper scripts" (not provided or supported by Proxmox themselves) that people run without knowing what they do exactly and/or they forget that they installed some monitoring software that restarts VMs (because that software does not detect that the VM is already running fine).

 

[mihaib]

nothing in cron. I decided to change the scsi adaptor to virtio-scsi and this fixed the issue. the vm is up for 23h now.
in the mean time I also stopped the bkp job.