Salutations,
I am running Proxmox Backup Server 4.0.12 on my new server and noticed something unusual with the garbage collector task.
It shows as "running" all the time.
In the task log, everything seems fine:
However, its status never shows as finished.
Attempting to run a new task in the web UI returns an error: already running (400).
In the CLI:
The status shows:
Restarting the proxmox-backup-proxy service helps to finish the task:
However, after the next run, the task "hangs" again.
How can I fix this?
I am running Proxmox Backup Server 4.0.12 on my new server and noticed something unusual with the garbage collector task.
It shows as "running" all the time.
In the task log, everything seems fine:
Code:
2025-08-20T07:08:59+03:00: queued notification (id=9271212e-e0ed-4534-b58f-f351dff24f72)
2025-08-20T07:08:59+03:00: TASK OKHowever, its status never shows as finished.
Attempting to run a new task in the web UI returns an error: already running (400).
In the CLI:
Code:
# proxmox-backup-manager garbage-collect start bs-un
starting garbage collection on store bs-un
queued notification (id=6bae1ac5-34ff-4de5-9603-8671c2158cee)
TASK ERROR: Start GC failed - (already running/locked)
Error: task failed (status Start GC failed - (already running/locked))The status shows:
Code:
# proxmox-backup-manager garbage-collect status bs-un
┌──────────────────┬────────────────────────────────────────────────────────────────────────────────────────────┐
│ Name │ Value │
╞══════════════════╪════════════════════════════════════════════════════════════════════════════════════════════╡
│ store │ bs-un │
├──────────────────┼────────────────────────────────────────────────────────────────────────────────────────────┤
│ disk-bytes │ 23472960889567 │
├──────────────────┼────────────────────────────────────────────────────────────────────────────────────────────┤
│ disk-chunks │ 8825774 │
├──────────────────┼────────────────────────────────────────────────────────────────────────────────────────────┤
│ index-data-bytes │ 596073579579094 │
├──────────────────┼────────────────────────────────────────────────────────────────────────────────────────────┤
│ index-file-count │ 6685 │
├──────────────────┼────────────────────────────────────────────────────────────────────────────────────────────┤
│ pending-bytes │ 0 │
├──────────────────┼────────────────────────────────────────────────────────────────────────────────────────────┤
│ pending-chunks │ 0 │
├──────────────────┼────────────────────────────────────────────────────────────────────────────────────────────┤
│ removed-bad │ 0 │
├──────────────────┼────────────────────────────────────────────────────────────────────────────────────────────┤
│ removed-bytes │ 0 │
├──────────────────┼────────────────────────────────────────────────────────────────────────────────────────────┤
│ removed-chunks │ 0 │
├──────────────────┼────────────────────────────────────────────────────────────────────────────────────────────┤
│ still-bad │ 0 │
├──────────────────┼────────────────────────────────────────────────────────────────────────────────────────────┤
│ next-run │ 1755810000 │
├──────────────────┼────────────────────────────────────────────────────────────────────────────────────────────┤
│ schedule │ daily │
├──────────────────┼────────────────────────────────────────────────────────────────────────────────────────────┤
│ cache-stats │ {"hits":132544204,"misses":9078023} │
├──────────────────┼────────────────────────────────────────────────────────────────────────────────────────────┤
│ upid │ UPID:srv-back-un:00000864:000003C2:0000002A:68A4E5D0:garbage_collection:bs\x2dun:root@pam: │
└──────────────────┴────────────────────────────────────────────────────────────────────────────────────────────┘Restarting the proxmox-backup-proxy service helps to finish the task:
Code:
# systemctl restart proxmox-backup-proxyHowever, after the next run, the task "hangs" again.
How can I fix this?
Last edited: