Proxmox constantly trying to restart tigervnc server...

[intrax]

Since latest update today I got:

Mar 30 16:15:20 proxmox-bl systemd[1]: tigervncserver@:1.service: Main process exited, code=exited, status=1/FAILURE
Mar 30 16:15:20 proxmox-bl systemd[1]: tigervncserver@:1.service: Failed with result 'exit-code'.
Mar 30 16:15:30 proxmox-bl systemd[1]: tigervncserver@:1.service: Scheduled restart job, restart counter is at 105.
Mar 30 16:15:30 proxmox-bl systemd[1]: Stopped tigervncserver@:1.service - Remote desktop service (VNC).
Mar 30 16:15:30 proxmox-bl systemd[1]: Starting tigervncserver@:1.service - Remote desktop service (VNC)...
Mar 30 16:15:30 proxmox-bl vncserver[19431]: vncserver: Option ::1: Unrecognized!

constantly trying to restart my vncserver, which was running fine before !

What is going on ?

edit: I stopped and disabled the service, but still restarts continue!

ok got it: unit file changed from

Restart = always to Restart = on-abort

working again!

 

[bbgeek17]

"tigervncserver" is not something that PVE comes with. Its something you installed and you should be maintaining on your own.

That said:

Restart = always to Restart = on-abort
working again!

That likely means that your service still failed to start, but is not attempting to restart as it used to do before.

Restart
Configures whether to restart the service when the service’s process exits, is killed, or reaches a timeout:

no - The service will not be restarted. This is the default.

on-success - Restart only when the service process exits cleanly (exit code 0).

on-failure - Restart only when the service process does not exit cleanly (node-zero exit code).

on-abnormal - Restart if the process terminates with a signal or when a timeout occurs.

on-abort - Restart if the process exits due to an uncaught signal not specified as a clean exit status.

always - Always restart.

The previous errors meant that the VNC was failing to start, likely due to misconfiguration and systemd was trying to restart it, albeit unsuccessfully since the configuration was not fixed.

Now you set it to only restart when the binary fails due to uncaught/unrecognized runtime error. However, since it was never started the restart condition will never be hit.
If you check the status of your service, you will likely find it in "failed" state: systemctl status tigervncserver"

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[intrax]

"tigervncserver" is not something that PVE comes with. Its something you installed and you should be maintaining on your own.

True, but it was running fine until latest update today and is again running fine now. Probably the proxmox c. q. debian update pushed a new version of systemd which caused the initial setup to fail!
Thanks your attention!

edit:
changed to

Restart = on-success

works fine!