Search results

Thank you very much! Indeed, the Notifications were not set up and used the default root user (root@pam) without a proper email set. However, I still think it might be useful to have a separate logwatch rule to catch Proxmox issues in the system logs. Would be great if you managed to add it to...

That's the point - I do have backup failure notifications set, but they weren't sent. Looks like it's b/c the error happened before that actual backup had started.

just discovered that my backups didn't run since September.. here is the logwatch config that should catch and report proxmox errors (if any): cat /etc/logwatch/scripts/services/proxmox #!/bin/bash grep -i " pve" | egrep -i "(error|critical|failed)" cat...

Thanks @bor.paw ! You probably meant to add LogLevelMax=notice

More than a year has passed, still facing this issue on Proxmox 8.2.4 (the host is 24 cores Xeon X5670, 96GB RAM, 20 cores are allocated to the VM; no more VMs are running on this host):

Thanks for the workaround! Unfortunately it doesn't prevent systemd-journald logging. Any ideas how to fix it?

Hi, same here: root@vm-box-2:~# qm config 122 agent: 1 bootdisk: virtio0 cores: 2 description: windows ide2: trendy-images:iso/virtio-win-0.1.229.iso,media=cdrom,size=522284K memory: 5000 name: vm-wsus19 net0: virtio=9E:6A:4B:42:42:F3,bridge=vmbr0,firewall=1 numa: 0 onboot: 1 ostype: win10...

Hi, Anybody has a clue how to get this fixed, pls? root@vm-box-3:~# pct config 108 arch: amd64 cores: 1 ... ostype: centos swap: 512 unprivileged: 1 root@vm-box-3:~# pct enter 108 # yum update -y Last metadata expiration check: 0:18:38 ago on Fri 23 Jul 2021 03:03:41 PM MSK. Dependencies...

Thank you, Dominik, for all your quick and helpful answers!

I was just trying to figure this out without success: does Proxmox Backup Server export its storage thru NFS or it uses some other protocol?

yeah, good point. > What storage is it better to use instead of NFS to avoid the blocking issue you mentioned? would you pls answer this question?

Thank for your reply Dominik! What storage is it better to use instead of NFS to avoid the blocking issue you mentioned? What about my suggestion on checking the free space before doing a backup? I understand it's not a Proxmox's job to work as a monitoring engine, but it might be hard to...

Hi, I have a VM with two drives which is set to backup once a week by Proxmox internal backup tool. The backups are stored on an NFS share. Last backup has failed due to space issues on the NFS server: vzdump 122 127 --mailnotification failure --compress zstd --quiet 1 --storage trendy-images...

What was the reason for that? The other entries still have that "HASH" stuff and won't run upon schedule..

removed

root@vm-box-4:/etc/pve# cat /etc/pve/vzdump.cron # cluster wide vzdump cron schedule # Automatically generated file - do not edit PATH="/usr/sbin:/usr/bin:/sbin:/bin" 45 0 * * 7 root vzdump 100 116 130 131 132 126 --mode snapshot --prune-backups 'HASH(0x55e4ca7691e0)'...

Hi, root@vm-box-4:~# pveversion pve-manager/6.3-3/eee5f901 (running kernel: 5.4.78-2-pve) I cannot say the action from my side that caused this issue (probably, installing the latest updates), Proxmox backups stopped working. There's a letter from crond: 400 Parameter verification failed...

Thank you very much! I've deleted pve-root-ca and pve-ssl files and regenerated certs with the command you provided.

I'm sorry, it's not clear for me what you're asking about. do i need to delete existing custom certificates and upload them again?

Hi, For some reason PVE tries to update my custom certificate and predictably fails with truncating the cert file which leads to inaccessible web interface: # pveversion pve-manager/6.2-15/48bd51b6 (running kernel: 5.4.65-1-pve) # systemctl status pve-daily-update.service ... Nov 17 03:14:33...