thanks. Here are logs from uwsgi.log, all of them are complaining death or relives:
...The work of process 7583 is done. Seeya! DAMN ! process 7533 died :( trying respawn ... Respawned uWSGI worker (new pid: 7655) DAMN ! process 7583 died :( trying respawn ... worker respawning too fast !!! i have to sleep a bit... ...The work of process 7238 is done. Seeya! ./pyxn/__init__.py:59: DeprecationWarning: the md5 module is deprecated; use hashlib instead import md5 Respawned uWSGI worker (new pid: 7716) DAMN ! process 7238 died :( trying respawn ... worker respawning too fast !!! i have to sleep a bit... Respawned uWSGI worker (new pid: 7766) ./pyxn/__init__.py:59: DeprecationWarning: the md5 module is deprecated; use hashlib instead import md5 ./pyxn/__init__.py:59: DeprecationWarning: the md5 module is deprecated; use hashlib instead import md5 ./pyxn/__init__.py:59: DeprecationWarning: the md5 module is deprecated; use hashlib instead import md5 ...The work of process 7766 is done. Seeya! DAMN ! process 7766 died :( trying respawn ... Respawned uWSGI worker (new pid: 7849) ...The work of process 7299 is done. Seeya! ...The work of process 7716 is done. Seeya! ./pyxn/__init__.py:59: DeprecationWarning: the md5 module is deprecated; use hashlib instead import md5 DAMN ! process 7299 died :( trying respawn ... Respawned uWSGI worker (new pid: 7905) DAMN ! process 7716 died :( trying respawn ... worker respawning too fast !!! i have to sleep a bit... ./pyxn/__init__.py:59: DeprecationWarning: the md5 module is deprecated; use hashlib instead import md5 Respawned uWSGI worker (new pid: 7971) ./pyxn/__init__.py:59: DeprecationWarning: the md5 module is deprecated; use hashlib instead import md5 ...The work of process 7971 is done. Seeya! ...The work of process 7849 is done. Seeya! ...The work of process 7905 is done. Seeya! DAMN ! process 7849 died :( trying respawn ... Respawned uWSGI worker (new pid: 8043) DAMN ! process 7905 died :( trying respawn ... worker respawning too fast !!! i have to sleep a bit... Respawned uWSGI worker (new pid: 8093) DAMN ! process 7971 died :( trying respawn ... worker respawning too fast !!! i have to sleep a bit... Respawned uWSGI worker (new pid: 8144) On Tue, Mar 8, 2011 at 5:27 PM, Roberto De Ioris <[email protected]> wrote: > > Il giorno 08/mar/2011, alle ore 10.09, Samuel ha scritto: > > > Hi, > > > > I'm very new to server administration, and I cannot find some tech guys > to help me currently. My server is almost down, actually it was down this > morning, but alive this afternoon. > > > > I got a lot of error log like > > > > 2011/03/08 17:04:46 [error] 8041#0: *390310 upstream prematurely closed > connection while reading response header from upstream, client: > 114.255.28.23, server: 17bdc.com, request: "GET / HTTP/1.1", upstream: > "uwsgi://192.168.155.99:8088" > > > > The error causes a lot of request abortions or timeouts, and the server > is very very slow. > > > > Thanks for your suggestions and possible fixes in advance. > > > > All my servers below are instances on linode vps. I'm thinking if any > relevance with vps. > > > > > > server structures: > > nginx server (svr nginx) + nginx_server_app (srv nginx_app) + 3 apps > server (svr app1-3) > > + 3 apps server ( > svr4-6) > > + 1 db server(db) + 1 > memcached server (memcached) > > > > svr app1-3 serve heavily loaded urls: /reviews/fetch/, /review/status/. > > srv app4-6 serve all the other urls > > > > nginx configuration: > > > > worker_processes 7; > > > > > > > > Hi, uWSGI has its logfile, can you check/report its content ? > > From what you are saying it looks like uWSGI is blocked in some way. > > -- > Roberto De Ioris > http://unbit.it > > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > -- Samuel
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
