Issue #10418 has been updated by Jason Smith.
I don't know about anyone else, but I have not seen this problem in any of the RHEL6 kernels, neither 6.1 nor 6.2. Note, the RHEL6 kernel (based on 2.6.32) is completely different than the rhel5 one (based on 2.6.18). As Peter said, for the RHEL5 kernels, the bugzilla ticket says that RedHat has verified that they have fixed it in their 2.6.18-299 kernel, so I would assume any RHEL5 kernel version greater than that would have the fix. Hopefully this is almost done going through RedHat's QA and will be released soon, either in a RHEL5.7 errata or possibly the soon to be released 5.8. XiangJun Wu wrote: > Hopefully, CentOS6.2 will include fix. > Peter Meier wrote: > > XiangJun Wu wrote: > > > Does CentOS6.1 fix it? > > > > No. According to the RHEL Bugtracker this will be fixed in > > kernel-2.6.18-299.el5 , which will then be taken up by CentOS. ---------------------------------------- Bug #10418: Puppet agent hangs when listen is true and reading from /proc filesystem on redhat https://projects.puppetlabs.com/issues/10418 Author: Jo Rhett Status: Investigating Priority: Normal Assignee: Category: agent Target version: Affected Puppet version: 2.6.12 Keywords: enabledisable hang select proc listen redhat Branch: Mon Oct 31 23:03:31 +0000 2011 Puppet (notice): Caught TERM; calling stop Ever since the 2.6.12 upgrade I've been seeing these reports reach us. As in, about a hundred of a half thou machines. Most of the time we find that $vardir/state/puppetdlock is in place and blocking further puppet runs, which requires a manual resolution. I wrote a quick cron script to look for puppetdlock files older than one hour, remove them and mail me a report and I've received several dozen in the last few hours. Something is clearly broken in 2.6.12, we are backgrading our systems to 2.6.11. No-- I have no other information than that it crosses all of our machine types, and we have had no significant changes in our modules in this time period. Many of the machines which have failed have had zero module or manifest changes which would apply to them. I cannot get this to replicate on the command line. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
