On Monday, March 5, 2012 12:23:52 PM UTC+1, Krzysztof Wilczynski wrote:
>
> I would imagine, that adding code to either ignore SIGCHLD, or collect
> child status (exit code), or use Process.detach could help :-)
>
> How and what in the what what now?
--
You received this message because you a
Ok, it fails at early run.
Mar 5 03:57:33 srzarnsas007 puppet-agent[22690]: Retrieving plugin
Mar 5 03:57:35 srzarnsas007 puppet-agent[22690]: Loading facts in
/var/lib/puppet/lib/facter/facter_dot_d.rb
Mar 5 03:57:35 srzarnsas007 puppet-agent[22690]: Loading facts in
/var/lib/puppet/lib/fact
On 3 mar, 17:59, Russell Van Tassell wrote:
> 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.
How do I se
> 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 whi
