Could you check the server logs and run the master with --verbose --debug --trace?
The information I'm looking for is a backtrace to the file and ljne number that raised that exception. Thanks, -Jeff On Oct 18, 2012, at 5:26 AM, Fabrice Bacchella <[email protected]> wrote: > My puppet setup break just a few hours with this message. > > I didn't upgrade anything, didn't really changed my module and it just broke. > The node what where working suddenly stop working. > > I'm using the official Puppet 3.0 on Scientific Linux (aka Redhat) 6.3 > > Can some one explain me this magic ? > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to [email protected]. > 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. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. 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.
