Connection failed (Error 500: close (rename) atomic file '/var/log/pve/tasks/active' failed: Permission denied)

pongista

New Member
Feb 2, 2026
5
0
1
please, some one can help me to solve this problem? I have error 500:

Connection failed (Error 500: close (rename) atomic file '/var/log/pve/tasks/active' failed: Permission denied)

thanks a lot who can help me
 
Just the error message isn't enough for providing useful advice. Would you like to describe the setup you're using and how you triggered the error?
 
How I can describe my setup?, I have proxmox with some virtual machines. This error come out for everything, even if I try to do a virtual machine backup, even if I clic on proxmox shell
Immagine 2026-02-02 081208.png
 
Have you used the Proxmox VE Helper-Scripts? If yes, the problem might be caused there and you have to get back to the authors of the used scripts.

For some additional information for troubleshooting: Connect to your node via ssh or a local console. Provide the output of the following commands

Bash:
systemctl status pve-cluster
mount | grep pve
ls -la /var/log/pve/tasks/
 
Have you used the Proxmox VE Helper-Scripts? If yes, the problem might be caused there and you have to get back to the authors of the used scripts.

For some additional information for troubleshooting: Connect to your node via ssh or a local console. Provide the output of the following commands

Bash:
systemctl status pve-cluster
mount | grep pve
ls -la /var/log/pve/tasks/
this is the result
1.png
 
Nothing unusual to spot.
You could try getting rid of the blocking file with following commands.
Bash:
systemctl stop pve-cluster
rm -f /var/log/pve/tasks/active*
rm -f /var/log/pve/tasks/index*
systemctl start pve-cluster
 
I tried your commands and restarted Proxmox, but nothing changed. When I click on shell, this appears, and so does all the other virtual machines. They don't start automatically, but if I go to each one and click start, they start, but it still gives me the same error.
1.png
 
If you have a backup of the vm/lxc you could reinstall Proxmox and restore the backups.
The used Proxmox VE version 8.0.3 is from somewhen in 2023. You might consider updating it to at least the current version of the 8.x branch (apt-get update && apt-get dist-upgrade).