[SOLVED]/[INFORMATIONAL] - Lighttpd throwing error after piAware install


#1

After performing a fresh installation:

pi@piaware:/var/www/html$ sudo service lighttpd status
? lighttpd.service - Lighttpd Daemon
Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled)
Active: failed (Result: exit-code) since Thu 2018-04-19 16:33:16 CDT; 20s ago
Process: 11545 ExecStartPre=/usr/sbin/lighttpd -t -f /etc/lighttpd/lighttpd.co nf (code=exited, status=255)

Apr 19 16:33:16 piaware lighttpd[11545]: Duplicate config variable in condit…e
Apr 19 16:33:16 piaware lighttpd[11545]: 2018-04-19 16:33:16: (configfile.c…)
Apr 19 16:33:16 piaware lighttpd[11545]: 2018-04-19 16:33:16: (configfile.c…)
Apr 19 16:33:16 piaware lighttpd[11545]: 2018-04-19 16:33:16: (configfile.c…)
Apr 19 16:33:16 piaware systemd[1]: lighttpd.service: control process exite…55
Apr 19 16:33:16 piaware systemd[1]: Failed to start Lighttpd Daemon.
Apr 19 16:33:16 piaware systemd[1]: Unit lighttpd.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.

Attempts to force reinstall resulted in:

pi@piaware:/var/www/html$ sudo apt-get --reinstall install lighttpd
Reading package lists… Done
Building dependency tree
Reading state information… Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/222 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database … 73316 files and directories currently installed.)
Preparing to unpack …/lighttpd_1.4.35-4+deb8u1_armhf.deb …
Unpacking lighttpd (1.4.35-4+deb8u1) over (1.4.35-4+deb8u1) …
Processing triggers for systemd (215-17+deb8u7) …
Processing triggers for man-db (2.7.5-1~bpo8+1) …
Setting up lighttpd (1.4.35-4+deb8u1) …
Job for lighttpd.service failed. See ‘systemctl status lighttpd.service’ and ‘jo urnalctl -xn’ for details.
invoke-rc.d: initscript lighttpd, action “start” failed.
Failed to start Lighttpd. Maybe another webserver is already listening on port 8 0?

Changing to another port and attempting to start threw the same error. Noticed in the conf-enabled folder the symlink to 89-dump1090.conf was pointing to /etc/lighttpd/conf-available/89-dump1090.conf, which doesn’t exist.

Deleted that symlink and created another in the /conf-enabled folder for 89-dump1090-fa.conf was pointing to /etc/lighttpd/conf-available/89-dump1090-fa.conf
and now the issue is resolved. SkyView is working again!!

Image version is 3.5.3


#2

How did you do these?

"
Changing to another port and attempting to start threw the same error. Noticed in the conf-enabled folder the symlink to 89-dump1090.conf was pointing to /etc/lighttpd/conf-available/89-dump1090.conf, which doesn’t exist.

Deleted that symlink and created another in the /conf-enabled folder for 89-dump1090-fa.conf was pointing to /etc/lighttpd/conf-available/89-dump1090-fa.conf
and now the issue is resolved. SkyView is working again!!
"


#3

Create a symlink
ln -s /path/to/file /path/to/symlink
Change a symlink
ln -sfs /path/to/file /path/to/symlink

Delete the old symlink using sudo rm filename


#4

@jvhutchisonjr: Good workaround. Thanks.

This is easier: