Can't load RADOS for module PVE::RADOS, GUI and CLI tools fail

CheesyPete

Member
Sep 14, 2020
13
3
23
24
Hello, my proxmox server has been running happily for a few months since last reboot. I tried to run a new container and got this message:
Code:
Can't load '/usr/lib/x86_64-linux-gnu/perl5/5.36/auto/PVE/RADOS/RADOS.so' for module PVE::RADOS: libboost_iostreams.so.1.74.0: cannot open shared object file: No such file or directory at /usr/lib/x86_64-linux-gnu/perl-base/DynaLoader.pm line 201, <DATA> line 960.
 at /usr/share/perl5/PVE/Storage/RBDPlugin.pm line 16.
Compilation failed in require at /usr/share/perl5/PVE/Storage/RBDPlugin.pm line 16, <DATA> line 960.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Storage/RBDPlugin.pm line 16, <DATA> line 960.
Compilation failed in require at /usr/share/perl5/PVE/Storage.pm line 34, <DATA> line 960.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Storage.pm line 34, <DATA> line 960.
Compilation failed in require at /usr/share/perl5/PVE/GuestHelpers.pm line 8, <DATA> line 960.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/GuestHelpers.pm line 8, <DATA> line 960.
Compilation failed in require at /usr/share/perl5/PVE/CLI/pct.pm line 14, <DATA> line 960.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/CLI/pct.pm line 14, <DATA> line 960.
Compilation failed in require at /usr/sbin/pct line 6, <DATA> line 960.
BEGIN failed--compilation aborted at /usr/sbin/pct line 6, <DATA> line 960.
After a restart, nothing 'proxmox' works. The server boots fine and I can ssh into it, but there is no GUI, trying to restart pveproxy.service and pvedaemon.service or even trying pct list gives the same error and journalctl -b -u pvedaemon.service is littered with the same error again.

I have tried:
  • Updating packages
  • Reinstalling librados2
  • Reinstalling qemu-server
  • Reinstalling pve-ha-manager
  • Removing all zfs pools
  • Disabling my NFS exports
Version:
Code:
root@pve:~# pveversion
pve-manager/8.3.2/3e76eec21c4a14a7 (running kernel: 6.8.12-5-pve)

Is it that something has updated while it has been running and has broken? I only found the error while trying to run a container, so it could have been an issue for a while?
Any help is much appreciated, let me know if there is more information needed or I anything for me to try.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!