Note that there are some explanatory texts on larger screens.

plurals
  1. PORainbows worker is being killed after timeout even though it replied
    primarykey
    data
    text
    <p>I have a Sinatra app running on Rainbows. I log the following :</p> <pre><code>before do logger.info("#{Process.pid} #{Time.now} #{request.ip} #{request.path_info} # {params.to_s}") end </code></pre> <p>and</p> <pre><code>after do logger.info("#{Process.pid} #{Time.now} #{request.ip} #{request.path_info} #{params.to_s} =&gt; #{response.headers['X-API-Status']} (#{response.successful?})") end </code></pre> <p>and in my logs I can read:</p> <pre><code>25988 2012-11-13 11:57:52 +0100 192.168.90.1 /req {"u"=&gt;"810000027"} 25988 2012-11-13 11:57:59 +0100 192.168.90.1 /req {"u"=&gt;"810000027"} =&gt; 200 (true) 192.168.90.1 - - [13/Nov/2012 11:57:59] "POST /req HTTP/1.1" **200** 14 7.5862 25988 2012-11-13 11:57:59 +0100 192.168.90.1 /req {"u"=&gt;"810000027"} 25988 2012-11-13 11:57:59 +0100 192.168.90.1 /req {"u"=&gt;"810000027"} =&gt; 200 (true) 192.168.90.1 - - [13/Nov/2012 11:57:59] "POST /req HTTP/1.1" 200 14 0.0223 E, [2012-11-13T11:58:04.099913 #25875] ERROR -- : worker=2 PID:**25988** timeout (12s &gt; 11s), killing E, [2012-11-13T11:58:04.106428 #25875] ERROR -- : reaped #&lt;Process::Status: pid 25988 SIGKILL (signal 9)&gt; worker=2 </code></pre> <p>My worker (pid 25988) is being killed as if it had not responded to the first request... But it has, obviously! It even handled another request (and I use Base concurrency model -> no concurrency)</p> <p>My Rainbows configuration is:</p> <pre><code>Rainbows! do timeout(10) end listen(3000) pid('/tmp/rainbows.pid') stderr_path('/var/log/rainbows.log') stdout_path('/var/log/rainbows.log') working_directory('/opt/app') worker_processes(4) </code></pre> <p>Do you have any idea of what happens ? Or how I could investigate further ? Thanks !</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload