Ticket #1460 (new defect)

Opened 10 months ago

Last modified 7 months ago

TG crashes after a random amount of time not related to mysql connection

Reported by: gamegiants Assigned to: anonymous
Priority: high Milestone:
Component: CherryPy Version: 1.0.3
Severity: normal Keywords:
Cc:

Description

Upgraded from 1.0.1 to TurboGears-1.0.3.2-py2.4.egg TG crashes at random times when run as:

nohup ./start-ship.py > /dev/null 2>&1&

Used to have a similar problem under 1.0.1 related to losing the db connection but added a script to load the application every 15min via a cron job (this bug still not resolved in 1.0.3.2 should be a stopper!) to make sure the db connection is "pinged".

Application are now crashing in 1.0.3.2 even if the application does not use the db (does not even open a connection) or if it is "pinged" as descibed above

Change History

08/01/07 22:52:32 changed by gamegiants

Here is what it looks like when it goes down:

127.0.0.1 - - "GET /cat HTTP/1.1" 200 5516 "" "Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp)" 2007-08-01 20:00:02,125 cherrypy.msg INFO ENGINE: SystemExit? raised: shutting down autoreloader 2007-08-01 20:00:02,132 cherrypy.msg INFO HTTP: HTTP Server shut down 2007-08-01 20:00:02,147 cherrypy.msg INFO ENGINE: CherryPy? shut down

Right after getting crawled in this case....

10/03/07 16:17:39 changed by faide

Do you have any more info to give us ? I have one such case of system exit raised, but I know it comes from a Java library I use through jpype... in some special cases it brings down the entire python process without anythin I could do.

Do you have any special methods, libs or processes that could make the system exit happen... Do you monitor the resources on your machine ? I had a case where a server hosted on an OpenBSD server was starved for threads and just crashed badly...

Best regards and thanks for reporting this bug.

Florent.