lighttpd tries to start but fails when apache is running

Bug #174289 reported by Adam Lebsack on 2007-12-06
Affects Status Importance Assigned to Milestone
lighttpd (Ubuntu)

Bug Description

If apache, or anything, for that matter, is running on port 80 when lighttpd is installed, it fails to start. If you reboot, the init script is still enabled, but before apache2 in the boot order. (S20 vs S91, respectively). This would cause a change in web server preference by simply installing lighttpd by the next reboot.

I do not think these packages should conflict, as having both binaries installed would be useful (rails development in my case). Perhaps a solution would be to check for the default port for lighttpd, and configure for a new port if 80 is in use... maybe even supply an option to disable lighttpd's boot with an /etc/defaults/lighttpd entry.

Related branches

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package lighttpd - 1.4.19-0ubuntu2

lighttpd (1.4.19-0ubuntu2) hardy; urgency=low

  * debian/rules: (LP: #174289)
    - set DEB_UPDATE_RCD_PARAMS to "defaults 91 09" to not start lighty before
      apache2 but in the same runlevel with the same priority

 -- Stephan Hermann <email address hidden> Mon, 17 Mar 2008 16:50:10 +0100

Changed in lighttpd:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers