I understand your frustration with this problem, but you've now mentioned in almost every email that puppet is "not doing anything", "puppet isn't doing it's job", and "it's not doing anything". Since there are many happy users of puppet, it's a good indicator that puppet does indeed work, and it's most likely an issue specific to your configuration.
The comment from "chalex" was meant to indicate an option on how you can check what's wrong with puppet, not as a way to manually perform the tasks instead of using puppet. Before this goes too off-topic about logging, it would be a good idea to reread the comment from Andrew Shafer where he suggests: > > "Does it appear that puppet is doing other things? Because I suspect it > isn't doing anything. > The mystery is to figure out why your puppet clients aren't > running/retrieving their catalogs. > That's the right answer. Figure out why puppet isn't working. On Thu, Sep 18, 2008 at 4:39 PM, josh <[EMAIL PROTECTED]> wrote: > > Splunk is in the works, puppet was the first step in the formula. > We do have a centralized log server, it's just that not all the client > boxes have the proper syslog-ng config in place - another think that > puppet was supposed to "fix" but since it's not doing anything, I'm > SOL. > > I have enabled reporting for some stores manually, and it looks like > things are working, but out of ~680 I'm only seeing 40 reporting back. > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
