when emerging the latest stable apache net-www/apache-2.0.52-r1 the ssl dir in /etc/apache2/conf dosnt get created whereas system.crt and server.key dosnt get installed. Creating /etc/apache2/conf/ssl and re-emerg apache does install the files. Unmasking APACHE2_OPTS="-D SSL" in /etc/conf.d/apache2 make a failure in starting apache [!!]. Masking the line again makes apache start. Reproducible: Always Steps to Reproduce: 1. USE="ssl" emerge apache 2. mkdir /etc/apache2/conf/ssl 3. USE="ssl" emerge apache 4. /etc/init.d/apache2 start 5. eneble APACHE2_OPTS="-D SSL" in /etc/conf.d/apache2 6. /etc/init.d/apache2 restart Actual Results: apache2 aint starting [!!] Expected Results: apache should run with ssl enabled /usr/lib/portage/bin/ebuild.sh: line 384: cd: //etc/apache2/conf/ssl: File or catalog dosnt exist
Created attachment 44130 [details, diff] Patch for apache-2.0.52-r1 ebuild /var/lib/dav, /var/log/apache2, and /var/cache/apache2 were also not being created because they were are being created from within pkg_postinst which is called after the package has been installed.
*** Bug 70917 has been marked as a duplicate of this bug. ***
I have the same problem with a clean install. /usr/portage/net-www/apache/apache-2.0.52-r1.ebuild: line 384: cd: //etc/apache2 /conf/ssl: No such file or directory * * Generating self-signed test certificate in /etc/apache2/conf/ssl... * >>> Regenerating /etc/ld.so.cache... * Caching service dependencies ... [ ok ] >>> net-www/apache-2.0.52-r1 merged. >>> Recording net-www/apache in "world" favorites file... nano /etc/conf.d/apache2 APACHE2_OPTS="-D SSL -D PHP5" ~ # /etc/init.d/apache2 start * Apache2 has detected a syntax error in your configuration files: Syntax error on line 44 of /usr/lib/apache2/conf/modules.d/41_mod_ssl.default-vh ost.conf: SSLCertificateFile: file '/usr/lib/apache2/conf/ssl/server.crt' does not exist o r is empty ~ # cat /etc/passwd|grep apache apache:x:81:81:apache:/home/httpd:/bin/false
Patch applied to apache-2.0.52-r2, which will appear in Portage at some point over the weekend. Once it's there, please test, and let me know if this fixes your bug. Best regards, Stu
Last night, I tried apache-2.0.52-r1 but the result was fail.. I am not sure if I tried r2 patch but I think the same. I hope this information helps.
*** Bug 78970 has been marked as a duplicate of this bug. ***
This still an issue ?