On Tue, Oct 16, 2012 at 10:48 AM, HPUX_PUPPET <dride...@gmail.com> wrote:
> What is the best way to get a full trace of what puppet is doing, with > variable dumps and state, to troubleshoot problems like where a user's > password keeps getting reset every time puppet runs even though the > password hashes match? > In these situations I try and run both the master and the agent with the following options turned on: --verbose --debug --trace --evaltrace > I want to hack out a way to get HPUX working like we have our Linux > environments but need to be able to track down right where a problem is > coming in so I can adjust / override / submit changes to the code base. > With the --debug flag, providers will print out the exact command they're executing to modify the system. --noop is also useful to see what commands Puppet _would_ execute without actually executing them. -Jeff -- 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 puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
