Got error while backup CT


New Member
Mar 22, 2019
HI! Got a such problem: now i'm trying to make backup in "stop" mode of CT. But reseaved timeout. Wot/s goin on?

<pre>INFO: starting new backup job: vzdump 202 --mode stop --node GPR --compress lzo --storage local --remove 0
INFO: Starting Backup of VM 202 (lxc)
INFO: status = running
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: CT Name: Ticket
INFO: stopping vm
command 'lxc-stop -n 202 --timeout 600' failed: got timeout

pveversion -v
proxmox-ve: 5.3-1 (running kernel: 4.15.18-12-pve)
pve-manager: 5.3-12 (running version: 5.3-12/5fbbbaf6)
pve-kernel-4.15: 5.3-3
pve-kernel-4.15.18-12-pve: 4.15.18-35
pve-kernel-4.15.17-1-pve: 4.15.17-9
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-3
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-48
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-12
libpve-storage-perl: 5.0-39
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-3
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-24
pve-cluster: 5.0-34
pve-container: 2.0-35
pve-docs: 5.3-3
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-18
pve-firmware: 2.0-6
pve-ha-manager: 2.0-8
pve-i18n: 1.0-9
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 2.12.1-2
pve-xtermjs: 3.10.1-2
qemu-server: 5.0-47
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2

pct config 202
arch: amd64
cores: 2
hostname: Ticket
lock: backup
memory: 2048
net0: name=eth0,bridge=vmbr2,hwaddr=96:B3:5E:1F:A9:61,ip=dhcp,type=veth
onboot: 1
ostype: debian
rootfs: virthard2:202/vm-202-disk-0.raw,size=50G
startup: order=9,up=60,down=60
swap: 0

systemctl status lxc@202.service
lxc@202.service - LXC Container: 202
Loaded: loaded (/lib/systemd/system/lxc@.service; disabled; vendor preset: enabled)
Drop-In: /lib/systemd/system/lxc@.service.d
Active: failed (Result: timeout) since Thu 2019-04-18 14:38:06 UTC; 15h ago
Docs: man:lxc-start
Process: 3570 ExecStopPost=/usr/share/lxc/lxc-pve-reboot-trigger 202 (code=exited, status=0/SUCCESS)
Process: 29204 ExecStop=/usr/bin/lxc-stop -n 202 (code=killed, signal=TERM)
Process: 29185 ExecStart=/usr/bin/lxc-start -F -n 202 (code=exited, status=0/SUCCESS)
Main PID: 29185 (code=exited, status=0/SUCCESS)
CPU: 35ms

Apr 18 14:36:06 GPR systemd[1]: Started LXC Container: 202.
Apr 18 14:36:06 GPR lxc-start[29185]: lxc-start: 202: tools/lxc_start.c: main: 280 Container is already running
Apr 18 14:37:08 GPR lxc-stop[29204]: lxc-stop: 202: commands_utils.c: lxc_cmd_sock_rcv_state: 70 Resource temporarily unavailable - Failed to receive message
Apr 18 14:38:06 GPR systemd[1]: lxc@202.service: Stopping timed out. Terminating.
Apr 18 14:38:06 GPR systemd[1]: Stopped LXC Container: 202.
Apr 18 14:38:06 GPR systemd[1]: lxc@202.service: Unit entered failed state.
Apr 18 14:38:06 GPR systemd[1]: lxc@202.service: Failed with result 'timeout'.


i'm shure, that it enough place in all hdd for this operation. If i try to stop backup job. CT stay in blocked by backup mode.
Please, help!


  • Clip2net_190419093029.png
    145.2 KB · Views: 2
Looks like your container could not be stopped in time. Which OS and version are you running in the container?


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!