[mod_python] Apache children crashing with mod_python 3.0 beta4

See the README file. On FreeBSD you need to have threads enabled in both
Python and Apache. The default Python port will have threads enabled, and
to make Apache thread-enabled, you need --enable-threads in the Makefile.

On Sun, 10 Nov 2002, Arcady Genkin wrote:

> I'm trying out mod_python-3 beta 4 on FreeBSD 4.7.  Python is version
> 2.2.2 compiled from ports without threading support.  Apache is 2.0.43
> compiled from ports with threads enabled, running with default
> configuration (apart from mod_python customizations); mod_python is
> the only non-stock module loaded into it.
>
> Even though mod_python seems to be working fine, I am seeing the
> following in the apache's error logs:
>
> Fatal Python error: PyThreadState_Delete: tstate is still current
> Fatal Python error: PyThreadState_Delete: tstate is still current
> Fatal Python error: PyThreadState_Delete: tstate is still current
> Fatal Python error: PyThreadState_Delete: tstate is still current
> [Sun Nov 10 12:29:32 2002] [notice] child pid 27272 exit signal Abort trap (6)
> [Sun Nov 10 12:29:32 2002] [notice] child pid 27267 exit signal Abort trap (6)
> [Sun Nov 10 12:29:32 2002] [notice] child pid 27266 exit signal Abort trap (6)
> [Sun Nov 10 12:29:32 2002] [notice] child pid 27265 exit signal Abort trap (6)
>
> How likely is this due to a misconfiguration?  Any pointers?
>
> Many thanks,
> --
> Arcady Genkin
>
> guilt is the cause of more disauders
> than history's most obscene marorders                       (E.E. Cummings)
> _______________________________________________
> Mod_python mailing list
> Mod_python at modpython.org
> http://www.modpython.org/mailman/listinfo/mod_python
>