Backup failing on a LXC container

[Xionous]

Hello,

I am wondering if someone can help me determine why a backup is failing on an LXC container. Here is the log from the backup:

INFO: starting new backup job: vzdump 201 --notes-template '{{guestname}}' --node pmx --remove 0 --storage pmx-b --mode snapshot
INFO:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
INFO:                                  Dload  Upload   Total   Spent    Left  Speed
INFO:   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
INFO:   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
INFO: curl: (7) Failed to connect to localhost port 19999: Connection refused
INFO: Starting Backup of VM 201 (lxc)
INFO: Backup started at 2023-10-06 11:39:30
INFO: status = running
INFO: CT Name: dhcp
INFO: including mount point rootfs ('/') in backup
INFO: mode failure - some volumes do not support snapshots
INFO: trying 'suspend' mode instead
INFO: backup mode: suspend
INFO: ionice priority: 7
INFO: CT Name: dhcp
INFO: including mount point rootfs ('/') in backup
INFO: starting first sync /proc/81869/root/ to /var/tmp/vzdumptmp82663_201
ERROR: Backup of VM 201 failed - command 'rsync --stats -h -X -A --numeric-ids -aH --delete --no-whole-file --sparse --one-file-system --relative '--exclude=/tmp/?*' '--exclude=/var/tmp/?*' '--exclude=/var/run/?*.pid' /proc/81869/root//./ /var/tmp/vzdumptmp82663_201' failed: exit code 11
INFO: Failed at 2023-10-06 11:39:32
INFO:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
INFO:                                  Dload  Upload   Total   Spent    Left  Speed
INFO:   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
INFO:   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
INFO: curl: (7) Failed to connect to localhost port 19999: Connection refused
INFO: Backup job finished with errors
TASK ERROR: job errors

 

[stream-everything]

Hi Xionous,

May be there's something wrong with your permissions. Where are you going to store your backups?

I also recommend reading this thread...

For me this solution worked:
nano /etc/vzdump.conf
and then editing the first line to tmpdir: /tmp (see also screenshot below)



Kind regards

 

[Xionous]

Hi Xionous,

May be there's something wrong with your permissions. Where are you going to store your backups?

I also recommend reading this thread...

For me this solution worked:
nano /etc/vzdump.conf
and then editing the first line to tmpdir: /tmp (see also screenshot below)

View attachment 56379

Kind regards

Thank you for the reply, I will try that but i do not think that is the issue. There are 12 VMs that also get backed up at the same time and there is no issue with those, it is just a single LXC container that fails to backup. My backups are going to a Proxmox Backup Server.

 

[Xionous]

For me this solution worked:
nano /etc/vzdump.conf

Tried this and it did not solve the issue.

 

[stream-everything]

Thank you for the reply, I will try that but i do not think that is the issue. There are 12 VMs that also get backed up at the same time and there is no issue with those, it is just a single LXC container that fails to backup. My backups are going to a Proxmox Backup Server.

Tried this and it did not solve the issue.

Did you also edit the first line of that vzdump.conf file on your proxmox host?

 

[Xionous]

Did you also edit the first line of that vzdump.conf file on your proxmox host?

Yes

 

[fiona]

Hi,

Hello,

I am wondering if someone can help me determine why a backup is failing on an LXC container. Here is the log from the backup:

INFO: starting new backup job: vzdump 201 --notes-template '{{guestname}}' --node pmx --remove 0 --storage pmx-b --mode snapshot
INFO:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
INFO:                                  Dload  Upload   Total   Spent    Left  Speed
INFO:   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
INFO:   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
INFO: curl: (7) Failed to connect to localhost port 19999: Connection refused

This is unusual output. Is this caused by some hookscript you have configured?

ERROR: Backup of VM 201 failed - command 'rsync --stats -h -X -A --numeric-ids -aH --delete --no-whole-file --sparse --one-file-system --relative '--exclude=/tmp/?*' '--exclude=/var/tmp/?*' '--exclude=/var/run/?*.pid' /proc/81869/root//./ /var/tmp/vzdumptmp82663_201' failed: exit code 11

Looking it up in man rsync, exit code 11 means Error in file I/O. Can you check that everything is okay with the involved storages and the physical disks (e.g. with smartctl)? Are there any messages in the system logs/journal around the time the issue occurs?

 

[Xionous]

Hi,

This is unusual output. Is this caused by some hookscript you have configured?

Yes that was being caused by a script.

Looking it up in man rsync, exit code 11 means Error in file I/O. Can you check that everything is okay with the involved storages and the physical disks (e.g. with smartctl)? Are there any messages in the system logs/journal around the time the issue occurs?

I could not find any issues, but based on this info i figured i would try removing and re-adding my PBS and this seems to have solved the issue, the container now backs up normally.

 

[fiona]

I could not find any issues, but based on this info i figured i would try removing and re-adding my PBS and this seems to have solved the issue, the container now backs up normally.

Glad that it worked! But I'm a bit surprised, because it had failed on the first sync to the tmpdir, before PBS was involved:

INFO: starting first sync /proc/81869/root/ to /var/tmp/vzdumptmp82663_201
ERROR: Backup of VM 201 failed - command 'rsync --stats -h -X -A --numeric-ids -aH --delete --no-whole-file --sparse --one-file-system --relative '--exclude=/tmp/?*' '--exclude=/var/tmp/?*' '--exclude=/var/run/?*.pid' /proc/81869/root//./ /var/tmp/vzdumptmp82663_201' failed: exit code 11