pveproxy can't start

lyddragon

Member
Jan 3, 2017
13
0
6
44

# PVE manager panel display(192.168.1.2's virtual pc):
Error Connection error 595: Connection refused

# cluster status:

$ pvecm status
Quorum information
------------------
Date: Tue Feb 6 13:36:35 2018
Quorum provider: corosync_votequorum
Nodes: 3
Node ID: 0x00000002
Ring ID: 1/332
Quorate: Yes
Votequorum information
----------------------
Expected votes: 3
Highest expected: 3
Total votes: 3
Quorum: 2
Flags: Quorate
Membership information
----------------------
Nodeid Votes Name
0x00000001 1 192.168.1.1
0x00000002 1 192.168.1.2 (local)
0x00000003 1 192.168.1.3

# cluster nodes:
$ pvecm nodes
Membership information
----------------------
Nodeid Votes Name
1 1 pve1
2 1 pve2 (local)
3 1 pve3

# pveproxy service start/stop processe, on 192.168.1.2(pve2), and can't killed (-9):

root 35911 0.0 0.0 239764 66488 ? Ds Jan09 0:00 /usr/bin/perl -T /usr/bin/pveproxy stop
root 41562 0.0 0.0 239764 66560 ? Ds Jan09 0:00 /usr/bin/perl -T /usr/bin/pveproxy start
root 45072 0.0 0.0 239232 65760 ? Ds Jan09 0:00 /usr/bin/perl -T /usr/bin/spiceproxy stop
root 47888 0.0 0.0 239752 66300 ? Ds 12:25 0:00 /usr/bin/perl -T /usr/bin/pveproxy start
root 50827 0.0 0.0 239740 66312 ? Ds Jan09 0:00 /usr/bin/perl -T /usr/bin/pveproxy start
root 54195 0.0 0.0 239180 66032 ? Ds Jan09 0:00 /usr/bin/perl -T /usr/bin/spiceproxy start

# tcp listen, no spiceproxy/pveproxy work:
$ netstat -nltp |grep -Ev 'sshd|master|rpc|zabbix'
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:85 0.0.0.0:* LISTEN 2283/pvedaemon


service pveproxy can't start !!!
 
$ systemctl status pveproxy
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled)
Active: failed (Result: timeout) since Tue 2018-02-06 14:03:32 CST; 10h ago
Main PID: 86664 (code=exited, status=0/SUCCESS)
Feb 06 14:00:32 pve2 systemd[1]: pveproxy.service start operation timed out. Terminating.
Feb 06 14:02:02 pve2 systemd[1]: pveproxy.service stop-final-sigterm timed out. Killing.
Feb 06 14:03:32 pve2 systemd[1]: pveproxy.service still around after final SIGKILL. Entering failed mode.
Feb 06 14:03:32 pve2 systemd[1]: Failed to start PVE API Proxy Server.
Feb 06 14:03:32 pve2 systemd[1]: Unit pveproxy.service entered failed state.

