Public bug reported:
After installing Gutsy, Apache 2 would no longer start:
$ sudo /etc/init.d/apache2 start
* Starting web server apache2
(98)Address already in use: make_sock: could not bind to address [::]:443
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:443
no listening sockets available, shutting down
Unable to open logs
After an `ls -lct /etc/apache2/`, it looks like ports.conf was changed
or created during the upgrade. I already have a "Listen" directive in
httpd.conf, so the double directive seem to be the reason for the error.
Obviously it'll be too difficult to make sure none of the changes by the
upgrade break the setup, but how about either of these:
- Move the current config files away (after looking through the setup files
recursively for "Include" directives).
- If Apache is running when the upgrade starts, warn the user about the
possible breakage.
- Put a warning in the upgrade log (/var/log/dist-upgrade/main.log?).
Work-around: Remove the excess "Listen" directive from either file.
** Affects: apache2 (Ubuntu)
Importance: Undecided
Status: New
--
Gutsy ports.conf file breaks Feisty config
https://bugs.launchpad.net/bugs/155309
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
