FlightAware Discussions

Dump 1090 Errors

When I look at my FlightAware ADS-B receiver, I am getting the following error every minute or so:

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.

A minute or so later, the message goes away and the aircraft list is updated. Then it happens again.

I just updated to 3.7.2. Everything was working fine until about a month or two ago. Then I wasn’t seeing any aircraft. After updating to 3.7.2, I started seeing aircraft again, but now I have this problem.


It could be a busy CPU or network connectivity issue.

run top or htop to see how busy the device is.

Looking at your feeder 93993 I see a lot of hours in the hourly reports with no received reports. Is this site using WiFi for connectivity of the Pi to the network?

I would be suspicious of network connectivity. If you are using a PC running Windows or Linux try running a continuous ping to the ip of your FlightAware ADS-B receiver (ping -t 192.168.0.x) and see if you get any time out or unreachable messages.

If you are using WiFi and you are loosing connectivity I suggest you take a look at this post for possible solutions. PiAware WiFi looses connection randomly - Work-round found

The problem is internal in the Pi system, not in the WiFi connection to my network. I am pinging the feeder continuously and it consistently has ~40ms ping times, without any dropouts. When I am looking at the feeder map, about once a minute, the yellow error box pops up in the bottom left corner of the map and the aircraft list freezes for about 20 seconds. During this time, the clock at the top of the screen is still updating. After about 20 seconds, the aircraft list starts updating again, and the warning box disappears.

I’m not very technically inclined. How do I do that?

If you don’t have anything besides PiAware running on the RPi I think the simplest thing would be to re-image the SD card. The only thing you need to be concerned about if you do that, is keeping your existing feeder id, but how to do that is documented here https://flightaware.com/adsb/piaware/upgrade. The only caveat is where it says

piaware-config feeder-id 12345678-1234-1234-1234-123456789abc

Be sure to insert sudo in front of it, like this

sudo piaware-config feeder-id 12345678-1234-1234-1234-123456789abc

I doubt it’s gonna be a software issue.

Most likely the power supply or the dongle is dying.
Anyway that’s my guesses.

If you want to further diagnose the issue you’ll need ssh access:
For Beginners - How-to SSH to RPi - Setup Putty in Windows

While configuring that, it doesn’t hurt to reimage the sd-card with a fresh image as you have the sd-card out anyway.
(For Beginners - How to Get Back Existing Station Number in A Fresh Install)

40ms seems really high. I get that ping servers on the West coast from the East coast of the USA.