Gutsy ports.conf file breaks Feisty config
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| apache2 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
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/
Work-around: Remove the excess "Listen" directive from either file.
| Mathias Gug (mathiaz) wrote | #1 |
| Changed in apache2: | |
| status: | New → Incomplete |
| Victor Engmark (victor-engmark) wrote | #2 |
| Mathias Gug (mathiaz) wrote | #3 |
| Changed in apache2: | |
| status: | Incomplete → Invalid |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Feisty already has the ports.conf file installed with apache2. Did you remove this file before upgrading from feisty ?