Ursprüngliche Nachricht-
> Von: Andrew Beekhof [mailto:and...@beekhof.net]
> Gesendet: Dienstag, 23. April 2013 01:45
> An: The Pacemaker cluster resource manager
> Betreff: Re: [Pacemaker] Enabling debugging with cman, corosync, pacemaker
> at runtime
>
> Depending on your
Hi Andrew,
thank you for that hint.
Best regards
Andreas Mock
-Ursprüngliche Nachricht-
Von: Andrew Beekhof [mailto:and...@beekhof.net]
Gesendet: Dienstag, 23. April 2013 01:45
An: The Pacemaker cluster resource manager
Betreff: Re: [Pacemaker] Enabling debugging with cman, corosync
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
Subseq
, 22. April 2013 19:39
An: 'The Pacemaker cluster resource manager'
Betreff: Re: [Pacemaker] Enabling debugging with cman, corosync, pacemaker
at runtime
Hi Michael,
this doesn't seem to have the desired effect.
Please enlight me how to change the cluster.conf and
telling
11
An: 'The Pacemaker cluster resource manager'
Betreff: Re: [Pacemaker] Enabling debugging with cman, corosync, pacemaker
at runtime
Hi Michael,
thank you. I'll have a look at it.
Best regards
Andreas Mock
Von: Michael Schwartzkopff [mailto:mi...@clusterbau.com]
Hi Michael,
thank you. I'll have a look at it.
Best regards
Andreas Mock
Von: Michael Schwartzkopff [mailto:mi...@clusterbau.com]
Gesendet: Montag, 22. April 2013 18:51
An: The Pacemaker cluster resource manager
Betreff: Re: [Pacemaker] Enabling debugging with cman, cor
Am Montag, 22. April 2013, 18:41:33 schrieb Andreas Mock:
> 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 for cluster.conf, assuming that this
> determines the value of the config-db-keys
> cluste
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 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
