My guess ... Just look in your puppet log to see what manifest ran last. At one of my previous engagements, we routinely had zombied processes off of puppet ... Eventually found an unclosed loop in a child process that was causing it.
-- Russell M. Van Tassell [email protected] This message was sent using my wireless handheld device. On Mar 3, 2012 2:09 AM, "Raboo" <[email protected]> wrote: > > How do I begin looking on what can be wrong? > > This error has appeared on both 2.7.6 and 2.7.11. > Ok, a question to my own thread. > Is there a way to set a timeout on both how long a class/module can > run and a total timeout how long puppet can run it's catalog? > That way I will actually find out which module that gets stuck, if > there is a class timeout. > > -- > 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.
