Created attachment 307383 [details]
It dies at the end of the configure:
checking which MPM to use by default... itk
configure: error: MPM itk is not supported on this platform.
Created attachment 307385 [details]
There was also (early this morning) a new release of the mpm-itk patch for 2.4.1:
And the mailing list message:
checking which MPM to use by default... peruser
configure: error: MPM peruser is not supported on this platform.
!!! Please attach the following file when seeking support:
* ERROR: www-servers/apache-2.4.1-r2 failed (configure phase):
* econf failed
Sorry, was in a hurry. Here's the config log and emerge -vp output.
$ sudo FEATURES="noclean" ACCEPT_KEYWORDS="~amd64" emerge -vp apache
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild U ] www-servers/apache-2.4.1-r1 [2.2.21-r1] USE="doc* ssl -debug -ldap (-selinux) -static -suexec -threads" APACHE2_MODULES="alias* auth_basic* auth_digest* authn_anon* authn_default* authn_file* authz_dbm* authz_default* authz_host* authz_user* autoindex* cgid* deflate* dir* env* expires* filter* headers* include* log_config* logio* mime* rewrite setenvif* -actions -asis -authn_alias -authn_dbd -authn_dbm -authz_groupfile -authz_owner -cache -cern_meta -cgi -charset_lite -dav -dav_fs -dav_lock -dbd -disk_cache -dumpio -ext_filter -file_cache -ident -imagemap -info -log_forensic -mem_cache -mime_magic -negotiation -proxy* -proxy_ajp -proxy_balancer -proxy_connect* -proxy_ftp -proxy_http* -proxy_scgi -reqtimeout -speling -status -substitute -unique_id -userdir -usertrack -version -vhost_alias" APACHE2_MPMS="itk* -event -peruser -prefork -worker" 0 kB
Created attachment 307419 [details]
same 'problem' here. Found some patches around to port this MPM to 2.4 but haven't had time to test it
ITK users are probably better off waiting a while before upgrading to the 2.4.x (or even 2.5.x) series. The updated patchset should work here; however, the author recently announced that upstream changes will finally obviate the need to patch Apache at all:
Apache maintainence has slowed recently (no offense to those who stepped up to fix bugs!), and personally I'd feel more comfortable compiling a separate package that I or someone else can maintain against a vanilla Apache (which necessarily gets more attention).
I just ran into this issue as well. Is there any progress on this issue, possibly even a workaround using an overlay to get this running?
Attaching a new ebuild www-apache/mpm_itk following upstreams direction in providing a separate module instead of patching apache directly now that apache 2.4 supports this kind of stuff. Currently apache 2.4.4 still needs 3 minor patches (shipped with mpm_itk tarball) which according to the mpm_itk readme are already applied in svn trunk. I'm also attaching the apache patches for completeness and since one of them needs a little modification.
Created attachment 340382 [details]
Created attachment 340384 [details]
Created attachment 340386 [details]
Created attachment 340388 [details]
Created attachment 340390 [details]
Created attachment 340392 [details]
I have the same problem too, with apache 2.4.4 in stable portage.
I tried to use ebuild and patches given, it compiles but doesn't start.
what I did :
=> grep apache /etc/portage/package.keywords
ls -R /usr/local/portage/www-apache/mpm_itk/
(ebuild digest is ok)
added epatch_user to /usr/portage/www-servers/apache/apache-2.4.4-r1.ebuild
added -D MPM_ITK to /etc/conf.d/apache2
Apache seems to be patched :
* Applying user patches from /etc/portage/patches//www-servers/apache-2.4.4-r1 ...
* Done with patching
# /etc/init.d/apache2 restart
* apache2 has detected an error in your setup:
apache2: Syntax error on line 156 of /etc/apache2/httpd.conf: Syntax error on line 2 of /etc/apache2/modules.d/00_mpm_itk.conf: Cannot load modules/mpm_itk.so into server: /usr/lib64/apache2/modules/mpm_itk.so: undefined symbol: ap_hook_pre_htaccess
* ERROR: apache2 failed to stop
(sorry for my bad english)
In fact, patches seems not to be applied, I don't know why.
I tried to patch manually after ebuild $(equery which apache) configure
(I had to modify a little the patches), then merge. Rebuild modules like php (subversion conf gives a warning) and it seems to work now.
(In reply to comment #16)
> But :
> # /etc/init.d/apache2 restart
> * apache2 has detected an error in your setup:
> apache2: Syntax error on line 156 of /etc/apache2/httpd.conf: Syntax error
> on line 2 of /etc/apache2/modules.d/00_mpm_itk.conf: Cannot load
> modules/mpm_itk.so into server: /usr/lib64/apache2/modules/mpm_itk.so:
> undefined symbol: ap_hook_pre_htaccess
> * ERROR: apache2 failed to stop
> (sorry for my bad english)
Apache failed to *stop*. If you killed it manually (without letting it parse the config and try to load that module), it probably would have started up afterwards.
Unrelated: 2.4.4_p4 was just released and it looks like at least the seccomp fix was upstreamed.
Created attachment 341226 [details]
Created attachment 341228 [details]
To ease testing a tarball containing a modified apache ebuild (based on apache-2.4.4-r1) with the needed patches and the recent mpm_itk ebuild (mpm_itk-2.4.4_p4) attached above.
I can confirm that this patch works and I have been using it since the 7th of March 2013. I have not encountered any issues so far.
Created attachment 354112 [details]
Created attachment 354114 [details, diff]
Created attachment 354116 [details, diff]
Upstream has accepted/backported the open_htaccess_hook patch to branch 2.4.x:
What are we waiting for on this bug? :)
The last word from upstream was,
At this point, I think we should wait for a separate mpm-itk, hopefully in the next apache release.
That puts us closer to upstream, and reduces the complexity in the ebuild.
Since apache 2.4.7 has been released now it carries the last missing piece (open_htaccess_hook) to build mpm_itk as an external module without patching apache. mpm_itk-2.4.6_p1 still builds against apache 2.4.7 and also seems to work just fine.
And we have an official mpm-itk release for apache-2.4.7:
Due to the way the apache ebuild is written, it's difficult to modify/test in an overlay. I'd like to test this ASAP, but I'll probably wait for apache-2.4.7 to hit ~arch and then begin testing a standalone mpm-itk-2.4.7 based on Timo's ebuild.
Once standalone mpm-itk hits the tree, apache can be revbumped to clean up its build system.
So, if APACHE2_MPMS="itk" doesn't work anymore, why mpm_itk isn't in portage tree ?
(In reply to Christophe PEREZ from comment #30)
> So, if APACHE2_MPMS="itk" doesn't work anymore, why mpm_itk isn't in portage
> tree ?
I said I'd test with apache-2.4.7 ASAP, but I've had another project over the winter break. Realistically it will be either spring break (March) or summer before I can give this a good testing. We have several hundred sites I'd have to upgrade first.
If someone else wants to package mpm-itk and just stick it in ~arch, that's fine with me though.
Confirmed this bug on Apache 2.4.7 too
Now, there must be a way to get this working somehow. Some easy way. Since PERUSER seems dead, ITK seems the only option to run Apache with a reasonable performance gain in a multiuser vhost environment. Although the option to use ITK is documented even on gentoo setup tutorials, emerge fails.
This bug should be confirmed and considered important.
Created attachment 370724 [details]
thank you Timo for this ebuild which seems to match the 2.4.7 Apache.
Unfortunatly, I have no idea what to do with this file to make my Apache compile, I never used ebuilds. Any short hints?
It's really nuts. I run a couple gentoo boxes since 1999 and Apache / PHP emerge has always been the most - lets say - "challanging" part. Thank you :)
Created attachment 373014 [details]
I've removed itk mpm from >=apache-2.4.9-r3
So if anyone wants to add the standalone package to the tree, go ahead.
School's out, I am promising to do this within the week.
Created attachment 377636 [details]
Here's what I've got. I'll probably commit this in a day or two unless someone makes noise.
Created attachment 377638 [details]
Default conf file
FWIW, your latest ebuild and config file work great for me. However, I stumbled across the fact that mpm-itk needs a non-threaded apache and says so while failing to configure. Could that be incorporated into the ebuild to keep people from running into this and instead having an appropriate USE flag restriction?
Good idea. The 2.4.x series supports building more than one MPM, so depending on apache[-threads] won't work eventually. But for now, it should (see bug #511658). If that ever changes I can add an elog about it or something.
*mpm_itk-2.4.7_p2 (28 May 2014)
28 May 2014; Michael Orlitzky <firstname.lastname@example.org> +files/00_mpm_itk.conf,
New package: www-apache/mpm_itk, for itk support in apache-2.4. Fixes bug