Tinsy little problem when logging into the web gui

N

nethfel

Member
Dec 26, 2014
151
0
16
Hi all,

I know I've seen this in the forum before but I can't seem to figure out the the right search terms to find it.

Basically - when I log in now, for a few seconds just after logging in, 2 nodes show red. They aren't offline, it's consistently two nodes and they only show red for about 3 seconds then they show green. If I close the tab that has the gui open and make a new connection to the server (without logging out) the system connects and shows all green, it's only if I log off and log back in does this happen. It doesn't matter what node I log into the gui through, (even if it's one of the two nodes that show red then green). All three show the same version data:

pve-1 (this was the machine that had to be rebuilt)
Code: 
proxmox-ve-2.6.32: 3.4-150 (running kernel: 2.6.32-37-pve)
pve-manager: 3.4-3 (running version: 3.4-3/2fc72fee)
pve-kernel-2.6.32-37-pve: 2.6.32-150
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-2
pve-cluster: 3.0-16
qemu-server: 3.4-3
pve-firmware: 1.1-4
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-32
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-8
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

pve-2
Code: 
proxmox-ve-2.6.32: 3.4-150 (running kernel: 2.6.32-37-pve)
pve-manager: 3.4-3 (running version: 3.4-3/2fc72fee)
pve-kernel-2.6.32-37-pve: 2.6.32-150
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-2
pve-cluster: 3.0-16
qemu-server: 3.4-3
pve-firmware: 1.1-4
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-32
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-8
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1



pve-3
Code: 
proxmox-ve-2.6.32: 3.4-150 (running kernel: 2.6.32-37-pve)
pve-manager: 3.4-3 (running version: 3.4-3/2fc72fee)
pve-kernel-2.6.32-37-pve: 2.6.32-150
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-2
pve-cluster: 3.0-16
qemu-server: 3.4-3
pve-firmware: 1.1-4
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-32
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-8
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1


All three show:
pvecm nodes
Code: 
Node  Sts   Inc   Joined               Name
   1   M   1044   2015-04-30 08:07:09  pve-1
   2   M   1020   2015-04-30 08:05:32  pve-2
   3   M   1028   2015-04-30 08:06:06  pve-3


And the statuses:

Code: 
root@pve-1:/usr/share/pve-manager/ext4# pvecm status
Version: 6.2.0
Config Version: 7
Cluster Name: pvecluster
Cluster Id: 48308
Cluster Member: Yes
Cluster Generation: 1044
Membership state: Cluster-Member
Nodes: 3
Expected votes: 3
Total votes: 3
Node votes: 1
Quorum: 2  
Active subsystems: 1
Flags: 
Ports Bound: 0  
Node name: pve-1
Node ID: 1
Multicast addresses: 239.192.188.113 
Node addresses: 172.16.6.10 


root@pve-2:/usr/share/pve-manager/ext4# pvecm status
Version: 6.2.0
Config Version: 7
Cluster Name: pvecluster
Cluster Id: 48308
Cluster Member: Yes
Cluster Generation: 1044
Membership state: Cluster-Member
Nodes: 3
Expected votes: 3
Total votes: 3
Node votes: 1
Quorum: 2  
Active subsystems: 5
Flags: 
Ports Bound: 0  
Node name: pve-2
Node ID: 2
Multicast addresses: 239.192.188.113 
Node addresses: 172.16.6.11 


root@pve-3:/var/log# pvecm status
Version: 6.2.0
Config Version: 7
Cluster Name: pvecluster
Cluster Id: 48308
Cluster Member: Yes
Cluster Generation: 1044
Membership state: Cluster-Member
Nodes: 3
Expected votes: 3
Total votes: 3
Node votes: 1
Quorum: 2  
Active subsystems: 5
Flags: 
Ports Bound: 0  
Node name: pve-3
Node ID: 3
Multicast addresses: 239.192.188.113 
Node addresses: 172.16.6.12

I also see nothing in the logs that would indicate any sort of problem.

ps - I should note it take almost exactly 4 seconds after I log in for both of the nodes to go from red to green.
 
Last edited:
Update:
Now that I'm at home using a VPN connection into work, I see the problem a little differently. When I first log in, for the first 4 - 4.5 seconds, the node icons on the left show red, but the summary on the right shows them all green. After that ~4-4.5 seconds, it shows all green. The VMs are working normally and nothing changes in that regard when I exit the web gui. I'm just not sure what could be causing it.

Here's an unlisted youtube link to show what I'm seeing which may explain it a bit better:

https://youtu.be/hKvKOCc0AgU

I'll also note, that after the first login, if I log off and then log back on, it doesn't do the red/green swap. It only happens when I first launch the browser (made me wonder if it was a caching issue, but I don't remember having this problem in the past).
 
this is the expected behavior, so nothing wrong here.
 
Ok, interesting - is it like an update or something where it's still scanning the various nodes?
 
yes, the GUI updates the page regularly.
 
I guess I just found it odd to show all red then switch to green, I figured on first login, the gui would/should show an initial status that is accurate to the state of the machines instead of what appears to be some sort of a cached state.
 
You must log in or register to reply here.
Top Bottom