On Mon, 2006-12-18 at 11:14 +0000, Frederik Ferner wrote: > Hi List, > > I am currently testing Redhat Cluster Suite for a number of two node > clusters accessing EMC storage systems. Everything seems to be running > fine expect for qdisk. > > On Friday we had a network problem during which the nodes were still > able to see each other but none of the addresses used in my heuristics > for qdisk. The result was not what I expected, when the network came > back, both nodes claimed to be master. > Dec 15 10:31:47 duoserv2 ccsd[5595]: Cluster is quorate. Allowing connections. > Dec 15 10:31:50 duoserv2 clurgmgrd: [7950]: <info> /dev/mapper/logs1-logs1 is not mounted > Dec 15 10:31:51 duoserv2 qdiskd[31393]: <crit> Critical Error: More than one master found! > Dec 15 10:31:51 duoserv2 qdiskd[31393]: <crit> A master exists, but it's not me?! > Dec 15 10:31:52 duoserv2 qdiskd[31393]: <info> Node 1 is the master > ... > > At the same time on the second node: > Dec 15 10:31:45 duoserv1 qdiskd[316]: <notice> Score sufficient for master operation (5/3; max=6); upgrading > Dec 15 10:31:46 duoserv1 qdiskd[316]: <info> Assuming master role > Dec 15 10:31:47 duoserv1 kernel: CMAN: quorum regained, resuming activity > Dec 15 10:31:47 duoserv1 ccsd[5624]: Cluster is quorate. Allowing connections. > Dec 15 10:31:47 duoserv1 clurgmgrd[3631]: <notice> Quorum Achieved > Dec 15 10:31:51 duoserv1 qdiskd[316]: <crit> Critical Error: More than one master found! > Dec 15 10:31:52 duoserv1 qdiskd[316]: <info> Node 2 is the master > Dec 15 10:31:52 duoserv1 qdiskd[316]: <crit> Critical Error: More than one master found! > ... > > This continues until I finally notice and restart qdiskd on both nodes, > when they agree on one master again. This should never happen. Please file a bugzilla. -- Lon
Attachment:
signature.asc
Description: This is a digitally signed message part
-- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
