On Fri, Apr 24, 2009 at 6:25 AM, threetee <three...@gmail.com> wrote: > > On Apr 21, 12:19 am, Jean-Baptiste Quenot <cara...@gmail.com> wrote: >> 2009/4/6 Mike Renfro <ren...@tntech.edu>: >> >> > I'd normally expect that to work, but I just have puppet keep cron >> > running, and have a periodic cron job that checks if puppet has died, >> > and if so, restarts it: >> >> Interesting, but why would you expect Puppet to die? Would you expect >> Apache, Nginx or worse MySQL to die randomly like this? >> >> I'm a Puppet user since nearly two years now, and in the big picture >> of my web servers I find that puppetd is not the most reliable piece >> of software. It dies every day, and my colleagues complain about this >> regularly because their installed packages are not uptodate as they >> expect. So I have to start it again and again on all machines. Is >> Puppetd dying because of network problems? I believe so, but I think >> it should be fixed instead of finding creative ways to keep puppetd >> running, especially since I request it to run every 5 minutes as a >> daemon. >> >> Is anyone using puppetd in a WAN setup with default Webrick server >> successfully? Shall I switch the HTTP server to Mongrel to gain >> reliability? I'll test this setup. But if puppetd fails on the >> client side, I'm not certain that changing the server's HTTP server >> would actually prevent the client to fail at all... >> >> I'm a bit eager with this, and I'm really looking forward to find a >> solution, community-wise. Your comments are welcome. >> -- >> Jean-Baptiste Quenothttp://jbq.caraldi.com/ > > This has already been mentioned in this thread, but I'll add my $0.02 > anyway. I use puppet to manage about 500 servers, and I started having > the same scalability problems everyone else is having with Webrick: > puppetd started randomly dying on clients, IIRC when I reached around > 50 nodes. I initially thought about working around it by putting > puppet into cron, I didn't want to sacrifice some of the features that > puppetd provides (scheduling, ability to monitor puppetd status from a > central location). I was also concerned that puppet might still have > problems pulling files from the fileserver with a Webrick-based > solution. I kicked Webrick to the curb and replaced it with Passenger/ > Rack on my puppetmaster, using the instructions at > http://reductivelabs.com/trac/puppet/wiki/UsingPassenger. This dropped > the puppetd mortality rate on my client nodes to nearly zero, and I > get to keep using puppetd on the clients. :)
I have some python code that fires off a bunch of simultaneous threads that mimic puppet clients supplying facts and requesting a compiled manifest (planning to release this btw), and I've been amazed at just how much better Passenger/Rack performs compared to Pound/Nginx/Mongrel. -- Nigel Kersten nig...@google.com System Administrator Google, Inc. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
