Issue on proxmox-daily-update for PBS

[OliverW87]

Hi all,

we are running PBS 3.2.7 and getting an error at cron proxmox-daily-update.

Nov 14 08:35:24 pbs001 proxmox-daily-update[1735998]: thread 'UPID:pbs001:001A7D3E:0B938BA7:00000000:6735A838:aptupdate::root@pam:' panicked at /usr/share/cargo/registry/proxmox-notify-0.4.1/src/context/mod.rs:50:32:
Nov 14 08:35:24 pbs001 proxmox-daily-update[1735998]: context for proxmox-notify has not been set yet
Nov 14 08:35:24 pbs001 proxmox-daily-update[1735998]: TASK ERROR: worker panicked: unknown type.

there is an known issue here?

kind regards
Oliver

 

[OliverW87]

After a bit of further research i found some more informations about this.

We have an repository configured which notified in the GUI as misconfigured. But this correct.
Proxmox GUI says that the Suite name "stable" will not be correct. But thats the correct one.

When disable this repository the proxmox-daily-update will work.

curl -s https://packages.wazuh.com/key/GPG-KEY-WAZUH | gpg --no-default-keyring --keyring gnupg-ring:/usr/share/keyrings/wazuh.gpg --import && chmod 644 /usr/share/keyrings/wazuh.gpg
echo "deb [signed-by=/usr/share/keyrings/wazuh.gpg] https://packages.wazuh.com/4.x/apt/ stable main" | tee -a /etc/apt/sources.list.d/wazuh.list

 

[Chris]

Hi,
what is the output of proxmox-backup-manager version --verbose? Is the reported running version equal to the installed one?

 

[OliverW87]

Hi Chris,
jep. i'm running 3.2.7

root@pbs001:/etc/apt/sources.list.d# proxmox-backup-manager version --verbose
proxmox-backup                     3.2.0        running kernel: 6.8.12-2-pve
proxmox-backup-server              3.2.7-1      running version: 3.2.7
proxmox-kernel-helper              8.1.0
proxmox-kernel-6.8                 6.8.12-2
proxmox-kernel-6.8.12-2-pve-signed 6.8.12-2
proxmox-kernel-6.8.8-2-pve-signed  6.8.8-2
proxmox-kernel-6.5.13-6-pve-signed 6.5.13-6
proxmox-kernel-6.5                 6.5.13-6
ifupdown2                          3.2.0-1+pmx9
libjs-extjs                        7.0.0-4
proxmox-backup-docs                3.2.7-1
proxmox-backup-client              3.2.7-1
proxmox-mail-forward               0.2.3
proxmox-mini-journalreader         1.4.0
proxmox-offline-mirror-helper      0.6.7
proxmox-widget-toolkit             4.2.3
pve-xtermjs                        5.3.0-3
smartmontools                      7.3-pve1
zfsutils-linux                     2.2.6-pve1

 

[Chris]

Okay, looked at the code and this issue has already been fixed with this commit [0]. The fix is included in proxmox-backup-server version 3.2.8. Please do upgrade and see if the issue persists.

[0] https://git.proxmox.com/?p=proxmox-backup.git;a=commit;h=f629a56c4760eb2b7107618c07d69956dbe1e9f3

 

[OliverW87]

Hi Chris,

thanks for that info.

our Repo is the subscription and not non-subscription.
So we stay on 3.2.7 and it looks like no update for 3.2.8 is available.

 

[Chris]

So you could either pull in the latest upgrades just once by temporarily switching to the no-subscription repo and install version 3.2.8 (be aware of this issue 5868, which can cause you troubles if e.g. you have a uptime monitoring tool which drops the tcp connection right after a connection to the api) or you stay on the current version and check the state of the subscription and acme certs if present manually (normally handled by the daily update), until the upgrade is available to you.