When I just checked: https://www.adsbexchange.com/api/feeders/?feed=04a86894-0fc4-11ea-a61f-b827eb42471b It was blank. After restarting stats, working just fine. Status of feed and mlat, before and after restarting STATS in the text file. [email protected]:~ $ sudo systemctl status adsbexchange-stats ● adsbexchange-stats.service - ADSBexchange Stats Loaded: loaded (/etc/systemd/system/adsbexchange-stats.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2020-01-04 21:30:37 UTC; 19h ago Main PID: 1544 (json-status) Tasks: 3 (limit: 4915) CGroup: /system.slice/adsbexchange-stats.service ├─1544 /bin/bash /usr/bin/json-status ├─1546 inotifywait -q -m -e moved_to /run/dump1090-fa/ └─1547 /bin/bash /usr/bin/json-status Jan 04 21:30:37 piaware systemd[1]: Stopped ADSBexchange Stats. Jan 04 21:30:37 piaware systemd[1]: Started ADSBexchange Stats. Jan 05 04:08:56 piaware json-status[1544]: cp: skipping file '/run/dump1090-fa//aircraft.json', as it was replaced while being copied Jan 05 04:08:56 piaware json-status[1544]: jq: error: Could not open file /var/run/json-VpqWnrzKbM: No such file or directory Jan 05 04:08:57 piaware json-status[1544]: rm: cannot remove '/var/run/json-VpqWnrzKbM': No such file or directory Jan 05 08:40:21 piaware json-status[1544]: cp: skipping file '/run/dump1090-fa//aircraft.json', as it was replaced while being copied Jan 05 08:40:21 piaware json-status[1544]: jq: error: Could not open file /var/run/json-FqffyRQ282: No such file or directory Jan 05 08:40:22 piaware json-status[1544]: rm: cannot remove '/var/run/json-FqffyRQ282': No such file or directory [email protected]:~ $ Restart Stats sudo systemctl restart adsbexchange-stats Now status shows: [email protected]:~ $ sudo systemctl status adsbexchange-stats ● adsbexchange-stats.service - ADSBexchange Stats Loaded: loaded (/etc/systemd/system/adsbexchange-stats.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2020-01-05 16:40:47 UTC; 18min ago Main PID: 12885 (json-status) Tasks: 4 (limit: 4915) CGroup: /system.slice/adsbexchange-stats.service ├─12885 /bin/bash /usr/bin/json-status ├─12889 inotifywait -q -m -e moved_to /run/dump1090-fa/ ├─12890 /bin/bash /usr/bin/json-status └─26403 sleep 5 Jan 05 16:40:47 piaware systemd[1]: Started ADSBexchange Stats. [email protected]:~ $
After typing sudo systemctl restart adsbexchange-stats 127.0.0.1/tar1090 is fine rpi 3+, stretch, outside 1090 antenna
@Gary_B Where is your dump1090-fa or dump1090-mutability you are using writing json? stats assumes that it's either default location ... ADSBX_JSON="/run/dump1090-mutability/" FA_JSON="/run/dump1090-fa/" What image and setup?
@Mark Richardson Where is your dump1090-fa configured to write the json? I assumed piaware image is /run/dump1090-fa by default ...
ADSBX_JSON="/run/dump1090-mutability/" rpi 3+, https://www.adsbexchange.com/how-to-feed/ git clone https://github.com/adsbxchange/adsb-exchange.git stretch outside 1090 antenna Where would ADSBX_JSON be?
Depends on your dump1090 install. If you aren't using one of our premade images ... the scripts don't install dump1090 ... they assume you have a working dump1090 already ..
I uninstall dump1090-fa, then installed dump1090-mutability. Using sudo apt-get install/remove commands
Basically the stats script needs to know where your dump1090 is configured to be writing json. Normally you should write to /run/dump1090-mutability since /run is mounted as tmpfs and uses ram no SD - thus preventing SD from being obliterated in a week ADSBX feeder scripts need dump1090 port 30005 active (which should be by default) If removed and installed and haven't rebooted .. the /run directories might still be there and that's why it's not working ... I'm not sure ... Try rebooting the Pi.
It is, the error is normal, if you have the file being changed during the copy, it spits out this error. So actually that shows the directory is being used correctly. I'd assume the problem is independent of that?
The status is not that interesting .... @James .... better put the journalctl command in the readme, the systemctl status is often ... useless. Gary let's see the output for this command: Code: sudo journalctl --no-pager -u adsbexchange-stats
I think I broke it, I started by installing adsb-receiver and then adsbexchange on top of that, dump1090-fa was installed, then removed, I then installed dump1090-mutability. VirtualRadarServer is still working, FR24feed is working. Readsb, tar1090, radar, some of adsb-exchange is now not working.
readsb and dump1090 variants shouldn't be used at the same time. readsb fullfills the same function as dump1090 variants. Only use one application that talks to your receiver. The adsb receiver project is poorly maintained and is kinda annoying to remove. If you want readsb, try this: https://github.com/wiedehopf/adsb-scripts/wiki/Automatic-installation-for-readsb Or if you want dump1090-fa instead, i'd recommend this: https://github.com/wiedehopf/adsb-scripts/wiki/Bundle-install-for-dump1090fa Both scripts will clean up the other applications using the receiver. Depending on what you want to do, it might be easiest to start fresh if this doesn't work. I'm not sure James script works with readsb yet, so i'd recommend just going with dump1090-fa.
Which one do you prefer and the least amount of problems. I might go with the custom ADSBexchange sd-card image.
I went with https://github.com/wiedehopf/adsb-scripts/wiki/Automatic-installation-for-readsb, looks like adsbexchange is working now. Just about everything except piaware
