On Tue, Apr 10, 2012 at 11:05 PM, Timo Schäpe <scha...@dfn-cert.de> wrote:
> Hi,
> for whom it may interest, here's something that cost me a whole day of work:
>
> I used CTS to test my cluster configuration and it worked fine. For
> debugging a resource agent I switched on the debug output in corosync.conf:
>
> logging {
> [...]
> debug: on
> [...]
> }
>
> After I fixed the bug, I forgot to switch debug output off. This caused
> most of the CTS tests to fail with this warning:
>
> CTS: Warn: Startup pattern not found: myhost crmd:.*The local CRM is
> operational
>
> After I switched debug output off, the CTS worked fine as before.
We've since added a BadNews pattern that looks for syslog messages
being dropped/throttled.
How was your experience with CTS otherwise?
Periodically I try to improve the usability so that eventually
non-developers can use it, it would be interesting to hear how we're
doing.
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
