Issue #8239 has been updated by Giles Constant.

Well, when I said "sorry I can't give you more info", I wasn't being secretive, 
I just couldn't think of anything relevant to paste here!  I'm going to idle on 
the puppet IRC channel today, so if you're around.  I'm logged in as "umami".

[constantg ~]$ rpm -qa |grep puppet
puppet-2.7.1-1
puppet-server-2.7.1-1
puppet-dashboard-1.1.1-1
[constantg ~]$ rpm -qa |grep facter
facter-1.6.0-1
[constantg ~]$ rpm -qa |grep ruby
ruby-shadow-1.4.1-7.el5
ruby-rdoc-1.8.6.399-2
rubygem-mixlib-cli-1.2.0-1.el5
rubygem-abstract-1.0.0-1.el5
rubygem-stomp-1.1-1.el5
rubygem-fastthread-1.0.1-1.el5
rubygem-rake-0.8.3-1.el5
ruby-1.8.6.399-2
libselinux-ruby-1.33.4-5.5.el5
ruby-augeas-0.3.0-2.el5
ruby-irb-1.8.6.399-2
rubygems-1.3.5-1.el5
rubygem-mixlib-log-1.1.0-1.el5
rubygem-extlib-0.9.13-5.el5
rubygem-ruby-openid-2.1.4-1.el5
rubygem-erubis-2.6.5-2.el5
rubygem-ohai-0.5.6-2.el5
rubygem-chef-0.7.16.3-1
rubygem-daemons-1.0.7-2.el5
rubygem-eventmachine-0.12.10-1
rubygem-activesupport-2.1.1-2.el5
ruby-sqlite3-1.1.0-6.el5
ruby-mysql-2.7.3-1.el5
rubygem-passenger-2.2.4-1.el5
rubygem-mongrel-1.0.1-6.el5
ruby-libs-1.8.6.399-2
rubygem-json-1.1.9-1.el5
rubygem-mixlib-config-1.1.0-2.el5
rubygem-systemu-1.2.0-3.el5
rubygem-rubyforge-1.0.3-1.el5
rubygem-activerecord-2.1.1-2.el5
rubygem-gem_plugin-0.2.2-2.el5

----------------------------------------
Bug #8239: zombie getconf processes, possibly from facter
https://projects.puppetlabs.com/issues/8239

Author: Giles Constant
Status: Investigating
Priority: Normal
Assignee: Adrien Thebo
Category: agent
Target version: 
Affected Puppet version: 2.7.1
Keywords: getconf zombie defunct
Branch: 


I'm seeing this..

     [root@xxxxx001 ~]# pstree |grep getconf
          |-puppetd---574*[getconf]

574 getconf zombies!

    root     32530 17822  0 Jun27 ?        00:00:00 [getconf] <defunct>
    root     32532 17822  0 Jun29 ?        00:00:00 [getconf] <defunct>
    root     32546 17822  0 Jul05 ?        00:00:00 [getconf] <defunct>
    ...etc...


Facter version 1.5.8, Puppet 2.6.6.

I've had a look at the old bug relating to 'timeout' in resolution.rb, but 
setting it to an integer other than 0 didn't make the problem go away.



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