Your message dated Wed, 24 Mar 2010 20:50:50 +0000 (WET)
with message-id <[email protected]>
and subject line Package libapache2-mod-php4 has been removed from Debian
has caused the Debian Bug report #410549,
regarding Apache children segfault after Wordpress 2.1 upgrade
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
410549: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=410549
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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.
--- End Message ---
--- Begin Message ---
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
--- End Message ---
