Hi,
as a workaround we downgraded to version 2.2.3-4+etch3 with
cd /var/cache/apt/archives
dpkg -i apache2_2.2.3-4+etch3_all.deb apache2.2-common_2.2.3-4+etch3_i386.deb
apache2-mpm-worker_2.2.3-4+etch3_i386.deb
Maybe that is useful to someone.
Be sure you are not vulnerable to any of these
On Thursday 28 February 2008, Jason J. Rodrigues wrote:
Yes, that seems to fix the problem. What was the problem, out of
curiosity? Was this fix published elsewhere, I checked a few
databases and coulden't find anything like it.
It was a bug I introduced when backporting the patch for
On Thursday 28 February 2008, Jason Rodrigues wrote:
After upgading to the latest build of apache2 (From a Build in Sept
2007), visiting a BalancerMember's status page to
enable/disable/see details results in a segfault in apache.
Sigh.
Can you please try if the packages from
On Thu, Feb 28, 2008 at 09:47:14PM +0100, Stefan Fritsch wrote:
On Thursday 28 February 2008, Jason Rodrigues wrote:
After upgading to the latest build of apache2 (From a Build in Sept
2007), visiting a BalancerMember's status page to
enable/disable/see details results in a segfault in
Package: apache2.2-common
Version: 2.2.3-4+etch4
Severity: important
After upgading to the latest build of apache2 (From a Build in Sept
2007), visiting a BalancerMember's status page to enable/disable/see
details results in a segfault in apache.
I noticed this, because one of our servers had a
5 matches
Mail list logo