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@yj-1914-cna6:/var/log# service pveproxy restart > Job for pveproxy.service failed. See 'systemctl status pveproxy.service' and > 'journalctl -xn' for details. > root@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@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@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user