On Apr 21, 2009, at 8:39 AM, Daniel Dekok wrote: > > Hi, > > 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. If we run manually > as a oneshot or a test via the init.d script, there's no problems, but > there's no activity on the logs of active runs. I've tested running > puppetd with --ignorecache, and also disabling and enableing --splay > (we keep it enabled normally) with no change, and in recent tests > dropped the runinterval to 60, but also with no difference. Even with > debug, the client logs are quite simply blank and there's no activity, > the debug logs on the puppetmaster only have some basic connections > upon first run. > > Not sure if to take it to redhat or not, but there could be a > correlation between this feature and the fact these machines are on > RHEL4, we've got some RHEL5/centos 5 machines that seem to be ok. > > Cant think of any other tests to try, as its in the internal > scheduling, not forcing a update/run, and ideas would be appreciated.
What happens if you run in debug mode with --no-daemonize? I've not seen this, and I'd think you'd get at least some kind of message somewhere. -- It is said that power corrupts, but actually it's more true that power attracts the corruptible. The sane are usually attracted by other things than power. -- David Brin --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
