FlightAware Discussions

Persistent AJAX error

I’m running a pi 4 with the SDRPlay disk image connected to an rsp1a. I have no trouble getting reception or connecting to FlightAware, but I can’t get the map to work. I get the persistent error:

Problem fetching data from dump1090.
AJAX call failed (error: Not Found). Maybe dump1090 is no longer running?
The displayed map data will be out of date.

I am forced to run the SDRPlay disk image’s build of dump1090, which might be the problem. I can’t get dump1090-fa to recognize my rsp1a. I imagine if I could, I might get the live data map to display the aircraft being tracked. Anyone have any advice?

PS, I’m a novice to linux to say nothing of debian or raspbian. I am finding some of the quirks of both the pi 4’s ARM64 architecture combined with debian buster to be really difficult to overcome so bonus points for explicit instructions.

ls /run/dump1090-fa
ls /run/dump1090

Have you checked this URL: /dump1090 ?

Also check the debug command for lighttpd listed here:
https://github.com/wiedehopf/adsb-wiki/wiki/Debug-commands

I’m not sure what you mean by the URL: /dump1090, but if you mean to attach it to the end of my local device ip address, it loads the same map with the AJAX error.

What are the other commands supposed to accomplish? There is no dump1090 folder in /run on this system.

I ran the line commands from the lighttpd heading and the results were:

sudo journalctl --no-pager -u lighttpd
– Logs begin at Thu 2019-02-14 05:12:00 EST, end at Mon 2020-01-06 19:52:39 EST. –
Jan 06 19:47:42 raspberrypi systemd[1]: Starting Lighttpd Daemon…
Jan 06 19:47:45 raspberrypi systemd[1]: Started Lighttpd Daemon.

ls /etc/lighttpd/conf-enabled
88-dump1090-fa-statcache.conf 89-dump1090-fa.conf 90-javascript-alias.conf

Again, the issue when I attempt the line command dump1090-fa is this:

Mon Jan 6 19:53:13 2020 EST dump1090-fa 3.8.0~bpo9+1 starting up.
rtlsdr: no supported devices found.

Yeah, the problem is you have the configuration files for dump1090-fa but not dump1090.

ls /run/dump1090
ls /run/dump1090-mutability

In any case, my interface does some detection which feeder is running:
https://github.com/wiedehopf/tar1090#tar1090

So it should work.
You could make dump1090-fa run in --net-only mode as well if you wanted to do that.
You’d also need to change all the ports so they don’t conflict and then pump in the other data.

Something like this is scripted here: https://github.com/wiedehopf/combine1090

There are a few possibilities.
Let’s see this output as well:

pgrep -a dump1090