$ journalctl -u pveproxy
Dec 21 06:25:04 pve2 pveproxy[86664]: worker 86667 started
Dec 21 06:25:04 pve2 systemd[1]: Started PVE API Proxy Server.
Jan 08 16:24:00 pve2 pveproxy[86666]: Use of uninitialized value $v in substitution (s///) at /usr/share/perl5/PVE/HTTPServer.pm line 675.
Jan 08 16:24:00 pve2 pveproxy[86666]: Use of uninitialized value $v in substitution (s///) at /usr/share/perl5/PVE/HTTPServer.pm line 676.
Jan 08 16:24:00 pve2 pveproxy[86666]: Use of uninitialized value $v in substitution (s///) at /usr/share/perl5/PVE/HTTPServer.pm line 675.
Jan 08 16:24:00 pve2 pveproxy[86666]: Use of uninitialized value $v in substitution (s///) at /usr/share/perl5/PVE/HTTPServer.pm line 676.
Jan 08 16:24:13 pve2 pveproxy[86667]: worker exit
Jan 08 16:24:13 pve2 pveproxy[86664]: worker 86667 finished
Jan 08 16:24:13 pve2 pveproxy[86664]: starting 1 worker(s)
Jan 08 16:24:13 pve2 pveproxy[86664]: worker 182688 started
Jan 08 16:24:14 pve2 pveproxy[86665]: worker exit
Jan 08 16:24:14 pve2 pveproxy[86664]: worker 86665 finished
Jan 08 16:24:14 pve2 pveproxy[86664]: starting 1 worker(s)
Jan 08 16:24:14 pve2 pveproxy[86664]: worker 182701 started
Jan 08 16:24:16 pve2 pveproxy[86666]: Use of uninitialized value $v in substitution (s///) at /usr/share/perl5/PVE/HTTPServer.pm line 675.
Jan 08 16:24:16 pve2 pveproxy[86666]: Use of uninitialized value $v in substitution (s///) at /usr/share/perl5/PVE/HTTPServer.pm line 676.
Jan 08 16:24:16 pve2 pveproxy[182688]: Use of uninitialized value $v in substitution (s///) at /usr/share/perl5/PVE/HTTPServer.pm line 675.
Jan 08 16:24:16 pve2 pveproxy[182688]: Use of uninitialized value $v in substitution (s///) at /usr/share/perl5/PVE/HTTPServer.pm line 676.
Jan 08 16:24:27 pve2 pveproxy[86666]: worker exit
Jan 08 16:24:27 pve2 pveproxy[86664]: worker 86666 finished
Jan 08 16:24:27 pve2 pveproxy[86664]: starting 1 worker(s)
Jan 08 16:24:27 pve2 pveproxy[86664]: worker 182872 started
Jan 08 16:24:52 pve2 pveproxy[182872]: Use of uninitialized value $v in substitution (s///) at /usr/share/perl5/PVE/HTTPServer.pm line 675.
Jan 08 16:24:52 pve2 pveproxy[182872]: Use of uninitialized value $v in substitution (s///) at /usr/share/perl5/PVE/HTTPServer.pm line 676.
Jan 08 16:24:52 pve2 pveproxy[182872]: Use of uninitialized value $v in substitution (s///) at /usr/share/perl5/PVE/HTTPServer.pm line 675.
Jan 08 16:24:52 pve2 pveproxy[182872]: Use of uninitialized value $v in substitution (s///) at /usr/share/perl5/PVE/HTTPServer.pm line 676.
Jan 08 16:25:10 pve2 pveproxy[86664]: worker 182701 finished
Jan 08 16:25:10 pve2 pveproxy[86664]: starting 1 worker(s)
Jan 08 16:25:10 pve2 pveproxy[86664]: worker 183439 started
Jan 08 16:25:11 pve2 pveproxy[183438]: worker exit
Jan 08 16:25:11 pve2 pveproxy[182872]: Use of uninitialized value $v in substitution (s///) at /usr/share/perl5/PVE/HTTPServer.pm line 675.
Jan 08 16:25:11 pve2 pveproxy[182872]: Use of uninitialized value $v in substitution (s///) at /usr/share/perl5/PVE/HTTPServer.pm line 676.
Jan 08 16:25:12 pve2 pveproxy[182688]: worker exit
Jan 08 16:25:12 pve2 pveproxy[86664]: worker 182688 finished
Jan 08 16:25:12 pve2 pveproxy[86664]: starting 1 worker(s)
Jan 08 16:25:12 pve2 pveproxy[86664]: worker 183450 started
Jan 08 16:25:21 pve2 pveproxy[182872]: worker exit
Jan 08 16:25:21 pve2 pveproxy[86664]: worker 182872 finished
Jan 08 16:25:21 pve2 pveproxy[86664]: starting 1 worker(s)
Jan 08 16:25:21 pve2 pveproxy[86664]: worker 183567 started
Jan 08 16:25:26 pve2 pveproxy[183450]: Use of uninitialized value $v in substitution (s///) at /usr/share/perl5/PVE/HTTPServer.pm line 675.
Jan 08 16:25:26 pve2 pveproxy[183450]: Use of uninitialized value $v in substitution (s///) at /usr/share/perl5/PVE/HTTPServer.pm line 676.
Jan 09 06:25:02 pve2 systemd[1]: Stopping PVE API Proxy Server...
Jan 09 06:26:32 pve2 systemd[1]: pveproxy.service stopping timed out. Terminating.
Jan 09 06:26:32 pve2 pveproxy[86664]: received signal TERM
Jan 09 06:26:32 pve2 pveproxy[86664]: server closing
Jan 09 06:26:32 pve2 pveproxy[86664]: worker 183450 finished
Jan 09 06:26:32 pve2 pveproxy[86664]: worker 183567 finished
Jan 09 06:26:32 pve2 pveproxy[86664]: worker 183439 finished
Jan 09 06:26:32 pve2 pveproxy[86664]: server stopped
Jan 09 06:28:02 pve2 systemd[1]: pveproxy.service stop-sigterm timed out. Killing.
Jan 09 06:29:32 pve2 systemd[1]: pveproxy.service still around after SIGKILL. Ignoring.
Jan 09 06:31:02 pve2 systemd[1]: pveproxy.service stop-final-sigterm timed out. Killing.
Jan 09 06:32:33 pve2 systemd[1]: pveproxy.service still around after final SIGKILL. Entering failed mode.
Jan 09 06:32:33 pve2 systemd[1]: Unit pveproxy.service entered failed state.
Jan 09 06:32:33 pve2 systemd[1]: Starting PVE API Proxy Server...
Jan 09 06:34:03 pve2 systemd[1]: pveproxy.service start operation timed out. Terminating.
Jan 09 06:35:33 pve2 systemd[1]: pveproxy.service stop-final-sigterm timed out. Killing.
Jan 09 06:37:03 pve2 systemd[1]: pveproxy.service still around after final SIGKILL. Entering failed mode.
Jan 09 06:37:03 pve2 systemd[1]: Failed to start PVE API Proxy Server.
Jan 09 06:37:03 pve2 systemd[1]: Unit pveproxy.service entered failed state.
Jan 09 06:44:35 pve2 systemd[1]: Starting PVE API Proxy Server...
Jan 09 06:46:05 pve2 systemd[1]: pveproxy.service start operation timed out. Terminating.
Jan 09 06:47:35 pve2 systemd[1]: pveproxy.service stop-final-sigterm timed out. Killing.
Jan 09 06:49:05 pve2 systemd[1]: pveproxy.service still around after final SIGKILL. Entering failed mode.
Jan 09 06:49:05 pve2 systemd[1]: Failed to start PVE API Proxy Server.
Jan 09 06:49:05 pve2 systemd[1]: Unit pveproxy.service entered failed state.
Feb 06 12:25:10 pve2 systemd[1]: Starting PVE API Proxy Server...
Feb 06 12:26:40 pve2 systemd[1]: pveproxy.service start operation timed out. Terminating.
Feb 06 12:28:10 pve2 systemd[1]: pveproxy.service stop-final-sigterm timed out. Killing.
Feb 06 12:29:41 pve2 systemd[1]: pveproxy.service still around after final SIGKILL. Entering failed mode.
Feb 06 12:29:41 pve2 systemd[1]: Failed to start PVE API Proxy Server.
Feb 06 12:29:41 pve2 systemd[1]: Unit pveproxy.service entered failed state.
Feb 06 12:34:23 pve2 systemd[1]: Stopped PVE API Proxy Server.
Feb 06 12:34:55 pve2 systemd[1]: Stopped PVE API Proxy Server.
Feb 06 13:59:02 pve2 systemd[1]: Starting PVE API Proxy Server...
Feb 06 14:00:32 pve2 systemd[1]: pveproxy.service start operation timed out. Terminating.
Feb 06 14:02:02 pve2 systemd[1]: pveproxy.service stop-final-sigterm timed out. Killing.
Feb 06 14:03:32 pve2 systemd[1]: pveproxy.service still around after final SIGKILL. Entering failed mode.
Feb 06 14:03:32 pve2 systemd[1]: Failed to start PVE API Proxy Server.
Feb 06 14:03:32 pve2 systemd[1]: Unit pveproxy.service entered failed state.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!