[PVE-User] pve4.2 connection refused(595)

Wed Oct 19 11:22:53 CEST 2016

thanks
I has look it url,it is not my question,now my pveproxy does not start.
pve node "load" very high,my vm's load only 0.02,but kvm's load is very high,cpu usage 32.2%
why?
my vm's load is "load average: 0.07, 0.09, 0.06",and cpu usage is 4.3%
but,pve node's kvm process is 32.2%
top - 17:09:29 up 154 days, 23 min,  2 users,  load average: 15.91, 16.57, 16.12
Tasks: 505 total,   2 running, 503 sleeping,   0 stopped,   0 zombie
%Cpu(s): 22.9 us, 16.7 sy,  0.0 ni, 57.2 id,  1.6 wa,  0.0 hi,  1.6 si,  0.0 st
KiB Mem:  65674780 total, 50343244 used, 15331536 free,   167068 buffers
KiB Swap:  8388604 total,        0 used,  8388604 free.  1779916 cached Mem


  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND                                                          
26757 root      20   0 3032592 2.021g  13780 S  32.2  3.2  45702:04 /usr/bin/kvm -id 107 -chardev socket,id=qmp,path=/var/run/qemu-s+
28906 root      20   0 2987532 1.993g  13816 S  23.3  3.2  36427:44 /usr/bin/kvm -id 125 -chardev socket,id=qmp,path=/var/run/qemu-s+
 9859 root      20   0 5633816 4.401g  13860 S  12.0  7.0   6712:15 /usr/bin/kvm -id 164 -chardev socket,id=qmp,path=/var/run/qemu-s+
 3182 root      20   0 9217548 2.197g  13636 S  11.6  3.5   5351:35 /usr/bin/kvm -id 117 -chardev socket,id=qmp,path=/var/run/qemu-s+
14929 root      20   0 9853.6m 1.193g  13728 S  11.3  1.9   4299:14 /usr/bin/kvm -id 141 -chardev socket,id=qmp,path=/var/run/qemu-s+
 2524 root      20   0 16.494g 0.011t  13528 S  11.0 18.5  15248:41 /usr/bin/kvm -id 134 -chardev socket,id=qmp,path=/var/run/qemu-s+
 1069 root      20   0 2012660 1.010g  13424 S   9.6  1.6   3890:15 /usr/bin/kvm -id 120 -chardev socket,id=qmp,path=/var/run/qemu-s+
12200 root      20   0 5084684 692660  13728 S   9.6  1.1   3118:58 /usr/bin/kvm -id 124 -chardev socket,id=qmp,path=/var/run/qemu-s+
21437 root      20   0 1877504 1.023g  13820 S   9.6  1.6   4249:47 /usr/bin/kvm -id 241 -chardev socket,id=qmp,path=/var/run/qemu-s+
26355 root      20   0 4015624 958496  13516 S   9.6  1.5   1661:09 /usr/bin/kvm -id 167 -chardev socket,id=qmp,path=/var/run/qemu-s+
19561 root      20   0 1881568 1.022g  13596 S   9.3  1.6   4981:22 /usr/bin/kvm -id 235 -chardev socket,id=qmp,path=/var/run/qemu-s+
31607 root      20   0 1582548 1.027g  13708 S   9.3  1.6   3708:07 /usr/bin/kvm -id 223 -chardev socket,id=qmp,path=/var/run/qemu-s+
28295 root      20   0 1869284 775460  13636 S   9.0  1.2   3901:47 /usr/bin/kvm -id 225 -chardev socket,id=qmp,path=/var/run/qemu-s+
32375 root      20   0 1832416 650252  13568 S   9.0  1.0   3284:50 /usr/bin/kvm -id 115 -chardev socket,id=qmp,path=/var/run/qemu-s+
 5051 root      20   0 1865184 518248  13856 S   8.6  0.8   3207:06 /usr/bin/kvm -id 143 -chardev socket,id=qmp,path=/var/run/qemu-s+


What am I to do？


At 2016-10-19 16:26:50, "Emmanuel Kasper" <e.kasper at proxmox.com> wrote:
>Hi Haoyun
>Have a look at
>https://forum.proxmox.com/threads/pveproxy-become-blocked-state-and-cannot-be-killed.24386/page-2#post-149858
>
>for some hints for this problem
>
>
>On 10/19/2016 10:25 AM, haoyun wrote:
>> and i restart pveproxy failed,command was blocked long time:
>> 
>> 
>> root at yj-1914-cna6:/var/log# service pveproxy restart
>> Job for pveproxy.service failed. See 'systemctl status pveproxy.service' and 'journalctl -xn' for details.
>> root at yj-1914-cna6:/var/log# systemctl restart pveproxy.service
>> Job for pveproxy.service failed. See 'systemctl status pveproxy.service' and 'journalctl -xn' for details.
>> root at yj-1914-cna6:/var/log# journalctl -xn
>> -- Logs begin at Thu 2016-05-19 00:46:08 CST, end at Wed 2016-10-19 16:20:55 CST. --
>> Oct 19 16:17:01 yj-1914-cna6 CRON[22305]: pam_unix(cron:session): session closed for user root
>> Oct 19 16:17:54 yj-1914-cna6 systemd[1]: pveproxy.service start operation timed out. Terminating.
>> Oct 19 16:18:52 yj-1914-cna6 postfix/scache[22107]: statistics: start interval Oct 19 16:15:32
>> Oct 19 16:18:52 yj-1914-cna6 postfix/scache[22107]: statistics: domain lookup hits=7 miss=8 success=46%
>> Oct 19 16:18:52 yj-1914-cna6 postfix/scache[22107]: statistics: address lookup hits=15 miss=8 success=65%
>> Oct 19 16:18:52 yj-1914-cna6 postfix/scache[22107]: statistics: max simultaneous domains=1 addresses=1 connection=8
>> Oct 19 16:19:24 yj-1914-cna6 systemd[1]: pveproxy.service stop-final-sigterm timed out. Killing.
>> Oct 19 16:20:55 yj-1914-cna6 systemd[1]: pveproxy.service still around after final SIGKILL. Entering failed mode.
>> Oct 19 16:20:55 yj-1914-cna6 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
>> 
>
>_______________________________________________
>pve-user mailing list
>pve-user at pve.proxmox.com
>http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user