On Thu, Feb 9, 2012 at 17:19, Gonzalo Servat <gser...@gmail.com> wrote: > On Thu, Feb 9, 2012 at 5:08 PM, Gonzalo Servat <gser...@gmail.com> 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 fairly heavy ways to figure out what is >>> going on. >> >> OK I'm now running it with --debug into separate log files, to compare a >> working and non-working runs. Unfortunately the hung Puppet doesn't seem to >> reveal anything interesting in the logs. A working puppet run looks like >> this: > > [..snip..] > > I'm having an increasing number of nodes now with puppet hangs. I now have > 26 nodes where puppetd just hangs. Any ideas on what I can try? > I've tried removing any Puppet configuration for the hanging nodes, but it > doesn't help so it looks like a client side problem and not the catalog that > gets applied to them.
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? We have some reports that can cause hangs, and eliminating it will make sure this doesn't descend from there. Otherwise we really have to start getting into more aggressive debugging. Would you be comfortable doing some hacking / patching of the code to narrow this down, and/or installing some development tools on one of the nodes that triggers the hang? -- Daniel Pittman ⎋ Puppet Labs Developer – http://puppetlabs.com ♲ Made with 100 percent post-consumer electrons -- 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.
