After emerge www-apache/mod_fcgid can not restart (start) apache2. Reproducible: Always Steps to Reproduce: 1. emerge www-apache/mod_fcgid 2. /etc/init.d/apache2 restart Actual Results: * Stopping apache2... Syntax error on line 3 of /usr/lib/apache2/conf/modules.d/20_mod_fcgid.conf: Cannot load /usr/lib/apache2/modules/mod_fcgid.so into server: /usr/lib/apache2/modules/mod_fcgid.so: cannot open shared object file: No such file or di [ ok ] * Apache2 has detected a syntax error in your configuration files: Syntax error on line 3 of /usr/lib/apache2/conf/modules.d/20_mod_fcgid.conf: Cannot load /usr/lib/apache2/modules/mod_fcgid.so into server: /usr/lib/apache2/modules/mod_fcgid.so: cannot open shared object file: No such file or directory Expected Results: Restarting of Apache2. Pleas change in /etc/apache2/conf/modules.d/20_mod_fcgid.conf line LoadModule fcgid_module modules/mod_fcgid.so to LoadModule fcgid_module extramodules/mod_fcgid.so
Commited. Sorry I didn't catch that before!
Uhm, no - this is incompatible with ~x86 Apache versions! Please revert this back. And also the ebuild installs this into wrong location. It should inherit apache-module. See Bug 76457.
One more comment. Bug 79313 contains a perfectly valid, apache-module eclass compliant ebuild. Why this one has not been commited just evades me. There has been a _lot_ of mess with the whole Apache refresh and now a _new_ incompatible ebuild gets into portage. People running ~arch Apache run ~arch Apache modules, because this is the only way to keep the whole thing working. Now we have ~x86 mod_fcgid which installs into bogus directory and is "fixed" to contain bogus conf file. This just makes no sense. I *really beg* - please do not introduce more problems. Don
One more comment. Bug 79313 contains a perfectly valid, apache-module eclass compliant ebuild. Why this one has not been commited just evades me. There has been a _lot_ of mess with the whole Apache refresh and now a _new_ incompatible ebuild gets into portage. People running ~arch Apache run ~arch Apache modules, because this is the only way to keep the whole thing working. Now we have ~x86 mod_fcgid which installs into bogus directory and is "fixed" to contain bogus conf file. This just makes no sense. I *really beg* - please do not introduce more problems. Don´t confuse people even more. This whole thing has done enough damage already. :-/
Since the ~ apache is still being worked on, this ebuild was commited to work with the stable ebuild for apache (our nodes are using this version of apache thus I needed that). Also, since the eclass you mention isn't backwards compatible with the old apache ebuild, I can't use that eclass yet. This ebuild is marked ~ because its the initial commit of it. I don't see the point of using the new layout until it actually gets committed as stable. For now I can modify the ebuild so that you can only install it unless you are using the stable version of apache. I haven't been pleased with this whole mess myself but we just have to be patient and deal. I don't see how I can incorporate both types of installs in one ebuild without making a huge mess. So for now, this ebuild will just work for the current stable release of apache. If you woudl like to use the other ebuild and test it, please do that as we'll be using that once the apache updates have been all stablized.
Thanks for reply. Please, add the Apache version check (like mod_php did) so that this ebuild only installs to stable (old layout or whatever) Apache and close the bug then. Otherwise, I like this one. ;-)
Ok, I'll probably get to that later tonight as I'm working all day today. Thanks for the info!
Ok, I commited the fix so that it only installs if you're using the current stable apache2 ebuild. Let me know how this works.
Seems to work fine so far. Thanks for the ebuild - mod_fastcgi sucks. ;-)
Great, glad it works!
