On Oct 10, 2012, at 11:37 AM, Will S. G. wrote: > However, there is still that pesky Caught TERM; calling stop error, which > seems to be related to the recent kernel upgrade. Any thoughts?
Look for resources which would notify => Service['puppet']. Run puppet with --debug and you'll see what resource triggered it. (or whatever service is restarting, if its not puppet) -- Jo Rhett Net Consonance : net philanthropy to improve open source and internet projects. -- 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.
