[SOLVED] Problem with dependencies after remove ceph-common and ceph-fuse

fritzschmale

New Member
Oct 24, 2023
7
2
3
root@pve3:/# apt-get install --reinstall proxmox-ve
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
ceph-common : Depends: librbd1 (= 16.2.11+ds-2) but 17.2.6-pve1+3 is to be installed
Depends: python3-ceph-argparse (= 16.2.11+ds-2) but 17.2.6-pve1+3 is to be installed
Depends: python3-ceph-common (< 16.2.11+ds-2.1~) but 17.2.6-pve1+3 is to be installed
Depends: python3-cephfs (= 16.2.11+ds-2) but 17.2.6-pve1+3 is to be installed
Depends: python3-rados (= 16.2.11+ds-2) but 17.2.6-pve1+3 is to be installed
Depends: python3-rbd (= 16.2.11+ds-2) but 17.2.6-pve1+3 is to be installed
E: Unable to correct problems, you have held broken packages.

root@pve3:/# apt --fix-broken install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
libjs-sencha-touch liburing2 proxmox-default-kernel
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

I install this packages:
librbd1 (= 16.2.11+ds-2)
python3-ceph-argparse (= 16.2.11+ds-2)
python3-ceph-common (< 16.2.11+ds-2.1~)
python3-cephfs (= 16.2.11+ds-2)
python3-rados (= 16.2.11+ds-2)
python3-rbd (= 16.2.11+ds-2)

but it won't work.

The following Config Files exists after I use "apt --fix-broken install":

PVE Node Configuration: Location: /etc/pve/nodes/...
PVE Cluster Configuration:
pvecm Configuration: /etc/pve/corosync.conf
Network Configuration: Location: /etc/network/interfaces
PVE Datacenter Configuration: Location: /etc/pve/datacenter.cfg
Storage Configuration: Location: /etc/pve/storage.cfg
No Subscription Warning: Location: /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js
Web Interface Configuration: Location: /etc/default/pveproxy
Web Interface Log: /var/log/pveproxy/access.log

Since all essential configuration files are present, I likely haven't lost my configuration.
 
Last edited:
Using apt-get to download specific Ceph versions; encountered issues with 'libjaeger' package and 'python3-cherrypy3' version. Ignored invalid file extension:

apt-get download ceph-base=16.2.11+ds-2 ceph-mgr=16.2.11+ds-2 ceph-osd=16.2.11+ds-2 librados2=16.2.11+ds-2 librgw2=16.2.11+ds-2 python3-ceph-common=16.2.11+ds-2 python3-rgw=16.2.11+ds-2 ceph-common=16.2.11+ds-2 ceph-mgr-modules-core=16.2.11+ds-2 libcephfs2=16.2.11+ds-2 libradosstriper1=16.2.11+ds-2 python3-cephfs=16.2.11+ds-2 python3-rados=16.2.11+ds-2 ceph-mds=16.2.11+ds-2 ceph-mon=16.2.11+ds-2 libjaeger=16.2.11+ds-2 librbd1=16.2.11+ds-2 python3-ceph-argparse=16.2.11+ds-2 python3-cherrypy3=8.9.1-8 python3-rbd=16.2.11+ds-2
N: Ignoring file 'pve-enterprise.list.backup' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
E: Unable to locate package libjaeger
E: Version '8.9.1-8' for 'python3-cherrypy3' was not found
 
Last edited:
Now after ceph reinstall "apt full-upgrade" does this:

root@pve3:~# apt full-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
libjs-sencha-touch liburing2 proxmox-default-kernel
Use 'apt autoremove' to remove them.
The following NEW packages will be installed:
proxmox-kernel-6.2.16-18-pve
The following packages will be upgraded:
libknet1 libnozzle1 libssl3 openssl proxmox-kernel-6.2 pve-firmware
6 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/182 MB of archives.
After this operation, 572 MB of additional disk space will be used.
N: Ignoring file 'pve-enterprise.list.backup' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
Do you want to continue? [Y/n] Y
/bin/sh: 1: /usr/share/proxmox-ve/pve-apt-hook: not found
E: Sub-process /usr/share/proxmox-ve/pve-apt-hook returned an error code (127)
E: Failure running script /usr/share/proxmox-ve/pve-apt-hook

And "apt-get install --reinstall proxmox-ve" didn't change
 
Last edited:
My Solution:

