[mod_python] problems with 2.0 -> 2.3 upgrade
Gregory Trubetskoy
grisha at modpython.org
Sun Jun 11 16:03:47 EST 2000
Someone else reported this and I know what the problem is.
There are two things you can do:
1. downgrade to 2.2 and wait until 2.4
2. add a dummy PythonImport statement in the httpd.conf file between some
<Directory> tags, e.g.
PythonImport string
This is because I added the new PythonImport derective and did all the
testing and it worked fine, except when the directive is NOT specified and
thus the variable that holds the info is undefined.... Sorry, I'll be more
thorough next time!
--
Gregory (Grisha) Trubetskoy
grisha at modpython.org
On Sun, 11 Jun 2000, richard offer wrote:
>
> Hi,
>
> I upgraded from 2.0 to 2.3 this morning and am now seeing the following
> error message in the webservers log file
>
> [Sun Jun 11 12:23:33 2000] [notice] child pid 7340 exit signal Segmentation fault (11)
> [Sun Jun 11 12:23:33 2000] [notice] child pid 7339 exit signal Segmentation fault (11)
> [Sun Jun 11 12:23:35 2000] [notice] child pid 7343 exit signal Segmentation fault (11)
> [Sun Jun 11 12:23:36 2000] [notice] child pid 7345 exit signal Segmentation fault (11)
> [Sun Jun 11 12:23:36 2000] [notice] child pid 7344 exit signal Segmentation faul
>
>
> It seems like all child webservers are dying, but the master is running
> in a continous loop trying to spawn the children.
>
>
> Moving the old (2.0) DSO and python code back into place fixed it.
>
> [ Running Apache 1.3.12 on Redhat 6.1/2.2.16 ]
>
>
> Any hints ?
>
> richard.
>
> --
> richard offer @ home
> 84 FE 48 E4 74 D0 26 D4 31 8E B6 86 98 74 E2 7C 8A FB BF A3
> ___________________________________http://216.185.15.144/users/richard/
> _______________________________________________
> Mod_python mailing list
> Mod_python at modpython.org
> http://www.modpython.org/mailman/listinfo/mod_python
>
More information about the Mod_python
mailing list