quetz-mod_python-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Graham Dumpleton" <graham.dumple...@gmail.com>
Subject Re: Debian bug#433038: mod_python collides with mod_php5
Date Fri, 31 Aug 2007 06:21:08 GMT
In 411487 it mentions:

"""So, it seems it's directly related to libmhash2 (as [2] suggests)."""

Disabling of mhash module may not be enough if one of the other PHP
modules they list in 433038 also use libmhash2 library. Quite possible
that one of the crypto libraries use it, or the ldap module mentioned
in the mod_python mailing list mail.

Can you run ldd on main PHP module and all PHP modules and see which
one has a dependency on libmhash2, or any other md5 hash library.

Basic problem as we understand it is that libmhash2 uses a symbol name
which clashes with one used by Python md5 module. Which ever gets
loaded first, usually PHP version, takes precedence and since that is
not compatible with other package a crash occurs.

If it can be determined that it is libmhash2 and then which symbol in
it clashes with one in Python md5 module, one or the other could
somehow be namespace escaped to avoid the problem.

Graham

On 31/08/2007, Robert Edmonds <edmonds@debian.org> wrote:
> Hi,
>
> I'm one of the Debian maintainers of the libapache2-mod-python package.
> Could someone please take a look at the report filed here?
>
>     http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=433038
>
> The user writes,
>
>     If libapache2-mod-python is installed together with libapache2-mod-php5,
>     (at least) the mod_python.psp handler fails immediately without any proper
>     error message.
>
>     This also happens if the php5 mhash module is uninstalled, purged and
>     apache is restarted.  mod_python starts working immediately if mod-php5 is
>     disabled using "a2dismod php5" and restarting apache.
>
>     [...]
>
>     This effectively renders mod_python.psp unusuable as soon as mod-php5
>     (maybe together with some specific modules) is installed and it's also hard
>     to debug as there's no indication whatsoever of what is going wrong, other
>     than that it "doesn't work".
>
> More details are on the page.  I'm afraid I'm having difficulties
> tracking down the root cause of the user's problem.
>
> --
> Robert Edmonds
> edmonds@debian.org
>
>

Mime
View raw message