Search results

Well, switched nodes to use transport="udpu" in cluster.conf - cluster gets quorum. Will check it for a few days in bridge, then, will try bonding. Seems to be some problems with multicast: hardware or linux kernel, NIC drivers etc. Multicast node addresses don't cover 224.x.x.x range, used for...

I'm sorry about that. Sometimes forum gives nothing as an answer to my post, so, I send post again, thinking that error occurs. Will not do this more. This is a forum - maybe someone else knows :)

Not only with specific node (virt2). Here's logs from two other nodes: virt1 - cluster main node: Nov 21 09:15:46 corosync [TOTEM ] A processor failed, forming new configuration. Nov 21 09:15:58 corosync [CLM ] CLM CONFIGURATION CHANGE Nov 21 09:15:58 corosync [CLM ] New Configuration...

cesarpk Thanks for the answers. First, I tried with balance-xor with no success - cluster didn't collect neither with service restarting nor rebooting. Tried for 1 day. Then - active-backup - no success. Waited for 1 day. Switched to bridge mode with no switch trunking and bonding on...

cesarpk Thanks a lot for the answer. Ok, so seems to be problem with bonding type balance-rr. So, I'll change it, first, to balance-xor, for example... Thanks all for the help. I'll change bond type and paste here results.

macday Thanks for the reply. I tried different things of node turning and off, rebooting in some order or randomly - found no system in this. spirit Thanks a lot. I'm also thinking, that problem may be in bonding. No, i haven't try yet another bonding modes - old switch firmware can't do...

It's clear from documentation. Simple restart cman (and other services - see my post #1) doesn't work almost in all cases of quorum lose. But if I reboot problem node, it stops and starts these services too and rebooting helps. So, restarting cman with no reboot does nothing and restarting...

Multicast is OK - first thing, that was checked and re-checked. root@virt2:~# asmping 224.0.0.1 192.168.0.211 asmping joined (S,G) = (*,224.0.0.234) pinging 192.168.0.211 from 192.168.0.212 unicast from 192.168.0.211, seq=1 dist=0 time=0.214 ms multicast from 192.168.0.211, seq=1 dist=0...

root@virt2:~# service cman start Starting cluster: Checking if cluster has been disabled at boot... [ OK ] Checking Network Manager... [ OK ] Global setup... [ OK ] Loading kernel modules... [ OK ] Mounting configfs... [ OK ] Starting cman... [ OK ]...

Sorry, this thread is doubled, see here: http://forum.proxmox.com/threads/11773-Permanently-lose-quroum

Hi, aLL I have 3 servers joined in cluster. Each server has 2 NIC, joined to bond0 on each server. Servers connected with Nortel BayStack 5510 switch, server cards from each server joined to Multilink Trunk. Switch allows multicast. Usually, once or twice a week servers lose quorum. One, or...

Hi, aLL I have 3 servers in cluster, connected by Nortel BayStack 5510 switch. All servers have 2 NICs, joined in trunk on switch. Multicast is allowed and works. Hardware - servers, switch, connections, power etc. - are OK Permanently, once a week, maybe once in two weeks, one of the...