FYI: I ran into this exact same issue today. I upgraded before seeing/finding this thread. So it seems puppet for RHEL4 from EPEL is currently broke until they update Facter.
On Tue, Apr 21, 2009 at 9:10 PM, Daniel Dekok <[email protected]> wrote: > > Building a rpm of the facter 1.5.5rc1, using the EPEL 1.5.4 spec file > with a small mod or two (removing the permissions and not installing > the non existance COPYING file) and installing it fixes the problem in > my test environment as well, am going to fan it out today and confirm > its all good. > > for the sake of completeness, running it in no deamonize mode doesn't > change anything, after startup it just sits there. > > On Apr 22, 7:38 am, Avi Miller <[email protected]> wrote: >> On 21/04/2009, at 11:39 PM, Daniel Dekok wrote: >> >> > Last week we upgraded a bunch of our machines to 0.24.8, using the >> > 1.el4.1 rpm from epel/redhat, and ever since then, it looks like >> > they're no longer doing any runs on the half hour. >> >> I think you are hitting the same Facter bug that I did with EL4. >> Essentially, Facter hangs trying to read /proc/uptime and /proc/ >> virtual (on my XenU guests). You should try the new Facter 1.5.5 RC1 >> which has the fixes for these to see if that resolves the problem. >> >> I actually had to manually fix all my servers because Puppet had >> stopped working. Also, when upgrading Facter, make sure you restart >> Puppet (if you're running a daemon), otherwise you can also run into >> problems I've discovered. >> >> cYa, >> Avi > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
