Como detener la tarea de backup

exploradorgt

New Member
Mar 22, 2021
7
0
1
41
Hola a todos, quisiera su guía para saber que debo hacer ya que el proceso de backup se ha tardado más de lo normal y he tratado de matar los procesos pero no he logrado detenerlo, me sigue apareciendo de esta manera en las tareas:

1616435721828.png

y no me deja acceder a los servidores de cada nodo
1616435821085.png

Que podría ser?

Gracias a quien me de una luz de por donde revisar.

Saludos cordiales

LP
 
Using Google translate, I translated your question to:
Hello everyone, I would like your guide to know what I should do since the backup process has taken longer than normal and I have tried to kill the processes but I have not managed to stop it, it keeps appearing in this way in the tasks:
and does not let me access the servers of each node.
What could it be?
________________________________________________________________
What did you do, to try and kill the processes?
If you double click on the task, you will see a log of what is happening. Could you please post this log? There is also a "Stop" button within this task log window, which you could try to click.
 
  • Like
Reactions: exploradorgt
Using Google translate, I translated your question to:
Hello everyone, I would like your guide to know what I should do since the backup process has taken longer than normal and I have tried to kill the processes but I have not managed to stop it, it keeps appearing in this way in the tasks:
and does not let me access the servers of each node.
What could it be?
________________________________________________________________
What did you do, to try and kill the processes?
If you double click on the task, you will see a log of what is happening. Could you please post this log? There is also a "Stop" button within this task log window, which you could try to click.
Hello thank you very much, what I did was to see the processes at the console level and I did not let stop it with kill -9 IDProcess, and in what I wrote the post, I finished executing the task in the two nodes, but I still look for the reason for this to happen, to prevent it from happening again, today that I came had already been executed without any inconvenience.

Best Regards.
 
I would only use kill -9 PID as a final step, in case there is no other way to stop a process, because SIGKILL gives the process no opportunity to clean up and exit correctly, which can leave around unwanted locks and files.
But good that it finished without problem the second time. If it happens again, you can post the task log and /var/log/syslog here and I can try to see if there's any issues there.
 
  • Like
Reactions: exploradorgt
I would only use kill -9 PID as a final step, in case there is no other way to stop a process, because SIGKILL gives the process no opportunity to clean up and exit correctly, which can leave around unwanted locks and files.
But good that it finished without problem the second time. If it happens again, you can post the task log and /var/log/syslog here and I can try to see if there's any issues there.
Thank you for your help, I will posted the log the next time if continues that issue.
 
Could you post the output from the task itself also? It can be found in the GUI under<nodename> -> Task History or /var/log/vzdump/<vm/ct>.log.
Is your instance of Proxmox Backup Server local or in a remote location?
What kind of storage is the backup server using for this datastore?
 
Could you post the output from the task itself also? It can be found in the GUI under<nodename> -> Task History or /var/log/vzdump/<vm/ct>.log.
Is your instance of Proxmox Backup Server local or in a remote location?
What kind of storage is the backup server using for this datastore?
Thank you but that happened on Friday in the morning were made 2 more backups, you will not be able to see the log of that day

root@senacyt1:/var/log/vzdump# cat lxc-1016.log
2021-04-12 00:19:22 INFO: Starting Backup of VM 1016 (lxc)
2021-04-12 00:19:22 INFO: status = running
2021-04-12 00:19:22 INFO: CT Name: devjasper
2021-04-12 00:19:22 INFO: backup mode: snapshot
2021-04-12 00:19:22 INFO: ionice priority: 7
2021-04-12 00:19:22 INFO: create storage snapshot 'vzdump'
2021-04-12 00:19:23 INFO: creating archive '/var/lib/vz/dump/vzdump-lxc-1016-2021_04_12-00_19_22.tar.lzo'
2021-04-12 00:23:21 INFO: Total bytes written: 5706741760 (5.4GiB, 23MiB/s)
2021-04-12 00:23:21 INFO: archive file size: 4.12GB
2021-04-12 00:23:21 INFO: delete old backup '/var/lib/vz/dump/vzdump-lxc-1016-2021_04_10-00_21_45.tar.lzo'
2021-04-12 00:23:22 INFO: remove vzdump snapshot
2021-04-12 00:23:22 INFO: Finished Backup of VM 1016 (00:04:00)
 
The backup log that you posted doesn't seem to show any issues. Did this particular backup also lock up your system?

Today it happened again, this is what I see in the log.
In the system log that you posted, there is no mention of the backup job for ct1016 finishing. A log from an occurrence where the job never finishes could be more helpful. Double clicking the running task in the Task log will show this.
Could you provide some more information on your system and the container which is causing the problems?
pveversion -v
cat /etc/pve/lxc/1016.conf
Which kind of storage you are making backups to and is it remote or local?
 
Sorry, you asked me the type of backup, this is done locally on that node. The version is:

