Hallo
nach einem Debian upgrade von 8 auf 9 und einem reboot wollte der KVM nicht mehr booten
als ich via Proxmox zugreifen wollte klappte dies auch nicht.
proxmox-ve: 5.2-2 (running kernel: 4.15.18-1-pve)
leider habe ich nach dem Reboot vom Proxmox selber keinen zugriff mehr via GUI auf den Server.
via telnet habe ich zugriff und kann kommandos absetzen.
Mir scheint das alle KVM nicht gebootet haben...
ohne GUI bin ich ein wenig in Not ;-(
# qm list
ipcc_send_rec[1] failed: Connection refused
ipcc_send_rec[2] failed: Connection refused
ipcc_send_rec[3] failed: Connection refused
Unable to load access control list: Connection refused
oder auch
tail /var/log/daemon.log
Jul 10 20:44:01 srv-03 systemd[1]: pvesr.service: Failed with result 'exit-code'.
Jul 10 20:45:00 srv-03 systemd[1]: Starting Proxmox VE replication runner...
Jul 10 20:45:01 srv-03 pvesr[4361]: ipcc_send_rec[1] failed: Connection refused
Jul 10 20:45:01 srv-03 pvesr[4361]: ipcc_send_rec[2] failed: Connection refused
Jul 10 20:45:01 srv-03 pvesr[4361]: ipcc_send_rec[3] failed: Connection refused
Jul 10 20:45:01 srv-03 pvesr[4361]: Unable to load access control list: Connection refused
Jul 10 20:45:01 srv-03 systemd[1]: pvesr.service: Main process exited, code=exited, status=111/n/a
Jul 10 20:45:01 srv-03 systemd[1]: Failed to start Proxmox VE replication runner.
Jul 10 20:45:01 srv-03 systemd[1]: pvesr.service: Unit entered failed state.
Jul 10 20:45:01 srv-03 systemd[1]: pvesr.service: Failed with result 'exit-code'.
oder auch
systemctl status pveproxy
? pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2018-07-10 20:28:52 CEST; 17min ago
Process: 2804 ExecStart=/usr/bin/pveproxy start (code=exited, status=255)
CPU: 668ms
Jul 10 20:28:26 srv-03.kozo.ch systemd[1]: Starting PVE API Proxy Server...
Jul 10 20:28:52 srv-03.kozo.ch pveproxy[2804]: start failed - failed to get address info for: srv-03: Temporary failure in name resolution
Jul 10 20:28:52 srv-03.kozo.ch pveproxy[2804]: start failed - failed to get address info for: srv-03: Temporary failure in name resolution
Jul 10 20:28:52 srv-03.kozo.ch systemd[1]: pveproxy.service: Control process exited, code=exited status=255
Jul 10 20:28:52 srv-03.kozo.ch systemd[1]: Failed to start PVE API Proxy Server.
Jul 10 20:28:52 srv-03.kozo.ch systemd[1]: pveproxy.service: Unit entered failed state.
Jul 10 20:28:52 srv-03.kozo.ch systemd[1]: pveproxy.service: Failed with result 'exit-code'.
was kann ich machen?
gruss
vincent
nach einem Debian upgrade von 8 auf 9 und einem reboot wollte der KVM nicht mehr booten
als ich via Proxmox zugreifen wollte klappte dies auch nicht.
proxmox-ve: 5.2-2 (running kernel: 4.15.18-1-pve)
leider habe ich nach dem Reboot vom Proxmox selber keinen zugriff mehr via GUI auf den Server.
via telnet habe ich zugriff und kann kommandos absetzen.
Mir scheint das alle KVM nicht gebootet haben...
ohne GUI bin ich ein wenig in Not ;-(
# qm list
ipcc_send_rec[1] failed: Connection refused
ipcc_send_rec[2] failed: Connection refused
ipcc_send_rec[3] failed: Connection refused
Unable to load access control list: Connection refused
oder auch
tail /var/log/daemon.log
Jul 10 20:44:01 srv-03 systemd[1]: pvesr.service: Failed with result 'exit-code'.
Jul 10 20:45:00 srv-03 systemd[1]: Starting Proxmox VE replication runner...
Jul 10 20:45:01 srv-03 pvesr[4361]: ipcc_send_rec[1] failed: Connection refused
Jul 10 20:45:01 srv-03 pvesr[4361]: ipcc_send_rec[2] failed: Connection refused
Jul 10 20:45:01 srv-03 pvesr[4361]: ipcc_send_rec[3] failed: Connection refused
Jul 10 20:45:01 srv-03 pvesr[4361]: Unable to load access control list: Connection refused
Jul 10 20:45:01 srv-03 systemd[1]: pvesr.service: Main process exited, code=exited, status=111/n/a
Jul 10 20:45:01 srv-03 systemd[1]: Failed to start Proxmox VE replication runner.
Jul 10 20:45:01 srv-03 systemd[1]: pvesr.service: Unit entered failed state.
Jul 10 20:45:01 srv-03 systemd[1]: pvesr.service: Failed with result 'exit-code'.
oder auch
systemctl status pveproxy
? pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2018-07-10 20:28:52 CEST; 17min ago
Process: 2804 ExecStart=/usr/bin/pveproxy start (code=exited, status=255)
CPU: 668ms
Jul 10 20:28:26 srv-03.kozo.ch systemd[1]: Starting PVE API Proxy Server...
Jul 10 20:28:52 srv-03.kozo.ch pveproxy[2804]: start failed - failed to get address info for: srv-03: Temporary failure in name resolution
Jul 10 20:28:52 srv-03.kozo.ch pveproxy[2804]: start failed - failed to get address info for: srv-03: Temporary failure in name resolution
Jul 10 20:28:52 srv-03.kozo.ch systemd[1]: pveproxy.service: Control process exited, code=exited status=255
Jul 10 20:28:52 srv-03.kozo.ch systemd[1]: Failed to start PVE API Proxy Server.
Jul 10 20:28:52 srv-03.kozo.ch systemd[1]: pveproxy.service: Unit entered failed state.
Jul 10 20:28:52 srv-03.kozo.ch systemd[1]: pveproxy.service: Failed with result 'exit-code'.
was kann ich machen?
gruss
vincent