[SOLVED] restore task running without task log

I

Ivar418

Member
Oct 24, 2022
6
1
8
I'm running a live restore from a local Proxmox backup server of a bout 5 tb of data.

It's been running for about a day and a half now and since it's been running a day the progress log or item in the task bar has disappeared.
I noticed that all other previous tasks disappeared.

I'm kinda curious how far the restore is, but to my knowledge there is no other way to see it.

I still see the task running in Proxmox backup server, but that does not tell me how far it is.

Anyone any idea where I can look at the progress without restarting the restore?

Im running the following packages for proxmox:
proxmox-ve: 7.3-1 (running kernel: 5.15.85-1-pve)
pve-manager: 7.3-6 (running version: 7.3-6/723bb6ec)
pve-kernel-helper: 7.3-3
pve-kernel-5.15: 7.3-2
pve-kernel-5.15.85-1-pve: 5.15.85-1
pve-kernel-5.15.74-1-pve: 5.15.74-1
ceph-fuse: 15.2.17-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.3
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.3-1
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.3-2
libpve-guest-common-perl: 4.2-3
libpve-http-server-perl: 4.1-5
libpve-storage-perl: 7.3-2
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-1
lxcfs: 5.0.3-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.3.2-1
proxmox-backup-file-restore: 2.3.2-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.5
pve-cluster: 7.3-2
pve-container: 4.4-2
pve-docs: 7.3-1
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-7
pve-firmware: 3.6-3
pve-ha-manager: 3.5.1
pve-i18n: 2.8-2
pve-qemu-kvm: 7.1.0-4
pve-xtermjs: 4.16.0-1
qemu-server: 7.3-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+2
vncterm: 1.7-1
zfsutils-linux: 2.1.9-pve1
 
Hi, can you check if you can still see the active task in /var/log/pve/tasks/active? Its task type should be qmrestore, so the following command should find it:
Code: 
grep qmrestore /var/log/pve/tasks/active
The first column displays the task's "UPID", which is an internal task identifier. You could then use the UPID and find to locate the corresponding logfile:
Code: 
find /var/log/pve/tasks -name UPID:pve1:...:...:...:qmrestore:...:...
And finally print its current contents:
Code: 
cat /var/log/pve/tasks/1/...
Hope that helps!
 
  • Like
Reactions: Ivar418
fweber said:
Hi, can you check if you can still see the active task in /var/log/pve/tasks/active? Its task type should be qmrestore, so the following command should find it:
Code: 
grep qmrestore /var/log/pve/tasks/active
The first column displays the task's "UPID", which is an internal task identifier. You could then use the UPID and find to locate the corresponding logfile:
Code: 
find /var/log/pve/tasks -name UPID:pve1:...:...:...:qmrestore:...:...
And finally print its current contents:
Code: 
cat /var/log/pve/tasks/1/...
Hope that helps!
Click to expand...
Thank you for the reply.

In the meantime the task has ended successfully so I no longer need to check it. Perhaps someone else will find this usefull in the future
 
  • Like
Reactions: fweber
@fweber

FYI, I just had the same issue, a restore task was running but was not visible in the GUI. Thank you for these instructions, I was able to check the state

no visible via API
Code: 
root@mercury:/var/log/pve/tasks# pvesh  ls /nodes/mercury/tasks | grep restore
root@mercury:/var/log/pve/tasks#


but visible on host
Code: 
grep restore /var/log/pve/tasks/active
UPID:mercury:00117B8C:0EB99E79:65949842:qmrestore:999:root@pam: 0


=> Let me know if I can assist in reproducing anything, or if I should report a bug. Otherwise I will leave this topic be.

Code: 
proxmox-ve: 8.0.2 (running kernel: 6.2.16-10-pve)
pve-manager: 8.0.4 (running version: 8.0.4/d258a813cfa6b390)
proxmox-kernel-helper: 8.0.3
proxmox-kernel-6.2.16-10-pve: 6.2.16-10
proxmox-kernel-6.2: 6.2.16-10
ceph-fuse: 16.2.11+ds-2
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown: residual config
ifupdown2: 3.2.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.25-pve1
libproxmox-acme-perl: 1.4.6
libproxmox-backup-qemu0: 1.4.0
libproxmox-rs-perl: 0.3.1
libpve-access-control: 8.0.4
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.0.7
libpve-guest-common-perl: 5.0.4
libpve-http-server-perl: 5.0.4
libpve-rs-perl: 0.8.5
libpve-storage-perl: 8.0.2
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve3
novnc-pve: 1.4.0-2
proxmox-backup-client: 3.0.2-1
proxmox-backup-file-restore: 3.0.2-1
proxmox-kernel-helper: 8.0.3
proxmox-mail-forward: 0.2.0
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.2
proxmox-widget-toolkit: 4.0.6
pve-cluster: 8.0.3
pve-container: 5.0.4
pve-docs: 8.0.4
pve-edk2-firmware: 3.20230228-4
pve-firewall: 5.0.3
pve-firmware: 3.7-1
pve-ha-manager: 4.0.2
pve-i18n: 3.0.5
pve-qemu-kvm: 8.0.2-4
pve-xtermjs: 4.16.0-3
pve-zsync: 2.3.0
qemu-server: 8.0.6
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.1.12-pve1
 
Why not implement a button in the gui to get the task log screen back, if it's stil active?
Allready found it, doubleklik on running task at tasks below.
closed.
 
Last edited:
You must log in or register to reply here.
Top Bottom