Failed to start PVE API Proxy Server.

TechLineX

Active Member
Mar 2, 2015
213
5
38
Setup: 3 node cluster

Today I wanted to check the vms, all green in the webinterface, but 2 of 3 nodes cancle the connection to the interface. When I try to browse to the server with the last working one, I get Connection refused (595). Yesterday was all working.

Other nodes are pingable
Every node has a nfs which is shared with the others

When you need more info, tell it.

Can't start pveproxy or pvestatd

Code:
Usage: /etc/init.d/pveproxy {start|stop|restart|reload|force-reload}
root@host16:~# service pveproxy status
● pveproxy.service - PVE API Proxy Server
   Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled)
   Active: failed (Result: timeout) since Fri 2016-12-16 06:49:18 CET; 10h ago
  Process: 10234 ExecReload=/usr/bin/pveproxy restart (code=exited, status=0/SUC                                            CESS)
Main PID: 7209 (code=exited, status=0/SUCCESS)

Dec 16 06:46:17 host16 systemd[1]: pveproxy.service start operation timed o...g.
Dec 16 06:47:48 host16 systemd[1]: pveproxy.service stop-final-sigterm time...g.
Dec 16 06:49:18 host16 systemd[1]: pveproxy.service still around after fina...e.
Dec 16 06:49:18 host16 systemd[1]: Failed to start PVE API Proxy Server.
Dec 16 06:49:18 host16 systemd[1]: Unit pveproxy.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.
root@host16:~# service pveproxy start

Code:
root@host18:~# service pveproxy status
● pveproxy.service - PVE API Proxy Server
   Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled)
   Active: failed (Result: timeout) since Fri 2016-12-16 06:49:39 CET; 10h ago
  Process: 7784 ExecReload=/usr/bin/pveproxy restart (code=exited, status=0/SUCCESS)
Main PID: 2922 (code=exited, status=0/SUCCESS)

Dec 16 06:46:39 host18 systemd[1]: pveproxy.service start operation timed o...g.
Dec 16 06:48:09 host18 systemd[1]: pveproxy.service stop-final-sigterm time...g.
Dec 16 06:49:39 host18 systemd[1]: pveproxy.service still around after fina...e.
Dec 16 06:49:39 host18 systemd[1]: Failed to start PVE API Proxy Server.
Dec 16 06:49:39 host18 systemd[1]: Unit pveproxy.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.
root@host18:~# service pveproxy start
 
what does journalctl -xn say?
 
I have the same problem


root@ju025:/var/www/austausch/images# journalctl -xn
-- Logs begin at Fr 2016-12-30 19:13:07 CET, end at Fr 2016-12-30 19:22:10 CET. --
Dez 30 19:22:05 ju025 pveproxy[2216]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 14.
Dez 30 19:22:05 ju025 pveproxy[2216]: Compilation failed in require at /usr/share/perl5/PVE/Service/pveproxy.pm line 15.
Dez 30 19:22:05 ju025 pveproxy[2216]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pveproxy.pm line 15.
Dez 30 19:22:05 ju025 pveproxy[2216]: Compilation failed in require at /usr/bin/pveproxy line 11.
Dez 30 19:22:05 ju025 pveproxy[2216]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Dez 30 19:22:05 ju025 systemd[1]: pveproxy.service: control process exited, code=exited status=2
Dez 30 19:22:05 ju025 systemd[1]: Failed to start PVE API Proxy Server.
-- Subject: Unit pveproxy.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit pveproxy.service has failed.
--
-- The result is failed.
Dez 30 19:22:05 ju025 systemd[1]: Unit pveproxy.service entered failed state.
Dez 30 19:22:10 ju025 postfix/smtpd[2249]: connect from unknown[62.212.95.212]
Dez 30 19:22:10 ju025 postfix/smtpd[2249]: disconnect from unknown[62.212.95.212]