lighttpd and apache2 conflict and break edgy upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lighttpd (Debian) |
Fix Released
|
Unknown
|
|||
lighttpd (Ubuntu) |
Fix Released
|
Undecided
|
Soren Hansen | ||
update-manager (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
This bug results from having both lighttpd and apache2 installed prior to running the upgrade to Edgy. When lighttpd is updated, the installation script restarts the server. However, if you choose to replace the configuration file (the only option other than cancel), lighttpd will attempt to restart listening on port 80, which fails because apache2 has already claimed that port.
This "[fail]" causes the installer to bring up an error dialog stating that the upgrade has failed. If left open, the installation continues successfully in the background, but once you click "Close," it stops and warns you that you may have an unusable system. Everything appears fine, though.
This is a strange problem, but lighttpd and apache2 *can* coexist if configured correctly. Presumably, the fix to simply not fail the install, since there is no real failure.
Specifically, I used "sudo update-manager -c -d" to perform the update, and the contents of /var/log/
Related branches
Changed in lighttpd: | |
status: | Unknown → Unconfirmed |
Changed in lighttpd: | |
status: | New → Confirmed |
Changed in lighttpd: | |
status: | Confirmed → Won't Fix |
Changed in lighttpd (Debian): | |
status: | Won't Fix → New |
Changed in lighttpd (Debian): | |
status: | New → Fix Released |
Attaching logs.