On Wed, 2002-09-04 at 02:00, Ole Moller Nielsen wrote:
> Dear all
> I have recently made a WebKit application (a proximity searchable MySQL
> database of GPS points)
> and had been very happy with the way it works. The URL is
> I was especially impressed by the speedup obtained by using the WebKit
> However, I have observed over time that it tends to somehow die or
> become non-functional even though
> its processes are still alive.
Are you using any C modules? These are the most prone to problems --
memory leaks, segmentation faults, etc. You might not notice the
problems until the module has been loaded for days (like in Webware). I
haven't seen any complaints about this for MySQLdb, though (but other
database adapters have had occasional problems).
> Restarting it solves the problem, but often it can't be restarted
> without booting the system to get rid of
> all the 'ghost' processes.
> Has anyone observed something similar?
> And has anyone and idea how to solve the problem?
I sometimes get ghost processes that hang around for a short while, but
not long. Sometimes a port gets left open (I think FreeBSD was having
the most problems), but I think that's been somewhat resolved (or at
least I haven't had problems for a while, and no one's mentioned it on
the list). If the port is open, you'll get an error when restarting the
AppServer (Address In Use or something).
Have you tried killing the server more forcefully? Like "killall -9
python" ? What platform are you on?