Search results

Thanks for sticking with me on this... The GC ran for 24 hours and then I tried to stop it but even that didn't do anything except an extra line in the task log indicating that it received a stop request. So I rebooted the PBS container but upon reboot another GC started immediately and has...

I have a garbage collection running for the past 16 hours but it doesn't seem to be doing anything: Most of my other garbage collections have completed within 30 mins. Once this garbage collection finishes, I can test out a backup and see if it indicates anything.

Here's the PVE logs from the last 2 days: journalctl -b -u pvestatd --since "2 days ago" Jul 16 18:29:19 proxmox pvestatd[3756]: pbs: error fetching datastores - 500 Can't connect to 19.168.1.33:8007 (Connection timed out) Jul 16 18:29:19 proxmox pvestatd[3756]: status update time (7.334...

I started another backup and sure enough the pbs UI became non-responsive. Logs from pbs container: [pbs: ~]── - sudo journalctl -b -u proxmox-backup-proxy Jul 18 14:38:49 pbs systemd[1]: Starting proxmox-backup-proxy.service - Proxmox Backup API Proxy Server... Jul 18 14:38:49 pbs...

hi @dcsapak , Thanks for responding. The gmail (Network is unreachable) errors seem to be related to this : https://forum.proxmox.com/threads/gmail-unreachable-connection-timed-out.112676/ I, too, don't have any issues with accessing the internet and even accessing the proxmox server or any...

From PVE : the last 150 lines of the logs are: Jul 17 09:58:30 proxmox cgroup-network[3551336]: child pid 3551337 exited with code 1. Jul 17 09:58:30 proxmox cgroup-network[3551360]: Cannot open pid_from_cgroup() file '/sys/fs/cgroup/lxc/111/tasks'. Jul 17 09:58:30 proxmox...

hi @dcsapak , I started a backup from my desktop : Jul 17 10:01:00 pbs proxmox-backup-proxy[45822]: starting new backup on datastore 'pbsDatastore': "host/prodesk/2023-> Jul 17 10:01:00 pbs proxmox-backup-proxy[45822]: protocol upgrade done Jul 17 10:01:00 pbs proxmox-backup-proxy[45822]: GET...

any inputs ? I have disabled all the backups currently as PBS UI goes down whenever a backup starts and hangs...

Yes, but Enterprise SSDs also cost about 10x the price of HDDs. I use NAS HDDs and backup everything on my NAS. I also use ZFS replication that makes a backup of everything on my NAS to a RAIDZ2 pool of used Entrerprise HDDs on a different machine. For my home system, the performance is more...

You might find more relevant responses if this thread were in the PVE sub-forum.

Last few lines from the PBS container: Jul 13 19:17:03 pbs zed[10454]: Failed to initialize libzfs Jul 13 19:17:03 pbs systemd[1]: zfs-zed.service: Main process exited, code=exited, status=1/FAILURE Jul 13 19:17:03 pbs systemd[1]: zfs-zed.service: Failed with result 'exit-code'. Jul 13 19:17:03...

My PBS is a LXC container and I had all of this working prior to a shutdown that I did. After rebooting my proxmox server, the backups have not worked. Yesterday I upgraded Proxmox frm 7.4.3 to 8 and also PBS from 2.4 to 3.0 but I still have all my backups failing as below. INFO: starting new...

I went ahead and upgraded to PBS 3. No issues upgrading in LXC.

I have PBS installed in a LXC container and was wondering how strict the minimum 5GB space requirement is for the upgrade? Anyone out there who has upgraded PBS in a LXC container? Thanks.

Removed the local_lock=all option from the pbsDatastore nfs mount and the backups still work. I am back to where I started. Everything works as it did before the Nov 8 upgrade. The new upgrade that I did on Nov 29 has fixed everything back to how it was.

I wonder if I remount the NFS without the local_lock=all option --- will it still work. I'll test that after I backup all of my containers once as I have not had a backup since almost a month. :)

I tried a new privileged container over the Thanksgiving weekend and it exhibited the same behavior. Today however, I updated my PVE and my PBS container. The packages updated in the PBS container were: Calculating upgrade... Done The following NEW packages will be installed...

Thanks for your reply @fiona I can create/edit/delete files and folders from within the container. I tried this via ssh and from within the browser console. As for the setup not being supported, I understand that. Installing PBS in a container just seemed to be good in terms of separation of...

Any other suggestions here please? My pveversion just in case: [proxmox: ~]── - pveversion -v proxmox-ve: 7.2-1 (running kernel: 5.13.19-2-pve) pve-manager: 7.2-11 (running version: 7.2-11/b76d3178) pve-kernel-5.15: 7.2-14 pve-kernel-helper: 7.2-14 pve-kernel-5.13: 7.1-9...

I have a Archlinux desktop which I backup to PBS as well and I removed the systemd automount for the pbsDatastore and manually mounted the share using local_lock=all option. I checked it and it was set correctly. But running a backup resulted in the same error. So it's not working from the CTs...