Josh, that's this bug: http://projects.reductivelabs.com/issues/show/1551
and a simple server side patch will fix it, you can find the patch here: http://github.com/nigelkersten/puppetmaster/commit/65ce150b04e46cfb572d9d2682bf5d9a3b37da68 I'm not sure why more people haven't seen this. Does everyone simply upgrade all their puppet clients at exactly the same time they upgrade their servers? On Thu, Sep 18, 2008 at 8:19 AM, josh <[EMAIL PROTECTED]> wrote: > > Brian, > Sorry for getting a little bent out of shape, it's just that my boss > is pushing on me, etc. etc. > > Anyways, I think I see an issue. > I saw this in the log file on a client, and I bet I'll see it on many > others if I looked. > > Sep 18 10:48:55 puppetd[17896]: [ID 702911 daemon.error] Could not > retrieve catalog: undefined method `-' for #<XMLRPC::DateTime: > 0x8e6cf14> > > Looks like that started at around the same time that I went from using > Webrick for the web server to Apache2 in front of mongrel. > > I basically used the httpd.conf that is on the Puppet web site. > http://www.reductivelabs.com/trac/puppet/wiki/UsingMongrel > > Well at least now I see there's a problem that can be resolved. > Thank you for helping me see the forest for the trees (or whatever > that expression is!) > > Now I need to troubleshoot my apache2/mongrel configuration (as I'm > guessing that's where the issue lies). > > > On Sep 18, 10:51 am, "Brian Mathis" <[EMAIL PROTECTED]> wrote: > > 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. > > > -- Nigel Kersten Systems Administrator Tech Lead - MacOps --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
