WEBRick process not responding after few hours (rails 1.1.6 on linux)

rubyonrails-talk
1

the rail application I have developed (really simple one 2 -> db tables with no more than 100 records) works perfectly in development / production mode on my windows desktop (win200 pro + mysql + ruby 1.8.2 + rails 1.1.6). when deploying the application on linux (ruby 1.8.4 , rails 1.1.6 the same mysql as on windows) everything *seems* to work fine. well atleast for the first few hours. the next morning the rails application just don't react. it is even stranger since the webrick process still runs! I have checked the log files and there is nothing wrong with them. the probelm gets even stranger since I have deployed the application on another linux machine (Ubunto) and exactly the same happend. do I need to start WEBRick as root? do I have to install another server? does anyone has some idea?

2

s/Ubunto/Ubuntu/g :wink:

There are _no_ root privileges needed if you run it on a port above 1024.

Webrick runs, no reaction and nothing wrong in logfiles? Is there connection information for accessing the application or not? What's with netstat? Is it still listening on the specified port? Is Webrick really not responding or is something wrong with the app? Switch debug on to find out more. Use a tcp dump to know what's going over the network...

3

Hi, netstat tells me (see output at the end of post) that webrick is listening to port 3001, further more when I request hostname:3001 I see the welcome page of rails. when requesting any of my controller's url then webrick seems not to respond well atleast judging from the log files.

<output> tcp 0 0 0.0.0.0:3001 0.0.0.0:* LISTEN 16728/ruby tcp 1 0 192.168.5.33:3001 192.168.5.75:2927 CLOSE_WAIT 16728/ruby tcp 1 0 192.168.5.33:3001 192.168.5.75:2935 CLOSE_WAIT 16728/ruby tcp 1 0 192.168.5.33:3001 192.168.5.75:3396 CLOSE_WAIT 16728/ruby tcp 1 0 192.168.5.33:3001 192.168.5.75:2906 CLOSE_WAIT 16728/ruby tcp 1 0 192.168.5.34:3001 192.168.5.75:3657 CLOSE_WAIT 16728/ruby tcp 1 0 192.168.5.33:3001 192.168.5.60:1314 CLOSE_WAIT 16728/ruby tcp 1 0 192.168.5.34:3001 192.168.5.75:3931 CLOSE_WAIT 16728/ruby tcp 1 0 192.168.5.34:3001 192.168.5.75:2500 CLOSE_WAIT 16728/ruby tcp 0 0 192.168.5.34:3001 192.168.5.75:4006 VERBUNDEN 16728/ruby tcp 1 0 192.168.5.34:3001 192.168.5.75:2490 CLOSE_WAIT 16728/ruby tcp 1 0 192.168.5.34:3001 192.168.5.75:2460 CLOSE_WAIT 16728/ruby tcp 0 0 192.168.5.34:3001 192.168.5.75:3997 VERBUNDEN 16728/ruby
</output>