mhearse:
While I'm not aware of any way to see which process send you a signal, I am wondering if you might possibly be hitting a ulimit problem? Perhaps your program is running overlong and the kernel thinks it's been long enough or some such?
...roboticus
| [reply]
[d/l] |
Hmmm... That is possible. I should also mention that this only happens when running from the web. Running the same thing from the command line doesn't receive a SIGKILL.
| [reply] |
| [reply]
[d/l] |
I checked the ulimit for a regular user and the webserver user. They both appear to be unlimited.
| [reply] |
mhearse:
I have no Apache-fu, but perhaps it manages its child threads and kills 'em when it considers them unresponsive?
The only other suggestion I can think of is to perhaps suspend all other processes that aren't absolutely critical for your application and see if the signals go away. Then you can use a binary search to figure out which one of the ones you turned off was the culprit.
...roboticus
| [reply] |
It was a ulimit after all. Not one enforced by the operating system, but someething tied into our proprietary system...
| [reply] |
| [reply] |