Proxmox-Version:

Proxmox Virtual Environment 8.0.4

Problem:
After deleting the packages ceph-common and ceph-fuse, issues with missing dependencies arose. To resolve this problem, I created the file "touch /please-remove-proxmox-ve". This file serves as an instruction to remove Proxmox VE. However, the command "apt purge proxmox-ve" failed due to the missing dependencies.

Solution:
To address Proxmox VE issues, edit the /etc/apt/apt.conf.d/10pveapthook configuration file. Comment out lines referencing pve-apt-hook by adding a '#'. After, the file resembles commented pve-apt-hook lines. Save and exit. Execute commands to reconfigure DPKG, fix broken packages, and upgrade. Check dependencies, noting mismatches. Manually install dependencies for each package. Reinstall Proxmox, then reset the configuration file. Reactivate commented lines by removing the '#' to restore the file. Save and exit. This ensures Proxmox's efficient functioning.

  1. Edit the configuration file:
    Open the configuration file with nano or your preferred text editor:

    nano /etc/apt/apt.conf.d/10pveapthook

  2. Comment out the relevant lines:
    Add a # at the beginning of each of the lines referencing pve-apt-hook. The file should look something like this after you've commented out the relevant lines in 10pveapthook File:
    #DPkg::pre-Install-Pkgs { "/usr/share/proxmox-ve/pve-apt-hook"; };
    #DPkg::Tools::Options::/usr/share/proxmox-ve/pve-apt-hook "";
    #DPkg::Tools::Options::/usr/share/proxmox-ve/pve-apt-hook::Version "2";
    #DPkg::Tools::Options::/usr/share/proxmox-ve/pve-apt-hook::InfoFD "20";

  3. Save and exit:
    If using nano, you can save the file by pressing CTRL + O, then press Enter, and exit with CTRL + X.

  4. Thank God the following commands worked:

    a) Reconfigure DPKG:
    dpkg --configure -a
    b) Try to Fix Broken Packages: apt-get --fix-broken install

  5. Run a Full Upgrade:
    apt full-upgrade (works now!)

  6. Check all Dependencies:
    apt-get install librbd1=16.2.11+ds-2
    return:
    The following packages have unmet dependencies:
    librbd1 : Depends: librados2 (= 16.2.11+ds-2) but 17.2.6-pve1+3 is to be installed
    now you must install the dependencies for librbd1:
    apt-get install librados2=16.2.11+ds-2

    When you install all the dependencies for all packages it looks like:
    apt-get install librbd1=16.2.11+ds-2
    apt-get install python3-ceph-argparse=16.2.11+ds-2
    apt-get install python3-ceph-common=16.2.11+ds-2
    apt-get install python3-cephfs=16.2.11+ds-2
    dependencies: apt-get install libcephfs2=16.2.11+ds-2
    dependencies: apt-get install python3-rados=16.2.11+ds-2
    apt-get install python3-cephfs=16.2.11+ds-2
    apt-get install python3-rbd=16.2.11+ds-2

  7. Reinstall Proxmox:
    apt-get install --reinstall proxmox-ve

  8. Reset the configuration file:

    Open the configuration file with nano or your preferred text editor:

    nano /etc/apt/apt.conf.d/10pveapthook

  9. Activate the relevant lines:
    Delete the # at the beginning of each of the lines referencing pve-apt-hook. The file should look something like this after you've reactivate the relevant lines in 10pveapthook File:
    DPkg::pre-Install-Pkgs { "/usr/share/proxmox-ve/pve-apt-hook"; };
    DPkg::Tools::Options::/usr/share/proxmox-ve/pve-apt-hook "";
    DPkg::Tools::Options::/usr/share/proxmox-ve/pve-apt-hook::Version "2";
    DPkg::Tools::Options::/usr/share/proxmox-ve/pve-apt-hook::InfoFD "20";

  10. Save and exit:

    If using nano, you can save the file by pressing CTRL + O, then press Enter, and exit with CTRL + X.
 
Last edited:
  • Like
Reactions: aait
Maybe this helps?:
https://forum.proxmox.com/threads/e...x-ve-pve-apt-hook-not-found.45436/post-220202

Disclaimer:
I can not estimate which implications this has in your/the current state...

I temporarily disabled the 10pveapthook to bypass the error:"Sub-process /usr/share/proxmox-ve/pve-apt-hook returned an error code (127)E: Failure running script /usr/share/proxmox-ve/pve-apt-hook." While it was disabled, I was able to install the missing packages and reinstall Proxmox-VE.

