Raspbian Buster lighttpd failed to start

Thank you Sir for helping.

I had to do the same after upgrading my Raspberry Pi 3 Model B+ to Buster via: Upgrade Your Raspberry Pi to Raspbian Buster, Without Losing Data | Tom's Hardware

Sadly after reconfigue it killed it and I had to reboot and still not working so then did pihole -r and selected repair

Did something for lighttpd but lighttpd still is not working:

will@raspberrypi:~ $ sudo service lighttpd status
● lighttpd.service - Lighttpd Daemon
   Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2019-06-26 19:11:30 EDT; 3min 38s ago
  Process: 3263 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf (code=exited, status=255/EXCEPTION)

Jun 26 19:11:29 raspberrypi systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION
Jun 26 19:11:29 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Jun 26 19:11:29 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.
Jun 26 19:11:30 raspberrypi systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
Jun 26 19:11:30 raspberrypi systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 5.
Jun 26 19:11:30 raspberrypi systemd[1]: Stopped Lighttpd Daemon.
Jun 26 19:11:30 raspberrypi systemd[1]: lighttpd.service: Start request repeated too quickly.
Jun 26 19:11:30 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Jun 26 19:11:30 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.

- The process' exit code is 'exited' and its exit status is 255.
Jun 26 19:15:15 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- The unit lighttpd.service has entered the 'failed' state with result 'exit-code'.
Jun 26 19:15:15 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.
-- Subject: A start job for unit lighttpd.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit lighttpd.service has finished with a failure.
-- 
-- The job identifier is 1933 and the job result is failed.
Jun 26 19:15:15 raspberrypi systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
Jun 26 19:15:15 raspberrypi systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 5.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Automatic restarting of the unit lighttpd.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Jun 26 19:15:15 raspberrypi systemd[1]: Stopped Lighttpd Daemon.
-- Subject: A stop job for unit lighttpd.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A stop job for unit lighttpd.service has finished.
-- 
-- The job identifier is 1996 and the job result is done.
Jun 26 19:15:15 raspberrypi systemd[1]: lighttpd.service: Start request repeated too quickly.
Jun 26 19:15:15 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- The unit lighttpd.service has entered the 'failed' state with result 'exit-code'.
Jun 26 19:15:15 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.
-- Subject: A start job for unit lighttpd.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit lighttpd.service has finished with a failure.
-- 
-- The job identifier is 1996 and the job result is failed.
Jun 26 19:15:29 raspberrypi sudo[3750]:     will : TTY=pts/0 ; PWD=/home/will ; USER=root ; COMMAND=/bin/journalctl -xe
Jun 26 19:15:29 raspberrypi sudo[3750]: pam_unix(sudo:session): session opened for user root by (uid=0)

Your issue is totally different.

This is a known issue and a fix is already on the way.

https://discourse.pi-hole.net/t/getting-ready-for-buster/21001/19

Nice, thank you.

Then had to do sudo apt-get install gamin and lastly sudo service pihole-FTL restart and admin page back in business and DNS working again.

As well as: Pi-hole Web Interface not displaying correctly

gamin is not a Pi-hole dependency and the use for it, is on a case-by-case scenario.

It wouldn’t apply to everybody.

1 Like

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.