[SOLVED] cant get pveproxy to start

K

Kieeps

Member
Dec 16, 2018
19
1
6
39
seems like pveproxy just wont start.

$ pveproxy start
Failed to start pveproxy.service: Interactive authentication required.
See system logs and 'systemctl status pveproxy.service' for details.
command 'systemctl start pveproxy' failed: exit code 1

and when i run "systemctl status pveproxy.service" i get
"
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2018-12-16 20:36:11 CET; 14min ago
Process: 56815 ExecStop=/usr/bin/pveproxy stop (code=exited, status=0/SUCCESS)
Process: 56829 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
Main PID: 56846 (pveproxy)
Tasks: 4 (limit: 9830)
Memory: 118.7M
CPU: 13.539s
CGroup: /system.slice/pveproxy.service
├─ 1844 pveproxy worker
├─ 1845 pveproxy worker
├─ 1846 pveproxy worker
└─56846 pveproxy

Dec 16 20:50:26 MicroSurvur pveproxy[1819]: worker exit
Dec 16 20:50:26 MicroSurvur pveproxy[1820]: worker exit
Dec 16 20:50:26 MicroSurvur pveproxy[1844]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1647.
Dec 16 20:50:26 MicroSurvur pveproxy[56846]: worker 1819 finished
Dec 16 20:50:26 MicroSurvur pveproxy[56846]: worker 1820 finished
Dec 16 20:50:26 MicroSurvur pveproxy[56846]: starting 2 worker(s)
Dec 16 20:50:26 MicroSurvur pveproxy[56846]: worker 1845 started
Dec 16 20:50:26 MicroSurvur pveproxy[56846]: worker 1846 started
Dec 16 20:50:26 MicroSurvur pveproxy[1845]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1647.
Dec 16 20:50:26 MicroSurvur pveproxy[1846]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1647.
"

so i figured i'd just run "pvecm updadecerts" but that gives thjis:
pvecm updadecerts
ipcc_send_rec[1] failed: Connection refused
ipcc_send_rec[2] failed: Connection refused
ipcc_send_rec[3] failed: Connection refused
Unable to load access control list: Connection refused


any idea what i messed up?
 
is the service 'pve-cluster' started and healthy ?
 
No, the service wasnt even installed for some reason. and when i try to install it i get this:

$ sudo apt install pve-cluster
Reading package lists... Done
Building dependency tree
Reading state information... Done
pve-cluster is already the newest version (5.0-31).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 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.3-5) ...
Job for pvestatd.service failed because the control process exited with error code.
See "systemctl status pvestatd.service" and "journalctl -xe" for details.
pvestatd.service couldn't start.
dpkg: error processing package pve-manager (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of proxmox-ve:
proxmox-ve depends on pve-manager; however:
Package pve-manager is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
pve-manager
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)



So it seems like its more messed up then i thought :O
 
try
Code: 
apt install proxmox-ve

edit:
or the following:

Code: 
apt install --fix-broken
 
  • Like
Reactions: a26b52
sudo apt install proxmox-ve
Reading package lists... Done
Building dependency tree
Reading state information... Done
proxmox-ve is already the newest version (5.3-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 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.3-5) ...
Job for pvestatd.service failed because the control process exited with error code.
See "systemctl status pvestatd.service" and "journalctl -xe" for details.
pvestatd.service couldn't start.
dpkg: error processing package pve-manager (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of proxmox-ve:
proxmox-ve depends on pve-manager; however:
Package pve-manager is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
pve-manager
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)


--fix-broken gives the same result.

$ sudo systemctl status pvestatd.service
● pvestatd.service - PVE Status Daemon
Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2018-12-18 17:11:09 CET; 1min 46s ago
Process: 58417 ExecStart=/usr/bin/pvestatd start (code=exited, status=111)
CPU: 582ms

Dec 18 17:11:09 MicroSurvur pvestatd[58417]: ipcc_send_rec[1] failed: Connection refused
Dec 18 17:11:09 MicroSurvur pvestatd[58417]: ipcc_send_rec[2] failed: Connection refused
Dec 18 17:11:09 MicroSurvur pvestatd[58417]: ipcc_send_rec[2] failed: Connection refused
Dec 18 17:11:09 MicroSurvur pvestatd[58417]: ipcc_send_rec[3] failed: Connection refused
Dec 18 17:11:09 MicroSurvur pvestatd[58417]: ipcc_send_rec[3] failed: Connection refused
Dec 18 17:11:09 MicroSurvur pvestatd[58417]: Unable to load access control list: Connection refused
Dec 18 17:11:09 MicroSurvur systemd[1]: pvestatd.service: Control process exited, code=exited status=111
Dec 18 17:11:09 MicroSurvur systemd[1]: Failed to start PVE Status Daemon.
Dec 18 17:11:09 MicroSurvur systemd[1]: pvestatd.service: Unit entered failed state.
Dec 18 17:11:09 MicroSurvur systemd[1]: pvestatd.service: Failed with result 'exit-code'.

Journalctl gives this:
Dec 18 17:14:18 MicroSurvur audit[57296]: AVC apparmor="DENIED" operation="ptrace" profile="docker-default"
 
$ sudo systemctl status pve-cluster
● pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2018-12-19 02:04:45 CET; 18h ago
Process: 36601 ExecStart=/usr/bin/pmxcfs (code=exited, status=255)
CPU: 19ms

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable
 
please try to start it, and if it fails, post the output of the status command or log again
 
*sigh*
im so sorry...
went through the guide found here again and noticed i'w forgot to edit the hostfile to loop back to my ip :/
added that line and everything seems to work now :D

Now i'll just need to find a guide to help me log in :P

Thanks for the help though :)
 
  • Like
Reactions: RalphRalphio
Thank you @Kieeps, your clue to edit /etc/hosts worked to fix a problem I had with PBS (Proxmox Backup Server)!

My proxmox-backup-proxy.service couldn't start or run without errors.I had previously changed the machine's hostname when I converted it from VM to LXC. The new LXC's hostname was OK, but local loop wasn't changed in the conversion. Simple edit fixed it with a restart of the machine:
Code: 
 nano /etc/hosts
   127.0.0.1 localhost
   127.0.1.1 vm-oldname   -->  127.0.1.1 lxc-newname
   ...

P.S. Apologies for reviving this really old thread, I've seen this kind of problem with PBS reported in several threads with different symptoms, so someone might benefit down the road.
 
Last edited:
You must log in or register to reply here.
Top Bottom