Am Freitag, 5. Februar 2010 12:03:44 schrieb Andrew Beekhof: > Nothing there looks even remotely relevant. > Its also highly unlikely that I managed to make a change that > resurrected the exact same symptom from 1.0.5 (which I also did > nothing to actually fix - except add logging thats not been triggered > here).
Fully agree. I cannot explain myself. Perhaps a new bug? > What does the cluster do if you manually set a value for > expected-quorum-votes? Does the value stay set in the CIB or get > erased? the value stays in the CIB but is not evaluated for the quorum descision. > I can't imagine that its influencing quorum either. > This is the only line indicating a value change, and its set to the > correct value: > > Feb 4 21:22:22 debian2 corosync[6221]: [pcmk ] info: > update_expected_votes: Expected quorum votes 1024 -> 2 > > Strange Very strange, indeed. -- Dr. Michael Schwartzkopff MultiNET Services GmbH Addresse: Bretonischer Ring 7; 85630 Grasbrunn; Germany Tel: +49 - 89 - 45 69 11 0 Fax: +49 - 89 - 45 69 11 21 mob: +49 - 174 - 343 28 75 mail: mi...@multinet.de web: www.multinet.de Sitz der Gesellschaft: 85630 Grasbrunn Registergericht: Amtsgericht München HRB 114375 Geschäftsführer: Günter Jurgeneit, Hubert Martens --- PGP Fingerprint: F919 3919 FF12 ED5A 2801 DEA6 AA77 57A4 EDD8 979B Skype: misch42 _______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
