Re: [Puppet Users] puppetd hanging on some nodes

2012-02-14 Thread Daniel Pittman
On Tue, Feb 14, 2012 at 16:28, Gonzalo Servat wrote: > On Wed, Feb 15, 2012 at 11:02 AM, Daniel Pittman > wrote: >> >> Sorry for not getting back to this sooner.  If you are running 2.7.10, >> can you try removing the file >> `puppet/util/instrumentation/listeners/process_name.rb` and see if >> t

Re: [Puppet Users] puppetd hanging on some nodes

2012-02-14 Thread Gonzalo Servat
On Wed, Feb 15, 2012 at 11:02 AM, Daniel Pittman wrote: > Sorry for not getting back to this sooner. If you are running 2.7.10, > can you try removing the file > `puppet/util/instrumentation/listeners/process_name.rb` and see if > that fixes the problem? > No worries Daniel. Yes. It did fix the

Re: [Puppet Users] puppetd hanging on some nodes

2012-02-14 Thread Daniel Pittman
On Thu, Feb 9, 2012 at 17:19, Gonzalo Servat wrote: > On Thu, Feb 9, 2012 at 5:08 PM, Gonzalo Servat wrote: >>> >>> Damn.  Well, at least we eliminated one possible cause.  Is there any >>> chance you can run with `--debug` enabled on one of the failed >>> machines, and see if that points to the

Re: [Puppet Users] puppetd hanging on some nodes

2012-02-09 Thread Gonzalo Servat
On Thu, Feb 9, 2012 at 5:08 PM, Gonzalo Servat wrote: > Damn. Well, at least we eliminated one possible cause. Is there any >> chance you can run with `--debug` enabled on one of the failed >> machines, and see if that points to the right place? Otherwise we >> have to start to get into some f

Re: [Puppet Users] puppetd hanging on some nodes

2012-02-08 Thread Gonzalo Servat
> > Damn. Well, at least we eliminated one possible cause. Is there any > chance you can run with `--debug` enabled on one of the failed > machines, and see if that points to the right place? Otherwise we > have to start to get into some fairly heavy ways to figure out what is > going on. > OK

Re: [Puppet Users] puppetd hanging on some nodes

2012-02-08 Thread Daniel Pittman
On Wed, Feb 8, 2012 at 14:40, Gonzalo Servat wrote: > On Thu, Feb 9, 2012 at 5:44 AM, Daniel Pittman wrote: >> RedHat released some update kernels that reintroduced a bug from the >> 2.6.13 Linux kernel.  You can run any of the code in this gist to >> check if your kernel suffers that: https://gi

Re: [Puppet Users] puppetd hanging on some nodes

2012-02-08 Thread Gonzalo Servat
On Thu, Feb 9, 2012 at 5:44 AM, Daniel Pittman wrote: > RedHat released some update kernels that reintroduced a bug from the > 2.6.13 Linux kernel. You can run any of the code in this gist to > check if your kernel suffers that: https://gist.github.com/441278 > > The C code is obviously a pretty

Re: [Puppet Users] puppetd hanging on some nodes

2012-02-08 Thread Daniel Pittman
On Tue, Feb 7, 2012 at 23:56, Gonzalo Servat wrote: > On Wed, Feb 8, 2012 at 3:25 PM, Brian Gallew wrote: >> >> If you are like me, the problem is that the ruby for your platform sucks. >>  The webstack ruby 1.8.7 for Solaris 10 has a nasty tendency to hang (for >> the daemons) and core dump for

Re: [Puppet Users] puppetd hanging on some nodes

2012-02-07 Thread Gonzalo Servat
On Wed, Feb 8, 2012 at 3:25 PM, Brian Gallew wrote: > If you are like me, the problem is that the ruby for your platform sucks. > The webstack ruby 1.8.7 for Solaris 10 has a nasty tendency to hang (for > the daemons) and core dump for individual runs. Individual runs out of a > crontab are the

Re: [Puppet Users] puppetd hanging on some nodes

2012-02-07 Thread Brian Gallew
If you are like me, the problem is that the ruby for your platform sucks. The webstack ruby 1.8.7 for Solaris 10 has a nasty tendency to hang (for the daemons) and core dump for individual runs. Individual runs out of a crontab are the most reliable way I've found to make it all work. On Tue, Fe