We had this problem when we hit the scaling wall running webrick. We then moved our puppetmaster to a beefy server (dual quadcore with 16 GB ram). Here we run six puppetmasterds with mongrel and stored config. On the same server we run nginx. With this setup we can loop over a lot of servers restarting puppet client without any trouble at all. I tried doing more than 100 at the time without any trouble. So it certainly performs.
After setting this up the problem with dead puppet clients seemed to vanish. I have no idea how many servers you are running, but when pulling every fifth minute they sure should get some traffic. You will hit the scaling wall earlier. If you have 50 servers you need a setup that other people would use for a two/three hundred server setup. Are you really sure you need to pull that often? 2009/4/21 Ohad Levy <ohadl...@gmail.com> > We are using puppetd though cron, and it seems to me much more reliable and > much less resource hungry.. > > if you have more than a few clients, switch to mongrel/passenger. > WAN is not a real issue if its stable, of course it takes longer runs > but... > > cheers, > Ohad > > > On Tue, Apr 21, 2009 at 3:19 PM, 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 Quenot >> http://jbq.caraldi.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 -~----------~----~----~----~------~----~------~--~---
