Proxmox GUI communication failure (0)

[TechLineX]

Hi!

I use a cluster between 3 nodes. 1 of the 3 nodes seemed offline yesterday (GUI showed the server as offline). After a restart of the pvestatd it worked fine again.

Now I wanted to edit a server at the error-host. If i click on a host, i get the error: Connection timed out (596) or communication failure (0).

I already restarted pveproxy and pvestatd. Server is shown as online, stats of the node in proxmox is shown. Only the vmstats are now shown in the panel because of the errors.

Server is pingable accessable through the console or ssh. VMs hosted on the server are also online.

When I try to login with the panel: https://ipoftheerrorhost:8006) I have to login, but I can't login. I get a long time "Please wait" and after that "Login failed. Please try again". If I use the correct or the wrong error, I get the same error.

access.log:

MYIP - - [08/Dec/2016:10:53:12 +0100] "GET / HTTP/1.1" 200 673
MYIP - - [08/Dec/2016:10:53:14 +0100] "GET /api2/json/access/domains HTTP/1.1" 200 159
MYIP - - [08/Dec/2016:10:53:48 +0100] "POST /api2/extjs/access/ticket HTTP/1.1" 596 -
MYIP - - [08/Dec/2016:10:55:11 +0100] "POST /api2/extjs/access/ticket HTTP/1.1" 596 -

I had a problem with an NFS-Server yesterday, could it be hang together?

#News:
Configuration of a VM on the errorhost is loading, but it takes about 1-2 Minutes to load something..

What can I do?

Regards

 

[TechLineX]

Or could it be hang together, that the servers use ssl-certs? the errorhost uses let´s encrypt. the two others (1 uses let´s encrypt, the second uses a self signed).

 

[czechsys]

Confirming issue with package versions:

proxmox-ve: 4.3-75 (running kernel: 4.4.35-1-pve) pve-manager: 4.3-14 (running version: 4.3-14/3a8c61c7) pve-kernel-4.4.35-1-pve: 4.4.35-75 pve-kernel-4.4.21-1-pve: 4.4.21-71 pve-kernel-4.4.24-1-pve: 4.4.24-72 pve-kernel-4.4.19-1-pve: 4.4.19-66 lvm2: 2.02.116-pve3 corosync-pve: 2.4.0-1 libqb0: 1.0-1 pve-cluster: 4.0-48 qemu-server: 4.0-101 pve-firmware: 1.1-10 libpve-common-perl: 4.0-83 libpve-access-control: 4.0-19 libpve-storage-perl: 4.0-70 pve-libspice-server1: 0.12.8-1 vncterm: 1.2-1 pve-docs: 4.3-19 pve-qemu-kvm: 2.7.0-9 pve-container: 1.0-87 pve-firewall: 2.0-33 pve-ha-manager: 1.0-38 ksm-control-daemon: 1.2-1 glusterfs-client: 3.5.2-2+deb8u2 lxc-pve: 2.0.6-2 lxcfs: 2.0.5-pve1 criu: 1.6.0-1 novnc-pve: 0.5-8 smartmontools: 6.5+svn4324-1~pve80 zfsutils: 0.6.5.8-pve13~bpo80 openvswitch-switch: 2.6.0-2

[08/Dec/2016:14:54:14 +0100] "POST /api2/extjs/access/ticket HTTP/1.1" 596 -
[08/Dec/2016:14:54:35 +0100] "GET / HTTP/1.1" 200 671
[08/Dec/2016:14:54:36 +0100] "GET /pve2/css/fonts/fontawesome-webfont.woff2?v=4.5.0 HTTP/1.1" 200 66624
[08/Dec/2016:14:54:36 +0100] "GET /api2/json/access/domains HTTP/1.1" 200 238
[08/Dec/2016:14:55:09 +0100] "POST /api2/extjs/access/ticket HTTP/1.1" 596 -
[08/Dec/2016:14:55:10 +0100] "GET /pve2/ext6/theme-crisp/resources/images/shared/icon-error.png HTTP/1.1" 200 18494
[08/Dec/2016:14:55:58 +0100] "POST /api2/extjs/access/ticket HTTP/1.1" 200 654
[08/Dec/2016:14:55:58 +0100] "GET /api2/extjs/version?_dc=1481205358318 HTTP/1.1" 200 92
[08/Dec/2016:14:55:58 +0100] "GET /api2/extjs/nodes/localhost/subscription?_dc=1481205358319 HTTP/1.1" 200 129
[08/Dec/2016:14:55:58 +0100] "GET /api2/json/cluster/resources HTTP/1.1" 200 1503
[08/Dec/2016:14:55:58 +0100] "GET /api2/json/cluster/resources HTTP/1.1" 200 1494
[08/Dec/2016:14:55:59 +0100] "GET /api2/json/cluster/tasks HTTP/1.1" 200 3099
[08/Dec/2016:14:56:02 +0100] "GET /api2/json/cluster/resources HTTP/1.1" 200 1510
[08/Dec/2016:14:56:02 +0100] "GET /api2/json/cluster/tasks HTTP/1.1" 200 3099
[08/Dec/2016:14:56:33 +0100] "GET /api2/json/nodes/prox1/storage/local/status HTTP/1.1" 500 -

Able to login with AD account with "pve-manager: 4.3-9 (running version: 4.3-9/f7c6f0cd)", but same errors on updated node:
Unable to login with AD account. Able to login via PAM.
Unable to see Content of the storage -> "communication error".
No graphs working.

 

[TechLineX]

apt-get update
apt-get dist-upgrade
reboot

Solved the problem for the moment.