all VMs fail to have a connection

C

Commissar0617

New Member
Proxmox Subscriber
Feb 29, 2020
2
0
1
31
all my VMs are unable to be connected with novnc or SSH, after i just upgraded to 7.1-7 last night. they were working this morning, but are now not working. tried restarting the VMs, they did restart, but did not help. tried removing and readding the network device. no luck. my windows server manager appears to be working between my AD DC in a vm, and my PC, but it shows an error about long disk write times.

host is connectable by ssh, but not by console.


Bash: 
Dec 24 21:35:04 PVE1 pvedaemon[782891]: <root@pam> update VM 105: -net0 virtio,bridge=vmbr0,firewall=1
Dec 24 21:35:25 PVE1 pvedaemon[782891]: <root@pam> update VM 104: -net0 virtio,bridge=vmbr0,firewall=1
Dec 24 21:35:27 PVE1 pvedaemon[952734]: start VM 104: UPID:PVE1:000E899E:0091C694:61C6917F:qmstart:104:root@pam:
Dec 24 21:35:27 PVE1 pvedaemon[782891]: <root@pam> starting task UPID:PVE1:000E899E:0091C694:61C6917F:qmstart:104:root@pam:
Dec 24 21:35:27 PVE1 pvedaemon[782891]: <root@pam> end task UPID:PVE1:000E899E:0091C694:61C6917F:qmstart:104:root@pam: OK
Dec 24 21:35:29 PVE1 pvedaemon[952932]: start VM 105: UPID:PVE1:000E8A64:0091C7A1:61C69181:qmstart:105:root@pam:
Dec 24 21:35:29 PVE1 pvedaemon[554700]: <root@pam> starting task UPID:PVE1:000E8A64:0091C7A1:61C69181:qmstart:105:root@pam:
Dec 24 21:35:30 PVE1 pvedaemon[554700]: <root@pam> end task UPID:PVE1:000E8A64:0091C7A1:61C69181:qmstart:105:root@pam: OK
Dec 24 21:35:47 PVE1 pveproxy[859095]: worker exit
Dec 24 21:35:47 PVE1 pveproxy[2739]: worker 859095 finished
Dec 24 21:35:47 PVE1 pveproxy[2739]: starting 1 worker(s)
Dec 24 21:35:47 PVE1 pveproxy[2739]: worker 954992 started
Dec 24 21:36:10 PVE1 pvedaemon[956597]: starting vnc proxy UPID:PVE1:000E98B5:0091D78D:61C691AA:vncproxy:105:root@pam:
Dec 24 21:36:10 PVE1 pvedaemon[554700]: <root@pam> starting task UPID:PVE1:000E98B5:0091D78D:61C691AA:vncproxy:105:root@pam:
Dec 24 21:36:16 PVE1 pvedaemon[582288]: worker exit
Dec 24 21:36:16 PVE1 pvedaemon[2718]: worker 582288 finished
Dec 24 21:36:16 PVE1 pvedaemon[2718]: starting 1 worker(s)
Dec 24 21:36:16 PVE1 pvedaemon[2718]: worker 957144 started
Dec 24 21:36:20 PVE1 pvedaemon[956597]: connection timed out
Dec 24 21:36:20 PVE1 pvedaemon[554700]: <root@pam> end task UPID:PVE1:000E98B5:0091D78D:61C691AA:vncproxy:105:root@pam: connection timed out
Dec 24 21:36:23 PVE1 pvedaemon[957592]: starting vnc proxy UPID:PVE1:000E9C98:0091DCBF:61C691B7:vncproxy:105:root@pam:
Dec 24 21:36:23 PVE1 pvedaemon[554700]: <root@pam> starting task UPID:PVE1:000E9C98:0091DCBF:61C691B7:vncproxy:105:root@pam:
Dec 24 21:36:33 PVE1 pvedaemon[957592]: connection timed out
Dec 24 21:36:33 PVE1 pvedaemon[554700]: <root@pam> end task UPID:PVE1:000E9C98:0091DCBF:61C691B7:vncproxy:105:root@pam: connection timed out
Dec 24 21:38:39 PVE1 pvedaemon[2718]: received signal TERM
Dec 24 21:38:39 PVE1 pvedaemon[2718]: server closing
Dec 24 21:38:39 PVE1 pvedaemon[782891]: worker exit
Dec 24 21:38:39 PVE1 pvedaemon[554700]: worker exit
Dec 24 21:38:39 PVE1 pvedaemon[2718]: worker 782891 finished
Dec 24 21:38:39 PVE1 pvedaemon[2718]: worker 554700 finished
Dec 24 21:38:39 PVE1 pvedaemon[2718]: worker 957144 finished
Dec 24 21:38:39 PVE1 pvedaemon[2718]: server stopped
Dec 24 21:38:40 PVE1 pvedaemon[185465]: Failed to run vncproxy.
Dec 24 21:38:40 PVE1 systemd[1]: pvedaemon.service: Succeeded.
Dec 24 21:38:40 PVE1 systemd[1]: pvedaemon.service: Consumed 4min 37.424s CPU time.
Dec 24 21:38:41 PVE1 pveproxy[253004]: worker exit
Dec 24 21:38:41 PVE1 pvedaemon[964631]: starting server
Dec 24 21:38:41 PVE1 pvedaemon[964631]: starting 3 worker(s)
Dec 24 21:38:41 PVE1 pvedaemon[964631]: worker 964632 started
Dec 24 21:38:41 PVE1 pvedaemon[964631]: worker 964633 started
Dec 24 21:38:41 PVE1 pvedaemon[964631]: worker 964634 started
Dec 24 21:38:42 PVE1 pveproxy[2739]: received signal TERM
Dec 24 21:38:42 PVE1 pveproxy[2739]: server closing
Dec 24 21:38:42 PVE1 pveproxy[954992]: worker exit
Dec 24 21:38:42 PVE1 pveproxy[918606]: worker exit
Dec 24 21:38:42 PVE1 pveproxy[857452]: worker exit
Dec 24 21:38:42 PVE1 pveproxy[2739]: worker 857452 finished
Dec 24 21:38:42 PVE1 pveproxy[2739]: worker 954992 finished
Dec 24 21:38:42 PVE1 pveproxy[2739]: worker 918606 finished
Dec 24 21:38:42 PVE1 pveproxy[2739]: server stopped
Dec 24 21:38:43 PVE1 systemd[1]: pveproxy.service: Succeeded.
Dec 24 21:38:43 PVE1 systemd[1]: pveproxy.service: Consumed 6min 11.074s CPU time.
Dec 24 21:38:44 PVE1 pveproxy[964785]: starting server
Dec 24 21:38:44 PVE1 pveproxy[964785]: starting 3 worker(s)
Dec 24 21:38:44 PVE1 pveproxy[964785]: worker 964786 started
Dec 24 21:38:44 PVE1 pveproxy[964785]: worker 964787 started
Dec 24 21:38:44 PVE1 pveproxy[964785]: worker 964788 started
Dec 24 21:38:57 PVE1 pvedaemon[964634]: <root@pam> successful auth for user 'root@pam'
Dec 24 21:38:58 PVE1 pvedaemon[965537]: starting vnc proxy UPID:PVE1:000EBBA1:009218F8:61C69252:vncproxy:105:root@pam:
Dec 24 21:38:58 PVE1 pvedaemon[964632]: <root@pam> starting task UPID:PVE1:000EBBA1:009218F8:61C69252:vncproxy:105:root@pam:
Dec 24 21:39:00 PVE1 pvedaemon[965667]: starting vnc proxy UPID:PVE1:000EBC23:009219E7:61C69254:vncproxy:106:root@pam:
Dec 24 21:39:00 PVE1 pvedaemon[964633]: <root@pam> starting task UPID:PVE1:000EBC23:009219E7:61C69254:vncproxy:106:root@pam:
Dec 24 21:39:01 PVE1 pvedaemon[965788]: starting vnc proxy UPID:PVE1:000EBC9C:00921A57:61C69255:vncproxy:105:root@pam:
Dec 24 21:39:01 PVE1 pvedaemon[964634]: <root@pam> starting task UPID:PVE1:000EBC9C:00921A57:61C69255:vncproxy:105:root@pam:
Dec 24 21:39:02 PVE1 pvedaemon[965790]: starting vnc proxy UPID:PVE1:000EBC9E:00921AE5:61C69256:vncproxy:104:root@pam:
Dec 24 21:39:02 PVE1 pvedaemon[964633]: <root@pam> starting task UPID:PVE1:000EBC9E:00921AE5:61C69256:vncproxy:104:root@pam:
Dec 24 21:39:04 PVE1 pvedaemon[965964]: starting vnc proxy UPID:PVE1:000EBD4C:00921BAD:61C69258:vncproxy:103:root@pam:
Dec 24 21:39:04 PVE1 pvedaemon[964634]: <root@pam> starting task UPID:PVE1:000EBD4C:00921BAD:61C69258:vncproxy:103:root@pam:
Dec 24 21:39:05 PVE1 pvedaemon[965967]: starting vnc proxy UPID:PVE1:000EBD4F:00921C0B:61C69259:vncproxy:101:root@pam:
Dec 24 21:39:05 PVE1 pvedaemon[964632]: <root@pam> starting task UPID:PVE1:000EBD4F:00921C0B:61C69259:vncproxy:101:root@pam:
Dec 24 21:39:07 PVE1 pvedaemon[966070]: starting vnc proxy UPID:PVE1:000EBDB6:00921CAD:61C6925B:vncproxy:100:root@pam:
Dec 24 21:39:07 PVE1 pvedaemon[964634]: <root@pam> starting task UPID:PVE1:000EBDB6:00921CAD:61C6925B:vncproxy:100:root@pam:
Dec 24 21:39:08 PVE1 pvedaemon[965537]: connection timed out
Dec 24 21:39:08 PVE1 pvedaemon[964632]: <root@pam> end task UPID:PVE1:000EBBA1:009218F8:61C69252:vncproxy:105:root@pam: connection timed out
Dec 24 21:39:10 PVE1 pvedaemon[965667]: connection timed out
Dec 24 21:39:10 PVE1 pvedaemon[964633]: <root@pam> end task UPID:PVE1:000EBC23:009219E7:61C69254:vncproxy:106:root@pam: connection timed out
Dec 24 21:39:11 PVE1 pvedaemon[965788]: connection timed out
Dec 24 21:39:11 PVE1 pvedaemon[964634]: <root@pam> end task UPID:PVE1:000EBC9C:00921A57:61C69255:vncproxy:105:root@pam: connection timed out
Dec 24 21:39:12 PVE1 pvedaemon[965790]: connection timed out
Dec 24 21:39:12 PVE1 pvedaemon[964633]: <root@pam> end task UPID:PVE1:000EBC9E:00921AE5:61C69256:vncproxy:104:root@pam: connection timed out
Dec 24 21:39:14 PVE1 pvedaemon[965964]: connection timed out
Dec 24 21:39:14 PVE1 pvedaemon[964634]: <root@pam> end task UPID:PVE1:000EBD4C:00921BAD:61C69258:vncproxy:103:root@pam: connection timed out
Dec 24 21:39:15 PVE1 pvedaemon[965967]: connection timed out
Dec 24 21:39:15 PVE1 pvedaemon[964632]: <root@pam> end task UPID:PVE1:000EBD4F:00921C0B:61C69259:vncproxy:101:root@pam: connection timed out
Dec 24 21:39:17 PVE1 pvedaemon[966070]: connection timed out
Dec 24 21:39:17 PVE1 pvedaemon[964634]: <root@pam> end task UPID:PVE1:000EBDB6:00921CAD:61C6925B:vncproxy:100:root@pam: connection timed out
root@PVE1:~#
 
Last edited:
ok, so i reinstalled proxmox and restored from backup. the consoles now work in chrome, but not firefox, and are extremely delayed. like 20+ seconds typing delay

EDIT: delay likely due to vm restore from backups. and the vnc decided to work no. go figure.
 
Last edited:
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom