Are you using Webrick? If so, use Mongrel! There's a wiki page on it (UsingMongrel iirc). I'd recommend nginx as your proxy loadbalancer.
On 11/10/2008, at 12:3 AM, "Kenneth Holter" <[EMAIL PROTECTED]> wrote: > > Hello list. > > > We're running puppet version 0.24.4, and are having trouble with > puppetmaster running really slow. The puppetmaster has been running > fine until about a couple of day ago, and for no apparent reason it > just lost performance. I've also noticed that the puppet daemon on > many of our clients a dying. Both master and clients run very slow, > but I'm not sure if the client runs slow because of the master. > > The symptoms I've seen are that running puppet on a client often > takes a very long time (one of the nodes used close to 800 seconds > to run the config), or even times out. Once in a while, however, > things seems back to normal, and the run is executed in a few > seconds. On the server side the time between "Compiled configuration > for ..." messages takes a very long time (often several minutes), in > contrast to normal operations where configurations get compiled > quite frequently. > > What puzzles me is that there are no signs of resource starvation on > the server - we have low CPU and memory utilization. So there > shouldn't be, as far as I can see, any hardware limitations causing > puppetmaster to run slow. > > I don't have the exact number of active puppet nodes, but it should > be well under 100 nodes. > > Other than that, I can mention that "storeconfig" is set to "true" > in puppet.conf. > > And another question/observation: I started a client run more than > five minutes ago by issuing "puppet --server puppetmaster --test", > and it is either running very slow or something has crashed. The > last message on the screen is "notice: Starting catalogue run", and > it's been like that since I started the run. Is this a symptom of a > problem at the client side, or at the master side? I mean, when I > get to the message just mentions, I'd think that the puppetmaster > has done it's part, and now it's up to the client to execute. So > maybe this indicates that there is something wrong at the client > side also? > > > Anyways, any tip on how to figure this out will be very appreciated, > as we're quite dependent on puppet in our daily work. > > > Regards, > Kenneth Holter > > > --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
