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