My feed to FA seems to have an issue Today. No aircraft showing PiAware SkyAware (Local Web Interface) or SkyAware AnyWhere (Remote Web Interface).
No streak showing and my Hourly Received reports shows as this:
I have restarted PiAware and performed a device restart so any ideas please?
Thanks in advance
If you are familiar with command line and have access via SSH to the device, try logging on and check the logs for something suspicious.
first i would check that dump1090-fa and piaware are running. Use these commands (one after each other and check results in between):
sudo systemctl status dump1090-fa
sudo systemctl status piaware
If status is “failed” then one of them is not running.
Then i would continue with troubleshooting based on the results.
Later you can check the general journal for entries with
sudo journalctl -xe (works without sudo as well)
Thanks for that, I will give it a try
Output from 1st command
â—Ź dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2025-01-21 07:06:51 UTC; 29min ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Main PID: 7539 (dump1090-fa)
Tasks: 3 (limit: 2058)
CPU: 11min 59.467s
CGroup: /system.slice/dump1090-fa.service
└─7539 /usr/bin/dump1090-fa --quiet --device-type rtlsdr --device-index 0 --gain 60 --adaptive-range --fix --lat 52.75746 --lon -2.55661 --max-range 360 --net-ro-port 30002 --net-sbs-port 3000>
Jan 21 07:06:51 piaware dump1090-fa[7539]: Found Rafael Micro R820T tuner
Jan 21 07:06:51 piaware dump1090-fa[7539]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)
Jan 21 07:06:52 piaware dump1090-fa[7539]: adaptive: using 50% duty cycle
Jan 21 07:06:52 piaware dump1090-fa[7539]: adaptive: enabled adaptive gain control with gain limits 0.0dB (step 0) … 58.6dB (step 29)
Jan 21 07:06:52 piaware dump1090-fa[7539]: adaptive: enabled dynamic range control, target dynamic range 30.0dB
Jan 21 07:06:52 piaware dump1090-fa[7539]: Allocating 4 zero-copy buffers
Jan 21 07:07:02 piaware dump1090-fa[7539]: adaptive: available dynamic range (27.5dB) < required dynamic range (30.0dB), switching to downward scan
Jan 21 07:07:02 piaware dump1090-fa[7539]: adaptive: changing gain from 58.6dB (step 29) to 49.6dB (step 28) because: probing dynamic range gain lower bound
Jan 21 07:07:02 piaware dump1090-fa[7539]: rtlsdr: tuner gain set to 49.6 dB (gain step 28)
Jan 21 07:07:13 piaware dump1090-fa[7539]: adaptive: available dynamic range (37.5dB) >= required dynamic range (30.0dB), stopping downwards scan here
lines 1-20/20 (END)
Output from 2nd command
â—Ź piaware.service - FlightAware ADS-B uploader
Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2025-01-21 06:56:29 UTC; 42min ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Main PID: 3948 (piaware)
Tasks: 4 (limit: 2058)
CPU: 3min 40.468s
CGroup: /system.slice/piaware.service
├─3948 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
├─4910 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --results beast,listen,30105 --results ext_basestat>
└─7616 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 52.757 --lon -2.557
Jan 21 07:22:05 piaware piaware[3948]: 7686 msgs recv’d from dump1090-fa (2142 in last 5m); 7686 msgs sent to FlightAware
Jan 21 07:27:05 piaware piaware[3948]: 9997 msgs recv’d from dump1090-fa (2311 in last 5m); 9997 msgs sent to FlightAware
Jan 21 07:28:35 piaware piaware[3948]: mlat-client(4910): Receiver status: connected
Jan 21 07:28:35 piaware piaware[3948]: mlat-client(4910): Server status: synchronized with 582 nearby receivers
Jan 21 07:28:35 piaware piaware[3948]: mlat-client(4910): Receiver: 1428.2 msg/s received 224.6 msg/s processed (16%)
Jan 21 07:28:35 piaware piaware[3948]: mlat-client(4910): Server: 0.1 kB/s from server 0.0kB/s TCP to server 2.7kB/s UDP to server
Jan 21 07:28:35 piaware piaware[3948]: mlat-client(4910): Results: 20.3 positions/minute
Jan 21 07:28:35 piaware piaware[3948]: mlat-client(4910): Aircraft: 12 of 14 Mode S, 69 of 84 ADS-B used
Jan 21 07:32:05 piaware piaware[3948]: 12072 msgs recv’d from dump1090-fa (2075 in last 5m); 12072 msgs sent to FlightAware
Jan 21 07:37:05 piaware piaware[3948]: 14388 msgs recv’d from dump1090-fa (2316 in last 5m); 14388 msgs sent to FlightAware
lines 1-22/22 (END)
Everything now appears to be back to normal but due to the problem existing from midnight to 07:00 this morning I have lost my streak, is that normal for a relatively short outage ?
Your streak seems to be intact, looking at your page it is on 96 days
Odd, it wasn’t showing earlier but I just checked and you are indeed correct 
Run graphs1090 so you have local stats and don’t need to rely on FA for that.
Yes, that’s how it looks from the results of the two commands
Short hint for your next posting:
If you post results from logs etc. put them in as preformatted text.
This can be easily achieved by selecting all the text you want to have formatted and click on this icon in the editor menu:
It will then look like this which makes it a lot easier to read for everyone:
â—Ź dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2025-01-21 07:06:51 UTC; 29min ago
Docs: [PiAware - ADS-B and MLAT Receiver - FlightAware](https://flightaware.com/adsb/piaware/)
Main PID: 7539 (dump1090-fa)
Tasks: 3 (limit: 2058)
CPU: 11min 59.467s
Thanks for the tip and confirmation
Great tip for us newbies
I have exactly the same problem. It’s a Flight Feeder so I don’t have access to the Maintenance functions as in Pi’s.
My local screen shows more than 50 aircraft and message rate 300 to 400 per second.
Stats page shows “Last check-in 5 min ago”, but no aircraft positions being captured.
I’m fairly new to this, so help appreciated.
Your FlightFeeder has limited network connectivity and was previously feeding data via the internal management VPN. The management VPN is currently down for maintenance and should be back in a few days. As a workaround, you could look into why the FlightFeeder is not able to directly connect to FlightAware’s servers (on port 1200 TCP)
(we try to provide a lot of redundancy in terms of how your FlightFeeder can communicate with our servers, but unfortunately your network environment means that only one way works and that way is currently down)
Thank you for your explanation. It’s reporting not connecting to the VPN, which is what you told me. I connected it to my phone hot spot for a while and everything was working normally.
I’m in a school and our network is fairly well locked down. I got one of the staff to open port 1200 TCP on the VLAN on which it’s connected, but still unsuccessful.
I guess I’ll just wait until the VPN system is back up.
Well, that was helpful to know. It would have been better to communicate that instead of just sending email that there is something wrong with 2 of my FFs… !
(Yes, they are behind DMZs in corporate firewalls and port limited. The downside of for-free internet…)
/M
