Issue #12181 has been updated by Matt Goebel.

I don't know it it's the same issue or not but I'm seeing this happen with with 
CentOS 6.2 hosts now too.  Unlike CentOS 5 which is very much kernel specific 
and can be replicated 100% of the time if I'm using one of the affected kernels 
it with CentOS 6 it just appears that they randomly hang. With the newer CentOS 
6 kernels it does seem to happen more often though.  Killing the process and 
removing the lock file allows puppet to run a few more times but the issue 
usually comes back.
----------------------------------------
Bug #12181: Puppet 2.7.10 run stopps after loading facts.
https://projects.puppetlabs.com/issues/12181

Author: Marek Kroemeke
Status: Needs More Information
Priority: Normal
Assignee: Chris Price
Category: 
Target version: 
Affected Puppet version: 2.7.10
Keywords: 
Branch: 


Hello,

OS: RHEL 5.7

I've just upgraded 2.7.9 to 2.7.10 (puppetlabs rpms) and puppet simply stopped 
working (it stops after loading facts) :

-- cut --
<snip>
<pre>
debug: Loaded state in 0.08 seconds
info: Retrieving plugin
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; 
using pson
debug: Using cached certificate for ca
debug: Using cached certificate for foo.com
debug: Using cached certificate_revocation_list for ca
debug: Finishing transaction 23456250095500
info: Loading facts in /var/lib/puppet/lib/facter/foo_config.rb
info: Loading facts in /var/lib/puppet/lib/facter/network.rb
info: Loading facts in /var/lib/puppet/lib/facter/lldpd.rb
</pre>
-- cut --

Rolling back the client to 2.7.9 and leaving master on 2.7.10 fixes the problem.



-- 
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