Error timeout
- Thread starter frankz
- Start date
Hi,
first a few questions:
* did it work earlier and just happened now/once
* is there higher latency between that Proxmox VE setup and the PBS server?
* What storage is on the PBS (slow spinners or the fast stuff?)
In general, that can indicate an issue when QEMU tries to connect to the PBS in sync.
This whole deal got a lot better in QEMU 5.2, which allows to do some QEMU monitor commands (like this one) asynchrony, avoiding blocking too much.
It is currently available on
https://pve.proxmox.com/wiki/Package_Repositories
first a few questions:
* did it work earlier and just happened now/once
* is there higher latency between that Proxmox VE setup and the PBS server?
* What storage is on the PBS (slow spinners or the fast stuff?)
In general, that can indicate an issue when QEMU tries to connect to the PBS in sync.
This whole deal got a lot better in QEMU 5.2, which allows to do some QEMU monitor commands (like this one) asynchrony, avoiding blocking too much.
It is currently available on
pvetest, if you want to try it out.https://pve.proxmox.com/wiki/Package_Repositories
Hello and thanks for the reply . Then the storage space of the storage is sufficient, the percentage occupied is 50%. The transfer of the backups takes place on a dedicated nic, even if in the same net there is an nfs server, which generates little traffic. It only happened once. I am attaching some screenshots.
I hope this can help, if you want more just ask.
Attachments
Can you post the full text log of the problematic VMs or at least parts of that?
And, I assume this was still using QEMU 5.1?
PBS :
proxmox-backup: 1.0-4 (running kernel: 5.4.78-2-pve) proxmox-backup-server: 1.0.8-1 (running version: 1.0.8) pve-kernel-5.4: 6.3-3 pve-kernel-helper: 6.3-3 pve-kernel-5.4.78-2-pve: 5.4.78-2 pve-kernel-5.4.65-1-pve: 5.4.65-1 ifupdown2: 3.0.0-1+pve3 libjs-extjs: 6.0.1-10 proxmox-backup-docs: 1.0.8-1 proxmox-backup-client: 1.0.8-1 proxmox-mini-journalreader: 1.1-1 proxmox-widget-toolkit: 2.4-4 pve-xtermjs: 4.7.0-3 smartmontools: 7.1-pve2 zfsutils-linux: 0.8.5-pve1
NODE 1 cluster:
proxmox-ve: 6.3-1 (running kernel: 5.4.78-2-pve) pve-manager: 6.3-3 (running version: 6.3-3/eee5f901) pve-kernel-5.4: 6.3-3 pve-kernel-helper: 6.3-3 pve-kernel-5.3: 6.1-6 pve-kernel-5.0: 6.0-11 pve-kernel-5.4.78-2-pve: 5.4.78-2 pve-kernel-5.4.78-1-pve: 5.4.78-1 pve-kernel-5.3.18-3-pve: 5.3.18-3 pve-kernel-5.0.21-5-pve: 5.0.21-10 pve-kernel-5.0.15-1-pve: 5.0.15-1 ceph-fuse: 12.2.11+dfsg1-2.1+b1 corosync: 3.1.0-pve1 criu: 3.11-3 glusterfs-client: 5.5-3 ifupdown: 0.8.35+pve1 ksm-control-daemon: 1.3-1 libjs-extjs: 6.0.1-10 libknet1: 1.20-pve1 libproxmox-acme-perl: 1.0.7 libproxmox-backup-qemu0: 1.0.2-1 libpve-access-control: 6.1-3 libpve-apiclient-perl: 3.1-3 libpve-common-perl: 6.3-3 libpve-guest-common-perl: 3.1-4 libpve-http-server-perl: 3.1-1 libpve-storage-perl: 6.3-6 libqb0: 1.0.5-1 libspice-server1: 0.14.2-4~pve6+1 lvm2: 2.03.02-pve4 lxc-pve: 4.0.6-2 lxcfs: 4.0.6-pve1 novnc-pve: 1.1.0-1 proxmox-backup-client: 1.0.8-1 proxmox-mini-journalreader: 1.1-1 proxmox-widget-toolkit: 2.4-5 pve-cluster: 6.2-1 pve-container: 3.3-3 pve-docs: 6.3-1 pve-edk2-firmware: 2.20200531-1 pve-firewall: 4.1-3 pve-firmware: 3.2-1 pve-ha-manager: 3.1-1 pve-i18n: 2.2-2 pve-qemu-kvm: 5.1.0-8 pve-xtermjs: 4.7.0-3 qemu-server: 6.3-5 smartmontools: 7.1-pve2 spiceterm: 3.1-1 vncterm: 1.6-2 zfsutils-linux: 0.8.5-pve1
Error log :
