Debian Bug report logs - #410549
Apache children segfault after Wordpress 2.1 upgrade

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: "Frederic Wenzel" <freeed@gmail.com>

To: submit@bugs.debian.org

Subject: Apache children segfault after Wordpress 2.1 upgrade

Date: Sun, 11 Feb 2007 09:43:25 -0800

Package: libapache2-mod-php4
Version: 4.3.10

I am running debian sarge on my webserver, and after upgrading several
blogs to wordpress 2.1, frequent apache segfaults occur:

[Sun Feb 11 17:19:47 2007] [notice] child pid 24229 exit signal
Segmentation fault (11)
[Sun Feb 11 17:19:49 2007] [notice] child pid 26052 exit signal
Segmentation fault (11)
[Sun Feb 11 17:25:14 2007] [notice] child pid 23910 exit signal
Segmentation fault (11)
[Sun Feb 11 17:33:02 2007] [notice] child pid 1759 exit signal
Segmentation fault (11)
[Sun Feb 11 17:40:55 2007] [notice] child pid 7190 exit signal
Segmentation fault (11)

I made a stack backtrace in the related wordpress ticket
(http://trac.wordpress.org/ticket/3678) and it seems like this is not
a wordpress 2.1 issue:
http://trac.wordpress.org/attachment/ticket/3678/backtrace.24347

I am running Debian Sarge on a VM (Kernel
2.6.9-022stab078.14-enterprise) with libc6 2.3.2.ds1-22sarge4.
Apache 2.0.54, PHP 4.3.10, MySQL 4.1.11.

Message #14 received at 410549@bugs.debian.org (full text, mbox, reply):

From: Steve Langasek <vorlon@debian.org>

To: Frederic Wenzel <freeed@gmail.com>, 410549@bugs.debian.org

Subject: Re: [php-maint] Bug#410549: Apache children segfault after Wordpress 2.1 upgrade

Date: Mon, 12 Feb 2007 00:26:59 -0800

On Sun, Feb 11, 2007 at 09:43:25AM -0800, Frederic Wenzel wrote:
> Package: libapache2-mod-php4
> Version: 4.3.10

> I am running debian sarge on my webserver, and after upgrading several
> blogs to wordpress 2.1, frequent apache segfaults occur:

> [Sun Feb 11 17:19:47 2007] [notice] child pid 24229 exit signal
> Segmentation fault (11)
> [Sun Feb 11 17:19:49 2007] [notice] child pid 26052 exit signal
> Segmentation fault (11)
> [Sun Feb 11 17:25:14 2007] [notice] child pid 23910 exit signal
> Segmentation fault (11)
> [Sun Feb 11 17:33:02 2007] [notice] child pid 1759 exit signal
> Segmentation fault (11)
> [Sun Feb 11 17:40:55 2007] [notice] child pid 7190 exit signal
> Segmentation fault (11)

> I made a stack backtrace in the related wordpress ticket
> (http://trac.wordpress.org/ticket/3678) and it seems like this is not
> a wordpress 2.1 issue:
> http://trac.wordpress.org/attachment/ticket/3678/backtrace.24347

> I am running Debian Sarge on a VM (Kernel
> 2.6.9-022stab078.14-enterprise) with libc6 2.3.2.ds1-22sarge4.
> Apache 2.0.54, PHP 4.3.10, MySQL 4.1.11.

The linked backtrace points to a PHP memory management problem.  Do you also
have any Zend extensions installed?  Please forward your php.ini.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon@debian.org                                   http://www.debian.org/

Message #19 received at 410549@bugs.debian.org (full text, mbox, reply):

From: "Frederic Wenzel" <freeed@gmail.com>

To: "Steve Langasek" <vorlon@debian.org>

Cc: 410549@bugs.debian.org

Subject: Re: [php-maint] Bug#410549: Apache children segfault after Wordpress 2.1 upgrade

Date: Wed, 14 Feb 2007 11:16:22 -0800

[Message part 1 (text/plain, inline)]

On 2/12/07, Steve Langasek <vorlon@debian.org> wrote:
> On Sun, Feb 11, 2007 at 09:43:25AM -0800, Frederic Wenzel wrote:
> > Package: libapache2-mod-php4
> > Version: 4.3.10
>
> > I am running debian sarge on my webserver, and after upgrading several
> > blogs to wordpress 2.1, frequent apache segfaults occur:
>
> > [Sun Feb 11 17:19:47 2007] [notice] child pid 24229 exit signal
> > Segmentation fault (11)
> > [Sun Feb 11 17:19:49 2007] [notice] child pid 26052 exit signal
> > Segmentation fault (11)
> > [Sun Feb 11 17:25:14 2007] [notice] child pid 23910 exit signal
> > Segmentation fault (11)
> > [Sun Feb 11 17:33:02 2007] [notice] child pid 1759 exit signal
> > Segmentation fault (11)
> > [Sun Feb 11 17:40:55 2007] [notice] child pid 7190 exit signal
> > Segmentation fault (11)
>
> > I made a stack backtrace in the related wordpress ticket
> > (http://trac.wordpress.org/ticket/3678) and it seems like this is not
> > a wordpress 2.1 issue:
> > http://trac.wordpress.org/attachment/ticket/3678/backtrace.24347
>
> > I am running Debian Sarge on a VM (Kernel
> > 2.6.9-022stab078.14-enterprise) with libc6 2.3.2.ds1-22sarge4.
> > Apache 2.0.54, PHP 4.3.10, MySQL 4.1.11.
>
> The linked backtrace points to a PHP memory management problem.  Do you also
> have any Zend extensions installed?  Please forward your php.ini.

No, I don't have any additional extensions installed. My php.ini
should be quite the defaults, IIRC I just raised the memory limit.
It's attached (hope that works).

[php.ini (text/plain, attachment)]

Message #24 received at 410549@bugs.debian.org (full text, mbox, reply):

From: Steve Langasek <vorlon@debian.org>

To: Frederic Wenzel <freeed@gmail.com>

Cc: 410549@bugs.debian.org

Subject: Re: [php-maint] Bug#410549: Apache children segfault after Wordpress 2.1 upgrade

Date: Fri, 16 Feb 2007 19:02:07 -0800

On Wed, Feb 14, 2007 at 11:16:22AM -0800, Frederic Wenzel wrote:
> >> I made a stack backtrace in the related wordpress ticket
> >> (http://trac.wordpress.org/ticket/3678) and it seems like this is not
> >> a wordpress 2.1 issue:
> >> http://trac.wordpress.org/attachment/ticket/3678/backtrace.24347

> >> I am running Debian Sarge on a VM (Kernel
> >> 2.6.9-022stab078.14-enterprise) with libc6 2.3.2.ds1-22sarge4.
> >> Apache 2.0.54, PHP 4.3.10, MySQL 4.1.11.

> >The linked backtrace points to a PHP memory management problem.  Do you 
> >also
> >have any Zend extensions installed?  Please forward your php.ini.

> No, I don't have any additional extensions installed. My php.ini
> should be quite the defaults, IIRC I just raised the memory limit.
> It's attached (hope that works).

Hmm.  Noteworthy is the large number of PHP extensions you have loaded, even
if you don't have any Zend extensions installed.  Could you try commenting
out any of these extensions not used by wordpress, and test whether that
affects your crash?

If it does, please uncomment the extensions one by one until the problem
shows up again, then send that list of extensions.  If it doesn't, please
send the minimum list of extensions that need to be enabled for your
wordpress instance to run.

In either case, it would be a good idea to try running apache under valgrind
to see if that permits pinning down the problem.

Alternatively, you may want to try the php version from etch to see if this
problem has resolved itself.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon@debian.org                                   http://www.debian.org/

Message #29 received at 410549@bugs.debian.org (full text, mbox, reply):

From: Paul TBBle Hampson <Paul.Hampson@Pobox.com>

To: 410549@bugs.debian.org, 410549-submitter@bugs.debian.org

Subject: Wordpress-2.1-triggered PHP4 segfault

Date: Sat, 17 Feb 2007 18:28:36 +1100

[Message part 1 (text/plain, inline)]

Just hit this bug myself, and glad to see a stacktrace's already
done to save me doing it...

Anyway, I'm the only extensions listed in my php.ini file are:

	dino:/etc/php4/apache2# grep extension php.ini |grep -v '^;'
	extension=idn.so
	extension=mysql.so
	extension=pgsql.so

I've attached my php.ini file as well, and will see if I can find
the time to run valgrind across apache2... It's a production web
server though, so I'm not exactly keen to recompile.

I can prolly get access to a Sarge box next week to test it on, if
nothing else.

-- 
Paul "TBBle" Hampson, Paul.Hampson@Pobox.com

Shorter .sig for a more eco-friendly paperless office.

[Message part 2 (application/pgp-signature, inline)]

Message #37 received at 410549@bugs.debian.org (full text, mbox, reply):

From: Steve Langasek <vorlon@debian.org>

To: Paul TBBle Hampson <Paul.Hampson@Pobox.com>, 410549@bugs.debian.org

Subject: Re: Bug#410549: Wordpress-2.1-triggered PHP4 segfault

Date: Sat, 17 Feb 2007 02:00:42 -0800

On Sat, Feb 17, 2007 at 06:28:36PM +1100, Paul TBBle Hampson wrote:
> I've attached my php.ini file as well

Nuh-uh :-)

(Not sure how much we need it, but just FYI :)

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon@debian.org                                   http://www.debian.org/

Message #42 received at 410549@bugs.debian.org (full text, mbox, reply):

From: Lucas Nussbaum <lucas@lucas-nussbaum.net>

To: 370375@bugs.debian.org, 341346@bugs.debian.org, 392839@bugs.debian.org, 298052@bugs.debian.org, 424937@bugs.debian.org, 410549@bugs.debian.org, 386041@bugs.debian.org, 271856@bugs.debian.org, 456728@bugs.debian.org, 264806@bugs.debian.org, 323585@bugs.debian.org, control@bugs.debian.org, libapache2-mod-php5@packages.debian.org

Subject: Reassigning bugs from libapache2-mod-php4 to libapache2-mod-php5

Date: Mon, 05 May 2008 10:19:37 +0200

reassign 370375 libapache2-mod-php5
reassign 341346 libapache2-mod-php5
reassign 392839 libapache2-mod-php5
reassign 298052 libapache2-mod-php5
reassign 424937 libapache2-mod-php5
reassign 410549 libapache2-mod-php5
reassign 386041 libapache2-mod-php5
reassign 271856 libapache2-mod-php5
reassign 456728 libapache2-mod-php5
reassign 264806 libapache2-mod-php5
reassign 323585 libapache2-mod-php5
thanks

The libapache2-mod-php4 package has been removed from Debian testing, unstable and
experimental. I am reassigning its bugs to the libapache2-mod-php5 package. Please
have a look at them, and close them if they don't apply to
libapache2-mod-php5 anymore.

Don't hesitate to reply to this mail if you have any question.
-- 
Lucas

Message #51 received at 410549-quiet@bugs.debian.org (full text, mbox, reply):

From: sean finney <seanius@debian.org>

To: control@bugs.debian.org

Cc: 370375-quiet@bugs.debian.org, 341346-quiet@bugs.debian.org, 392839-quiet@bugs.debian.org, 298052-quiet@bugs.debian.org, 424937-quiet@bugs.debian.org, 410549-quiet@bugs.debian.org, 386041-quiet@bugs.debian.org, 271856-quiet@bugs.debian.org, 456728-quiet@bugs.debian.org, 264806-quiet@bugs.debian.org, 323585-quiet@bugs.debian.org, Lucas Nussbaum <lucas@lucas-nussbaum.net>, pkg-php-maint@lists.alioth.debian.org

Subject: please don't

Date: Wed, 23 Jul 2008 22:09:52 +0200

[Message part 1 (text/plain, inline)]

reassign 370375 libapache2-mod-php4
reassign 341346 libapache2-mod-php4
reassign 392839 libapache2-mod-php4
reassign 298052 libapache2-mod-php4
reassign 424937 libapache2-mod-php4
reassign 410549 libapache2-mod-php4
reassign 386041 libapache2-mod-php4
reassign 271856 libapache2-mod-php4
reassign 456728 libapache2-mod-php4
reassign 264806 libapache2-mod-php4
reassign 323585 libapache2-mod-php4
thanks

this is not the first time someone has done a mass-reassignment on old php4 
bugs.  blindly reassigning bugs from php4->php5 is not the proper protocol 
here.  just because php4 will not be in lenny does not mean that it is not 
still in debian.  furthermore, if the bug affected php5 it should have 
already been cloned to php5.


thanks,
	sean

[signature.asc (application/pgp-signature, inline)]

Message #56 received at 410549-done@bugs.debian.org (full text, mbox, reply):

From: Marco Rodrigues <gothicx@gmail.com>

To: 410549-done@bugs.debian.org

Subject: Package libapache2-mod-php4 has been removed from Debian

Date: Wed, 24 Mar 2010 20:50:50 +0000 (WET)

Version: 6:4.4.6-2+rm

You filed the bug http://bugs.debian.org/410549 in Debian BTS
against the package libapache2-mod-php4. I'm closing it at *unstable*, but it will
remain open for older distributions.

For more information about this package's removal, read
http://bugs.debian.org/428266. That bug might give the reasons why
this package was removed and suggestions of possible replacements.

Don't hesitate to reply to this mail if you have any question.

Thank you for your contribution to Debian.

--
Marco Rodrigues

Send a report that this bug log contains spam.