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..] Hi Daniel, 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. Kernel on hanging nodes: 2.6.32-131.17.1.el6.x86_64. It would be nice if all the nodes running the above kernel had this problem, but unfortunately there are other nodes using the above kernel that are not hanging. Thanks in advance. Gonzalo -- 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.
