Issue #12588 has been updated by Chris Price.
>From ticket #12310: <pre> A work-around is to completely remove the process_name.rb file, thus this way it won’t be loaded. </pre> The full path to the file in question is: <pre> lib/puppet/util/instrumentation/listeners/process_name.rb </pre> Gonzalo, if it would be possible for you to try removing this file from one of your problematic 2.7.10 nodes and let us know if this makes a difference for you, that information would be very useful on our end. Thanks! ---------------------------------------- Bug #12588: Running Puppet in one-time mode from cron leaves hung puppetd processes https://projects.puppetlabs.com/issues/12588#change-54677 Author: Gonzalo Servat Status: Investigating Priority: Normal Assignee: Patrick Carlisle Category: Target version: Affected Puppet version: 2.7.10 Keywords: select timeout hung process Branch: (This bug may be identical/related to http://projects.puppetlabs.com/issues/10418, however this issue is presenting itself in a variety of kernels, across RHEL5 and RHEL6) I have an increasing number of nodes that have hung puppetd processes. Doing an strace on them shows the following loop: select(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout) gettimeofday({1328767567, 900875}, NULL) = 0 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 gettimeofday({1328767567, 901663}, NULL) = 0 <repeat> I have tried running puppetd in debug mode but it didn't reveal anything interesting. One kernel that seems to be particularly affected by this is 2.6.32-131.17.1.el6.x86_64 (RHEL 6.1), however it does happen on other kernels too (e.g. 2.6.32-220.2.1.el6.x86_64 on CentOS 6.2 and 2.6.32-71.el6.x86_64 on CentOS 6.0) Version info: puppet-2.7.10-1 ruby-1.8.7.299-7 I think this may have started happening after I upgraded from puppet 2.7.9 to 2.7.10. Possible? -- 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.
