With almost 700 nodes this isn't an option. The whole point of installing puppet in the first place was to not have to do this.
And like I said, if I run puppetd manually on each box it gets the files, runs the scripts, etc. etc. Also due to inconsistencies in the syslog config on these boxes, not all of them have puppet logging to syslog the right way. Maybe I will just configure puppet to log to a file locally on the box instead of via syslog and see if I can get some more insight that way. Josh On Sep 17, 12:23 pm, chalex <[EMAIL PROTECTED]> wrote: > I would do something like an ssh for loop that looked for the log > entries from the clients to see what they're doing: > > for i in $NODES > ssh $i grep puppetd /var/log/messages > etc > > On Sep 17, 9:48 am, josh <[EMAIL PROTECTED]> wrote: > > > I should have mentioned, I'm running four mongrel instances fronted by > > Apache/2.2.8 on the puppetmaster server for serving the clients. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
