Forum: Ruby on Rails WEBrick freezes overnight

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
7b74ccf93dde7dd2ac5d2980d14fdc7b?d=identicon&s=25 Paul Lynch (plynchnlm)
on 2007-03-15 18:56
(Received via mailing list)
Each morning when I return to work, I find that my WEBrick server has
stopped working.  The process is still running, but when I try to
connect to it with a web browser, the browser doesn't get any response
back.  Usually when this happens I cannot control-c the process to
shut it down, and not even "kill" works-- I have to get rid of it with
kill -9.  I then restart it and it runs fine for the rest of the day.

Is this a known problem with WEBrick?  Or does it reflect some
configuration problem?

I am running WEBrick on RedHat Enterprise Linux.

6ef8cb7cd7cd58077f0b57e4fa49a969?d=identicon&s=25 Brian Hogan (Guest)
on 2007-03-15 19:35
(Received via mailing list)
Yeah, it'll do that.
Most folks use Mongrel now.

sudo gem install mongrel

Recent versions of Rails (1.2.x) use Mongrel when you run script\server
you have it installed.

Otherwise, start it with

mongrel_rails start -d

That runs it in the background on port 3000 in dev mode.

Stop it with

mongrel_rails stop
7aa3c32f034122ff929be64f5de237e7?d=identicon&s=25 Luciano Ramalho (Guest)
on 2007-03-16 03:25
(Received via mailing list)
A lot of current documents, books etc. about Rails clearly state that
WEBrick is to be used only for development and testing, and never for
production. Perhaps you missed that, Paul.

Like Brian said, that's why Mongrel was created.


This topic is locked and can not be replied to.