Proxmox Big Problem only ???? at the Status

Dec 3, 2018
30
0
6
33
Germany
squote.de
Hey,

i have big Problems with my Host Maschine. After i start an reinstallation sometimes the Host is hanging up with Status ? at the Control Panel. After an reboot all works fine. But The node is online an all vps also online. I do not have any idea

What can i do to fixed the Problem.

Regards
Thorsten
 
Last edited:
where exactly do you see the '?'
in the webinterface? if yes, there is probably something hanging (most likely an nfs storage or similar), check the syslog of the node when this happens
 
Hey, same Problem now:( Here is my Syslog


Code:
Mar  7 18:21:01 vps01 CRON[1953]: (root) CMD (/usr/local/emps/bin/php /usr/local/virtualizor/scripts/powercron.php >> /var/virtualizor/log/powercron 2>&1)
Mar  7 18:21:01 vps01 systemd[1]: Started Proxmox VE replication runner.
Mar  7 18:21:35 vps01 pvedaemon[2263]: <root@pam> successful auth for user 'root@pam'
Mar  7 18:21:37 vps01 pvedaemon[2262]: <root@pam> successful auth for user 'root@pam'
Mar  7 18:21:37 vps01 pvedaemon[2262]: <root@pam> starting task UPID:vps01:000009A5:0D099E81:5C815321:vzcreate:1036:root@pam:
Mar  7 18:21:47 vps01 pvedaemon[2262]: <root@pam> end task UPID:vps01:000009A5:0D099E81:5C815321:vzcreate:1036:root@pam: OK
Mar  7 18:21:47 vps01 pvedaemon[2264]: disk image '/var/lib/vz/images/1036/vm-1036-disk-0.raw' does not exists
Mar  7 18:21:55 vps01 pvedaemon[2264]: <root@pam> successful auth for user 'root@pam'
Mar  7 18:21:55 vps01 pvedaemon[2263]: <root@pam> starting task UPID:vps01:00000B4A:0D09A588:5C815333:vzstart:1036:root@pam:
Mar  7 18:21:55 vps01 pvedaemon[2890]: starting CT 1036: UPID:vps01:00000B4A:0D09A588:5C815333:vzstart:1036:root@pam:
Mar  7 18:21:55 vps01 systemd[1]: Starting PVE LXC Container: 1036...
Mar  7 18:21:57 vps01 kernel: [2187360.074680] EXT4-fs (loop4): mounted filesystem with ordered data mode. Opts: (null)
Mar  7 18:21:57 vps01 systemd-udevd[2954]: Could not generate persistent MAC address for vethD6UQVP: No such file or directory
Mar  7 18:22:00 vps01 systemd[1]: Starting Proxmox VE replication runner...
Mar  7 18:22:00 vps01 systemd[1]: Started Proxmox VE replication runner.
Mar  7 18:22:01 vps01 CRON[3059]: (root) CMD (/usr/local/emps/bin/php /usr/local/virtualizor/scripts/powercron.php >> /var/virtualizor/log/powercron 2>&1)
Mar  7 18:23:00 vps01 systemd[1]: Starting Proxmox VE replication runner...
Mar  7 18:23:00 vps01 systemd[1]: Started Proxmox VE replication runner.
Mar  7 18:23:01 vps01 CRON[3296]: (root) CMD (/usr/local/emps/bin/php /usr/local/virtualizor/scripts/powercron.php >> /var/virtualizor/log/powercron 2>&1)
Mar  7 18:23:25 vps01 systemd[1]: pve-container@1036.service: Start operation timed out. Terminating.
Mar  7 18:23:25 vps01 systemd[1]: Failed to start PVE LXC Container: 1036.
Mar  7 18:23:25 vps01 systemd[1]: pve-container@1036.service: Unit entered failed state.
Mar  7 18:23:25 vps01 systemd[1]: pve-container@1036.service: Failed with result 'timeout'.
Mar  7 18:23:25 vps01 pvedaemon[2890]: command 'systemctl start pve-container@1036' failed: exit code 1
Mar  7 18:23:25 vps01 pvedaemon[2263]: <root@pam> end task UPID:vps01:00000B4A:0D09A588:5C815333:vzstart:1036:root@pam: command 'systemctl start pve-container@1036' failed: exit code 1
Mar  7 18:24:00 vps01 systemd[1]: Starting Proxmox VE replication runner...
Mar  7 18:24:01 vps01 systemd[1]: Started Proxmox VE replication runner.
Mar  7 18:24:01 vps01 CRON[4078]: (root) CMD (/usr/local/emps/bin/php /usr/local/virtualizor/scripts/cronm.php >> /var/virtualizor/log/cronm 2>&1)
Mar  7 18:24:01 vps01 CRON[4079]: (root) CMD (/usr/local/emps/bin/php /usr/local/virtualizor/scripts/powercron.php >> /var/virtualizor/log/powercron 2>&1)
Mar  7 18:24:06 vps01 pvedaemon[2262]: <root@pam> successful auth for user 'root@pam'
Mar  7 18:24:40 vps01 pvedaemon[2263]: <root@pam> successful auth for user 'root@pam'
Mar  7 18:24:52 vps01 pvedaemon[2262]: <root@pam> successful auth for user 'root@pam'
Mar  7 18:24:53 vps01 pvedaemon[2263]: <root@pam> successful auth for user 'root@pam'
Mar  7 18:25:00 vps01 systemd[1]: Starting Proxmox VE replication runner...
Mar  7 18:25:00 vps01 systemd[1]: Started Proxmox VE replication runner.
Mar  7 18:25:01 vps01 CRON[4869]: (root) CMD (/usr/local/emps/bin/php /usr/local/virtualizor/scripts/powercron.php >> /var/virtualizor/log/powercron 2>&1)
Mar  7 18:25:34 vps01 pveproxy[11165]: proxy detected vanished client connection
Mar  7 18:26:00 vps01 systemd[1]: Starting Proxmox VE replication runner...
Mar  7 18:26:01 vps01 systemd[1]: Started Proxmox VE replication runner.
Mar  7 18:26:01 vps01 CRON[5604]: (root) CMD (/usr/local/emps/bin/php /usr/local/virtualizor/scripts/powercron.php >> /var/virtualizor/log/powercron 2>&1)
Mar  7 18:27:00 vps01 systemd[1]: Starting Proxmox VE replication runner...
Mar  7 18:27:01 vps01 systemd[1]: Started Proxmox VE replication runner.
Mar  7 18:27:01 vps01 CRON[6142]: (root) CMD (/usr/local/emps/bin/php /usr/local/virtualizor/scripts/powercron.php >> /var/virtualizor/log/powercron 2>&1)
Mar  7 18:28:00 vps01 systemd[1]: Starting Proxmox VE replication runner...


Mar  7 18:27:00 vps01 systemd[1]: Starting Proxmox VE replication runner...
Mar  7 18:27:01 vps01 systemd[1]: Started Proxmox VE replication runner.
Mar  7 18:27:01 vps01 CRON[6142]: (root) CMD (/usr/local/emps/bin/php /usr/local/virtualizor/scripts/powercron.php >> /var/virtualizor/log/powercron 2>&1)
Mar  7 18:28:00 vps01 systemd[1]: Starting Proxmox VE replication runner...
Mar  7 18:28:01 vps01 systemd[1]: Started Proxmox VE replication runner.
Mar  7 18:28:01 vps01 CRON[6755]: (root) CMD (/usr/local/emps/bin/php /usr/local/virtualizor/scripts/powercron.php >> /var/virtualizor/log/powercron 2>&1)
Mar  7 18:29:00 vps01 systemd[1]: Starting Proxmox VE replication runner...
Mar  7 18:29:01 vps01 CRON[7256]: (root) CMD (/usr/local/emps/bin/php /usr/local/virtualizor/scripts/powercron.php >> /var/virtualizor/log/powercron 2>&1)
Mar  7 18:29:01 vps01 systemd[1]: Started Proxmox VE replication runner.
Mar  7 18:30:00 vps01 systemd[1]: Starting Proxmox VE replication runner...
Mar  7 18:30:01 vps01 CRON[7854]: (root) CMD (/usr/local/emps/bin/php /usr/local/virtualizor/scripts/powercron.php >> /var/virtualizor/log/powercron 2>&1)
Mar  7 18:30:01 vps01 systemd[1]: Started Proxmox VE replication runner.
Mar  7 18:30:18 vps01 pvedaemon[2262]: <root@pam> successful auth for user 'root@pam'
Mar  7 18:30:29 vps01 pvedaemon[2264]: <root@pam> successful auth for user 'root@pam'
Mar  7 18:31:00 vps01 systemd[1]: Starting Proxmox VE replication runner...
Mar  7 18:31:01 vps01 CRON[8595]: (root) CMD (/usr/local/emps/bin/php /usr/local/virtualizor/scripts/powercron.php >> /var/virtualizor/log/powercron 2>&1)
Mar  7 18:31:01 vps01 systemd[1]: Started Proxmox VE replication runner.
Mar  7 18:32:00 vps01 systemd[1]: Starting Proxmox VE replication runner...
Mar  7 18:32:01 vps01 CRON[9150]: (root) CMD (/usr/local/emps/bin/php /usr/local/virtualizor/scripts/powercron.php >> /var/virtualizor/log/powercron 2>&1)
Mar  7 18:32:01 vps01 CRON[9149]: (root) CMD (/usr/local/emps/bin/php /usr/local/virtualizor/scripts/cronm.php >> /var/virtualizor/log/cronm 2>&1)
Mar  7 18:32:01 vps01 systemd[1]: Started Proxmox VE replication runner.
Mar  7 18:32:07 vps01 pvedaemon[2264]: <root@pam> successful auth for user 'root@pam'
Mar  7 18:33:00 vps01 systemd[1]: Starting Proxmox VE replication runner...
Mar  7 18:33:01 vps01 systemd[1]: Started Proxmox VE replication runner.
Mar  7 18:33:01 vps01 CRON[9834]: (root) CMD (/usr/local/emps/bin/php /usr/local/virtualizor/scripts/powercron.php >> /var/virtualizor/log/powercron 2>&1)
Mar  7 18:34:00 vps01 systemd[1]: Starting Proxmox VE replication runner...
Mar  7 18:34:01 vps01 CRON[10354]: (root) CMD (/usr/local/emps/bin/php /usr/local/virtualizor/scripts/powercron.php >> /var/virtualizor/log/powercron 2>&1)
Mar  7 18:34:01 vps01 systemd[1]: Started Proxmox VE replication runner.
Mar  7 18:35:00 vps01 systemd[1]: Starting Proxmox VE replication runner...
Mar  7 18:35:01 vps01 systemd[1]: Started Proxmox VE replication runner.
Mar  7 18:35:01 vps01 CRON[10954]: (root) CMD (/usr/local/emps/bin/php /usr/local/virtualizor/scripts/powercron.php >> /var/virtualizor/log/powercron 2>&1)
Mar  7 18:36:00 vps01 systemd[1]: Starting Proxmox VE replication runner...
Mar  7 18:36:01 vps01 systemd[1]: Started Proxmox VE replication runner.
Mar  7 18:36:01 vps01 CRON[11406]: (root) CMD (/usr/local/emps/bin/php /usr/local/virtualizor/scripts/powercron.php >> /var/virtualizor/log/powercron 2>&1)
Mar  7 18:37:00 vps01 systemd[1]: Starting Proxmox VE replication runner...
Mar  7 18:37:01 vps01 systemd[1]: Started Proxmox VE replication runner.
Mar  7 18:37:01 vps01 CRON[11627]: (root) CMD (/usr/local/emps/bin/php /usr/local/virtualizor/scripts/powercron.php >> /var/virtualizor/log/powercron 2>&1)
Mar  7 18:37:14 vps01 systemd[1]: Created slice User Slice of root.
Mar  7 18:37:14 vps01 systemd[1]: Starting User Manager for UID 0...
Mar  7 18:37:14 vps01 systemd[1]: Started Session 170722 of user root.
Mar  7 18:37:14 vps01 systemd[11671]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Mar  7 18:37:14 vps01 systemd[11671]: Reached target Paths.
Mar  7 18:37:14 vps01 systemd[11671]: Listening on GnuPG cryptographic agent and passphrase cache.
Mar  7 18:37:14 vps01 systemd[11671]: Reached target Timers.
Mar  7 18:37:14 vps01 systemd[11671]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Mar  7 18:37:14 vps01 systemd[11671]: Listening on GnuPG cryptographic agent (access for web browsers).
Mar  7 18:37:14 vps01 systemd[11671]: Reached target Sockets.
Mar  7 18:37:14 vps01 systemd[11671]: Reached target Basic System.
Mar  7 18:37:14 vps01 systemd[11671]: Reached target Default.
Mar  7 18:37:14 vps01 systemd[11671]: Startup finished in 8ms.
Mar  7 18:37:14 vps01 systemd[1]: Started User Manager for UID 0.
 
have you tried restarting pvestatd ?
 
Hey,

yes but it does not work. Only ? in Webgui. When i reboot the Maschine, it works. after a small time, i will make an reinstall or create a new Server the Maschine is going to ? :(

Regards
Thorsten
 
sounds like a hanging store or something like that, can you do a 'pvesm status' and see if it hangs for some storage, also a bigger section of the syslog/journal would probably be helpful
 
Hey,

here:

Code:
root@vHost01:~# pvesm status
Name         Type     Status           Total            Used       Available        %
local         dir     active       940536184       291156776       601533008   30.96%

Code:
Mar 19 12:50:18 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:50:22 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:50:27 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:50:30 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:50:31 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d9:55:4c via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:50:31 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:50:35 vHost01 dhcpd[15501]: DHCPREQUEST for 134.255.236.193 (134.255.236.71) from e4:11:5b:d9:55:4c via vmbr0: unknown lease 134.255.236.193.
Mar 19 12:50:38 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d5:68:96 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:50:40 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:50:42 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d5:68:96 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:50:47 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:50:50 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:50:51 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d5:68:96 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:50:54 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:50:58 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:50:59 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d9:55:4c via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:50:59 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:51:00 vHost01 systemd[1]: Starting Proxmox VE replication runner...
Mar 19 12:51:00 vHost01 systemd[1]: Started Proxmox VE replication runner.
Mar 19 12:51:01 vHost01 CRON[466]: (root) CMD (/usr/local/emps/bin/php /usr/local/virtualizor/scripts/powercron.php >> /var/virtualizor/log/powercron 2>&1)
Mar 19 12:51:03 vHost01 dhcpd[15501]: DHCPREQUEST for 134.255.236.193 (134.255.236.71) from e4:11:5b:d9:55:4c via vmbr0: unknown lease 134.255.236.193.
Mar 19 12:51:03 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:51:07 vHost01 dhcpd[15501]: DHCPDISCOVER from 60:eb:69:6e:a2:e0 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:51:07 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d5:68:96 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:51:11 vHost01 dhcpd[15501]: DHCPDISCOVER from 60:eb:69:6e:a2:e0 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:51:15 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:51:19 vHost01 dhcpd[15501]: DHCPDISCOVER from 60:eb:69:6e:a2:e0 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:51:26 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:51:27 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d9:55:4c via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:51:32 vHost01 dhcpd[15501]: DHCPREQUEST for 134.255.236.193 (134.255.236.71) from e4:11:5b:d9:55:4c via vmbr0: unknown lease 134.255.236.193.
Mar 19 12:51:36 vHost01 dhcpd[15501]: DHCPDISCOVER from 60:eb:69:6e:a2:e0 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:51:38 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:51:40 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d5:68:96 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:51:42 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:51:47 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:51:51 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:51:53 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:51:56 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d9:55:4c via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:51:56 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:52:00 vHost01 dhcpd[15501]: DHCPREQUEST for 134.255.236.193 (134.255.236.71) from e4:11:5b:d9:55:4c via vmbr0: unknown lease 134.255.236.193.
Mar 19 12:52:00 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:52:00 vHost01 systemd[1]: Starting Proxmox VE replication runner...
Mar 19 12:52:00 vHost01 systemd[1]: Started Proxmox VE replication runner.
Mar 19 12:52:01 vHost01 CRON[695]: (root) CMD (/usr/local/emps/bin/php /usr/local/virtualizor/scripts/powercron.php >> /var/virtualizor/log/powercron 2>&1)
Mar 19 12:52:10 vHost01 dhcpd[15501]: DHCPDISCOVER from 60:eb:69:6e:a2:e0 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:52:10 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:52:14 vHost01 dhcpd[15501]: DHCPDISCOVER from 60:eb:69:6e:a2:e0 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:52:19 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:52:23 vHost01 dhcpd[15501]: DHCPDISCOVER from 60:eb:69:6e:a2:e0 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:52:24 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d9:55:4c via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:52:28 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d9:55:4c via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:52:32 vHost01 dhcpd[15501]: DHCPREQUEST for 134.255.236.193 (134.255.236.71) from e4:11:5b:d9:55:4c via vmbr0: unknown lease 134.255.236.193.
Mar 19 12:52:34 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:52:39 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:52:39 vHost01 dhcpd[15501]: DHCPDISCOVER from 60:eb:69:6e:a2:e0 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:52:43 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:52:44 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d5:68:96 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:52:48 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:52:51 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:52:53 vHost01 dhcpd[15501]: DHCPDISCOVER from da:e9:78:24:fa:6c via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:52:55 vHost01 dhcpd[15501]: DHCPDISCOVER from da:e9:78:24:fa:6c via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:52:56 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d9:55:4c via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:52:56 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:52:57 vHost01 dhcpd[15501]: DHCPDISCOVER from da:e9:78:24:fa:6c via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:52:58 vHost01 dhcpd[15501]: DHCPDISCOVER from da:e9:78:24:fa:6c via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:53:00 vHost01 systemd[1]: Starting Proxmox VE replication runner...
Mar 19 12:53:00 vHost01 dhcpd[15501]: DHCPREQUEST for 134.255.236.193 (134.255.236.71) from e4:11:5b:d9:55:4c via vmbr0: unknown lease 134.255.236.193.
Mar 19 12:53:00 vHost01 systemd[1]: Started Proxmox VE replication runner.
Mar 19 12:53:01 vHost01 CRON[953]: (root) CMD (/usr/local/emps/bin/php /usr/local/virtualizor/scripts/powercron.php >> /var/virtualizor/log/powercron 2>&1)
Mar 19 12:53:07 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:53:12 vHost01 dhcpd[15501]: DHCPDISCOVER from 60:eb:69:6e:a2:e0 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:53:15 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:53:16 vHost01 dhcpd[15501]: DHCPDISCOVER from 60:eb:69:6e:a2:e0 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:53:20 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:53:23 vHost01 dhcpd[15501]: DHCPDISCOVER from 60:eb:69:6e:a2:e0 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:53:24 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:53:24 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d9:55:4c via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:53:24 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:53:29 vHost01 dhcpd[15501]: DHCPREQUEST for 134.255.236.193 (134.255.236.71) from e4:11:5b:d9:55:4c via vmbr0: unknown lease 134.255.236.193.
Mar 19 12:53:29 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:53:33 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d9:55:4c via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:53:34 vHost01 dhcpd[15501]: DHCPDISCOVER from 60:eb:69:6e:a2:e0 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:53:35 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:53:37 vHost01 dhcpd[15501]: DHCPREQUEST for 134.255.236.193 (134.255.236.71) from e4:11:5b:d9:55:4c via vmbr0: unknown lease 134.255.236.193.
Mar 19 12:53:48 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:53:49 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d5:68:96 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:53:52 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:53:53 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d5:68:96 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:53:56 vHost01 dhcpd[15501]: DHCPDISCOVER from 60:eb:69:6e:a2:e0 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:53:56 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:53:58 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:54:00 vHost01 systemd[1]: Starting Proxmox VE replication runner...
Mar 19 12:54:01 vHost01 systemd[1]: Started Proxmox VE replication runner.
Mar 19 12:54:01 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d9:55:4c via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:54:01 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:54:01 vHost01 CRON[1155]: (root) CMD (/usr/local/emps/bin/php /usr/local/virtualizor/scripts/powercron.php >> /var/virtualizor/log/powercron 2>&1)
Mar 19 12:54:01 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d5:68:96 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:54:04 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:54:05 vHost01 dhcpd[15501]: DHCPREQUEST for 134.255.236.193 (134.255.236.71) from e4:11:5b:d9:55:4c via vmbr0: unknown lease 134.255.236.193.
Mar 19 12:54:05 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:54:05 vHost01 dhclient[1033]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 7
Mar 19 12:54:13 vHost01 dhclient[1033]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 18
Mar 19 12:54:17 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:54:18 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d5:68:96 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:54:29 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d9:55:4c via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:54:31 vHost01 dhclient[1033]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 12
Mar 19 12:54:33 vHost01 dhcpd[15501]: DHCPREQUEST for 134.255.236.193 (134.255.236.71) from e4:11:5b:d9:55:4c via vmbr0: unknown lease 134.255.236.193.
Mar 19 12:54:34 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:54:43 vHost01 dhclient[1033]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 13
Mar 19 12:54:49 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:54:50 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d5:68:96 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:54:56 vHost01 dhclient[1033]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 10
Mar 19 12:54:56 vHost01 pvedaemon[5417]: <root@pam> successful auth for user 'root@pam'
Mar 19 12:54:57 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d9:55:4c via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:55:00 vHost01 systemd[1]: Starting Proxmox VE replication runner...
Mar 19 12:55:00 vHost01 systemd[1]: Started Proxmox VE replication runner.
Mar 19 12:55:01 vHost01 CRON[1333]: (root) CMD (/usr/local/emps/bin/php /usr/local/virtualizor/scripts/powercron.php >> /var/virtualizor/log/powercron 2>&1)
Mar 19 12:55:01 vHost01 dhcpd[15501]: DHCPREQUEST for 134.255.236.193 (134.255.236.71) from e4:11:5b:d9:55:4c via vmbr0: unknown lease 134.255.236.193.
Mar 19 12:55:04 vHost01 pvedaemon[32566]: <root@pam> starting task UPID:vHost01:00000584:04E5BC1B:5C90D898:vncproxy:1022:root@pam:
Mar 19 12:55:04 vHost01 pvedaemon[1412]: starting lxc termproxy UPID:vHost01:00000584:04E5BC1B:5C90D898:vncproxy:1022:root@pam:
Mar 19 12:55:04 vHost01 pvedaemon[32566]: <root@pam> successful auth for user 'root@pam'
Mar 19 12:55:05 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:55:06 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d9:55:4c via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:55:06 vHost01 pvedaemon[32566]: <root@pam> end task UPID:vHost01:00000584:04E5BC1B:5C90D898:vncproxy:1022:root@pam: OK
Mar 19 12:55:06 vHost01 dhclient[1033]: No DHCPOFFERS received.
Mar 19 12:55:06 vHost01 dhclient[1033]: No working leases in persistent database - sleeping.
Mar 19 12:55:10 vHost01 dhcpd[15501]: DHCPREQUEST for 134.255.236.193 (134.255.236.71) from e4:11:5b:d9:55:4c via vmbr0: unknown lease 134.255.236.193.
Mar 19 12:55:12 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:55:17 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:55:20 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:55:20 vHost01 systemd[1]: Started Session 59682 of user root.
Mar 19 12:55:24 vHost01 systemd[1]: Started Session 59683 of user root.
Mar 19 12:55:25 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:55:28 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:55:34 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d9:55:4c via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:55:34 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:55:38 vHost01 dhcpd[15501]: DHCPREQUEST for 134.255.236.193 (134.255.236.71) from e4:11:5b:d9:55:4c via vmbr0: unknown lease 134.255.236.193.
Mar 19 12:55:38 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:55:49 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:55:53 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:55:55 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d5:68:96 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:55:57 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:56:00 vHost01 systemd[1]: Starting Proxmox VE replication runner...
Mar 19 12:56:00 vHost01 systemd[1]: Started Proxmox VE replication runner.
Mar 19 12:56:01 vHost01 CRON[1655]: (root) CMD (/usr/local/emps/bin/php /usr/local/virtualizor/scripts/cronm.php >> /var/virtualizor/log/cronm 2>&1)
Mar 19 12:56:01 vHost01 CRON[1656]: (root) CMD (/usr/local/emps/bin/php /usr/local/virtualizor/scripts/powercron.php >> /var/virtualizor/log/powercron 2>&1)
Mar 19 12:56:02 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d9:55:4c via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:56:02 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:56:02 vHost01 pvedaemon[32566]: <root@pam> successful auth for user 'root@pam'
Mar 19 12:56:06 vHost01 dhcpd[15501]: DHCPREQUEST for 134.255.236.193 (134.255.236.71) from e4:11:5b:d9:55:4c via vmbr0: unknown lease 134.255.236.193.
Mar 19 12:56:06 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:56:09 vHost01 dhcpd[15501]: DHCPDISCOVER from 60:eb:69:6e:a2:e0 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:56:10 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:56:13 vHost01 dhcpd[15501]: DHCPDISCOVER from 60:eb:69:6e:a2:e0 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:56:21 vHost01 dhcpd[15501]: DHCPDISCOVER from 60:eb:69:6e:a2:e0 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:56:30 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d9:55:4c via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:56:31 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:56:34 vHost01 dhcpd[15501]: DHCPREQUEST for 134.255.236.193 (134.255.236.71) from e4:11:5b:d9:55:4c via vmbr0: unknown lease 134.255.236.193.
Mar 19 12:56:38 vHost01 dhcpd[15501]: DHCPDISCOVER from 60:eb:69:6e:a2:e0 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:56:41 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:56:45 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:56:49 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:56:51 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:56:56 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:56:58 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d9:55:4c via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:56:58 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:57:00 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d5:68:96 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:57:00 vHost01 systemd[1]: Starting Proxmox VE replication runner...
Mar 19 12:57:00 vHost01 systemd[1]: Started Proxmox VE replication runner.
Mar 19 12:57:01 vHost01 CRON[1953]: (root) CMD (/usr/local/emps/bin/php /usr/local/virtualizor/scripts/powercron.php >> /var/virtualizor/log/powercron 2>&1)
Mar 19 12:57:02 vHost01 dhcpd[15501]: DHCPREQUEST for 134.255.236.193 (134.255.236.71) from e4:11:5b:d9:55:4c via vmbr0: unknown lease 134.255.236.193.
Mar 19 12:57:02 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:57:04 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d5:68:96 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:57:07 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:57:12 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d5:68:96 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:57:12 vHost01 dhcpd[15501]: DHCPDISCOVER from 60:eb:69:6e:a2:e0 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:57:17 vHost01 dhcpd[15501]: DHCPDISCOVER from 60:eb:69:6e:a2:e0 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:57:19 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:57:26 vHost01 dhcpd[15501]: DHCPDISCOVER from 60:eb:69:6e:a2:e0 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:57:27 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d9:55:4c via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:57:29 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d5:68:96 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:57:31 vHost01 dhcpd[15501]: DHCPREQUEST for 134.255.236.193 (134.255.236.71) from e4:11:5b:d9:55:4c via vmbr0: unknown lease 134.255.236.193.
Mar 19 12:57:35 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d9:55:4c via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:57:35 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:57:39 vHost01 dhcpd[15501]: DHCPREQUEST for 134.255.236.193 (134.255.236.71) from e4:11:5b:d9:55:4c via vmbr0: unknown lease 134.255.236.193.
Mar 19 12:57:42 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:57:42 vHost01 dhcpd[15501]: DHCPDISCOVER from 60:eb:69:6e:a2:e0 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:57:46 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:57:46 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:57:54 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:58:00 vHost01 systemd[1]: Starting Proxmox VE replication runner...
Mar 19 12:58:01 vHost01 systemd[1]: Started Proxmox VE replication runner.
Mar 19 12:58:01 vHost01 CRON[2219]: (root) CMD (/usr/local/emps/bin/php /usr/local/virtualizor/scripts/powercron.php >> /var/virtualizor/log/powercron 2>&1)
Mar 19 12:58:01 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d5:68:96 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:58:03 vHost01 dhcpd[15501]: DHCPDISCOVER from e4:11:5b:d9:55:4c via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:58:03 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:58:05 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:58:07 vHost01 dhcpd[15501]: DHCPREQUEST for 134.255.236.193 (134.255.236.71) from e4:11:5b:d9:55:4c via vmbr0: unknown lease 134.255.236.193.
Mar 19 12:58:15 vHost01 dhcpd[15501]: DHCPDISCOVER from 60:eb:69:6e:a2:e0 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:58:19 vHost01 dhcpd[15501]: DHCPDISCOVER from 60:eb:69:6e:a2:e0 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:58:22 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:58:25 vHost01 dhcpd[15501]: DHCPREQUEST for 152.89.245.50 from 68:05:ca:8b:e8:eb via vmbr0: unknown lease 152.89.245.50.
Mar 19 12:58:25 vHost01 dhcpd[15501]: DHCPDISCOVER from 60:eb:69:6e:a2:e0 via vmbr0: network 0.0.0.0/0: no free leases
Mar 19 12:58:26 vHost01 dhcpd[15501]: DHCPDISCOVER from c8:0a:a9:9e:13:34 via vmbr0: network 0.0.0.0/0: no free leases
 
what does
Code:
systemctl status pvestatd
say?
 
root@vHost01:~# systemctl status pvestatd
● pvestatd.service - PVE Status Daemon
Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; vendor preset:
Active: active (running) since Sun 2019-03-10 00:46:16 CET; 1 weeks 2 days ag
Main PID: 1873 (pvestatd)
Tasks: 2 (limit: 4915)
Memory: 80.9M
CPU: 2h 46min 53.026s
CGroup: /system.slice/pvestatd.service
├─ 1873 pvestatd
└─22894 lxc-info -n 1040 -p

Mar 10 02:36:27 vHost01.squote.de pvestatd[1873]: modified cpu set for lxc/1030:
Mar 10 20:02:08 vHost01.squote.de pvestatd[1873]: modified cpu set for lxc/1022:
Mar 10 20:33:47 vHost01.squote.de pvestatd[1873]: modified cpu set for lxc/1022:
Mar 11 17:24:22 vHost01.squote.de pvestatd[1873]: ipcc_send_rec[1] failed: Conne
Mar 11 17:24:22 vHost01.squote.de pvestatd[1873]: ipcc_send_rec[2] failed: Conne
Mar 11 17:24:22 vHost01.squote.de pvestatd[1873]: ipcc_send_rec[3] failed: Conne
Mar 11 17:24:22 vHost01.squote.de pvestatd[1873]: ipcc_send_rec[4] failed: Conne
Mar 11 17:24:22 vHost01.squote.de pvestatd[1873]: status update error: Connectio
Mar 11 17:24:22 vHost01.squote.de pvestatd[1873]: status update time (5.012 seco
Mar 11 17:28:07 vHost01.squote.de pvestatd[1873]: modified cpu set for lxc/1022:
lines 1-21/21 (END)...skipping...
● pvestatd.service - PVE Status Daemon
Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2019-03-10 00:46:16 CET; 1 weeks 2 days ago
Main PID: 1873 (pvestatd)
Tasks: 2 (limit: 4915)
Memory: 80.9M
CPU: 2h 46min 53.026s
CGroup: /system.slice/pvestatd.service
├─ 1873 pvestatd
└─22894 lxc-info -n 1040 -p

Mar 10 02:36:27 vHost01.squote.de pvestatd[1873]: modified cpu set for lxc/1030: 6,8-9,11
Mar 10 20:02:08 vHost01.squote.de pvestatd[1873]: modified cpu set for lxc/1022: 1-3,7
Mar 10 20:33:47 vHost01.squote.de pvestatd[1873]: modified cpu set for lxc/1022: 1-2,4,7
Mar 11 17:24:22 vHost01.squote.de pvestatd[1873]: ipcc_send_rec[1] failed: Connection refused
Mar 11 17:24:22 vHost01.squote.de pvestatd[1873]: ipcc_send_rec[2] failed: Connection refused
Mar 11 17:24:22 vHost01.squote.de pvestatd[1873]: ipcc_send_rec[3] failed: Connection refused
Mar 11 17:24:22 vHost01.squote.de pvestatd[1873]: ipcc_send_rec[4] failed: Connection refused
Mar 11 17:24:22 vHost01.squote.de pvestatd[1873]: status update error: Connection refused
Mar 11 17:24:22 vHost01.squote.de pvestatd[1873]: status update time (5.012 seconds)
Mar 11 17:28:07 vHost01.squote.de pvestatd[1873]: modified cpu set for lxc/1022: 0,2-3,7
~
 
Hey,

Code:
root@vHost01:~# systemctl status pve-cluster corosync
● pve-cluster.service - The Proxmox VE cluster filesystem
   Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2019-03-11 17:26:00 CET; 1 weeks 0 days ago
  Process: 3544 ExecStartPost=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
  Process: 3520 ExecStart=/usr/bin/pmxcfs (code=exited, status=0/SUCCESS)
 Main PID: 3530 (pmxcfs)
    Tasks: 7 (limit: 4915)
   Memory: 50.3M
      CPU: 6min 23.931s
   CGroup: /system.slice/pve-cluster.service
           └─3530 /usr/bin/pmxcfs

Mar 19 04:25:59 vHost01.squote.de pmxcfs[3530]: [dcdb] notice: data verification successful
Mar 19 05:25:59 vHost01.squote.de pmxcfs[3530]: [dcdb] notice: data verification successful
Mar 19 06:25:59 vHost01.squote.de pmxcfs[3530]: [dcdb] notice: data verification successful
Mar 19 07:25:59 vHost01.squote.de pmxcfs[3530]: [dcdb] notice: data verification successful
Mar 19 08:25:59 vHost01.squote.de pmxcfs[3530]: [dcdb] notice: data verification successful
Mar 19 09:25:59 vHost01.squote.de pmxcfs[3530]: [dcdb] notice: data verification successful
Mar 19 10:25:59 vHost01.squote.de pmxcfs[3530]: [dcdb] notice: data verification successful
Mar 19 11:25:59 vHost01.squote.de pmxcfs[3530]: [dcdb] notice: data verification successful
Mar 19 12:25:59 vHost01.squote.de pmxcfs[3530]: [dcdb] notice: data verification successful
Mar 19 13:25:59 vHost01.squote.de pmxcfs[3530]: [dcdb] notice: data verification successful

● corosync.service - Corosync Cluster Engine
   Loaded: loaded (/lib/systemd/system/corosync.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2019-03-11 17:26:00 CET; 1 weeks 0 days ago
     Docs: man:corosync
           man:corosync.conf
           man:corosync_overview
 Main PID: 3555 (corosync)
    Tasks: 2 (limit: 4915)
   Memory: 37.6M
      CPU: 1h 51min 9.817s
   CGroup: /system.slice/corosync.service
           └─3555 /usr/sbin/corosync -f

Mar 11 17:26:00 vHost01.squote.de corosync[3555]:  [QUORUM] This node is within the primary component and will provide service.
Mar 11 17:26:00 vHost01.squote.de corosync[3555]:  [QUORUM] Members[0]:
Mar 11 17:26:00 vHost01.squote.de corosync[3555]:  [SERV  ] Service engine loaded: corosync vote quorum service v1.0 [5]
Mar 11 17:26:00 vHost01.squote.de corosync[3555]:  [QB    ] server name: votequorum
Mar 11 17:26:00 vHost01.squote.de corosync[3555]:  [SERV  ] Service engine loaded: corosync cluster quorum service v0.1 [3]
Mar 11 17:26:00 vHost01.squote.de corosync[3555]:  [QB    ] server name: quorum
Mar 11 17:26:00 vHost01.squote.de corosync[3555]:  [TOTEM ] A new membership (152.89.247.253:4) was formed. Members joined: 1
Mar 11 17:26:00 vHost01.squote.de corosync[3555]:  [CPG   ] downlist left_list: 0 received
Mar 11 17:26:00 vHost01.squote.de corosync[3555]:  [QUORUM] Members[1]: 1
Mar 11 17:26:00 vHost01.squote.de corosync[3555]:  [MAIN  ] Completed service synchronization, ready to provide service.

I have only one Maschine
 
I have only one Maschine
was this machine in a cluster at any point in time?

if no, stop corosync, delete /etc/corosync/corosync.conf
and restart pve-cluster and pvestatd

and post the status of them afterwards
 
Code:
root@vHost01:~# systemctl status pve-cluster
● pve-cluster.service - The Proxmox VE cluster filesystem
   Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor pres
   Active: active (running) since Tue 2019-03-19 14:18:54 CET; 5s ago
  Process: 21221 ExecStartPost=/usr/bin/pvecm updatecerts --silent (code=exited,
  Process: 21200 ExecStart=/usr/bin/pmxcfs (code=exited, status=0/SUCCESS)
 Main PID: 21213 (pmxcfs)
    Tasks: 5 (limit: 4915)
   Memory: 13.3M
      CPU: 200ms
   CGroup: /system.slice/pve-cluster.service
           └─21213 /usr/bin/pmxcfs

Mar 19 14:18:53 vHost01.squote.de pmxcfs[21213]: [dcdb] crit: can't initialize s
Mar 19 14:18:53 vHost01.squote.de pmxcfs[21213]: [status] crit: cpg_initialize f
Mar 19 14:18:53 vHost01.squote.de pmxcfs[21213]: [status] crit: can't initialize
Mar 19 14:18:54 vHost01.squote.de systemd[1]: Started The Proxmox VE cluster fil
Mar 19 14:18:59 vHost01.squote.de pmxcfs[21213]: [status] notice: update cluster
Mar 19 14:18:59 vHost01.squote.de pmxcfs[21213]: [status] notice: node has quoru
Mar 19 14:18:59 vHost01.squote.de pmxcfs[21213]: [dcdb] notice: members: 1/21213
Mar 19 14:18:59 vHost01.squote.de pmxcfs[21213]: [dcdb] notice: all data is up t
Mar 19 14:18:59 vHost01.squote.de pmxcfs[21213]: [status] notice: members: 1/212
Mar 19 14:18:59 vHost01.squote.de pmxcfs[21213]: [status] notice: all data is up
lines 1-22/22 (END)...skipping...
● pve-cluster.service - The Proxmox VE cluster filesystem
   Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2019-03-19 14:18:54 CET; 5s ago
  Process: 21221 ExecStartPost=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
  Process: 21200 ExecStart=/usr/bin/pmxcfs (code=exited, status=0/SUCCESS)
 Main PID: 21213 (pmxcfs)
    Tasks: 5 (limit: 4915)
   Memory: 13.3M
      CPU: 200ms
   CGroup: /system.slice/pve-cluster.service
           └─21213 /usr/bin/pmxcfs

Mar 19 14:18:53 vHost01.squote.de pmxcfs[21213]: [dcdb] crit: can't initialize service
Mar 19 14:18:53 vHost01.squote.de pmxcfs[21213]: [status] crit: cpg_initialize failed: 2
Mar 19 14:18:53 vHost01.squote.de pmxcfs[21213]: [status] crit: can't initialize service
Mar 19 14:18:54 vHost01.squote.de systemd[1]: Started The Proxmox VE cluster filesystem.
Mar 19 14:18:59 vHost01.squote.de pmxcfs[21213]: [status] notice: update cluster info (cluster name  vCluster01, version = 1)
Mar 19 14:18:59 vHost01.squote.de pmxcfs[21213]: [status] notice: node has quorum
Mar 19 14:18:59 vHost01.squote.de pmxcfs[21213]: [dcdb] notice: members: 1/21213
Mar 19 14:18:59 vHost01.squote.de pmxcfs[21213]: [dcdb] notice: all data is up to date
Mar 19 14:18:59 vHost01.squote.de pmxcfs[21213]: [status] notice: members: 1/21213
Mar 19 14:18:59 vHost01.squote.de pmxcfs[21213]: [status] notice: all data is up to date

Code:
root@vHost01:~# systemctl status pvestatd.service
● pvestatd.service - PVE Status Daemon
   Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2019-03-10 00:46:16 CET; 1 weeks 2 days ago
 Main PID: 1873 (pvestatd)
    Tasks: 2 (limit: 4915)
   Memory: 80.9M
      CPU: 2h 46min 53.055s
   CGroup: /system.slice/pvestatd.service
           ├─ 1873 pvestatd
           └─22894 lxc-info -n 1040 -p

Mar 10 02:36:27 vHost01.squote.de pvestatd[1873]: modified cpu set for lxc/1030: 6,8-9,11
Mar 10 20:02:08 vHost01.squote.de pvestatd[1873]: modified cpu set for lxc/1022: 1-3,7
Mar 10 20:33:47 vHost01.squote.de pvestatd[1873]: modified cpu set for lxc/1022: 1-2,4,7
Mar 11 17:24:22 vHost01.squote.de pvestatd[1873]: ipcc_send_rec[1] failed: Connection refused
Mar 11 17:24:22 vHost01.squote.de pvestatd[1873]: ipcc_send_rec[2] failed: Connection refused
Mar 11 17:24:22 vHost01.squote.de pvestatd[1873]: ipcc_send_rec[3] failed: Connection refused
Mar 11 17:24:22 vHost01.squote.de pvestatd[1873]: ipcc_send_rec[4] failed: Connection refused
Mar 11 17:24:22 vHost01.squote.de pvestatd[1873]: status update error: Connection refused
Mar 11 17:24:22 vHost01.squote.de pvestatd[1873]: status update time (5.012 seconds)
Mar 11 17:28:07 vHost01.squote.de pvestatd[1873]: modified cpu set for lxc/1022: 0,2-3,7
root@vHost01:~# systemctl restart pvestatd.service
root@vHost01:~# systemctl status pvestatd.service
● pvestatd.service - PVE Status Daemon
   Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2019-03-19 14:19:37 CET; 1s ago
  Process: 21457 ExecStop=/usr/bin/pvestatd stop (code=exited, status=0/SUCCESS)
  Process: 21463 ExecStart=/usr/bin/pvestatd start (code=exited, status=0/SUCCESS)
 Main PID: 21476 (pvestatd)
    Tasks: 1 (limit: 4915)
   Memory: 65.7M
      CPU: 287ms
   CGroup: /system.slice/pvestatd.service
           └─21476 pvestatd

Mar 19 14:19:37 vHost01.squote.de systemd[1]: Starting PVE Status Daemon...
Mar 19 14:19:37 vHost01.squote.de pvestatd[21476]: starting server
Mar 19 14:19:37 vHost01.squote.de systemd[1]: Started PVE Status Daemon.

The Maschien was in a CLuster to Migrate from the Old one.
 
Hey,

yes i do this, than is all fine, but after a few Days the Same Problem. And always reboot is not fine:( I am not alone with this Problem.

So if you will have access to this wrote me an PN we find a way to check this.
 
i guess because you have/had a corosync conf and corosync was started, in a moment where it was disrupted something broke
delete the corosync config, stop corosync, restart the server then hopefully it should not occur again

if that is not the reason, i do not see the real reason in your outputs
 
Good Day,

i have do this, at the moment it´s running.


Code:
root@vHost01:~# 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: active (running) since Sat 2019-03-23 01:28:11 CET; 9h ago
  Process: 2013 ExecStartPost=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
  Process: 1429 ExecStart=/usr/bin/pmxcfs (code=exited, status=0/SUCCESS)
 Main PID: 1489 (pmxcfs)
    Tasks: 6 (limit: 4915)
   Memory: 59.3M
      CPU: 14.073s
   CGroup: /system.slice/pve-cluster.service
           └─1489 /usr/bin/pmxcfs

Mar 23 01:28:10 vHost01.squote.de systemd[1]: Starting The Proxmox VE cluster filesystem...
Mar 23 01:28:11 vHost01.squote.de systemd[1]: Started The Proxmox VE cluster filesystem.

Code:
root@vHost01:~# systemctl status pvestatd.service
● pvestatd.service - PVE Status Daemon
   Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2019-03-23 01:28:11 CET; 9h ago
  Process: 2030 ExecStart=/usr/bin/pvestatd start (code=exited, status=0/SUCCESS)
 Main PID: 2080 (pvestatd)
    Tasks: 1 (limit: 4915)
   Memory: 76.4M
      CPU: 5min 17.858s
   CGroup: /system.slice/pvestatd.service
           └─2080 pvestatd

Mar 23 01:28:11 vHost01.squote.de systemd[1]: Starting PVE Status Daemon...
Mar 23 01:28:11 vHost01.squote.de pvestatd[2080]: starting server
Mar 23 01:28:11 vHost01.squote.de systemd[1]: Started PVE Status Daemon.
Mar 23 01:28:59 vHost01.squote.de pvestatd[2080]: modified cpu set for lxc/1022: 0,5-7
Mar 23 01:29:00 vHost01.squote.de pvestatd[2080]: status update time (38.268 seconds)
Mar 23 01:29:10 vHost01.squote.de pvestatd[2080]: modified cpu set for lxc/1027: 0,5,8-9
Mar 23 01:29:10 vHost01.squote.de pvestatd[2080]: modified cpu set for lxc/1030: 1,4,10-11
 

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!