Error 596 (not only) when communicating with pbs for backups

omgs

Renowned Member
Aug 19, 2016
69
5
73
58
I'm using at a server running Debian bullseye (PVE 7.4) and I have a PBS for backups. Everything was working from PVE until about one week ago (maybe I upgraded to pbs 3.3). I had a daily backup job for a pool. If I try to run the job manually from the gui, I get a "Broken pipe (596)" error. I've been trying several things like restarting the pbs, but no luck. If I use vzdump from the command line for the pbs, it works perfectly.

I've tried disabling the job and reenabling, with no luck. Also disabling the pbs storage, with the same results.

Now, I have to manually setup the cron job out of pve backup schedule. How can I debug this?

Thanks in advance.
 
Hi,
did you already try clearing the browser cache (or use a different browser to see if the issue lies there)? Is there anything in the system logs/journal of the Proxmox VE node?
 
I've just tried another browser, and have the same problem. Besides, I think if it was a browser issue, the schedule should work, but it doesn't. Nothing related to the pbs storage works from PVE. I guess that the PVE can't be "too old".
 
I've just tried another browser, and have the same problem. Besides, I think if it was a browser issue, the schedule should work, but it doesn't. Nothing related to the pbs storage works from PVE. I guess that the PVE can't be "too old".
No, it still should be compatible. Please check the system logs/journal on both sides.
 

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!