hi,
this is the last bit of configuring i'd like to do on my pihole (for now) and even though the process has confounded me pretty severely at times, i've finally managed to work myself past all the problems i had getting a certificate up and whatnot and at long last i was justrr one restart away from being done and this happens:
pi@raspberrypi:~ $ sudo service lighttpd restart
Job for lighttpd.service failed because the control process exited with error code.
See "systemctl status lighttpd.service" and "journalctl -xe" for details.
bringing up the indicated commands gives me:
pi@raspberrypi:~ $ systemctl status lighttpd.service _
* lighttpd.service - Lighttpd Daemon
_ Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled)
_ Active: failed (Result: exit-code) since Sun 2019-02-17 18:25:32 PST; 13min ago_
_ Process: 4582 ExecStart=/usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf (code=exited, status=0/SUCCESS)_
_ Process: 5018 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf (code=exited, status=255)_
_ Main PID: 4582 (code=exited, status=0/SUCCESS)_
Feb 17 18:25:32 raspberrypi systemd[1]: lighttpd.service: Control process exited, code=exited status=255
Feb 17 18:25:32 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.
Feb 17 18:25:32 raspberrypi systemd[1]: lighttpd.service: Unit entered failed state.
Feb 17 18:25:32 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Feb 17 18:25:32 raspberrypi systemd[1]: lighttpd.service: Service hold-off time over, scheduling restart.
Feb 17 18:25:32 raspberrypi systemd[1]: Stopped Lighttpd Daemon.
Feb 17 18:25:32 raspberrypi systemd[1]: lighttpd.service: Start request repeated too quickly.
Feb 17 18:25:32 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.
Feb 17 18:25:32 raspberrypi systemd[1]: lighttpd.service: Unit entered failed state.
Feb 17 18:25:32 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'.
and:
pi@raspberrypi:~ $ journalctl -xe
-- Unit lighttpd.service has failed.
_-- _
-- The result is failed.
Feb 17 18:41:33 raspberrypi systemd[1]: lighttpd.service: Unit entered failed state.
Feb 17 18:41:33 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Feb 17 18:41:33 raspberrypi systemd[1]: lighttpd.service: Service hold-off time over, scheduling restart.
Feb 17 18:41:33 raspberrypi systemd[1]: Stopped Lighttpd Daemon.
-- Subject: Unit lighttpd.service has finished shutting down
-- Defined-By: systemd
_-- Support: https://www.debian.org/support_
_-- _
-- Unit lighttpd.service has finished shutting down.
Feb 17 18:41:33 raspberrypi systemd[1]: lighttpd.service: Start request repeated too quickly.
Feb 17 18:41:33 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.
-- Subject: Unit lighttpd.service has failed
-- Defined-By: systemd
_-- Support: https://www.debian.org/support_
_-- _
-- Unit lighttpd.service has failed.
_-- _
-- The result is failed.
Feb 17 18:41:33 raspberrypi systemd[1]: lighttpd.service: Unit entered failed state.
Feb 17 18:41:33 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'.
frankly, i'm utterly clueless as to what has gone wrong here. the only way to restore lighttpd functionality is to delete the external.conf file, which is what i plan to do for now. but i would still very much like to make this work. is there anything anyone can suggest that could fix this issue for me?
(and yes, my knowledge of *nix is limited -- or just enough to be a danger to myself and my pi.)
thanks in advance!
Mod Edit: Moved from Enabling HTTPS for your Pi-hole Web Interface