Task result "Unknown" for daily task "Update package database"

Nov 29, 2024
26
23
3
Hi,

my newly installed PBS 8.3.3 shows the result "Unknown" for the daily Update package database task. There is not output in the task output window, and the status is:

Bildschirmfoto 2025-03-19 um 08.58.32.png

When I update the package database in the GUI, everything works just fine. The syslog for the daily update looks good, too:

Code:
Mar 19 03:38:04 pbs-ota01 systemd[1]: Starting proxmox-backup-daily-update.service - Daily Proxmox Backup Server update and maintenance activities...
Mar 19 03:38:04 pbs-ota01 proxmox-daily-update[62876]: starting apt-get update
Mar 19 03:38:08 pbs-ota01 proxmox-daily-update[62876]: Get:1 http://security.debian.org bookworm-security InRelease [48.0 kB]
Hit:2 http://ftp.de.debian.org/debian bookworm InRelease
Hit:3 http://download.proxmox.com/debian/pbs bookworm InRelease
Get:4 http://ftp.de.debian.org/debian bookworm-updates InRelease [55.4 kB]
Fetched 103 kB in 2s (50.7 kB/s)
Reading package lists...
Mar 19 03:38:08 pbs-ota01 proxmox-daily-update[62876]: Certificate does not expire within the next 30 days, not renewing.
Mar 19 03:38:08 pbs-ota01 systemd[1]: proxmox-backup-daily-update.service: Deactivated successfully.
Mar 19 03:38:08 pbs-ota01 systemd[1]: Finished proxmox-backup-daily-update.service - Daily Proxmox Backup Server update and maintenance activities.
Mar 19 03:38:08 pbs-ota01 systemd[1]: proxmox-backup-daily-update.service: Consumed 3.112s CPU time.

It's not a big issue, but I have set up a Nagios check for task errors, and so that came up.

Cheers, Andreas
 
Hi Chris, thanks for the fast reply. I'm looking forward to the patch and will exclude "unknown" from my Nagios tests in the meantime.

Keep up the good work on PBS!
 
Last edited:
Hey @alietz, I’ve run into something similar before—when a scheduled task shows “unknown,” it’s usually because something blocked it from starting or finishing properly. It could be as simple as the system not having internet access, or DNS settings being off. I'd suggest checking your /etc/resolv.conf to make sure DNS is set correctly, and maybe try running apt update manually in the terminal to see if anything pops up. That often gives a clearer idea of what’s going wrong. If everything looks fine there, have a look at the logs with journalctl—they can be super helpful. Hope it’s something simple and easy to fix! Let us know how it goes.
 
  • Like
Reactions: alietz