proxmox-ve: 6.1-2 (running kernel: 5.3.10-1-pve)
pve-manager: 6.1-3 (running version: 6.1-3/37248ce6)
pve-kernel-5.3: 6.0-12
pve-kernel-helper: 6.0-12
pve-kernel-5.3.10-1-pve: 5.3.10-1
ceph: 14.2.6-pve1
ceph-fuse: 14.2.6-pve1
corosync: 3.0.2-pve4
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.13-pve1
libpve-access-control: 6.0-5
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-9
libpve-guest-common-perl: 3.0-3
libpve-http-server-perl: 3.0-3
libpve-storage-perl: 6.1-2
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve3
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-1
pve-cluster: 6.1-2
pve-container: 3.0-14
pve-docs: 6.1-3
pve-edk2-firmware: 2.20191002-1
pve-firewall: 4.0-9
pve-firmware: 3.0-4
pve-ha-manager: 3.0-8
pve-i18n: 2.0-3
pve-qemu-kvm: 4.1.1-2
pve-xtermjs: 3.13.2-1
qemu-server: 6.1-2
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.2-pve2

~# cat /etc/pve/lxc/1016.conf
arch: amd64
cores: 2
memory: 4096
onboot: 1
ostype: ubuntu
rootfs: local-lvm:vm-1016-disk-0,size=40G
swap: 2048

This has already happened 2 times in this node, but last time it did not respond to any commands and the waiting time was extended so I had to restart the server.

Error task:


INFO: starting new backup job: vzdump --node senacyt1 --mailto lparedes@senacyt.gob.gt --quiet 1 --all 1 --mode snapshot --compress lzo --storage local --mailnotification always
INFO: Starting Backup of VM 1013 (lxc)
INFO: Backup started at 2021-04-09 00:00:02
INFO: status = running
INFO: CT Name: devweb
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: create storage snapshot 'vzdump'
Logical volume "snap_vm-1013-disk-0_vzdump" created.
INFO: creating archive '/var/lib/vz/dump/vzdump-lxc-1013-2021_04_09-00_00_02.tar.lzo'
INFO: Total bytes written: 3579125760 (3.4GiB, 16MiB/s)
INFO: archive file size: 1.64GB
INFO: delete old backup '/var/lib/vz/dump/vzdump-lxc-1013-2021_04_07-00_00_02.tar.lzo'
INFO: remove vzdump snapshot
Logical volume "snap_vm-1013-disk-0_vzdump" successfully removed
INFO: Finished Backup of VM 1013 (00:03:47)
INFO: Backup finished at 2021-04-09 00:03:49
INFO: Starting Backup of VM 1014 (lxc)
INFO: Backup started at 2021-04-09 00:03:49
INFO: status = running
INFO: CT Name: devdb
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: create storage snapshot 'vzdump'
Logical volume "snap_vm-1014-disk-0_vzdump" created.
INFO: creating archive '/var/lib/vz/dump/vzdump-lxc-1014-2021_04_09-00_03_49.tar.lzo'
INFO: Total bytes written: 12926392320 (13GiB, 39MiB/s)
INFO: archive file size: 2.20GB
INFO: delete old backup '/var/lib/vz/dump/vzdump-lxc-1014-2021_04_07-00_03_40.tar.lzo'
INFO: remove vzdump snapshot
Logical volume "snap_vm-1014-disk-0_vzdump" successfully removed
INFO: Finished Backup of VM 1014 (00:05:20)
INFO: Backup finished at 2021-04-09 00:09:09
INFO: Starting Backup of VM 1015 (lxc)
INFO: Backup started at 2021-04-09 00:09:09
INFO: status = running
INFO: CT Name: devmongo
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: create storage snapshot 'vzdump'
Logical volume "snap_vm-1015-disk-0_vzdump" created.
INFO: creating archive '/var/lib/vz/dump/vzdump-lxc-1015-2021_04_09-00_09_09.tar.lzo'
INFO: Total bytes written: 21911316480 (21GiB, 37MiB/s)
INFO: archive file size: 18.62GB
INFO: delete old backup '/var/lib/vz/dump/vzdump-lxc-1015-2021_04_07-00_09_14.tar.lzo'
INFO: remove vzdump snapshot
Logical volume "snap_vm-1015-disk-0_vzdump" successfully removed
INFO: Finished Backup of VM 1015 (00:09:31)
INFO: Backup finished at 2021-04-09 00:18:40
INFO: Starting Backup of VM 1016 (lxc)
INFO: Backup started at 2021-04-09 00:18:40
INFO: status = running
INFO: CT Name: devjasper
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: create storage snapshot 'vzdump'
Logical volume "snap_vm-1016-disk-0_vzdump" created.
INFO: creating archive '/var/lib/vz/dump/vzdump-lxc-1016-2021_04_09-00_18_40.tar.lzo'
INFO: Total bytes written: 5706168320 (5.4GiB, 23MiB/s)
INFO: archive file size: 4.12GB
INFO: delete old backup '/var/lib/vz/dump/vzdump-lxc-1016-2021_04_07-00_18_22.tar.lzo'
 
Last edited:
Unfortunately, I can see no obvious issues in any of the details you provided. Could you try updating your systems to the latest available version and see if the problem persists?
 
Unfortunately, I can see no obvious issues in any of the details you provided. Could you try updating your systems to the latest available version and see if the problem persists?
Thank you for your help, I do your recommedation.
 

About

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!