[SOLVED] Verification Job duration shows 2 different times

[neon068]

EDIT: Already known bug

see https://bugzilla.proxmox.com/show_bug.cgi?id=5753 , which is basically the same issue

Not sure if this is already known, or if I'm just reading it wrong...

The verify job task Status tab shows a duration of 9h 34.7s and the actual last duration was 2m 1s as seen correctly in the Verify Jobs schedule.

I attached the output of the job log as well showing it only took 2 minutes.

Really not a big deal, but wasn't sure if I was just reading it wrong, have something configured wrong, or if it's an actual bug.

 

[neon068]

Ah I see what's going on... I checked it again and it keeps increasing in time each time I open the window. The Duration time on the Status page is checking if there's currently a PID in the system with the same Process ID still running, in this case "PID 911". Since it sees a process with a PID of 911 running, even though this isn't the actual verification job PID, it thinks that the job is still running and calculates how long it has been since the job start time and now. The real PID 911 has been running since it booted:
root 991 0.0 0.0 0 0 ? S Oct29 0:00 [z_upgrade]


I checked this out on another PBS instance, and I'm able to reproduce. This is showing a GC Job with a PID of 211 that only took 5s to run, is still running (15h and counting) in the Show Log -> Status tab of the GC task. The real PID 211 is:
root@pbs:~# ps aux | grep 211
backup 211 0.4 1.3 4236252 57036 ? Ssl Oct27 29:37 /usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-backup-proxy




So... bug? Yeah. Priority? Nah.

 

[Johannes S]

If you are it's a Bug you should report it on https://bugzilla.proxmox.com

 

[neon068]

If you are it's a Bug you should report it on https://bugzilla.proxmox.com

Thanks for the link! Will do once I get more confirmation on reproducibility and nail down exactly where all it's appearing. The task history view looks fine, but I think this only shows up if you navigate to the job results within the datastore sub-menu

 

[fabian]

see https://bugzilla.proxmox.com/show_bug.cgi?id=5753 , which is basically the same issue

 

[neon068]

see https://bugzilla.proxmox.com/show_bug.cgi?id=5753 , which is basically the same issue

Ahhh nice! I wouldn't have suspected it given the title and didn't get to start digging into inspecting the UI API calls. Thanks for the confirmation, glad it wasn't just me!