My feeder's been running fine for months but apparently something's gone wrong. I've cold-started and warm-started it a few times, it runs normally for an hour or so and then no longer sends any detected aircraft. Journal entries below. Any ideas? -- Logs begin at Thu 2019-02-14 03:11:59 MST, end at Thu 2020-12-17 21:14:46 MST. -- Dec 17 18:19:59 raspberrypi systemd[1]: Started adsbexchange-feed. Dec 17 18:19:59 raspberrypi adsbexchange-feed[474]: Could not connect to 127.0.0.1:30005, retry in 30 seconds. Dec 17 18:20:39 raspberrypi adsbexchange-feed[474]: Fri Dec 18 01:20:39 2020 GMT feed-adsbx starting up. Dec 17 18:20:39 raspberrypi adsbexchange-feed[474]: Version: 2685f45 Sat Jul 4 17:37:29 2020 0200: print commandline used on argparse error Dec 17 18:20:39 raspberrypi adsbexchange-feed[474]: Net-only mode, no SDR device or file open. Dec 17 18:20:39 raspberrypi adsbexchange-feed[474]: BeastReduce TCP output: Attempting connection to feed.adsbexchange.com port 30005 ... Dec 17 18:20:39 raspberrypi adsbexchange-feed[474]: Beast TCP input: Attempting connection to 127.0.0.1 port 30005 ... Dec 17 18:20:39 raspberrypi adsbexchange-feed[474]: Beast TCP input: Connection established: 127.0.0.1 port 30005 Dec 17 18:20:39 raspberrypi adsbexchange-feed[474]: Beast TCP input: Attempting connection to localhost port 30157 ... Dec 17 18:20:39 raspberrypi adsbexchange-feed[474]: Beast TCP input: Connection to localhost :1) port 30157 failed: 111 (Connection refused) Dec 17 18:20:39 raspberrypi adsbexchange-feed[474]: BeastReduce TCP output: Connection established: feed.adsbexchange.com (216.48.109.64) port 30005 Dec 17 18:20:39 raspberrypi adsbexchange-feed[474]: UUID: 0c42cdbe-c65b-492d-829e-a4068214764e Dec 17 18:20:39 raspberrypi adsbexchange-feed[474]: Beast TCP input: Attempting connection to localhost port 30157 ... Dec 17 18:20:39 raspberrypi adsbexchange-feed[474]: Beast TCP input: Connection to localhost (127.0.0.1) port 30157 failed: 111 (Connection refused) Dec 17 18:21:09 raspberrypi adsbexchange-feed[474]: Beast TCP input: Attempting connection to localhost port 30157 ... Dec 17 18:21:09 raspberrypi adsbexchange-feed[474]: Beast TCP input: Connection established: localhost :1) port 30157 Dec 17 18:33:38 raspberrypi adsbexchange-feed[474]: Beast TCP input: Remote server disconnected: 127.0.0.1 port 30005 (fd 4, SendQ 0, RecvQ 0) Dec 17 18:33:41 raspberrypi adsbexchange-feed[474]: Beast TCP input: Attempting connection to 127.0.0.1 port 30005 ... Dec 17 18:33:41 raspberrypi adsbexchange-feed[474]: Beast TCP input: Connection to 127.0.0.1 port 30005 failed: 111 (Connection refused) Dec 17 18:34:11 raspberrypi adsbexchange-feed[474]: Beast TCP input: Attempting connection to 127.0.0.1 port 30005 ... Dec 17 18:34:11 raspberrypi adsbexchange-feed[474]: Beast TCP input: Connection established: 127.0.0.1 port 30005 Dec 17 18:39:21 raspberrypi adsbexchange-feed[474]: Beast TCP input: Remote server disconnected: 127.0.0.1 port 30005 (fd 4, SendQ 0, RecvQ 0) Dec 17 18:39:24 raspberrypi adsbexchange-feed[474]: Beast TCP input: Attempting connection to 127.0.0.1 port 30005 ... Dec 17 18:39:24 raspberrypi adsbexchange-feed[474]: Beast TCP input: Connection to 127.0.0.1 port 30005 failed: 111 (Connection refused) Dec 17 18:39:54 raspberrypi adsbexchange-feed[474]: Beast TCP input: Attempting connection to 127.0.0.1 port 30005 ... Dec 17 18:39:54 raspberrypi adsbexchange-feed[474]: Beast TCP input: Connection established: 127.0.0.1 port 30005 Dec 17 20:05:41 raspberrypi adsbexchange-mlat[467]: Fri Dec 18 03:05:41 2020 Receiver status: connected Dec 17 20:05:41 raspberrypi adsbexchange-mlat[467]: Fri Dec 18 03:05:41 2020 Server status: ready Dec 17 20:05:41 raspberrypi adsbexchange-mlat[467]: Fri Dec 18 03:05:41 2020 Receiver: 142.4 msg/s received 78.1 msg/s processed (55%) Dec 17 20:05:41 raspberrypi adsbexchange-mlat[467]: Fri Dec 18 03:05:41 2020 Server: 0.0 kB/s from server 0.7kB/s TCP to server 0.0kB/s UDP to server Dec 17 20:05:41 raspberrypi adsbexchange-mlat[467]: Fri Dec 18 03:05:41 2020 Results: 19.4 positions/minute Dec 17 20:05:41 raspberrypi adsbexchange-mlat[467]: Fri Dec 18 03:05:41 2020 Aircraft: 3 of 14 Mode S, 20 of 28 ADS-B used Dec 17 20:20:41 raspberrypi adsbexchange-mlat[467]: Fri Dec 18 03:20:41 2020 Receiver status: connected Dec 17 20:20:41 raspberrypi adsbexchange-mlat[467]: Fri Dec 18 03:20:41 2020 Server status: ready Dec 17 20:20:41 raspberrypi adsbexchange-mlat[467]: Fri Dec 18 03:20:41 2020 Receiver: 111.5 msg/s received 60.4 msg/s processed (54%) Dec 17 20:20:41 raspberrypi adsbexchange-mlat[467]: Fri Dec 18 03:20:41 2020 Server: 0.0 kB/s from server 0.5kB/s TCP to server 0.0kB/s UDP to server Dec 17 20:20:41 raspberrypi adsbexchange-mlat[467]: Fri Dec 18 03:20:41 2020 Results: 17.8 positions/minute Dec 17 20:20:41 raspberrypi adsbexchange-mlat[467]: Fri Dec 18 03:20:41 2020 Aircraft: 0 of 0 Mode S, 0 of 0 ADS-B used Dec 17 20:35:42 raspberrypi adsbexchange-mlat[467]: Fri Dec 18 03:35:42 2020 Receiver status: connected Dec 17 20:35:42 raspberrypi adsbexchange-mlat[467]: Fri Dec 18 03:35:42 2020 Server status: ready Dec 17 20:35:42 raspberrypi adsbexchange-mlat[467]: Fri Dec 18 03:35:42 2020 Receiver: 0.0 msg/s received 0.0 msg/s processed (0%) Dec 17 20:35:42 raspberrypi adsbexchange-mlat[467]: Fri Dec 18 03:35:42 2020 Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server Dec 17 20:35:42 raspberrypi adsbexchange-mlat[467]: Fri Dec 18 03:35:42 2020 Aircraft: 0 of 0 Mode S, 0 of 0 ADS-B used Dec 17 20:50:42 raspberrypi adsbexchange-mlat[467]: Fri Dec 18 03:50:42 2020 Receiver status: connected Dec 17 20:50:42 raspberrypi adsbexchange-mlat[467]: Fri Dec 18 03:50:42 2020 Server status: ready Dec 17 20:50:42 raspberrypi adsbexchange-mlat[467]: Fri Dec 18 03:50:42 2020 Receiver: 0.0 msg/s received 0.0 msg/s processed (0%) Dec 17 20:50:42 raspberrypi adsbexchange-mlat[467]: Fri Dec 18 03:50:42 2020 Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server Dec 17 20:50:42 raspberrypi adsbexchange-mlat[467]: Fri Dec 18 03:50:42 2020 Aircraft: 0 of 0 Mode S, 0 of 0 ADS-B used Dec 17 21:05:42 raspberrypi adsbexchange-mlat[467]: Fri Dec 18 04:05:42 2020 Receiver status: connected Dec 17 21:05:42 raspberrypi adsbexchange-mlat[467]: Fri Dec 18 04:05:42 2020 Server status: ready Dec 17 21:05:42 raspberrypi adsbexchange-mlat[467]: Fri Dec 18 04:05:42 2020 Receiver: 0.0 msg/s received 0.0 msg/s processed (0%) Dec 17 21:05:42 raspberrypi adsbexchange-mlat[467]: Fri Dec 18 04:05:42 2020 Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server Dec 17 21:05:42 raspberrypi adsbexchange-mlat[467]: Fri Dec 18 04:05:42 2020 Aircraft: 0 of 0 Mode S, 0 of 0 ADS-B used
Most likely is power failure. The SDR can also fail. Check for power issues: https://github.com/wiedehopf/adsb-wiki/wiki/Debug-commands#undervoltage If the SDR is connected via an USB extension, plug it in directly. Test the SDR: https://github.com/wiedehopf/adsb-wiki/wiki/Debug-commands#test-the-rtl-sdr-receiver I don't know which decoder you run ... you should check that log as well. Or just run the readsb install script here: https://github.com/wiedehopf/adsb-wiki/wiki/Raspbian-Lite:-ADS-B-receiver https://github.com/wiedehopf/adsb-scripts/wiki/Automatic-installation-for-readsb That page also has a command on how to look at the log.
The diagnosis and fix were even easier: Since the PI was running perfectly I shut it down, powered it off, pulled out the SDR stick, sprayed contact cleaner on the USB plug and jack, plugged it back in and started it up. It's been running fine for hours. Thanks anyway.
A failing power supply can create weirdness. The SDR requires a stable 5V as close as you can get. Pi 3 struggles with that in best conditions, so when power supply starts to fail, down it goes. Pi 4 should have no issue maintain 5V to the SDR. Seems like in your case it just wasn't making a good USB connection.
