Title about sums it up. Installed adsb custom image, all set up, all working well. Installed flightradar24 feed and I no long have the web service on my Rasperry Pi. As I'm a linux beginner, but not a general computer beginner I really dont' have much experience of what to look for or how to check the web service part of my Pi. Sudo systemctl status - on readsb, adsbexchange-mlat, adsbexchange-feed and fr24feed all show as running. Feed status page at asdb and flight radar websites both show good feeds too. Can anyone suggest where and how to start looking for whatever it is I've knocked off or broken, or even if the web service needs to be restarted as I powered my Pi down to move it to it's final installation position.
Does /tar1090 still work? Web service isn't terribly precise sadly. Also you're not specifying how it's not working.
I type in the ip address of the Pi expecting the top menu offering tar1090, 8 hours tracking etc, and get no connection at all. I.e. whatever service that serves the web pages does not appear to be working.
Sounds to me like the IP changed. Try ssh. I suppose you can check the lighttpd log: sudo journalctl -u lighttpd | tail -n30
Hi, the IP is the same, tried sudo journalctl -u lighttpd | tail -n30 it says 'failed to match 'ighttpd': Invalid argument . However, sudo systemctl status lighttpd gives me ● lighttpd.service - Lighttpd Daemon Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2021-02-07 19:03:53 UTC; 14h ago Process: 1495 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf (code=exited, status=255/EXCEPTION) Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable. So, just googled lighttpd - it's the web server. This seems to have failed. Doing sudo systemctl status shows me a tree of services on the Pi, but no mention of lighttpd though. Where should I go from here ? Thanks for the help so far, while I've been around computers since the ZX81, the world of Linux has always been a mystery to me, so apologies for any huge gaps in my understanding.
You had a typo try again. Also you might need to restart it so the log wasn't cycled out: Code: sudo systemctl restart lighttpd sudo journalctl -u lighttpd | tail -n30 after that the log should have something.
ok, restart failed, as expected. it helpfully suggests I look at lighttpd.service status, finished with exception. The log file ( no typo this time ) tells me lighttpd.conf file - parser failed, so wil open it with an editor ( now need do find out about editors that work from SSH ) . That'll be nano then. So, the log then Feb 08 10:21:07 raspberrypi lighttpd[24868]: 2021-02-08 10:21:07: (configfile.c.1296) source: /etc/lighttpd/lighttpd.conf line: 46 pos: 15 parser failed somehow near here: (EOL) Feb 08 10:21:07 raspberrypi systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION Feb 08 10:21:07 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'. Feb 08 10:21:07 raspberrypi systemd[1]: Failed to start Lighttpd Daemon. Feb 08 10:21:07 raspberrypi systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart. Feb 08 10:21:07 raspberrypi systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 3. Feb 08 10:21:07 raspberrypi systemd[1]: Stopped Lighttpd Daemon. Feb 08 10:21:07 raspberrypi systemd[1]: Starting Lighttpd Daemon... Feb 08 10:21:08 raspberrypi lighttpd[24880]: Duplicate config variable in conditional 0 global: server.stat-cache-engine Feb 08 10:21:08 raspberrypi lighttpd[24880]: 2021-02-08 10:21:07: (configfile.c.1296) source: /etc/lighttpd/conf-enabled/89-dump1090.conf line: 19 pos: 1 parser failed somehow near here: (EOL) Feb 08 10:21:08 raspberrypi lighttpd[24880]: 2021-02-08 10:21:07: (configfile.c.1296) source: /etc/lighttpd/lighttpd.conf line: 46 pos: 15 parser failed somehow near here: (EOL) Feb 08 10:21:08 raspberrypi systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION Feb 08 10:21:08 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'. Feb 08 10:21:08 raspberrypi systemd[1]: Failed to start Lighttpd Daemon. Feb 08 10:21:08 raspberrypi systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart. Feb 08 10:21:08 raspberrypi systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 4. Feb 08 10:21:08 raspberrypi systemd[1]: Stopped Lighttpd Daemon. Feb 08 10:21:08 raspberrypi systemd[1]: Starting Lighttpd Daemon... Feb 08 10:21:08 raspberrypi lighttpd[24891]: Duplicate config variable in conditional 0 global: server.stat-cache-engine Feb 08 10:21:08 raspberrypi lighttpd[24891]: 2021-02-08 10:21:08: (configfile.c.1296) source: /etc/lighttpd/conf-enabled/89-dump1090.conf line: 19 pos: 1 parser failed somehow near here: (EOL) Feb 08 10:21:08 raspberrypi lighttpd[24891]: 2021-02-08 10:21:08: (configfile.c.1296) source: /etc/lighttpd/lighttpd.conf line: 46 pos: 15 parser failed somehow near here: (EOL) Feb 08 10:21:08 raspberrypi systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION Feb 08 10:21:08 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'. Feb 08 10:21:08 raspberrypi systemd[1]: Failed to start Lighttpd Daemon. Feb 08 10:21:08 raspberrypi systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart. Feb 08 10:21:08 raspberrypi systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 5. Feb 08 10:21:08 raspberrypi systemd[1]: Stopped Lighttpd Daemon. Feb 08 10:21:08 raspberrypi systemd[1]: lighttpd.service: Start request repeated too quickly. Feb 08 10:21:08 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'. Feb 08 10:21:08 raspberrypi systemd[1]: Failed to start Lighttpd Daemon. Looking at line 46 - here is line 45 to 50 #server.compat-module-load = "disable" server.modules += ( "mod_compress", "mod_dirlisting", "mod_staticfile", ) Also the log mentions line 19 in /etc/lighttpd/conf-enabled/89-dump1090.conf Here is the complete 8-dump1090.conf file with 18 lines only # Allows access to the static files that provide the dump1090 map view, # and also to the dynamically-generated json parts that contain aircraft # data and are periodically written by the dump1090 daemon. url.redirect += ( "^/dump1090/$" => "/dump1090/gmap.html", "^/dump1090$" => "/dump1090/gmap.html" ) alias.url += ( "/dump1090/data/" => "/run/dump1090-mutability/", "/dump1090/" => "/usr/share/dump1090-mutability/html/" ) # The stat cache must be disabled, as aircraft.json changes # frequently and lighttpd's stat cache often ends up with the # wrong content length. server.stat-cache-engine = "disable" It's only got 18 lines ! I'd like to say that something jumped out at me as being wong in here, but without an original conf file to check I dont know what's been changed. Many thanks for your help so far BTW.
Yeah you selected DVB-T in the fr24feed install, that's bad, we don' t want any dump1090 on the system, we run readsb. If you would have used the autoconfig it would have been correct ;P Code: sudo apt remove dump1090 sudo rm /etc/lighttpd/conf-enabled/89-dump1090.conf I'd recommend following these instructions if you really have to feed FR24 ... https://github.com/wiedehopf/adsb-wiki/wiki/Raspbian-Lite:-ADS-B-receiver#10-feed-fr24-optional This should make it so the stupid automatic install for dump1090 and any stupid stuff along those lines never runs. fr24feed is bad code ... and by default has autoupdate which is very ugly. Anyhow ... with those instructions it usually shouldn't interfere.
Excellent stuff, worked a charm, restarted lighttpd, checked status, running, I now have my info back. I'll check the flight radar info you've given me as ideally I'd like to feed both, my good lady prefers flight radar ! Thank you again for all your help with this, it's much appreciated.
