Eric,
The problem is a firewall that sits between the servers and the database.
It is an idle session timeout of 30 minutes, so it is silently killing the
connection. I have reached out to our Network Engineering department but
they are saying they can not change that idle session timeout, nor c
I appreciate all your help Eric and Daniel. I have not solved this yet,
but I think I have narrowed it down to a Firewall timeout issue. One app
uses a database connection to Oracle, the other app uses a 3rd Party API
(still on location, but across the network). The ping times to both of
these d
Yep, it occurs after 30 minutes of inactivity. Down to the minute; I hit
the site at 3:40 and tried at 4:10 and sure enough:
E, [2014-08-04T16:10:52.143541 #2596] ERROR -- : worker=3D0 PID:2599 timeou=
t
(21s > 20s), killing
E, [2014-08-04T16:10:52.158459 #2596] ERROR -- : reaped # worker=3D0
I,
Thank you Eric,
I will look into the other worker to see what is going on with it. I still
appreciate any hints you all can give me on where I can check. I'm also
looking into the OS TCP timeouts to see if what Daniel said may be a
problem.
Eric Wong wrote:
>
> OK. Does the other app conne
Eric,
Thank you for responding. We use a database on only one of the apps, it is
a Oracle 11G RAC Server. I'll get the DBA to double check the idle timeout
for that DB. Though the other app does not use a database.
On Mon, Aug 4, 2014 at 2:39 PM, Eric Wong wrote:
> Tony Devli
Current Setup: (the problem existed before updating nginx, unicorn and
rails; but in an attempt to solve the problem I updated them).
CentOS 6.3 (x64)
Ruby 2.1.2p95
Rails 4.0.0
Nginx 1.6.0
Unicorn 4.8.3
We have an issue where if a site is not accessed for around (average) 30
minutes the ne
