Nigel Kersten wrote:
> so I've found myself with a few reasons to need to debug
> puppetd/puppetmasterd lately since we upgraded to 0.24.5
>
> I've been doing this by basically throwing Puppet.notice/warning
> statements into the code, which feels rather primitive...
>
> How are people doing debugging? I've poked around a bit and looked at
> some options for Ruby debugging, but was wondering what other people
> are using ....
Puppet has some weaknesses there in that it is too fragile (breaking on
class syntax errors) and quiet.
Here are some things I do to help mitigate those issues and visualize
what is going on.
Start puppetmasterd / puppetd with --verbose as default, and add
--debug or use strace if things get really nasty.
Put a line at the beginning of every class:
notice("Reached class: name-of-class")
Tie into subversion with commit hooks...
1. pre-commit hook runs puppet --parseonly to vet any syntax errors on
classes
2. post-commit hook extracts the manifests/files/plugins al to where
puppetmaster can see them
3. post-commit hook sends a commit notification with log message and
diff output to commits@
Using puppetized nrpe agent watched by nagios to verify puppetd is
running on the hosts it *should be*
--
Mark Foster - Sr. Systems Engineer - BitPusher, LLC
We push your bits so you don't have to!
http://www.bitpusher.com/
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
