Depending on your version of pacemaker you can do... # Enable trace logging (if it isn't already) killall -USR1 process_name
# Dump trace logging to disk killall -TRAP process_name # Find out what file it was dumped to grep blackbox /var/log/messages # Read it qb-blackbox /path/to/file Subsequent calls to "killall -TRAP ..." will have only logs since the last dump. On 23/04/2013, at 2:41 AM, Andreas Mock <andreas.m...@web.de> wrote: > Hi all, > > is there a way to enable debug output on a cman, corosync, pacemaker > stack without restarting the whole cman stuff. > > I've found <logging debug="on"/> for cluster.conf, assuming that this > determines the value of the config-db-keys > cluster.logging.debug=on > logging.debug=on > > Is it enough to write new values to these keys? > Or do I have to notify one or several processes to react on this change? > > Best regards > Andreas Mock > > > > _______________________________________________ > 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
