I have been investigating this issue as well, and assuming you are also seeing SSL errors with your logs, it is very likely the same cause as over here.
I've been able to find information about a bug in older Ruby versions whowing exactly this sort of SSL (mal)behaviour. So maybe this can give you some extra hints to search for. I don't recall the places I found this information unfortunately, since we did not have the option to upgrade our Ruby version at this point. We've chosen to ignore htese errors if they are due to SSL errors, as subsequent puppet runs (about 30 minutes later) will usually be fine. Not a real solution, sorry. On Monday, February 25, 2013 10:03:18 PM UTC+1, Jagga Soorma wrote: > > Hi Guys, > > I am running puppet server version 3.0.2-1 on a RHEL 5.8 virtual machine > with about 110 clients. I am seeing intermittent errors with my clients > that are failing with the following error messages: > > -- > Could not retrieve catalog from remote server: Error 400 on SERVER: Could > not find class motd for xxx on node xxx > -- > > If I login to that host which failed and manually run a "puppet agent -t" > it finishes without any error messages. These errors are intermittent but > have caused corruption of my passwd file since I also manage that via > puppet. This message shows up for different servers with different classes > in the error message. I have looked at my classes and I don't see any > problems with it. Any idea what might be causing this problem? > > Any help would be greatly appreciated. > > Thanks! > -J > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
