Either insane ... or ignorant of the fact that one shouldn't push WEBrick that far. Or maybe both.
Today I bit the bullet and used the instructions here: http://reductivelabs.com/trac/puppet/wiki/UsingPassenger to migrate to Passenger. Pretty painless. I tested it on 8141 first, leaving WEBrick running, then cut over. So far, so good. Next up is Puppet 0.25! Pete On Tue, Oct 6, 2009 at 3:03 PM, Paul Lathrop <paul.lath...@gmail.com> wrote: > > On Tue, Oct 6, 2009 at 2:10 PM, Pete Emerson <pemer...@gmail.com> wrote: >> >> I'm seeing this in my logs: >> >> kernel: possible SYN flooding on port 8140. Sending cookies. >> Could not call fileserver.describe: #<Errno::ECONNRESET: Connection >> reset by peer> >> >> I'm running 0.24 with webrick, and have approximately 180 hosts under it. > > Respectfully... > You're insane. It's dumb luck you've gotten this far :-D > >> I'm guessing that I'm simply hitting the limits of what webrick can do >> (I'm working on moving to 0.25 and passenger). Is that true? >> What's the simplest way to alleviate the problem in the meantime? Is > > Turn off puppet. > >> there a simple way to migrate to 0.24 and passenger, for example? Or >> maybe something easier, like configure puppet to run less frequently >> (or perhaps only on demand)? >> >> Any thoughts appreciated. > > Most people hit this wall at 30-40 hosts, I made it to about 50. I'm > shocked you got up to 180. Your only choice is to move to one of the > scalable options (Mongrel, Passenger, etc.) > > --Paul > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
