I'm actually not sure. How do I determine that? I just use the redhat rpms from the epel repository, and I don't remember seeing an option for that anywhere.
-- Michael Conigliaro Computer Analyst Fuss & O'Neill Technologies www.fandotech.com -----Original Message----- From: puppet-users@googlegroups.com [mailto:puppet-us...@googlegroups.com] On Behalf Of Ohad Levy Sent: Monday, May 04, 2009 10:48 AM To: puppet-users@googlegroups.com Subject: [Puppet Users] Re: long catalog run times and random connection timeouts are you using webrick? On Mon, May 4, 2009 at 10:41 PM, Michael Conigliaro <mconigli...@fandotech.com> wrote: Hello, I've been seeing some strange behavior for the last few days, and I'm not sure what else to do to troubleshoot it. It started when two of my puppet clients (always the same two) suddenly began to take forever to finish their catalog runs. I'm not sure what changed around 5pm last Thursday to cause this, but well, check out the logs... Apr 30 16:50:50 emsdb01 puppetd[11363]: Finished catalog run in 4.59 seconds Apr 30 17:26:29 emsdb01 puppetd[11363]: Finished catalog run in 292.65 seconds Apr 30 16:43:05 emsweb01 puppetd[1345]: Finished catalog run in 4.47 seconds Apr 30 17:18:27 emsweb01 puppetd[1345]: Finished catalog run in 292.53 seconds Now when emsdb01 and emsweb01 are checking in, all the other clients seem to queue up behind them. So I end up seeing... Conection timeout calling puppetmaster.getconfig: execution expired And... Could not retrieve catalog: Connection Timeout from all the other clients. For those that don't time out, I see a flurry of "finished catalog run" as they all complete at the same time (but with excessive catalog run times, presumably because everyone else got held up by emsdb01 and emsweb01). When I run "puppetd --test --debug" on emsdb01 and emsweb01, I don't see anything unusual happening. Both servers are basically idle while the catalog run is happening. What I do see is that they get hung up on these tasks for some reason: debug: Calling puppetmaster.getconfig debug: Calling fileserver.describe When I look at the puppetmaster as this is going on, I don't see anything unusual in regards to server load there either. At first, I suspected some kind of network connectivity issue, but I have run several tcpdumps, and everything seems to be connecting fine. Is there something else I should be looking at to determine the cause of this problem? -- Michael Conigliaro Computer Analyst Fuss & O'Neill Technologies www.fandotech.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. 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 -~----------~----~----~----~------~----~------~--~---
