Hi, >> + APACHE2_NEED_ACTION=1 >> + a2enmod -m -q cgi >> + return 1 >> dpkg: error processing package icinga-cgi (--configure):
this is the actual problem. The maintscript-helper could not enable the CGI module and thus fails out. So far that's correct behavior. Now, the underlying question ist _why_ it fails. I cannot reproduce this in a default installation of Apache 2.4 and a clean chroot either. However, note that a2enmod selects cgid over cgi when a threaded MPM was found. Thus, "a2enmod cgi" will actually enable "cgid" when the event/worker MPM is used. Either way this is handled correctly I think: (work-amd64)root@build:/build/apache# a2enmod cgi ; echo $? Your MPM seems to be threaded. Selecting cgid instead of cgi. Enabling module cgid. To activate the new configuration, you need to run: service apache2 restart 0 (work-amd64)root@build:/build/apache# (work-amd64)root@build:/build/apache# a2query -m cgi No module matches cgi (work-amd64)root@build:/build/apache# a2query -m cgid cgid (enabled by site administrator) (work-amd64)root@build:/build/apache# a2dismod cgid Module cgid disabled. To activate the new configuration, you need to run: service apache2 restart (work-amd64)root@build:/build/apache# a2enmod -m -q cgi ; echo $? Your MPM seems to be threaded. Selecting cgid instead of cgi. Enabling module cgid. 0 What's special in your environment Andreas making this fail? -- mit freundlichen Grüßen, Arno Töll GnuPG Key-ID: 0x9D80F36D
signature.asc
Description: OpenPGP digital signature
