Hi guys, Apologies if this is covered elsewhere. I''ve had a hunt through Google, Redline, and the FAQs but dont see it. Puppet 0.24.8 (and 24.7 on teh same box) starts up fine, but then just sits there, regardless of what I set runinterval to be. Puppet Server debug output stops at: debug: Creating default schedules debug: /Settings[/etc/puppet/puppet.conf]/Settings[puppetmasterd]/File [/etc/puppet/manifests/site.pp]: Autorequiring File[/etc/puppet/ manifests] debug: Finishing transaction -606538988 with 0 changes info: Listening on port 8140 notice: Starting Puppet server version 0.24.8 And similarly the client sits there with: debug: Finishing transaction -606641094 with 1 changes notice: Starting Puppet client version 0.24.8 debug: Loaded state in 0.00 seconds And frustratingly doesnt do any more. site.pp just contains the owner/ group example for /etc/passwd, and this works fine if I force a run with "puppetd --test", but the scheduling seems to have just stopped. Any pointers? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On 22/04/2009, at 5:29 PM, manowar wrote:> Apologies if this is covered elsewhere. I''ve had a hunt through > Google, Redline, and the FAQs but dont see it.Actually, I sent an email about this yesterday: 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 puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Thanks Avi, facter (1.5.4) seems to run fine when it''s called from the command line on its own, and as mentioned, puppetd --test called from cron does the job. But I''ll give 1.5.5 RC1 a try and see if that helps. Stu --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
manowar wrote:> facter (1.5.4) seems to run fine when it''s called from the command > line on its own, and as mentioned called from cron does the job.Yes, those both work -- however, Facter as called by Puppet still hangs. It was pretty tricky to debug, but after being taught how to strace the process, you could see Facter just looping over and over during a normal run. 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 puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---