Search results

Update: rebooting the host (which runs PBS in LXC) resolved the issue. I have no idea why this was an issue, but at least rebooting resolved it.

I'm struggling with this error when attempting a file restore: "PBS connect failed: command error: error trying to connect: error:0A000086:SSL routines:tls_post_process_server_certificate:certificate verify failed:../ssl/statem/statem_clnt.c:1889:" I'm not sure if it's because I have a self...

I hate to do this, but I want to bump this thread in hopes that someone can help with this issue. I asked on Reddit and it sounds like I'm not the only one with this issue, but so far I haven't found a solution...

I'm attempting to do a file restore on a backup for one of my VMs, and I get this error message in a popup with no other context, not even whatever it's referring to "above." Error: Starting VM failed. See output above for more information. I tried from the shell and that gives some more...

I have a couple backups configured in Proxmox (going to PBS). Both of them have "On failure only" set for Notify. Up until now this worked fine, I only get emails when something fails. All of a sudden, as of yesterday, I have been getting notifications for all backups including successful ones...

Thanks! I found the same information yesterday but wasn't sure if that was related. I will keep an eye on this going forward, but it doesn't sound like a major issue.

The journalctl log was before the reboot, when I was having the issue. The udev failures are interesting, specifically the zd16 is the one that corresponds to vm-125. How can I determine the root cause for the udev failures? Edit: Since the latest reboot, I still see the 1 udev-worker failure

This output includes everything since this morning's reboot, but previously it was missing vm-103 and vm-125 root@pve:~# ls -l /dev/zvol/nvme1tb/ total 0 lrwxrwxrwx 1 root root 10 Oct 4 09:02 vm-103-disk-0 -> ../../zd48 lrwxrwxrwx 1 root root 12 Oct 4 09:02 vm-103-disk-0-part1 -> ../../zd48p1...

Thanks. I want to start with the fact that I ran apt update && apt full-upgrade which updated the kernel version and zfs version, then rebooted. After the reboot everything is working as expected. So I'm not sure if there was a fix or something in either the kernel or zfs, but it appears to have...

After rebooting, one of my VMs fails to start with this message "TASK ERROR: timeout: no zvol device link for 'vm-125-disk-0' found after 300 sec found." This is on 8.0.4 and here are some outputs I think might be relevant. Any ideas how I can resolve this?

Thank you for all your help!

Ok, I removed the /var/log mount in /etc/fstab and uninstalled the folder2ram service. I had previously been trying to get proxmox to write logs somewhere besides the SSD it's installed on to reduce write wear, but clearly not doing it correctly. After rebooting, I ran journalctl -b >...

I enabled debugging and modified a config under /etc/pve and attached the resulting journalctl.txt file. It does seem to include up to date information this time. I don't use ZFS on the root filesystem, it's EXT4. I don't use Ansible or any other system to automate provisioning of configurations...

Those are all the logs from the output of journalctl -b > journalctl.txt The issue seems to occur any time I reboot which has been 3 times including the upgrade a couple weeks ago. I don't recall any issues during the upgrade, other than noticing this issue and resolving it manually afterward...

Sorry, I should have just posted the full output. root@pve:~# systemctl status pve-cluster.service ● pve-cluster.service - The Proxmox VE cluster filesystem Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; preset: enabled) Active: active (running) since Mon 2023-10-02...

Thanks. This is just a single PVE node, not part of any cluster. The output of the service status shows that it's active/running but only since this morning at 8:25AM EST. The output of journalctl -b -u pve-cluster.service shows that it was started yesterday around 4:20PM which is when I...

I recently upgraded to proxmox 8.0 and noticed that after rebooting, my LXC templates and VMs had been reverted to older versions. I'm not sure on the details, but things like mount points had been changed, and some instances wouldn't start due to the root disk pointing to old storage locations...

Thanks, that worked for me! I wasn't able to determine that from the documentation, but I changed from the IP address to the name of the backup target which in my case is "backup"

Due to a mistake on my part, I need to restore a LXC container from a backup. I have some snapshots in PBS and I know they work because in PBS I can browse files and restore from there. I tried through the UI from the stopped container, but it errored out stating that it can't find the disk...

Thank you, I updated vzdump.conf to point tmpdir to another location on the disk and my backups are working now!