This bug did not go away by updating from Stretch to Buster.
A quick fix seems to be changing 'reload' to 'restart' in the
logrotate conf file /etc/logrotate.d/apache2.
--
Harri
Package: libapache2-mod-fcgid
Version: 1:2.3.9-1+b1
Followup-For: Bug #779077
Dear Maintainer,
In early January I upgraded from Jessie to Stretch.
The server is running Sympa, which uses fcgid in Stretch for the web interface,
and for Soap services.
Shortly after the upgrade I encountered
This problem has started for me across the board since upgrading to Jessie.
I believe it is this upstream bug:
https://bz.apache.org/bugzilla/show_bug.cgi?id=48769
The patch mentioned in Comment #7 might solve the problem? I will work on
reproducing the problem and then see if that patch
reassign 779077 libapache2-mod-fcgid
found 779077 1:2.3.9-1
affects 779077 apache2
thanks
On Tuesday 03 November 2015 13:02:00, Chris Boot wrote:
> We've just hit the same crash again, but on a different server for a
> different client of ours. This time it was an upgrade from Wheezy
> to Jessie,
Hi,
We've just hit the same crash again, but on a different server for a
different client of ours. This time it was an upgrade from Wheezy to
Jessie, but the MPM is still worker.
This time in particular we hit the crash during the phpmyadmin security
upgrade recently. If I read the phpmyadmin
Package: apache2-bin
Version: 2.4.10-9
Severity: important
Dear maintainers,
When reloading apache2 gracefully (/etc/init.d/apache2 reload) twice in
quick succession, the parent process can crash. Below are the
backtraces from 3 core dumps several days in a row that happened during
logrotate.
6 matches
Mail list logo
