/etc/init.d/apache2 start: .:10:46:. <+infowolfe> * Starting apache2... .:10:46:. <+infowolfe> (2)No such file or directory: apache2: could not open error log file /usr/lib/apache2/logs/error_log. .:10:46:. <+infowolfe> Unable to open logs Reproducible: Always Steps to Reproduce: 1. USE="apache2" emerge apache 2. /etc/init.d/apache2 start Actual Results: see Details Expected Results: apache should have started without complaint
this seems to have been made by having /usr/lib/apache2/logs as a file instead of a directory. (bodge) fix: su to root cd /usr/lib/apache2/ rm logs mkdir logs nano -w logs error_log. in the file just do a space then delete the space so its modified and save the file. That will give you the full path /usr/lib/apache2/logs/error_log. and allows /etc/init.d/apache2 start to work
sorry, the line in that should have been nano -w logs/error_log.
After install /usr/lib/apache2/logs is a symlink to /var/log/apache2, which is correct imho. But the ebuild does a keepdir on /var/log/apache2, but doesn't do a dodir, _that_ should be fixed.
bug report #48063 is a duplicate of this one.
Please reference bug report 48063. It notes that several additional directories are not created: /var/cache/apache2 and /etc/apache2/conf/ssl, as well as the ssl test certificates. The same reason that /var/log/apache2 is not created applies to these directories and files: the change from using /bin/install (2.0.50) to keepdir ( >= 2.0.51) in pkg_postinst() function in the ebuild.
fixed in apache-2.0.52-r2.
Can we get that fixed in -r1 too or move -r2 to stable? -r1 is latest stable and on a fresh system a fresh emerge'd apache won't start because of the missing dir.
*** Bug 75129 has been marked as a duplicate of this bug. ***