My Proxmox server is currently up and running again. Still, thank you very much for your response! :)

By the way, I will never uninstall important packages from my VE servers again, such as ceph-common and ceph-fuse :D
 
Last edited:
My Solution:

Proxmox-Version:

Proxmox Virtual Environment 8.0.4

Problem:
After deleting the packages ceph-common and ceph-fuse, issues with missing dependencies arose. To resolve this problem, I created the file "touch /please-remove-proxmox-ve". This file serves as an instruction to remove Proxmox VE. However, the command "apt purge proxmox-ve" failed due to the missing dependencies.

Solution:
To address Proxmox VE issues, edit the /etc/apt/apt.conf.d/10pveapthook configuration file. Comment out lines referencing pve-apt-hook by adding a '#'. After, the file resembles commented pve-apt-hook lines. Save and exit. Execute commands to reconfigure DPKG, fix broken packages, and upgrade. Check dependencies, noting mismatches. Manually install dependencies for each package. Reinstall Proxmox, then reset the configuration file. Reactivate commented lines by removing the '#' to restore the file. Save and exit. This ensures Proxmox's efficient functioning.

  1. Edit the configuration file:
    Open the configuration file with nano or your preferred text editor:

    nano /etc/apt/apt.conf.d/10pveapthook

  2. Comment out the relevant lines:
    Add a # at the beginning of each of the lines referencing pve-apt-hook. The file should look something like this after you've commented out the relevant lines in 10pveapthook File:
    #DPkg::pre-Install-Pkgs { "/usr/share/proxmox-ve/pve-apt-hook"; };
    #DPkg::Tools::Options::/usr/share/proxmox-ve/pve-apt-hook "";
    #DPkg::Tools::Options::/usr/share/proxmox-ve/pve-apt-hook::Version "2";
    #DPkg::Tools::Options::/usr/share/proxmox-ve/pve-apt-hook::InfoFD "20";

  3. Save and exit:
    If using nano, you can save the file by pressing CTRL + O, then press Enter, and exit with CTRL + X.

  4. Thank God the following commands worked:

    a) Reconfigure DPKG:
    dpkg --configure -a
    b) Try to Fix Broken Packages: apt-get --fix-broken install

  5. Run a Full Upgrade:
    apt full-upgrade (works now!)

  6. Check all Dependencies:
    apt-get install librbd1=16.2.11+ds-2
    return:
    The following packages have unmet dependencies:
    librbd1 : Depends: librados2 (= 16.2.11+ds-2) but 17.2.6-pve1+3 is to be installed
    now you must install the dependencies for librbd1:
    apt-get install librados2=16.2.11+ds-2

    When you install all the dependencies for all packages it looks like:
    apt-get install librbd1=16.2.11+ds-2
    apt-get install python3-ceph-argparse=16.2.11+ds-2
    apt-get install python3-ceph-common=16.2.11+ds-2
    apt-get install python3-cephfs=16.2.11+ds-2
    dependencies: apt-get install libcephfs2=16.2.11+ds-2
    dependencies: apt-get install python3-rados=16.2.11+ds-2
    apt-get install python3-cephfs=16.2.11+ds-2
    apt-get install python3-rbd=16.2.11+ds-2

  7. Reinstall Proxmox:
    apt-get install --reinstall proxmox-ve

  8. Reset the configuration file:

    Open the configuration file with nano or your preferred text editor:

    nano /etc/apt/apt.conf.d/10pveapthook

  9. Activate the relevant lines:
    Delete the # at the beginning of each of the lines referencing pve-apt-hook. The file should look something like this after you've reactivate the relevant lines in 10pveapthook File:
    DPkg::pre-Install-Pkgs { "/usr/share/proxmox-ve/pve-apt-hook"; };
    DPkg::Tools::Options::/usr/share/proxmox-ve/pve-apt-hook "";
    DPkg::Tools::Options::/usr/share/proxmox-ve/pve-apt-hook::Version "2";
    DPkg::Tools::Options::/usr/share/proxmox-ve/pve-apt-hook::InfoFD "20";

  10. Save and exit:

    If using nano, you can save the file by pressing CTRL + O, then press Enter, and exit with CTRL + X.
That's it, thank you for the detailed fix!
 

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!