> We had some weird issues with mongrel >=1.1, which we never understood, but > after downgrading > to 1.0.4 things are going well again. Kirk Haines looked into it, but I have > to admit > I never understood what the reason of the problem with newer mongrel is.
He mentioned someone was having lockups. If you could gdb the process that locked and generate a backtrace that would be a big help. Evan On Jan 4, 2008 2:54 AM, Armin Roehrl <[EMAIL PROTECTED]> wrote: > > > * Framework, if any (Camping, Merb, Rails, Nitro, Ramaze, IOWA, Rack...) > > > rack > > * Mongrel version > > > 1.0.4 > > * Mongrel handlers used (rails, dirhandler, camping, cgiwrapper...) > > > rack > > * How many mongrel routes and handlers per route registered (if you > > don't know, it's probably <= 2) > > > <=2 > > * Any Mongrel plugins used (mongrel_upload_progress, mongrel_gzip, > > mongrel_cow_cluster, mongrel_experimental...) > > > none > > * Mongrel runners used (mongrel_rails, mongrel::cluster, > > mongrel_service, RV, others... please be *very specific* about which > > options of the runner you use. For example, some people use > > mongrel::cluster but only for the --clean functionality, not for the > > clustering). > > > ? none I think. > > * Number of mongrels per server per app > > > depends on the application 1-100 > > * Monitoring system (runit, monit, god...) > > > simple self-written scripts > > * Proxy or software loadbalancer, if any (apache mod_proxy_balancer, > > nginx, pen...) > > > nginx > > * HW loadbalancer, if any (Netscaler...) > > > none > > * Caching strategy (memcached fragments, memcached object, squid, > > rails page cache, rails page fragments, ESI) > > > memcached & self-grown hacks. > > * Whether you serve media assets via mongrel itself, as opposed to > > through a webserver > > > no > > * Operating system including distribution or version (OS X 10.4.10, > > Ubuntu/Linux 7.10, WinXP SP2, OpenBSD 4.1...) > > > gentoo linux > > * Architecture, via 'uname -a' preferably (x86, x86_64, Sparc, PPC, > > Arm (ha), JRuby) > > > Linux prod8 2.6.22-gentoo-r8-a #1 SMP Wed Oct 3 06:41:23 CDT 2007 x86_64 > Dual-Core AMD Opteron(tm) Processor 8212 AuthenticAMD GNU/Linux > > > * CPU count > > > 4 dual core > > * Ruby version including custom distribution patches, > > (1.8.6p110+threadhooks, 1.8.5, JRuby 1.1b1, Rubinius trunk... also > > note where you got it, in case it isn't clear, for example, OS X 10.5 > > built-in, Ubuntu apt, Instant Rails, direct compile from source) > > > ruby 1.8.6 (2007-09-24 patchlevel 111) [x86_64-linux] (direct from > emerge ruby) > > > * Rubygems (yes/no, version) > > > y, 0.9.4 > > Please mention anything else about your system that's kind of weird, > > and anything that's been particularly troublesome regarding mongrel > > deployment. > > > > > We had some weird issues with mongrel >=1.1, which we never understood, > but after downgrading > to 1.0.4 things are going well again. Kirk Haines looked into it, but I > have to admit > I never understood what the reason of the problem with newer mongrel is. > > Thanks to all mongrel hackers for the amazing work! > > Ciao, > -Armin > > > > _______________________________________________ > Mongrel-users mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/mongrel-users > -- Evan Weaver Cloudburst, LLC _______________________________________________ Mongrel-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/mongrel-users
