Re: [Puppet Users] Puppet agent hangs after running a few hours, defunct sh process
The comments in the redhat bug indicated that this breakage came from upstream, as did the fix. So it's entirely possible that this bug appeared in some Debian kernels, but I don't know which. On Jan 10, 2012, at 8:41 AM, jcbollinger wrote: > On Jan 9, 11:40 am, Jo Rhett wrote: >> On Jan 7, 2012, at 7:40 PM, Andreas N wrote: >> >>> That doesn't tell me anything other than that the puppet agent is blocking >>> on select() with a timeout of two seconds. >> >> Sounds like #10418. Check your kernel version. >> https://projects.puppetlabs.com/issues/10418 > > It sounds similar, but 10418 is specific to a particular RedHat / > CentOS kernel, and the OP is observing his problem on Ubuntu. My > awareness of that issue is one of the reasons I advised the OP to look > at kernel versions, however. > > > John > > -- > 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. > -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness -- 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.
[Puppet Users] Puppet agent hangs after running a few hours, defunct sh process
Hi, On a node running Puppet 2.7.9 from apt.puppetlabs.com, using Ubuntu 10.04.3 the agent hangs after a few hours of operation. I have to kill -9 it, nothing else helps. Obviously, this is unfortunate. Looking at ps -ef I see this: root 4842 4594 0 Jan04 pts/000:00:55 /usr/bin/ruby1.8 /usr/bin/puppet agent --verbose --no-daemonize --debug root 9803 4842 0 Jan04 pts/000:00:00 [sh] It seems a defunct sh process is responsible. This has happened before on that node so I started the agent with the command line arguments you see above. Unfortunately the produced debug logs don't look any different from the debug logs on a node where I haven't observed this behavior. The logs from the last run can be found here, nonetheless: http://pastie.org/3128200 The problem seems to happen regularly on that particular node but I looked around other nodes we have running and it seems to happen on a few others as well. These nodes don't have anything in common (not even the puppet master) but do have a few common modules applied. Could this be caused by one of those modules? How would I go about debugging? Or does anyone already know what's going on here? Thanks, Andreas -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/z6W5nxo-DqAJ. 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.
