[mod_python] Mod_python quit working

Dan R. Olsen III wrote:

>
>>>>> Yes, I've restarted Apache and I have echoed a simple string and 
>>>>> niether of those have worked.
>>>>
>>>
>>>> Try getting the page with 'wget', see what headers you get back and if
>>>> there is any content.
>>>
>>>
>>> I get the following:
>>>
>>> --12:38:00--  http://dev.eclab.byu.edu/rose.py
>>>            => `rose.py'
>>> Resolving dev.eclab.byu.edu... 128.187.170.133
>>> Connecting to dev.eclab.byu.edu[128.187.170.133]:80... connected.
>>> HTTP request sent, awaiting response...
>>> 12:38:00 ERROR -1: No data received.
>>
>>
>>
>> What does it say in the apache logs?
>
>
> [Tue Jan 11 06:03:25 2005] [notice] mod_python: (Re)importing rose 
> from None
> [Tue Jan 11 06:03:25 2005] [notice] mod_python: (Re)importing rose 
> from None
> [Tue Jan 11 06:03:25 2005] [notice] child pid 2243 exit signal 
> Segmentation fault (11)
> [Tue Jan 11 06:03:25 2005] [notice] child pid 8161 exit signal 
> Segmentation fault (11)
> [Tue Jan 11 06:03:33 2005] [notice] mod_python: (Re)importing rose 
> from None
> [Tue Jan 11 06:03:33 2005] [notice] child pid 2245 exit signal 
> Segmentation fault (11)

This is likely a hardware issue.  Possibly RAM going bad, (or possibly 
even a dead CPU fan!)
When you hit the page the server process is having it's memory corrupted 
(thus the Signal 11 segfault),
and dies w/ no reply.


--   M. Dragon