lighttpd does not start automatically

Bug #1633115 reported by Thomas Schweikle on 2016-10-13
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lighttpd (Ubuntu)

Bug Description

lighttpd does not start automatically even if it is configured to start automatically. Starting it manually after the system is up works.

Looks like lighttpd fails because dnsmasq does start late and trying to resolve hosts name fails. In tune lighttpd stops and is not restarted by systemd.

dnsmasq may start late if some interfaces are created late it is configured to bind to. I am seeing this problem with installed:

- vmware workstation
- vmware player
- virtual box
- kvm (if networking is build up via script while starting kvm)

dnsmasq may delay starting in such cases until all interfaces are up and configured. lighttpd does not wait until this happened. It bails out with resolver errors.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lighttpd 1.4.35-4ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
Uname: Linux 4.4.0-43-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Thu Oct 13 17:06:07 2016
InstallationDate: Installed on 2014-01-31 (986 days ago)
InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016)
 PATH=(custom, no user)
SourcePackage: lighttpd
UpgradeStatus: Upgraded to xenial on 2016-09-06 (37 days ago)
mtime.conffile..etc.lighttpd.lighttpd.conf: 2016-09-21T09:44:08.150749

Thomas Schweikle (tps) wrote :
gstrauss (gstrauss) wrote :

Duplicate #1811073

gstrauss (gstrauss) wrote :

Duplicate Bug #1811073

gstrauss (gstrauss) wrote :

Fixed in lighttpd 1.4.51 released Oct 2018

doc/systemd/lighttpd.service now uses
instead of, as recommended in

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

Other bug subscribers