Hello All - I am new to this… On the steep learning curve…
For some reason today I cannot get access to the web interface.
This feature was working yesterday. When I attempt to connect to web interface I receive the following error - “This site can’t be reached” My stats (site information) page seems to indicate that the receiver etc is collecting data and working correctly. Any ideas??
PS - Yes I have internet access. I have tried to access from several computers - including the RPi itself…
Check this log
sudo journalctl --no-pager -u lighttpd
Also check the output for this:
curl -s http://127.0.0.1/dump1090-fa/data/aircraft.json | head -n 4
Maybe you have just mixed up the IP address or it has changed?
Thank you for the reply !
I checked sudo journalctl --no-pager -u lighttpd and this is what I get…
Mar 25 08:15:02 raspberrypi systemd[1]: Starting Lighttpd Daemon…
Mar 25 08:15:04 raspberrypi lighttpd[435]: Duplicate config variable in conditional 0 global: server.stat-cache-engine
Mar 25 08:15:04 raspberrypi lighttpd[435]: 2020-03-25 08:15:03: (configfile.c.1289) source: /etc/lighttpd/conf-enabled/89-dump1090.conf line: 19 pos: 1 parser failed somehow near here: (EOL)
Mar 25 08:15:04 raspberrypi lighttpd[435]: 2020-03-25 08:15:03: (configfile.c.1289) source: /etc/lighttpd/lighttpd.conf line: 47 pos: 15 parser failed somehow near here: (EOL)
Mar 25 08:15:04 raspberrypi systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION
Mar 25 08:15:04 raspberrypi systemd[1]: lighttpd.service: Failed with result ‘exit-code’.
Mar 25 08:15:04 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.
Mar 25 08:15:04 raspberrypi systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
Mar 25 08:15:04 raspberrypi systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 1.
Mar 25 08:15:04 raspberrypi systemd[1]: Stopped Lighttpd Daemon.
Mar 25 08:15:04 raspberrypi systemd[1]: Starting Lighttpd Daemon…
Mar 25 08:15:05 raspberrypi lighttpd[537]: Duplicate config variable in conditional 0 global: server.stat-cache-engine
Mar 25 08:15:05 raspberrypi lighttpd[537]: 2020-03-25 08:15:04: (configfile.c.1289) source: /etc/lighttpd/conf-enabled/89-dump1090.conf line: 19 pos: 1 parser failed somehow near here: (EOL)
Mar 25 08:15:05 raspberrypi lighttpd[537]: 2020-03-25 08:15:04: (configfile.c.1289) source: /etc/lighttpd/lighttpd.conf line: 47 pos: 15 parser failed somehow near here: (EOL)
Mar 25 08:15:05 raspberrypi systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION
Mar 25 08:15:05 raspberrypi systemd[1]: lighttpd.service: Failed with result ‘exit-code’.
Mar 25 08:15:05 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.
Mar 25 08:15:05 raspberrypi systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
Mar 25 08:15:05 raspberrypi systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 2.
Mar 25 08:15:05 raspberrypi systemd[1]: Stopped Lighttpd Daemon.
Mar 25 08:15:05 raspberrypi systemd[1]: Starting Lighttpd Daemon…
Mar 25 08:15:05 raspberrypi lighttpd[545]: Duplicate config variable in conditional 0 global: server.stat-cache-engine
Mar 25 08:15:05 raspberrypi lighttpd[545]: 2020-03-25 08:15:05: (configfile.c.1289) source: /etc/lighttpd/conf-enabled/89-dump1090.conf line: 19 pos: 1 parser failed somehow near here: (EOL)
Mar 25 08:15:05 raspberrypi lighttpd[545]: 2020-03-25 08:15:05: (configfile.c.1289) source: /etc/lighttpd/lighttpd.conf line: 47 pos: 15 parser failed somehow near here: (EOL)
Mar 25 08:15:05 raspberrypi systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION
Mar 25 08:15:05 raspberrypi systemd[1]: lighttpd.service: Failed with result ‘exit-code’.
Mar 25 08:15:05 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.
Mar 25 08:15:06 raspberrypi systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
Mar 25 08:15:06 raspberrypi systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 3.
Mar 25 08:15:06 raspberrypi systemd[1]: Stopped Lighttpd Daemon.
Mar 25 08:15:06 raspberrypi systemd[1]: Starting Lighttpd Daemon…
Mar 25 08:15:06 raspberrypi lighttpd[555]: Duplicate config variable in conditional 0 global: server.stat-cache-engine
Mar 25 08:15:06 raspberrypi lighttpd[555]: 2020-03-25 08:15:06: (configfile.c.1289) source: /etc/lighttpd/conf-enabled/89-dump1090.conf line: 19 pos: 1 parser failed somehow near here: (EOL)
Mar 25 08:15:06 raspberrypi lighttpd[555]: 2020-03-25 08:15:06: (configfile.c.1289) source: /etc/lighttpd/lighttpd.conf line: 47 pos: 15 parser failed somehow near here: (EOL)
Mar 25 08:15:06 raspberrypi systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION
Mar 25 08:15:06 raspberrypi systemd[1]: lighttpd.service: Failed with result ‘exit-code’.
Mar 25 08:15:06 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.
Mar 25 08:15:06 raspberrypi systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
Mar 25 08:15:06 raspberrypi systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 4.
Mar 25 08:15:06 raspberrypi systemd[1]: Stopped Lighttpd Daemon.
Mar 25 08:15:06 raspberrypi systemd[1]: Starting Lighttpd Daemon…
Mar 25 08:15:07 raspberrypi lighttpd[573]: Duplicate config variable in conditional 0 global: server.stat-cache-engine
Mar 25 08:15:07 raspberrypi lighttpd[573]: 2020-03-25 08:15:06: (configfile.c.1289) source: /etc/lighttpd/conf-enabled/89-dump1090.conf line: 19 pos: 1 parser failed somehow near here: (EOL)
Mar 25 08:15:07 raspberrypi lighttpd[573]: 2020-03-25 08:15:06: (configfile.c.1289) source: /etc/lighttpd/lighttpd.conf line: 47 pos: 15 parser failed somehow near here: (EOL)
Mar 25 08:15:07 raspberrypi systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION
Mar 25 08:15:07 raspberrypi systemd[1]: lighttpd.service: Failed with result ‘exit-code’.
Mar 25 08:15:07 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.
Mar 25 08:15:07 raspberrypi systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
Mar 25 08:15:07 raspberrypi systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 5.
Mar 25 08:15:07 raspberrypi systemd[1]: Stopped Lighttpd Daemon.
Mar 25 08:15:07 raspberrypi systemd[1]: lighttpd.service: Start request repeated too quickly.
Mar 25 08:15:07 raspberrypi systemd[1]: lighttpd.service: Failed with result ‘exit-code’.
Mar 25 08:15:07 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.
pi@raspberrypi:~ $ Failed to start Lighttpd Daemon.
-bash: Failed: command not found
And when I execute - curl -s http://127.0.0.1/dump1090-fa/data/aircraft.json | head -n 4
I get a return prompt.
I check my router and the RPi and it looks like I am still on the same IP address as I was.
I have no clue what any of this means…
As added info… I poked around in my router but I don’t find anything that seems to be amiss. However, we had thunderstorms in the area last evening that did cause a disruption to cable internet service. In fact whatever happened caused YouTube to go out and I had to pull the plug on my TV display to get it to shut off and restart. Apparently the internet was in and out multiple times overnite…
You installed dump1090-mutability which won’t work at the same time with lighttpd as dump1090-fa.
I’d recommend just running this: Automatic installation for dump1090 fa · wiedehopf/adsb-scripts Wiki · GitHub
It will remove dump1090-mutability and clean up the lighttpd configuration. (it’s a common issue that’s why i’ve included it in the script)
Thank you very much !! That seems to have taken care of the problem !
I am looking forward to learning more, and experimenting. I have a new antenna installation planned. I also would like to experiment with the receiver gain…
Just curious, may I know why you have originally installed both dump1090-mutability and dump1090-fa?
I think the best answer I can give is because I have no idea what I am doing. I did not intentionally try to install mutability. I have no idea what that is. the first time my system crashed I found a thread that seemed to explain or how to work around some issues. My system locked up a couple more times and I was doing whatever I could to get it back running again.