Project

General

Profile

Forums » Help »

503 Service unavailable (mongrel + xampp)

Added by Pablo Bleyer about 14 years ago

Hi.

I am having problems with my Redmine installation on a Windows machine running xampp. Apache talks to mongrel via mod_fcgid. Everything was perfectly, however if mongrel is inactive for a while, I get a 503 error through Apache opening the Redmine page. After a minute or so, the connection works again and stays like that till other period of inactivity.
I have trying modifying the MySQL timeout but I don't think this is the source of the problem. My Apache error logs look like this:

[Tue Feb 23 09:34:43 2010] [error] [client 192.168.65.146] (OS 10054)An existing connection was forcibly closed by the remote host. : proxy: error reading status line from remote server localhost
[Tue Feb 23 09:34:44 2010] [error] (OS 10061)No connection could be made because the target machine actively refused it. : proxy: HTTP: attempt to connect to 127.0.0.1:3000 (localhost) failed
[Tue Feb 23 09:34:44 2010] [error] ap_proxy_connect_backend disabling worker for (localhost)

Does somebody have a clue?
Thanks. Regards.

Replies (4)

RE: 503 Service unavailable (mongrel + xampp) - Added by Pablo Bleyer about 14 years ago

BTW, I just looked at the Mongrel logs and I can see that I am getting segfaults:

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
  • Starting Mongrel listening at 0.0.0.0:3000
  • Starting Rails with production environment...
  • Rails loaded.
  • Loading any Rails specific GemPlugins
  • Signals ready. INT => stop (no restart).
  • Mongrel 1.1.5 available at 0.0.0.0:3000
  • Use CTRL-C to stop.
  • INT signal received.
  • Starting Mongrel listening at 0.0.0.0:3000
  • Starting Rails with production environment...
  • Rails loaded.
  • Loading any Rails specific GemPlugins
  • Signals ready. INT => stop (no restart).
  • Mongrel 1.1.5 available at 0.0.0.0:3000
  • Use CTRL-C to stop.
    C:/xampp/redmine/vendor/rails/activerecord/lib/active_record/connection_adapters/mysql_adapter.rb:589: [BUG] Segmentation fault
    ruby 1.8.6 (2008-08-11) [i386-mswin32]
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
  • Starting Mongrel listening at 0.0.0.0:3000
  • Starting Rails with production environment...
  • Rails loaded.
  • Loading any Rails specific GemPlugins
  • Signals ready. INT => stop (no restart).
  • Mongrel 1.1.5 available at 0.0.0.0:3000
  • Use CTRL-C to stop.
  • INT signal received.
  • Starting Mongrel listening at 0.0.0.0:3000
  • Starting Rails with production environment...
  • Rails loaded.
  • Loading any Rails specific GemPlugins
  • Signals ready. INT => stop (no restart).
  • Mongrel 1.1.5 available at 0.0.0.0:3000
  • Use CTRL-C to stop.
  • INT signal received.
  • Starting Mongrel listening at 0.0.0.0:3000
  • Starting Rails with production environment...
  • Rails loaded.
  • Loading any Rails specific GemPlugins
  • Signals ready. INT => stop (no restart).
  • Mongrel 1.1.5 available at 0.0.0.0:3000
  • Use CTRL-C to stop.
    C:/xampp/redmine/vendor/rails/activerecord/lib/active_record/connection_adapters/mysql_adapter.rb:589: [BUG] Segmentation fault
    ruby 1.8.6 (2008-08-11) [i386-mswin32]
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
  • Starting Mongrel listening at 0.0.0.0:3000
  • Starting Rails with production environment...
  • Rails loaded.
  • Loading any Rails specific GemPlugins
  • Signals ready. INT => stop (no restart).
  • Mongrel 1.1.5 available at 0.0.0.0:3000
  • Use CTRL-C to stop.
    C:/xampp/redmine/vendor/rails/activerecord/lib/active_record/connection_adapters/mysql_adapter.rb:589: [BUG] Segmentation fault
    ruby 1.8.6 (2008-08-11) [i386-mswin32]
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
  • Starting Mongrel listening at 0.0.0.0:3000
  • Starting Rails with production environment...
  • Rails loaded.
  • Loading any Rails specific GemPlugins
  • Signals ready. INT => stop (no restart).
  • Mongrel 1.1.5 available at 0.0.0.0:3000
  • Use CTRL-C to stop.

RE: 503 Service unavailable (mongrel + xampp) - Added by Zachary Zimmerman about 14 years ago

I'm receiving the same errors. Any fixes for this issue?

RE: 503 Service unavailable (mongrel + xampp) - Added by Pablo Bleyer about 14 years ago

Hello Zachary.

I updated to 0.9.3 and used the Mysql DLL pointed to in the installation guide [http://instantrails.rubyforge.org/svn/trunk/InstantRails-win/InstantRails/mysql/bin/libmySQL.dll]. No crashes so far; keeping my fingers crossed.

Regards.

RE: 503 Service unavailable (mongrel + xampp) - Added by Markus Peter almost 14 years ago

Hello,

I was experiencing the same problems. I'm using MySQL 5.x, and putting the above mentioned dll in the ruby\bin directory seems to have fixed the problem.

    (1-4/4)