similar to: Nightly mongrel issues...

Greetings, I need some help... please be gentle :-) MY SETUP: Solaris-X86, ruby-1.8.4, Apache-2.2.0, Mongrel-0.3.13.4, MySql-4.1.10a I am using the typical setup with apache proxying request to mongrel with mod_proxy_balancer. Currently, I am only running a single instance of mongrel behind the proxy. I am also using the following gems with this app: capistrano (1.2.0) daemons (1.0.2)

Hi. I have mongrel 1.0.1 running a really simple application and found to lock up (rarely, but still). There''s nothing in the logs, it just stops responding. When I mongrel_rails stop it, I get lots of entries like: Waiting for 3 requests to finish, could take 60 seconds /usr/lib64/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb:675:in `process''

Hello, maybe someone can help with backgroundrb. I''ve written an application, which makes use of backgroundrb. Everything works fine on my development machine, but it crashes on my production server. Something seems to be wrong with backgroundrb, but I don''t know the cause. All I get is the error message attached below, which is extracted from the production.log. I

i am using the following comman to fire up mongrel: [sergio@vb_workstation chatlogger]$ mongrel_rails start -d -p 8088 ** You have sendfile installed, will use that to serve files. and everything works fine until some point at night.. i think it is pooping out some time in the middle of the night.. if i try to hit the app in the morning, it just stalls out.. if i restart it, it''s

Hi all, I''ve been having problems with the apache 2.2-mod_proxy_balancer- mongrel setup. My setup is: CentOS 4.3 apache 2.2.3 (compiled from source) with mod_proxy_balancer mysql 4.1 ruby 1.8.4 mongrel 0.3.14 (I know I need to update but I think this problem is independent of the mongrel version) mongrel_cluster 0.2.0 rails_machine 0.1.1 I have apache setup as per Coda''s

Hi, After following the excellent tutorials in the Agile Web Development with Rails book, I was able to get my webservice working pretty much perfectly :) I can access it via SOAP and XML-RPC and look at service.wsdl to find the API. What I can''t do however is get the API for the XML-RPC call. It fails with : Internal protocol error: NilClass is not a valid input stream. It must

Hi guys, I''ve been running mongrel for a while now with Ruby 1.8.4, and last week upgraded to 1.8.6. Since upgrading, each morning when I wake up there''s a big problem: 1. Accessing the site returns a "500 Internal Server Error" 2. All the mongrel_rails processes are still running, but none of them are active (when I run top) 3. Lighttpd and pound are still

I am not sure when it exactly occurred but I have 2 servers I am about to migrate to apache+mongrel from lighty+fastcgi oddly, both my servers seemed to have died at the same time everytime I restart within a 24 hr period ( I don''t know when, my logs don''t show it ). Can someone please point me in the direction of what I need to do to trace the cause of this. Or what you would

Hi, I''m new to mongrel and so far have liked it a lot during development. I just tried to stand up a production server following the guide here: http://blog.innerewut.de/articles/2006/04/21/scaling-rails-with-apache-2-2-mod_proxy_balancer-and-mongrel This was working well for a few days, until this weekend it crashed with the following stack trace. It''s running on redhat

Hello, I don''t know if this is really relevant anymore because a new version is about to be released it seems, however I''ve been trying to run mongrel 0.3.12.4 on a development server in development mode (simply with mongrel_rails start). I try to access the server and the first page (static file) loads, but then the server dies and I get this in the logs. I''m

Hi One of the two mongrel processes has died in the middle of the night four times in the past 9 days, and I need help debugging this. Each time the symptoms are the same: * Each time I can restart the process via cap -a restart_app. * Before the restart, there is nothing unusual in production.log or mongrel.log. * During the restart, about 100 repetitions of an error message are generated in

Hi, Anyone succeeded in installing Mongrel on Sun Solaris? It looks like the installation is broken. I have started using Mongrel recently and not sure where to look when something is missing. First the file http11.so was not installed in /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib I''ve resolved that and when tried to start mongrel from the command line I received the

Hello, I''ve install ror/mongrel etc, etc on a linux server (rhes). As i''m not root, all package startinf from ruby have been install into ~/gconf/usr ruby-1.8.6 and all of this gem package: -r-xr--r-- 1 dimnce dba 168448 Aug 9 14:53 rails-1.2.3.gem -r-xr--r-- 1 dimnce dba 84480 Aug 9 14:56 rake-0.7.3.gem -r-xr--r-- 1 dimnce dba 217088

Hi, I am experiencing an error in the mongrel_rails script on a pc under cygwin/mongrel/rails. My installation details and error are as follows: With some guidance from various blogposts out there, I installed Cygwin on a Windows XP box followed by: Ruby 1.8.4(via cygwin setup), Gems (0.8.1 via ruby install.rb), Mongrel .3.12.4 (via gems), Rake 0.7.1(via gems, GemPlugin (via gems), Rails (via

We have a bunch of strange entries in our error log, and don''t know exactly what they mean: The errors are as follows ActionController::NotImplemented (Only requests are allowed.): /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/ routing.rb:1437:in `recognize_path'' /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/ routing.rb:1424:in

Dear ALL, I saw this in article from mongrel faq, Q: Mongrel stops working if it''s left alone for a long time. If you find that Mongrel stops working after a long idle time and you''re using MySQL then you''re hitting a bug in the MySQL driver that doesn''t properly timeout connections. What happens is the MySQL *server* side of the connection times out and

I am having different results between when I start mongrel with script/ server and with mongrel_rails start. When I run script/server to boot mongrel everything runs fine, no errors. When I run mongrel_rails start I get the following errors - verified the problem on a fresh app and on two different environments (mac and yes, windows server 2008). The actual line of fault changes but the problem

Hello Everyone, Mongrel is due for a 0.3.12 release which will feature some pretty insane goodies for everyone. There''s talk of IOWA support, lots of speed improvements (including sendfile support), a great Configurator which makes configuring Mongrel a snap (especially for framework implementers), and a ton of debugging stuff. WARNING This is a pre-release announcement for the

[That subject line is of course a severe truncation!] I''ve got a REST request that works fine from curl but causes a mongrel error when executed from a Java program. This all worked with fine with rails 1.1.6 and webrick. I''m trying to update the app to rails 1.2.1 (I need working around_filters). I''m running in development mode with mongrel 1.01 running on macosx

Following errors are taken from monrgrel running in development mode. It complained routes.rb, no such file or directory and then sometimes i get application.rb, no such file or directory.Doesn''t seem correct to me. Though not so often, but even production servers throw these errors sometimes, and i have no special routes setup or something.Its pretty much default one, except few changes