Debugging Elusive Puppet Errors | Comments (0)
Posted in Code, Linux/Unix on 8th June 2010, 6:14 pm by Stuart
On working on some puppet manifests I hit this error message:
$ sudo puppetd -t
err: Could not retrieve catalog from remote server: undefined method `closed?' for nil:NilClass
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping runCertainly not the most enlightening error message. After checking over the syntax of my mainfests it still wasn’t obvious what was wrong.
First port of call to diagnose the problem is to try enabling debugging on the client:
On the client:
# Run the client with debugging enabled.
$ sudo puppetd -t --debugIf that yields nothing useful try the following:
On the puppetmaster run:
# If it's running stop the puppetmasterd service
# change this to suit your distro - the following is debian specific
$ sudo /etc/init.d/puppetmaster stop
# start the puppetmasterd in debug mode without daemonizing it.
$ sudo puppetmasterd --no-daemonize --debugBack on the client re-run the puppetd:
$ sudo puppetd -tBy looking at the debug output on the puppetmaster I was able to see my problem which was that a generate command didn’t have permission to write a necessary file. Once I’d fixed it everything worked as expected.
Once finished ctrl-c the foreground puppetmasterd and restart the service if you’d stopped it to run it in debug mode:
$ sudo /etc/init.d/puppetmaster start