I reinstalled my web app on a new VM, and merged Nginx and Rails on the
same VM, and I still got the conneciton close problem, but now it
happens between the Postgresl VM and my rails app one.
So there is definitely a problem between Rails and Postgresql.
Taken from
--
The postgres gem is
On Wed, Jul 22, 2009 at 2:04 AM, Fernando Perez
rails-mailing-l...@andreas-s.net wrote:
This morning all my Thin process are stuck again :-(, something seems to
happen during the night or at least during a long period of time so that
all processes end up blocked.
Have you done any sand-box
Have you done any sand-box (i.e. staging server) testing prior to
migrating
your production application
from 2.3.2 to 2.3.3?
Everything works fine on my dev machine, and everything works fine (for
a limited time though) on the production server. This problem appeared
prior to upgrading
Cool my processes are blocking and here is what $ netstat -anp is giving
me:
Proto Recv-Q Send-Q Local Address Foreign Address
State PID/Program name
[...]
tcp 1239 0 10.0.0.2:3100 10.0.0.1:36186
CLOSE_WAIT -
tcp1 0 10.0.0.2:3100
Damn it was a former zombie Thin process that was still causing trouble!
With kill -9 and restarting all new Thin instances to take advantage of
the updated gem seems to have resolved the problem. I'll still keep an
eye on it, and provide feedback.
--
Posted via http://www.ruby-forum.com/.
5 matches
Mail list logo
