<div dir="ltr">Hi, <br><br>This saved my life-- <a href="https://roidelapluie.be/blog/2015/09/16/pcs-resource-debug/">https://roidelapluie.be/blog/2015/09/16/pcs-resource-debug/</a> . Well, OK, a bit of an exaggeration. Nonetheless, after a lot of frustration, it helped. <br><br>Kind regards,<br><br>Sean</div><br><div class="gmail_quote"><div dir="ltr">On Mon, Jan 22, 2018 at 9:24 PM Klaus Wenninger <<a href="mailto:kwenning@redhat.com">kwenning@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 01/22/2018 01:06 PM, Tomas Jelinek wrote:<br>
> Dne 22.1.2018 v 11:01 Klaus Wenninger napsal(a):<br>
>> On 01/22/2018 10:46 AM, Tomas Jelinek wrote:<br>
>>> Hello,<br>
>>><br>
>>> the --debug option is supposed to be used as an additional option for<br>
>>> a pcs command, for example:<br>
>>><br>
>>> pcs status --debug<br>
>>> pcs --debug resource create dummy ocf:pacemaker:Dummy<br>
>>><br>
>>> It writes what a command is doing in the background - running other<br>
>>> commands, communicating over network.<br>
>><br>
>> Although the misunderstood usage (like getting<br>
>> everything pcs is doing on a node logged to<br>
>> a terminal) might be an interesting feature ;-)<br>
>><br>
>> Or is it possible to enable this kind of logging<br>
>> already? Maybe via pcsd?<br>
><br>
> No. Currently it is possible to:<br>
> - increase pcsd.log verbosity by setting PCSD_DEBUG=true in<br>
> /etc/sysconfig/pcsd or /etc/default/pcsd or whatever your distro has<br>
> - use the --debug option in pcs commands<br>
> and that's it.<br>
<br>
Thanks for the info Tomas.<br>
When I had read the initial question on the list it just occurred to<br>
me that might be very handy in all cases where pcs is somehow<br>
driven by scripts/daemons.<br>
Without having had a look into the code I would e.g. guess<br>
digimere's 'Intelligent Availability' to fall into this category.<br>
<br>
Regards,<br>
Klaus<br>
<br>
><br>
> One item on our todo list is to improve logging. It is not going to<br>
> happen anytime soon, though, as it requires significant changes in<br>
> pcs/pcsd architecture.<br>
><br>
> Regards,<br>
> Tomas<br>
><br>
>><br>
>> Regards,<br>
>> Klaus<br>
>><br>
>>><br>
>>><br>
>>><br>
>>> Regards,<br>
>>> Tomas<br>
>>><br>
>>><br>
>>> Dne 22.1.2018 v 09:51 范国腾 napsal(a):<br>
>>>> Hello,<br>
>>>> The help of "pcs --debug" says " Print all network traffic and<br>
>>>> external commands run." But when I run the "pcs --debug", it still<br>
>>>> print the help information. How to trigger it to print the network<br>
>>>> traffic?<br>
>>>><br>
>>>> Thanks<br>
>>>> Steven<br>
>>>><br>
>>>> [root@db3 ~]# pcs --debug<br>
>>>><br>
>>>> Usage: pcs [-f file] [-h] [commands]...<br>
>>>> Control and configure pacemaker and corosync.<br>
>>>><br>
>>>> Options:<br>
>>>> -h, --help Display usage and exit.<br>
>>>> -f file Perform actions on file instead of active<br>
>>>> CIB.<br>
>>>> --debug Print all network traffic and external<br>
>>>> commands run.<br>
>>>> --version Print pcs version information.<br>
>>>> --request-timeout Timeout for each outgoing request to another<br>
>>>> node in<br>
>>>> seconds. Default is 60s.<br>
>>>><br>
>>>> Commands:<br>
>>>> cluster Configure cluster options and nodes.<br>
>>>> resource Manage cluster resources.<br>
>>>> stonith Manage fence devices.<br>
>>>> constraint Manage resource constraints.<br>
>>>> property Manage pacemaker properties.<br>
>>>> acl Manage pacemaker access control lists.<br>
>>>> qdevice Manage quorum device provider on the local host.<br>
>>>> quorum Manage cluster quorum settings.<br>
>>>> booth Manage booth (cluster ticket manager).<br>
>>>> status View cluster status.<br>
>>>> config View and manage cluster configuration.<br>
>>>> pcsd Manage pcs daemon.<br>
>>>> node Manage cluster nodes.<br>
>>>> alert Manage pacemaker alerts.<br>
>>>><br>
>>>> _______________________________________________<br>
>>>> Users mailing list: <a href="mailto:Users@clusterlabs.org" target="_blank">Users@clusterlabs.org</a><br>
>>>> <a href="http://lists.clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.clusterlabs.org/mailman/listinfo/users</a><br>
>>>><br>
>>>> Project Home: <a href="http://www.clusterlabs.org" rel="noreferrer" target="_blank">http://www.clusterlabs.org</a><br>
>>>> Getting started:<br>
>>>> <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" rel="noreferrer" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
>>>> Bugs: <a href="http://bugs.clusterlabs.org" rel="noreferrer" target="_blank">http://bugs.clusterlabs.org</a><br>
>>>><br>
>>><br>
>>> _______________________________________________<br>
>>> Users mailing list: <a href="mailto:Users@clusterlabs.org" target="_blank">Users@clusterlabs.org</a><br>
>>> <a href="http://lists.clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.clusterlabs.org/mailman/listinfo/users</a><br>
>>><br>
>>> Project Home: <a href="http://www.clusterlabs.org" rel="noreferrer" target="_blank">http://www.clusterlabs.org</a><br>
>>> Getting started:<br>
>>> <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" rel="noreferrer" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
>>> Bugs: <a href="http://bugs.clusterlabs.org" rel="noreferrer" target="_blank">http://bugs.clusterlabs.org</a><br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> Users mailing list: <a href="mailto:Users@clusterlabs.org" target="_blank">Users@clusterlabs.org</a><br>
>> <a href="http://lists.clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.clusterlabs.org/mailman/listinfo/users</a><br>
>><br>
>> Project Home: <a href="http://www.clusterlabs.org" rel="noreferrer" target="_blank">http://www.clusterlabs.org</a><br>
>> Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" rel="noreferrer" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
>> Bugs: <a href="http://bugs.clusterlabs.org" rel="noreferrer" target="_blank">http://bugs.clusterlabs.org</a><br>
>><br>
><br>
> _______________________________________________<br>
> Users mailing list: <a href="mailto:Users@clusterlabs.org" target="_blank">Users@clusterlabs.org</a><br>
> <a href="http://lists.clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.clusterlabs.org/mailman/listinfo/users</a><br>
><br>
> Project Home: <a href="http://www.clusterlabs.org" rel="noreferrer" target="_blank">http://www.clusterlabs.org</a><br>
> Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" rel="noreferrer" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
> Bugs: <a href="http://bugs.clusterlabs.org" rel="noreferrer" target="_blank">http://bugs.clusterlabs.org</a><br>
<br>
<br>
_______________________________________________<br>
Users mailing list: <a href="mailto:Users@clusterlabs.org" target="_blank">Users@clusterlabs.org</a><br>
<a href="http://lists.clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.clusterlabs.org/mailman/listinfo/users</a><br>
<br>
Project Home: <a href="http://www.clusterlabs.org" rel="noreferrer" target="_blank">http://www.clusterlabs.org</a><br>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" rel="noreferrer" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
Bugs: <a href="http://bugs.clusterlabs.org" rel="noreferrer" target="_blank">http://bugs.clusterlabs.org</a><br>
</blockquote></div>