I "emerge -auDNv apache" upgraded my apache 2.2.4 (IIRC) to the new 2.2.6 and did an etc-update afterwards. "/etc/init.d/apache2 restart" results in: * Stopping apache2 ... [ ok ] * Starting apache2 ... [Fri Sep 14 19:01:16 2007] [warn] _default_ VirtualHost overlap on port 443, the first has precedence [ !! ] afterwards no apache2 task is running the cause for this is, that there is an obviously obsolete /etc/apache2/modules.d/41_mod_ssl.default-vhost.conf with some errorneous settings. ( eg. "ErrorLog logs/ssl_error_log" resulting in: /var/logs/apache2/error_log: (2)No such file or directory: apache2: could not open error log file /usr/lib/apache2/logs/ssl_error_log. Unable to open logs ) Reproducible: Didn't try Steps to Reproduce: I don't know which part of my emerge/etc-update procedure causes the config problems but i guess it's just the update form 2.2.4 to 2.2.6 so: 1. "emerge -auDNv apache" ofcourse this probably only happens if /etc/conf.d/apache2 has "APACHE2_OPTS="-D SSL_DEFAULT_VHOST"" enabled
Neither 2.2.4 nor 2.2.6 installs /etc/apache2/modules.d/41_mod_ssl.default-vhost.conf - you can check the tarballs yourself. You have a stale junk left after apache-2.0.x; delete the orphaned file and move on. http://dev.gentoo.org/~hollow/dist/apache/gentoo-apache-2.2.4-r12-20070819.tar.bz2 http://dev.gentoo.org/~hollow/dist/apache/gentoo-apache-2.2.6-20070907.tar.bz2
Hmm, strange. But 2.2.4 worked fine while 2.2.6 didn't - with the same orphaned file in place. And it took me some time to figure out what happened. (In reply to comment #1) > Neither 2.2.4 nor 2.2.6 installs > /etc/apache2/modules.d/41_mod_ssl.default-vhost.conf - you can check the > tarballs yourself. You have a stale junk left after apache-2.0.x; delete the > orphaned file and move on. > > http://dev.gentoo.org/~hollow/dist/apache/gentoo-apache-2.2.4-r12-20070819.tar.bz2 > http://dev.gentoo.org/~hollow/dist/apache/gentoo-apache-2.2.6-20070907.tar.bz2 >