Restarting PVE Status Daemon: pvestatdERROR: can't aquire lock '/var/run/pvestatd.pid

[ictdude]

My gui was again corrupt because a mounted mapping got disconnected.

Normally: service pvestatd restart is fixing this. But now i see error:

Restarting PVE Status Daemon: pvestatdERROR: can't aquire lock '/var/run/pvestatd.pid

Is there a way to solve this ? With out rebooting the server ?

 

[dietmar]

Re: Restarting PVE Status Daemon: pvestatdERROR: can't aquire lock '/var/run/pvestatd

Stop (kill) the running pvestatd

 

[ictdude]

Re: Restarting PVE Status Daemon: pvestatdERROR: can't aquire lock '/var/run/pvestatd

Stop (kill) the running pvestatd

Did try to kill. But it is not dying

root@ ~ # ps aux | grep pvestatd

root 2659 1.0 0.1 180724 19048 ? D Apr21 162:29 pvestatd
root 983741 0.0 0.0 7556 884 pts/4 S+ 16:42 0:00 grep pvestatd

root@ ~ # kill 2659

 

[dietmar]

Re: Restarting PVE Status Daemon: pvestatdERROR: can't aquire lock '/var/run/pvestatd

root@ ~ # kill 2659

Don't be too friendly ;-) Use -9 to kill (I guess process hangs on IO)

# kill -9 2659

 

[ictdude]

Re: Restarting PVE Status Daemon: pvestatdERROR: can't aquire lock '/var/run/pvestatd

Don't be too friendly ;-) Use -9 to kill (I guess process hangs on IO)

# kill -9 2659

I also did try that Arrg. Hope i must not reboot ... pain in the ass ..this pvestatd ..

 

[dietmar]

Re: Restarting PVE Status Daemon: pvestatdERROR: can't aquire lock '/var/run/pvestatd

... pain in the ass ..this pvestatd ..

The real problem is the unreliable storage?

And if you find a way to reproduce the behavior we can try to find a workaround.

 

[ictdude]

Re: Restarting PVE Status Daemon: pvestatdERROR: can't aquire lock '/var/run/pvestatd

The real problem is the unreliable storage?

And if you find a way to reproduce the behavior we can try to find a workaround.

That is correct dietmar. I did move some servers from OVH to hetzner. Hetzner has an option
to map your ftp backup and mount this. But this mount is some times not stable.
I already contacted there support. But they don't support this

So if you make backups to a source that cutoff the mounting device, then the gui dont like that

The gui crashes. Mostly a pvestatd restart as workaround. In this case suddenly it don't work.
So can we see this as a bug ? Well maybe you can try that in a test environment. And just cutoff
the backup then you will see the same problem i think. Think this behavior will happen while a backup
is running. Then if the source is cut off then gui is not correct any more.

 

[dietmar]

Re: Restarting PVE Status Daemon: pvestatdERROR: can't aquire lock '/var/run/pvestatd

The gui crashes. Mostly a pvestatd restart as workaround. In this case suddenly it don't work.
So can we see this as a bug ?

We already tried to work around that, but this is a NFS option.
If you do not like that blocking behavior, mount with option 'soft'.

See 'man nfs' for details.

 

[ictdude]

Re: Restarting PVE Status Daemon: pvestatdERROR: can't aquire lock '/var/run/pvestatd

Have again this error. Is there a way to restore service pvestatd ? Cant kill process

Restarting PVE Status Daemon: pvestatdERROR: can't aquire lock '/var/run/pvestatd.pid.lock' - Resource temporarily unavailable
(warning).

I hope i must not reboot the complete system ..