Hi, I'm almost 100% sure I saw this before I even implemented Apache/Passenger...so I would say quite confidently that it's not Passenger related. My database server is very very underutilized at the moment, so I'm also quite sure it's not a load issue on MySQL.
But if it were a server-side issue, why would the error code be 400 (bad request)? Regards, On Wednesday, 27 June 2012 10:33:45 UTC+2, Felix.Frank wrote: > > Hi, > > On 06/25/2012 11:34 AM, Kmbu wrote: > > To me 400 implies that the client is responsible for the error, not the > > puppetmaster. > > this sounds a little far-fetched, to be honest. > > For example, the agent might be sending a broken request, making the > master believe a certain fact value is this long string instead of an > integer, true. But then, the master could get corrupted data from any > number of sources, few of them being the agent. > > If you cannot really reproduce, this will be hard to debug. Essentially > what I like doing is > 1. start a standalone puppet master with an alternative listen port with > no-daemonize and debug options > 2. have agents run using this master port and watch debug output > > Of course, in your case you'd have to keep trying until you trigger a > failure condition. If you consistently fail to do that, it may even be a > passenger related problem... > > Cheers, > Felix > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/Z8hkgL0pdSYJ. 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.
