[Pacemaker] Enabling debugging with cman, corosync, pacemaker at runtime
Andreas Mock
andreas.mock at web.de
Mon Apr 22 17:38:39 UTC 2013
Hi Michael,
this doesn't seem to have the desired effect.
Please enlight me how to change the cluster.conf and
telling all participants to react on that change.
Best regards
Andreas Mock
Von: Andreas Mock [mailto:andreas.mock at web.de]
Gesendet: Montag, 22. April 2013 19: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:misch at clusterbau.com]
Gesendet: Montag, 22. April 2013 18:51
An: The Pacemaker cluster resource manager
Betreff: Re: [Pacemaker] Enabling debugging with cman, corosync, pacemaker
at runtime
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 <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
cman_tool -r -S
For the details see man cman_tool.
--
Dr. Michael Schwartzkopff
Guardinistr. 63
81375 München
Tel: (0163) 172 50 98
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130422/46229d21/attachment.htm>
More information about the Pacemaker
mailing list