> That probably means that someone (i.e., you ;-) needs to dig > more into the logs of corosync & pacemaker. There's bound to > be a clue there; pacemaker is many things, but definitely not > shy when it comes to logging. > > > Regards, > Lars
Yes, that's what it probably means. :-) For what it is worth, I did in fact read through the logs looking for suspicious entries before I posted this question. Of course I also Googled first, too. Nothing jumped out, so I figured someone might be able to give me the clue that I am obviously overlooking. We have 3 or 4 other corosync-based clusters in production so we are not unfamiliar with the technology. I'll look at the logs again. -- Eric Robinson Disclaimer - October 31, 2012 This email and any files transmitted with it are confidential and intended solely for 'General Linux-HA mailing list'. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physicians' Managed Care or Physician Select Management. Warning: Although Physicians' Managed Care or Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments. This disclaimer was added by Policy Patrol: http://www.policypatrol.com/ _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
