Quorum issue

[justin]

Hi all,

After just a reboot, my 2 nodes can't see content of the other in web interface.
Add this, when I try to make a vm backup I get this error :
INFO: Use of uninitialized value $raw in pattern match (m//) at /usr/share/perl5/PVE/AccessControl.pm line 711.
INFO: unable to open file '/etc/pve/nodes/iet1/qemu-server/106.conf.tmp.17215' - Permission denied

I check the cluster status and it's look fine :
root@iet2:~# pvecm status
Quorum information
------------------
Date: Mon Nov 7 14:57:00 2016
Quorum provider: corosync_votequorum
Nodes: 2
Node ID: 0x00000002
Ring ID: 1432
Quorate: Yes

Votequorum information
----------------------
Expected votes: 2
Highest expected: 2
Total votes: 2
Quorum: 2
Flags: Quorate

Membership information
----------------------
Nodeid Votes Name
0x00000002 1 192.168.254.239 (local)
0x00000001 1 192.168.254.240

PVE Version also seems to be ok :
root@iet2:~# pveversion -v
proxmox-ve: 4.0-14 (running kernel: 4.2.1-1-pve)
pve-manager: 4.0-43 (running version: 4.0-43/60482016)
pve-kernel-4.2.1-1-pve: 4.2.1-14
lvm2: 2.02.116-pve1
corosync-pve: 2.3.5-1
libqb0: 0.17.2-1
pve-cluster: 4.0-21
qemu-server: 4.0-28
pve-firmware: 1.1-7
libpve-common-perl: 4.0-25
libpve-access-control: 4.0-8
libpve-storage-perl: 4.0-24
pve-libspice-server1: 0.12.5-1
vncterm: 1.2-1
pve-qemu-kvm: 2.4-9
pve-container: 1.0-2
pve-firewall: 2.0-12
pve-ha-manager: 1.0-9
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.3-1
lxcfs: 0.9-pve2
cgmanager: 0.37-pve2
criu: 1.6.0-1

Any clue about this error ?
Thanks,
Justin

 

[dcsapak]

please update to the latest version and try again (current is 4.3)

 

[justin]

Thanks for your fast reply.
In fact with version 3 once I make upgrade and I lost internal network connexion (see post here https://forum.proxmox.com/threads/l...er-upgrade-from-3-1-to-3-4.23429/#post-118757)
Since that, I'm very very cold to upgrade a stable proxmox environment, I don't want to loose all my vm !

Anyway once by month I backup all my vm & reboot all nodes and I'd like understand what's happend with this issue...

 

[fabian]

Thanks for your fast reply.
In fact with version 3 once I make upgrade and I lost internal network connexion (see post here https://forum.proxmox.com/threads/l...er-upgrade-from-3-1-to-3-4.23429/#post-118757)
Since that, I'm very very cold to upgrade a stable proxmox environment, I don't want to loose all my vm !

Anyway once by month I backup all my vm & reboot all nodes and I'd like understand what's happend with this issue...

you can't have your cake and eat it too. if you run a very outdated, unsupported version - you have to live with potential bugs and little help.

 

[justin]

Ok, in case of :
service pve-cluster restart

solve everything.