On 02/07/2013, at 8:20 PM, Lars Marowsky-Bree <l...@suse.com> wrote:
> On 2013-07-02T20:12:08, Andrew Beekhof <and...@beekhof.net> wrote: > >>> It seems related to the number of times I poll the CIB, too; I seem to >>> hit a transient window there, maybe. Since I dropped the number of polls >>> (instead of requesting the full CIB once per second) it hasn't >>> reproduced. But I'll reinstate that in the debug patch. >> Why not ask for updates instead? > > The code is signed up for updates. Ah, thats probably the issue. Occasionally a diff doesn't apply correctly (think ordering changes) and your copy of the error handling code results in cli_config_update() being called with a NULL pointer. Fix the case statements and you should be fine. > But every so often, it requests a > full refresh (which is part of the health check during pacemaker > integration; so that a paused/hung CIB process doesn't go unnoticed). > >>> I also tried to get the CIB to write a blackbox. But for some reason, it >>> logs that the blackbox logging has begun, but the file doesn't seem to >>> be created :-/ >> Did you send SIGTRAP and look in syslog for the file name like the blog says >> to? > > Yes. That file name doesn't get created, even though the directory > exists. I'll probably have to investigate that one too ;-) How odd. 0.14.x? > >>> (And enabling trace logging for PCMK_trace_functions=cli_config_update >>> didn't appear to produce any additional logging.) >> Not to syslog, only to files. >> If you don't have one configured in corosync already they'll be in >> /var/log/pacemaker.log (and syslog will mention this) > > Right, but cli_config_update doesn't do any trace logging, it appears. > And trace logging for all of the xml.c file is not advisable, I found > out that much ;-) yes :) > > > Thanks, > Lars > > -- > Architect Storage/HA > SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, > HRB 21284 (AG Nürnberg) > "Experience is the name everyone gives to their mistakes." -- Oscar Wilde > > > _______________________________________________ > 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 _______________________________________________ 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