Bug#892628: [Pkg-nagios-devel] Bug#892628: icinga-web: Ships Apache 2.2 config
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: > > ---snip--- > [...] > Order Allow,Deny<- Apache 2.2 > Allow From All <- Apache 2.2 > [...] > ---snap--- > > 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 severity. Kind Regards, Bas
Bug#892628: [Pkg-nagios-devel] Bug#892628: icinga-web: Ships Apache 2.2 config
Control: retitle -1 icinga-cgi: Ships Apache 2.2 config Control: reassign -1 icinga-cgi 1.13.4-2 Control: found -1 1.11.6-1 Hi Bas, Sebastiaan Couwenberg wrote: > Did you mean to file this package for icinga-cgi instead of > icinga-web? Yes. Sorry. My fault. Not sure why I always type icinga-web instead of icinga-cgi, but it happened before when I was looking up package details on the web for the bug report. Context for the icinga-cgi package maintainers: > 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: Sorry again. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#892628: [Pkg-nagios-devel] Bug#892628: icinga-web: Ships Apache 2.2 config
On 03/11/2018 03:51 PM, Axel Beckert wrote: > Package: icinga-web > Severity: grave > Version: 1.13.4-2 > Control: found -1 1.11.6-1 > > Hi, > > 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: Did you mean to file this package for icinga-cgi instead of icinga-web? There is no icinga-web version 1.13.4-2. The progress to update icinga to 1.14.2 is ongoing, but currently block to me not having found the time and motivation to test if all the jQuery stuff still works. If this issue is present in icinga-cgi I'll fix it there. I'm not sure if I want to bother with the version in jessie. Kind Regards, Bas
Bug#892628: icinga-web: Ships Apache 2.2 config
Package: icinga-web Severity: grave Version: 1.13.4-2 Control: found -1 1.11.6-1 Hi, 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: ---snip--- # apache configuration for icinga ScriptAlias /cgi-bin/icinga /usr/lib/cgi-bin/icinga # Where the stylesheets (config files) reside Alias /icinga/stylesheets /etc/icinga/stylesheets # Where the HTML pages live Alias /icinga /usr/share/icinga/htdocs Options FollowSymLinks DirectoryIndex index.html AllowOverride AuthConfig Order Allow,Deny<- Apache 2.2 Allow From All <- Apache 2.2 AuthName "Icinga Access" AuthType Basic AuthUserFile /etc/icinga/htpasswd.users Require valid-user Options FollowSymLinks MultiViews ---snap--- 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. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (990, 'unstable'), (980, 'unstable-debug'), (600, 'testing'), (111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental'), (105, 'experimental-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
