Apache Child Segfaults
I have been getting a LOT of these lately: [Sat Sep 28 19:50:25 2002] [notice] child pid 22504 exit signal Segmentation fault (11) [Sat Sep 28 19:50:26 2002] [notice] child pid 15395 exit signal Segmentation fault (11) [Sat Sep 28 20:28:59 2002] [notice] child pid 22621 exit signal Segmentation fault (11) [Sat Sep 28 20:28:59 2002] [notice] child pid 22620 exit signal Segmentation fault (11) [Sat Sep 28 23:12:39 2002] [notice] child pid 22560 exit signal Segmentation fault (11) [Sat Sep 28 23:12:39 2002] [notice] child pid 22531 exit signal Segmentation fault (11) [Sat Sep 28 23:12:41 2002] [notice] child pid 22615 exit signal Segmentation fault (11) [Sat Sep 28 23:12:41 2002] [notice] child pid 22562 exit signal Segmentation fault (11) Any ideas what they mean? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Apache Child Segfaults
Oops, missed the list the first reply around.. On Sun, 2002-09-29 at 12:52, Matthew Daubenspeck wrote: On Sun, Sep 29, 2002 at 12:37:23PM -0500, Justin Ryan wrote: what version of apache are you running ? there is a known vuln that can root a box on 64-but unix and windows and causes the child to die oni 32-bit unix.. $ apache -version Server version: Apache/1.3.26 (Unix) Debian GNU/Linux Am I to assume that all updates are applied? mod_ssl, OpenSSL? any related logs? can you cross-reference times to accesses of URLs? Perhaps a script is causing it somehow.. I'll end this with a great big Hrm.. :) -Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Apache Child Segfaults
what version of apache are you running ? there is a known vuln that can root a box on 64-but unix and windows and causes the child to die oni 32-bit unix.. $ apache -version Server version: Apache/1.3.26 (Unix) Debian GNU/Linux Am I to assume that all updates are applied? mod_ssl, OpenSSL? Yup, all updated and as current as 'sarge' permits :) any related logs? can you cross-reference times to accesses of URLs? Perhaps a script is causing it somehow.. That it is in the error logs. There was a standard 404 error now and then, I thought it may have something to do with it. I fixed the 404, and the problem still persists. I'll end this with a great big Hrm.. :) Me too :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Apache Child Segfaults
Am I to assume that all updates are applied? mod_ssl, OpenSSL? Yup, all updated and as current as 'sarge' permits :) what versions? since testing doesn't have security updates, it's possible that these are lagging.. any SSL related log entries? any related logs? can you cross-reference times to accesses of URLs? Perhaps a script is causing it somehow.. That it is in the error logs. There was a standard 404 error now and then, I thought it may have something to do with it. I fixed the 404, and the problem still persists. what I meant to ask was, can you cross reference the times with the access_log and find anything interesting? grab 10 or so of them and grep for the time (as well as one minute before/after just in case) to see if anything common is being accessed.. it's possible (though unlikely) that something which apache would not log as a specific error would cause the child to die.. -Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Apache Child Segfaults
On Sun, Sep 29, 2002 at 02:38:53PM -0500, Justin Ryan wrote: Am I to assume that all updates are applied? mod_ssl, OpenSSL? Yup, all updated and as current as 'sarge' permits :) what versions? since testing doesn't have security updates, it's possible that these are lagging.. any SSL related log entries? $ dpkg -l apache ||/ NameVersion Description +++-===-===-== ii apache 1.3.26-1.1 Versatile, high-performance HTTP server what I meant to ask was, can you cross reference the times with the access_log and find anything interesting? grab 10 or so of them and grep for the time (as well as one minute before/after just in case) to see if anything common is being accessed.. it's possible (though unlikely) that something which apache would not log as a specific error would cause the child to die.. Sorry, yes, I checked this out as well. Nothing out of the ordinary that I could see. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Apache Child Segfaults
what versions? since testing doesn't have security updates, it's possible that these are lagging.. any SSL related log entries? $ dpkg -l apache ||/ NameVersion Description +++-===-===-== ii apache 1.3.26-1.1 Versatile, high-performance HTTP server howabout openssl, libapache-mod-ssl? if openssl is 0.9.6e check the changelog and reference against the most recent DSA's on openssl. other than that, im stumped.. anything in error.log that looks like: Received Signal Segmentation Fault (11) -Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
