Issue #2211 has been updated by Michael Scherer.
I started to notice this on a 3rd server, and the issue occurs ( thanks to nagios to monitor it ) around 4h in the morning, just when the logrotate job is running. So I suspect the issue is linked to the load and I/O. While this will not be a proper fix for the core issue, I will see if the patch I sent for 7138 ( for not using exec for hostname ) lessen the problem for me. ---------------------------------------- Bug #2211: Facter timeouts reap all subprocesses thus confusing Puppet https://projects.puppetlabs.com/issues/2211 Author: John Florian Status: Accepted Priority: High Assignee: Markus Roberts Category: library Target version: 1.6.0 Affected Puppet version: 0.24.8 Keywords: Branch: Affected Facter version: It is no longer possible to have puppet install packages via yum/rpm if the network interface is not bound to an IP address. Our use case requires using puppet in the non-daemon mode and this is possible for us because the system will have all necessary manifests and other necessary files locally. This worked just fine with 0.24.6 on Fedora 10, but began failing upon the upgrade to 0.24.8. See the attachments for failure messages and a code diff that seems to have introduced the regression. If I revert this one change, things work nicely once again. Looks like a very simple fix if it weren't for the ominous looking comment in the code. :-) -- 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.
