Comment 6 for bug 247227

This continues to be a problem.

2008-07-28 14:04 UTC - lpnet1 had died and left stale pidfile - restarted
2008-07-27 21:40 UTC - staging had died and left stale pidfile - restarted
2008-07-25 20:05 UTC - lpnet2 had died and left stale pidfile - restarted
2008-07-25 18:58 UTC - lpnet2 had died and left stale pidfile - restarted
2008-07-25 11:28 UTC - lpnet2 had died and left stale pidfile - restarted
2008-07-25 09:15 UTC - lpnet4 had died and left stale pidfile - restarted
2008-07-24 01:40 UTC - staging had died and left stale pidfile - restarted
2008-07-22 18:38 UTC - lpnet3 had died and left stale pidfile - restarted
2008-07-18 18:55 UTC - lpnet1 had died and left stale pidfile - restarted
2008-07-14 17:38 UTC - lpnet7 had died and left stale pidfile - restarted
2008-07-11 16:11 UTC - lpnet3 had died and left stale pidfile - restarted
2008-07-10 08:40 UTC - lpnet6 had died and left stale pidfile - restarted

I have collected log files for a handful of these incidents listed above and can put them in a shared location for someone to look at.

I also tested Stuart's hypothesis above. Despite killing all lpnet1's connections to the DB, the app server continued running and happily reconnected.