Hi! One of the sites I managed has just disappeared, I know it´s a bit unreliable due to connection but it usually just reports that there is no feeding, so I can reboot it. Now it´s just not there in my stats. Can’t see that something has changed from FA’s side or a lot of posts of something similar. Any idea?
A site is removed automatically after several days without data.
So the downtime was longer than a day.
You need to check the status of Piaware on the device and try to improve the reliability
Ok, thanks. Still seems a bit odd, the downtime can not have been more than a week. But I will look into it.
I assume this is site #150834. This feeder is currently connected but is feeding no data, and last fed data on 2025-03-29 (i.e. a month ago).
From recent piaware logs, dump1090 is not running and piaware’s attempts to restart it are not helping.
2 Likes
Yes, it might well be the one. It’s the only one I can not access remotely. Worse than I thought then. Thanks for looking into this!
1 Like
Maybe not the downtime, but the time the last feed was received.
As @obj stated it seem to be long ago. Can happen that dump1090 and piaware are running, but not delivering any data. That’s why i am checking the FA stats at least once a day.
1 Like
Well, I got the Pi running again and gave it back to the owner. I now have vpn so I can access it remotely. However it seems to be a problem at least when accessing tar1090. How do I discover if the flightstick (Pro Stick Plus) is broken, on command line interface?
What problem do you have?
tar1090 is working even with a “dead” Flightaware Stick. But it shows an empty map and a warning that no data is received.
You can check via journalctl -xe|grep dump1090 the status of your decoder. Please replace “dump1090” with the decoder you are using (e.g. dump1090-fa or readsb)
Got this;
journalctl -u dump1090-fa -f
-- Logs begin at Thu 2019-02-14 10:11:59 GMT. --
May 21 20:37:51 raspberrypi dump1090-fa[29488]: Wed May 21 20:37:51 2025 BST dump1090-fa 10.0.1~bpo10+1 starting up.
May 21 20:37:51 raspberrypi dump1090-fa[29488]: rtlsdr: no supported devices found.
May 21 20:37:51 raspberrypi systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
May 21 20:37:51 raspberrypi systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.
May 21 20:38:17 raspberrypi systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
May 21 20:38:17 raspberrypi systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
May 21 20:38:17 raspberrypi dump1090-fa[29712]: Wed May 21 20:38:17 2025 BST dump1090-fa 10.0.1~bpo10+1 starting up.
May 21 20:38:17 raspberrypi dump1090-fa[29712]: rtlsdr: no supported devices found.
May 21 20:38:17 raspberrypi systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
May 21 20:38:17 raspberrypi systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.
rtlsdr: no supported devices found does not bode too well.
please excecute the command lsusb on the device.
The RTL device should be listed there. If not, it’s either dead or something blocks the access.
It should show something like this:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 1d50:60a1 OpenMoko, Inc. Airspy
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
My device is the Airspy, not the RTL, shown on the second line.
If not listed, shutdown the device and try a different USB port.
1 Like
It is, actually. After a reboot, so I will monitor it for a while and see if the traffic drops again. I’ll be back.