I noticed a few days ago that when I pull up the globe map for my feed (https://globe.adsbexchange.com/?feed=D2qG2NB9qNuE) there are no planes (or very, very few) - thought I broke something, but the feeder status page looks normal (for my little feeder) https://www.adsbexchange.com/api/feeders/?feed=D2qG2NB9qNuE I'm also showing good stats to flightaware. So I think all is well on my end. Thoughts?
Logs: [email protected]:~ $ sudo journalctl -u adsbexchange-feed | tail -n30 -- Logs begin at Fri 2022-07-08 20:20:09 UTC, end at Tue 2022-07-19 15:46:32 UTC. -- [email protected]:~ $ Local map: ADSB map:
ADSB feeder status: So everything suggests I'm seeing and feeding planes, just they are not showing up on the ADSB feeder map.
Are you sure you're feeding? Seems you only installed the stats script or something. Run this: https://github.com/adsbxchange/adsb-exchange#ads-b-exchange-setup-scripts-airplane Then re-run the stats install script. Your whole setup seems outdated redoing it: https://github.com/wiedehopf/adsb-wiki/wiki/Raspbian-Lite:-ADS-B-receiver
The planes not showing was a webinterface error (which i fixed). But still you only installed the stats script and aren't really feeding, so do what i described in the post above. Where did you read to only install the stats script, can you let me know so i can possibly clarify the readme somewhere.
Yay! Planes again! - Thanks! I'll add the redo to the summer job jar My ADSB folders date back to 2020, and my uptime is hundreds of days. I barely remember what I did yesterday - lol! Sorry, no idea what led me down the path I went. It's an old FlightAware setup that I tweaked to add ADSB to.
You're not feeding adsbexchange. Just run the setup, it's not hard. https://github.com/adsbxchange/adsb-exchange#ads-b-exchange-setup-scripts-airplane
So this says I'm feeding - to be fair I checked it after attempting the script you link. But it threw a bunch of fetching package errors. My Pi is old. Even running an apt-get update threw package 404 not found errors. Checking connectivity... done. WARNING: apt does not have a stable CLI interface yet. Use with caution in scripts. E: Unable to locate package libzstd-dev E: Unable to locate package libzstd1 WARNING: apt does not have a stable CLI interface yet. Use with caution in scripts. W: Failed to fetch http://mirrordirector.raspbian.org/raspbian/dists/jessie/main/binary-armhf/Packages 404 Not Found [IP: 93.93.128.193 80] W: Failed to fetch http://mirrordirector.raspbian.org/raspbian/dists/jessie/contrib/binary-armhf/Packages 404 Not Found [IP: 93.93.128.193 80] W: Failed to fetch http://mirrordirector.raspbian.org/raspbian/dists/jessie/non-free/binary-armhf/Packages 404 Not Found [IP: 93.93.128.193 80] W: Failed to fetch http://mirrordirector.raspbian.org/raspbian/dists/jessie/rpi/binary-armhf/Packages 404 Not Found [IP: 93.93.128.193 80] E: Some index files failed to download. They have been ignored, or old ones used instead.
My entire setup is sketchy - I won't deny that. I seem to recall when I first started feeding adsb that I ran some manual network cloning commands to copy my flightaware stream to an adsb target or something. I realize my PI is definitely in need of a tune up. So, yeah, I have work to do. Thanks for fixing the glitch on the maps!
Well it's sending data somehow, that's why i wrote nevermind. Also getting those raspbian jessie sources working .... isn't simple. It's basically so old that it's no longer supported. As i already linked, if you ever care to start with a fresh image: https://github.com/wiedehopf/adsb-wiki/wiki/Raspbian-Lite:-ADS-B-receiver
