Control: tags -1 unreproducible pending
Control: severity -1 normal
On 03/11/2018 03:51 PM, Axel Beckert wrote:
> at the Debian booth at Chemnitzer Linux-Tage a user of icinga-cgi
> (X-Debbugs-Cc'ed) showed up who had issues with replacing Nagios with
> Icinga 1 on Jessie, because icinga-cgi in Jessie still ships and
> installs an Apache 2.2 configuration incompatible with Apache 2.4 in
> Debian Jessie. He said that installing icinga-cgi breaks the existing
> Apache configuration because of that and Apache refuses to start up
> anymore until you fix the config syntax.
> This makes icinga-cgi breaking an unrelated package (apache2 and
> friends do not depend on icinga-web), hence RC-severity.
> I just checked icinga-cgi in unstable and testing, and the config
> shipped in there still has Apache 2.2 syntax:
> Order Allow,Deny <----- Apache 2.2
> Allow From All <----- Apache 2.2
> One possible short-term solution, at least for Jessie, would be to not
> only enable mod_cgi in postinst, but also mod_access_compat.
> Alternatively (and not that more complicated) the config file shipped
> needs to be patched for Apache 2.4 syntax.
While the icinga-cgi package in stretch and later still includes the
Order/Allow configuration, this does not actually cause apache startup
to fail since access_compat is enabled by default. I've tested this in
both a stretch & jessie cowbuilder chroot.
I've updated the configuration to no longer require access_compat, that
will be included in the next upload.
Since I cannot reproduce apache startup failure, I've downgraded the