Can not update Proxmox after choose wrong Repository (Debian buster instead stretch )

K

kotakomputer

Renowned Member
May 14, 2012
461
17
83
Jakarta, Indonesia
www.komputerindo.com
Using Proxmox 5.4-3, I accidentally use:

Code: 
deb http://download.proxmox.com/debian/pve buster pve-no-subscription

Then update failed #at apt dist-upgrade then I change it to:

Code: 
deb http://download.proxmox.com/debian/pve stretch  pve-no-subscription

Try to clean apt database then update/upgrade again:

Code: 
apt-get clean
cd /var/lib/apt
mv lists lists.old
mkdir -p lists/partial
apt-get update
apt-get upgrade

Errors as shown:

Code: 
# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up pve-manager (5.4-15) ...
Job for pvedaemon.service failed because the control process exited with error code.
See "systemctl status pvedaemon.service" and "journalctl -xe" for details.
dpkg: error processing package pve-manager (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 pve-manager
E: Sub-process /usr/bin/dpkg returned an error code (1)
#

Result of systemctl status pvedaemon.service:

Code: 
# systemctl status pvedaemon.service
● pvedaemon.service - PVE API Daemon
   Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
   Active: active (running) (Result: exit-code) since Mon 2021-06-14 16:16:51 WIB; 2 weeks 0 days ago
  Process: 48422 ExecReload=/usr/bin/pvedaemon restart (code=exited, status=255)
 Main PID: 2648 (pvedaemon)
    Tasks: 4 (limit: 7372)
   Memory: 533.5M
      CPU: 16min 51.734s
   CGroup: /system.slice/pvedaemon.service
           ├─ 2648 pvedaemon
           ├─ 7887 pvedaemon worker
           ├─29711 pvedaemon worker
           └─32885 pvedaemon worker

Jun 29 00:44:02 ids-801 pvedaemon[48422]: Compilation failed in require at /usr/share/perl5/PVE/API2/Cluster.pm line 17.
Jun 29 00:44:02 ids-801 pvedaemon[48422]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 17.
Jun 29 00:44:02 ids-801 pvedaemon[48422]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13.
Jun 29 00:44:02 ids-801 pvedaemon[48422]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13.
Jun 29 00:44:02 ids-801 pvedaemon[48422]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Jun 29 00:44:02 ids-801 pvedaemon[48422]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Jun 29 00:44:02 ids-801 pvedaemon[48422]: Compilation failed in require at /usr/bin/pvedaemon line 11.
Jun 29 00:44:02 ids-801 pvedaemon[48422]: BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 11.
Jun 29 00:44:02 ids-801 systemd[1]: pvedaemon.service: Control process exited, code=exited status=255
Jun 29 00:44:02 ids-801 systemd[1]: Reload failed for PVE API Daemon.
#

Any tip to solve above issue?
 
You must log in or register to reply here.
Top Bottom