FA status shows not connected but piaware is sending

FlightAware General
1

I received an email saying my site was not feeding FA, but skyaware-anywhere shows a/c, and the system service command shows that messages are being sent. On the stats page, the three PiAware, Flightaware and MLAT boxes are all red. The “hourly received reports” shows nothing received for the last 8 hours. Here’s the output of service piaware status:
$ service piaware status
● piaware.service - FlightAware ADS-B uploader
Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2022-11-07 13:50:00 EST; 1 weeks 1 days ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Main PID: 738 (piaware)
Tasks: 4 (limit: 1715)
CPU: 6h 1min 4.793s
CGroup: /system.slice/piaware.service
├─ 738 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
├─ 7181 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost>
└─14262 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 43.350 --lon -79.767

Nov 16 11:35:36 adsbx piaware[738]: 3853020 msgs recv’d from readsb (1723 in last 5m); 3852481 msgs sent to FlightAware
Nov 16 11:40:36 adsbx piaware[738]: 3854779 msgs recv’d from readsb (1759 in last 5m); 3854240 msgs sent to FlightAware
Nov 16 11:45:36 adsbx piaware[738]: 3856660 msgs recv’d from readsb (1881 in last 5m); 3856121 msgs sent to FlightAware
Nov 16 11:49:04 adsbx piaware[738]: mlat-client(7181): Receiver status: connected
Nov 16 11:49:04 adsbx piaware[738]: mlat-client(7181): Server status: synchronized with 305 nearby receivers
Nov 16 11:49:04 adsbx piaware[738]: mlat-client(7181): Receiver: 546.8 msg/s received 201.8 msg/s processed (37%)
Nov 16 11:49:04 adsbx piaware[738]: mlat-client(7181): Server: 0.0 kB/s from server 0.0kB/s TCP to server 2.4kB/s UDP to server
Nov 16 11:49:04 adsbx piaware[738]: mlat-client(7181): Aircraft: 5 of 14 Mode S, 56 of 77 ADS-B used
Nov 16 11:50:36 adsbx piaware[738]: 3858465 msgs recv’d from readsb (1805 in last 5m); 3857926 msgs sent to FlightAware
Nov 16 11:55:36 adsbx piaware[738]: 3860241 msgs recv’d from readsb (1776 in last 5m); 3859702 msgs sent to FlightAware

2

I see that you have 2 sites.
Site 13328 has stopped feeding.
Site 153066 started feeding at the time 13328 stopped.
Did you rebuild the feeder?

1 Like
3

ah yes, finger check on my part. I had the test feeder-id. thanks!

1 Like
4

Interestingly I had the wrong feederID in the config file for more than a week, but last night something caused the piaware service to reconnect to FA. It picked up the wrong feederID at that time and the problems started. The Pi didn’t reboot. It just lost the connection to FA and tried to reconnect repeatedly without success. Then at some point it restarted the piaware service, and connected successfully but with the wrong feederID. I was quite puzzled by the error since I had not touched the box for some time. It just didn’t have cause to restart the service until last night.

1 Like
5

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.