In case anyone is interested, we figured out what was causing this issue.
Being that we run a Ruby on Rails application and naturally Puppet runs on
Ruby as well, we actually load TC Malloc memory allocator for our
application. By running one of the "applying configuration" processes in
gstac
Just noticed something else interesting. When running puppet apply or
puppet agent and it doesn't hang, puppet only spawns 1 process and there is
no puppet process left running afterwards, it seems to clean itself up and
die off. When puppet runs and hangs, it spawns 2 processes each looking
>
> Hello,
>
I am Franck's coworker. I spent some time looking into this today and have
some more info but unfortunately am still really lost as to what is going
on or what is causing this.
Here is the output captured from a puppet agent -t --debug run where a node
hangs:
https://github.com
Thank you for your response John.
You made some good suggestions especially with running it in strace to
retrieve more information.
In regards to your question, whether we have observed the behavior of
puppet spawning multiple processes, I can definitely confirm this. When
some of our nodes
On Monday, June 15, 2015 at 9:12:03 PM UTC-5, Franck wrote:
>
> We've been experiencing a lot of "Command exceeded timeouts" on basic
> shell commands using the "exec" type for tasks that should execute fairly
> fast:
>
> Jun 15 15:45:44 host1 puppet-agent[57648]:
> (/Stage[main]/Timezone::Ut
