Issue #12181 has been updated by Brice Figureau.

Josh Cooper wrote:
> That's concerning because the instrumentation probes are supposed to be 
> disabled by default, so the process_name listener should not be getting 
> invoked.

Yes, that's what I thought too, but as we found in #12310, the listeners are 
loaded at puppet start (even though they're never executed).
During the load, the listeners are registered into the instrumentation 
framework, and the 'subscribed' callback is called.
For the process_name listener this callback creates a sleeping thread.
This is enough apparently to:

* induce a serious slow-down (see #12310)
* or even lock up the process

Which, I admit it, kind of seriously suck. I'm to be blamed on this serious 
issue (and for my defense I wouldn't have thought that creating a thread would 
so seriously f**k up a ruby process).

The work-around for the moment is to remove the 
@lib/puppet/util/instrumentation/listeners/process_name.rb@ file and restart 
the process.

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