View Single Post
  #1  
Old 29th July 2012, 22:05
Ovidiu Ovidiu is offline
Senior Member
 
Join Date: Sep 2005
Posts: 1,259
Thanks: 76
Thanked 23 Times in 19 Posts
Default Got a FASTCGI problem after my latestupdate

The server (a small VPS) is set up according to this how-to: http://www.lowendbox.com/blog/wordpr...-lowendscript/

The problems started after the last update:

apticron report [Fri, 27 Jul 2012 00:41:08 -0300]
================================================== ======================

apticron has detected that some packages need upgrading on:

The following packages are currently pending an upgrade:

mysql-client-5.5 5.5.25a-1~dotdeb.1
mysql-client-core-5.5 5.5.25a-1~dotdeb.1
mysql-common 5.5.25a-1~dotdeb.1
mysql-server 5.5.25a-1~dotdeb.1
mysql-server-5.5 5.5.25a-1~dotdeb.1
mysql-server-core-5.5 5.5.25a-1~dotdeb.1
php5-cgi 5.3.15-1~dotdeb.0
php5-cli 5.3.15-1~dotdeb.0
php5-common 5.3.15-1~dotdeb.0
php5-curl 5.3.15-1~dotdeb.0
php5-gd 5.3.15-1~dotdeb.0
php5-mcrypt 5.3.15-1~dotdeb.0
php5-mysql 5.3.15-1~dotdeb.0
php5-suhosin 5.3.15-1~dotdeb.0

When I did these updates, I always chose to keep my configs and not to replace them with the distro ones. I am facing the problem that php-cgi seems to "freeze" to death, it doesn't seem to serve anything, it works for a few hours, then it freezes and only starts working again after I killall -9 php-cgi and then starting it again as restarting it doesn't work either.
All I get are these errors in nginx error log:

2012/07/29 09:26:21 [error] 18038#0: *1909 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 173.245.52.14, server: knightsenglish.com, request: "GET / HTTP/1.0", upstream: "fastcgi://127.0.0.1:9000", host: "www.knightsenglish.com", referrer: "http://www.knightsenglish.com/"

Any ideas what could be wrong here? Any starting points to investigate? All this happened this weekend where there was almost zero traffic, I checked with netstat and there were maybe 10 connections active only :-(

As a first try, after googling this issue I added this value to my nginx configs: proxy_read_timeout 120; but that didn't change much.
Reply With Quote
Sponsored Links