[SOLVED] pve-manager not installed dpkg error proxmox v 7.0-2 [SOLVED]

E

egeuens

Member
Nov 3, 2021
7
2
8
58
Dear all
I have a running proxmox 7.0-2 node where pve-manager is not running. I did an distr-upgrade without succes.

My config is limited to 1 host (2 x intel xeon) with 64 gb of ram

herewith the full system report. Can you help me to get pve-manager installed?
Thank you
Erwin
 

Attachments

Hello,

Please try apt update && apt dist-upgrade if that not help, please try apt install pve-manager
 
Hi Moayad,
thx for your suggestions

apt update && apt dist-upgrade gave an error:

Reading package lists... Done
Building dependency tree... Done
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] y
Setting up pve-manager (7.0-11) ...
Job for pvedaemon.service failed.
See "systemctl status pvedaemon.service" and "journalctl -xe" for details.
dpkg: error processing package pve-manager (--configure):
installed pve-manager package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
pve-manager
E: Sub-process /usr/bin/dpkg returned an error code (1)


apt install pve-manager also:
root@pve:~# apt install pve-manager
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
pve-manager is already the newest version (7.0-11).
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] y
Setting up pve-manager (7.0-11) ...
Job for pvedaemon.service failed.
See "systemctl status pvedaemon.service" and "journalctl -xe" for details.
dpkg: error processing package pve-manager (--configure):
installed pve-manager package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
pve-manager
E: Sub-process /usr/bin/dpkg returned an error code (1)


any other idea?
 
I did an
systemctl status pvedaemon.service


pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2021-10-11 18:17:01 CEST; 3 weeks 1 days ago
Process: 3411089 ExecReload=/usr/bin/pvedaemon restart (code=exited, status=255/EXCEPTION)
Main PID: 1797 (pvedaemon)
Tasks: 8 (limit: 77150)
Memory: 422.3M
CPU: 25min 1.922s
CGroup: /system.slice/pvedaemon.service
├─ 1797 pvedaemon
├─2756277 pvedaemon worker
├─3349714 pvedaemon worker
├─3359047 pvedaemon worker
├─3372895 task UPID:pve:0033775F:0BBCB203:61826EE7:vncshell::root@pam:
├─3372896 /usr/bin/termproxy 5900 --path /nodes/pve --perm Sys.Console -- /usr/bin/pveupgrade --shell
├─3372900 /usr/bin/perl /usr/bin/pveupgrade --shell
└─3373021 /bin/bash -l

Nov 03 13:24:40 pve systemd[1]: Reloading PVE API Daemon.
Nov 03 13:24:46 pve pvedaemon[3410564]: start failed - can't acquire lock '/var/run/pvedaemon.pid.lock' - Resource temporarily unavailable
Nov 03 13:24:46 pve pvedaemon[3410564]: start failed - can't acquire lock '/var/run/pvedaemon.pid.lock' - Resource temporarily unavailable
Nov 03 13:24:46 pve systemd[1]: pvedaemon.service: Control process exited, code=exited, status=255/EXCEPTION
Nov 03 13:24:46 pve systemd[1]: Reload failed for PVE API Daemon.
Nov 03 13:25:20 pve systemd[1]: Reloading PVE API Daemon.
Nov 03 13:25:26 pve pvedaemon[3411089]: start failed - can't acquire lock '/var/run/pvedaemon.pid.lock' - Resource temporarily unavailable
Nov 03 13:25:26 pve pvedaemon[3411089]: start failed - can't acquire lock '/var/run/pvedaemon.pid.lock' - Resource temporarily unavailable
Nov 03 13:25:26 pve systemd[1]: pvedaemon.service: Control process exited, code=exited, status=255/EXCEPTION
Nov 03 13:25:26 pve systemd[1]: Reload failed for PVE API Daemon.
 
I found a solution.

I stopped the pvedaemon with systemctl stop pvedaemon.service
then I installed pve-managert with apt install pve-manager
and restarted the daemon

it seemed to work now:

root@pve:/var/run# systemctl status pvedaemon.service
● pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2021-11-03 13:30:17 CET; 4s ago
Process: 3413817 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS)
Main PID: 3413818 (pvedaemon)
Tasks: 4 (limit: 77150)
Memory: 127.3M
CPU: 1.417s
CGroup: /system.slice/pvedaemon.service
├─3413818 pvedaemon
├─3413819 pvedaemon worker
├─3413820 pvedaemon worker
└─3413821 pvedaemon worker

Nov 03 13:30:15 pve systemd[1]: Starting PVE API Daemon...
Nov 03 13:30:17 pve pvedaemon[3413818]: starting server
Nov 03 13:30:17 pve pvedaemon[3413818]: starting 3 worker(s)
Nov 03 13:30:17 pve pvedaemon[3413818]: worker 3413819 started
Nov 03 13:30:17 pve pvedaemon[3413818]: worker 3413820 started
Nov 03 13:30:17 pve pvedaemon[3413818]: worker 3413821 started
Nov 03 13:30:17 pve systemd[1]: Started PVE API Daemon.

and in the report it is now showing up:

==== general system info ==== # hostname pve # pveversion --verbose proxmox-ve: 7.0-2 (running kernel: 5.11.22-5-pve) pve-manager: 7.0-11 (running version: 7.0-11/63d82f4e) pve-kernel-helper: 7.1-2 pve-kernel-5.11: 7.0-8 pve-kernel-5.11.22-5-pve: 5.11.22-10 pve-kernel-5.11.22-4-pve: 5.11.22-9 pve-kernel-5.11.22-1-pve: 5.11.22-2

Thx all. I can close this topic now.
 
  • Like
Reactions: talistech
You must log in or register to reply here.
Top Bottom