Your message dated Fri, 14 Oct 2005 18:21:47 +0200
with message-id <[EMAIL PROTECTED]>
has caused the Debian Bug report #333117,
regarding apache2 + python + php + mysql not working
to be marked as having been forwarded to the upstream software
author(s) Andy Dustman <[EMAIL PROTECTED]>.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
---------------------------------------
Received: (at 333117-forwarded) by bugs.debian.org; 14 Oct 2005 16:21:56 +0000
>From [EMAIL PROTECTED] Fri Oct 14 09:21:56 2005
Return-path: <[EMAIL PROTECTED]>
Received: from ns1.kidns.de (diana50.kidns.de) [62.75.128.97]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EQSJf-0003xP-00; Fri, 14 Oct 2005 09:21:55 -0700
Received: from p54b2da2b.dip.t-dialin.net ([84.178.218.43] helo=resivo.mejo.net)
by diana50.kidns.de with esmtpsa (TLS-1.0:RSA_AES_256_CBC_SHA:32)
(Exim 4.50)
id 1EQSJQ-0004la-Ob; Fri, 14 Oct 2005 18:21:44 +0200
Received: from jonas by resivo.mejo.net with local (Exim 4.54)
id 1EQSJX-00053G-Hu; Fri, 14 Oct 2005 18:21:47 +0200
Date: Fri, 14 Oct 2005 18:21:47 +0200
From: Jonas Meurer <[EMAIL PROTECTED]>
To: Andy Dustman <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.11
X-SA-Exim-Connect-IP: 84.178.218.43
X-SA-Exim-Mail-From: [EMAIL PROTECTED]
Subject: MySQLdb Segfaults with mod_python and mod_php4 enabled in apache2
X-SA-Exim-Version: 4.2 (built Thu, 03 Mar 2005 10:44:12 +0100)
X-SA-Exim-Scanned: Yes (on diana50.kidns.de)
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
hello,
someone reported a bug against python-mysqldb in debian. He claimed that
MySQLdb segfaults when used by mod_python for apache2, but only in case
that mod_php4 is also enabled in apache2.
see http://bugs.debian.org/333117 for more information.
I successfully reproduced that bug, but unfortunately i've no idea where
to start debugging. I'm not even sure that this is related to the
MySQLdb python module.
I would be interested in what you think about it. Perhaps you can verify
that the bug exists, and maybe you have an assumption where it is located.
The bug can be produced by configuring apache2 to load mod_python and
mod_php4, and adding the following to apache2 configuration/.htaccess:
---snip ~/public_html/test/.htaccess ---
AddHandler mod_python .py
PythonHandler mod_python.publisher
PythonDebug On
---snip---
an example script to reproduce the segmentation fault:
---snip ~/public_html/test/test.py ---
import MySQLdb
def test ():
msq=MySQLdb.connect(user="username",passwd="******",db="test");
c=msq.cursor();
c.execute ("select * from table");
return c.fetchone();
---snip ---
if I open http://localhost/~jonas/test/test.py/test, an empty page
occurs, and error.log from apache2 gives:
[Fri Oct 14 09:14:37 2005] [notice] mod_python: (Re)importing module
'mod_python.publisher'
[Fri Oct 14 09:14:37 2005] [notice] mod_python: (Re)importing module 'test'
with path set to '['/home/jonas/public_html/test']'
[Fri Oct 14 09:14:38 2005] [notice] child pid 30427 exit signal Segmentation
fault (11)
the strange thing here is: when you disable the php4 module in apache2,
no segmenation fault, and the script works and the first query result is
printed as expected.
...
jonas
ps: did you test mysql-python with mysql 5.0? I plan to upload a package
built with mysql 5.0 soon, after running some rough tests and checking
backwards compatibility.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
