O'Reilly logo

Troubleshooting Puppet by Thomas Uphill

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

Debugging and logging

Any mco command can be run with the -v (verbose) option. The verbose option outputs progress information as well as a summary. To debug mco, you have to edit the configuration file (client.cfg) and change the loglevel parameter. The default logging level is warn. Change this to debug when debugging. Another important option is logger_type. The logger_type option defines how mco outputs its logging information. The possible values are syslog, file, and console. With loglevel set to debug, you can trace the connection to ActiveMQ, as shown in the following output:

[root@trouble ~]# mco find -v
...
info 2015/04/17 17:59:35: activemq.rb:114:in 'on_connecting' TCP Connection attempt 0 to stomp://client@puppet.example.com:61613 ...

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required