Comment 5 for bug 265855

No, having multiple versions of Python should not be causing
this. Nor should the SIGALRM handler being triggered cause
it, unless something is seriously broken in your setup --
but we've already been there.

The only way to see if a SIGTERM is actually being delivered
is running the processes under strace or gdb, but this
seriously disrupts regular operation. There is no way that i
know of to find out where a signal is coming from, once you
find out that it really is a signal. If it *isn't* a real
signal, I would start looking at libc bugs and other
platform bugs. You can try upgrading Python to 2.2.2 (the
latest bugfix release) but I would be very suprised if it
fixed your problem. RedHat does not have a great reputation
for stability, so be sure to check for any RedHat updates.