help for - pve-manager.service start failed

[DenLucky]

systemctl status pve-manager
● pve-manager.service - PVE VM Manager
Loaded: loaded (/lib/systemd/system/pve-manager.service; enabled)
Active: failed (Result: exit-code) since Wed 2016-12-14 15:19:17 EET; 17min ago
Process: 1006 ExecStart=/usr/bin/pvesh --nooutput create /nodes/localhost/startall (code=exited, status=12)
Main PID: 1006 (code=exited, status=12)

Dec 14 15:19:17 vmohp55 systemd[1]: Starting PVE VM Manager...
Dec 14 15:19:17 vmohp55 systemd[1]: pve-manager.service: main process exited, code=exited, status=12/n/a
Dec 14 15:19:17 vmohp55 systemd[1]: Failed to start PVE VM Manager.
Dec 14 15:19:17 vmohp55 systemd[1]: Unit pve-manager.service entered failed state.
________________
root@vmohp55:~# apt-get update
Reading package lists... Done
root@vmohp55:~# apt-get dist-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.
_________________
root@vmohp55:~# uname -a && cat /etc/os-release
Linux vmohp55 4.4.35-1-pve #1 SMP Fri Dec 9 11:09:55 CET 2016 x86_64 GNU/Linux
PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
NAME="Debian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
_________________
root@vmohp55:~# pveversion -v
proxmox-ve: 4.4-76 (running kernel: 4.4.35-1-pve)
pve-manager: 4.4-1 (running version: 4.4-1/eb2d6f1e)
pve-kernel-4.4.35-1-pve: 4.4.35-76
pve-kernel-4.4.8-1-pve: 4.4.8-52
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-48
qemu-server: 4.0-101
pve-firmware: 1.1-10
libpve-common-perl: 4.0-83
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-70
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-docs: 4.4-1
pve-qemu-kvm: 2.7.0-9
pve-container: 1.0-88
pve-firewall: 2.0-33
pve-ha-manager: 1.0-38
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.6-2
lxcfs: 2.0.5-pve1
criu: 1.6.0-1
novnc-pve: 0.5-8
smartmontools: 6.5+svn4324-1~pve80

how i can start pve-manager.service?

 

[wolfgang]

Hi,

can you send the output of

journalctl -u pve-manager.service

 

[DenLucky]

root@vmohp55:~# journalctl -u pve-manager.service
-- Logs begin at Wed 2016-12-14 15:19:09 EET, end at Wed 2016-12-14 16:09:59 EET. --
Dec 14 15:19:17 vmohp55 systemd[1]: Starting PVE VM Manager...
Dec 14 15:19:17 vmohp55 systemd[1]: pve-manager.service: main process exited, code=exited, status=12/n/a
Dec 14 15:19:17 vmohp55 systemd[1]: Failed to start PVE VM Manager.
Dec 14 15:19:17 vmohp55 systemd[1]: Unit pve-manager.service entered failed state.
Dec 14 15:37:19 vmohp55 systemd[1]: Starting PVE VM Manager...
Dec 14 15:37:19 vmohp55 systemd[1]: pve-manager.service: main process exited, code=exited, status=12/n/a
Dec 14 15:37:19 vmohp55 systemd[1]: Failed to start PVE VM Manager.
Dec 14 15:37:19 vmohp55 systemd[1]: Unit pve-manager.service entered failed state.
Dec 14 15:37:33 vmohp55 systemd[1]: Starting PVE VM Manager...
Dec 14 15:37:33 vmohp55 systemd[1]: pve-manager.service: main process exited, code=exited, status=12/n/a
Dec 14 15:37:33 vmohp55 systemd[1]: Failed to start PVE VM Manager.
Dec 14 15:37:33 vmohp55 systemd[1]: Unit pve-manager.service entered failed state.
Dec 14 15:43:59 vmohp55 systemd[1]: Starting PVE VM Manager...
Dec 14 15:44:00 vmohp55 systemd[1]: pve-manager.service: main process exited, code=exited, status=12/n/a
Dec 14 15:44:00 vmohp55 systemd[1]: Failed to start PVE VM Manager.
Dec 14 15:44:00 vmohp55 systemd[1]: Unit pve-manager.service entered failed state.

 

[DenLucky]

perhaps the reason for this?

root@vmohp55:~# systemctl status pveproxy.service
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled)
Active: failed (Result: exit-code) since Thu 2016-12-15 17:51:16 EET; 3min 18s ago
Process: 988 ExecStart=/usr/bin/pveproxy start (code=exited, status=255)

Dec 15 17:51:14 vmohp55 systemd[1]: Starting PVE API Proxy Server...
Dec 15 17:51:16 vmohp55 pveproxy[988]: start failed - can't put server into background - fork failed at /usr/share/perl5/PVE/Daemon.pm line 331.
Dec 15 17:51:16 vmohp55 pveproxy[988]: start failed - can't put server into background - fork failed at /usr/share/perl5/PVE/Daemon.pm line 331.
Dec 15 17:51:16 vmohp55 systemd[1]: pveproxy.service: control process exited, code=exited status=255
Dec 15 17:51:16 vmohp55 systemd[1]: Failed to start PVE API Proxy Server.
Dec 15 17:51:16 vmohp55 systemd[1]: Unit pveproxy.service entered failed state.

 

[multi]

perhaps the reason for this?

You solved your problem, I have an identical error. Installing on top of debian 8.7.1