Issue #10418 has been updated by Mike Ryan.

I would just like to add a couple of data points regarding this ticket. The 
reports all seems to refer to RedHat-based systems, and mention some old kernel 
versions, but the problem is much more widespread.

Some of my servers have recently exhibited the exact same symptoms as those 
described in this ticket, however I am running Ubuntu 12.04 with an up to date 
kernel. This bug would pop up intermittently, when absolutely nothing had 
changed on the instance. I could reliably reproduce it by running 'puppet 
apply' over and over again until it hung. strace showed it was reading some 
files from /proc just before it started hanging, so it appears to be the same 
bug.

Updating facter to 1.6.12 seems to have fixed it - thanks for the updated 
version and fix.
----------------------------------------
Bug #10418: Puppet agent hangs when listen is true and reading from /proc 
filesystem on redhat
https://projects.puppetlabs.com/issues/10418#change-70846

Author: Jo Rhett
Status: Closed
Priority: Normal
Assignee: eric sorenson
Category: agent
Target version: 
Affected Puppet version: 2.6.12
Keywords: enabledisable hang select proc listen redhat
Branch: https://github.com/puppetlabs/facter/pull/304


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.

Reply via email to