Not uploading data to Flightaware but ADSB and 24 loading up OK

FlightAware ADS-B Flight Tracking
1

Hi, last week my Raspberry Pi stopped sending feed data to all 3 sites. I rebooted the Pi and noticed I’d lost the wifi so used cable. Also stopped sending the feed to Flightaware but carries on sending to ADSB exchange and Flightradar24 with no problems. did a quick check using “systemctl status piaware” in termanal and got “piaware.service: Failed with result 'signal”.
Tried reinstall of PiAware with no results. MyAdsb page shows it can see my Pi but no feed been sent.

Any help would be grateful before I do a full reformat and install from beginning

Dave

1 Like
2

some simple suggestions :slight_smile:

restart the processes/ service

Dump1090
sudo service dump1090-fa restart

Piaware
sudo service piaware restart

If it fails it wil tell you that is failed and then you get a reason supplied

2 Likes
3

Both services restarted with no indication of fail. But still not sending feed to Flightaware. I can see my feed on Localhost:8080 no problem, a bit puzzeling

Dave

1 Like
4

well lets see what the logs are telling us then.
Let’s print the last 100 lines of the piaware log. If connected to dump1090-fa it will tell us that and also if it is reporting to the server

issue the following commands

cd /var/log
tail -n 100 piaware.log

Once you have got that then copy/paste the log here so it can be examined.

1 Like
5

I’ve had a similar issue today. Piaware is feeding OK, but FlightAware stats shows zero data. I’ve been chasing this issue with 6 feeders all day. It seems to move from feeder to feeder. IMO there is some issue on the the FA end. These same 6 feeders have shown intermittant connection refused on port 30005. I slipped a new mSD into CS4 feeder to see it have simillar troubles after an hour. I’ve even changed dongles and power supplies. All 6 feeders have run without issues for many months. The logs don’t show any clues. Piaware works perfectly. FlightAware24 is failing.

1 Like
6

How did you determine that piaware is feeding OK?

7

I looked at CS4 during the period approx 29 hours ago when it was transmitting no data per the site stats. We received no data, stats are correct. Piaware log messages show that there was nothing listening on port 30005 (as you mentioned above) and piaware’s attempts to restart dump1090 did not change this. So for that specific case it’s a feeder-side problem, you need to investigate what went wrong with dump1090.

8

Later in the day, the issue self-corrected. Other than Windows, I’m not much of a tech because I do not know how the RPi OS and apps such as dump1090 work or how to interpret their logs. My plan is to replace the 10 year old SD cards.

9

@tomvdhorst Here is my PiAware log.
It looks like a buffer overload, not sure what is causing it.

@obj sorry got mixed up, I can see that on the stats page when you float over the red PiAware box it sees that my Pi is running, also I thought if I view live data on Localhost it would be feeding.

Oct 29 12:21:55 PiAware piaware[1882]: creating pidfile /run/piaware/piaware.pid
Oct 29 12:21:55 PiAware piaware[1882]: ****************************************************
Oct 29 12:21:55 PiAware piaware[1882]: piaware version 7.2 is running, process ID 1882
Oct 29 12:21:55 PiAware piaware[1882]: your system info is: Linux PiAware 5.15.74-v7+ #1595 SMP Wed Oct 26 11:03:05 BST 2022 armv7l GNU/Linux
Oct 29 12:21:55 PiAware piaware[1882]: *** buffer overflow detected ***: /usr/bin/piaware terminated
Oct 29 12:22:26 PiAware piaware[1961]: creating pidfile /run/piaware/piaware.pid
Oct 29 12:22:26 PiAware piaware[1961]: ****************************************************
Oct 29 12:22:26 PiAware piaware[1961]: piaware version 7.2 is running, process ID 1961
Oct 29 12:22:26 PiAware piaware[1961]: your system info is: Linux PiAware 5.15.74-v7+ #1595 SMP Wed Oct 26 11:03:05 BST 2022 armv7l GNU/Linux
Oct 29 12:22:26 PiAware piaware[1961]: *** buffer overflow detected ***: /usr/bin/piaware terminated
Oct 29 12:22:56 PiAware piaware[2204]: creating pidfile /run/piaware/piaware.pid
Oct 29 12:22:56 PiAware piaware[2204]: ****************************************************
Oct 29 12:22:56 PiAware piaware[2204]: piaware version 7.2 is running, process ID 2204
Oct 29 12:22:56 PiAware piaware[2204]: your system info is: Linux PiAware 5.15.74-v7+ #1595 SMP Wed Oct 26 11:03:05 BST 2022 armv7l GNU/Linux
Oct 29 12:22:56 PiAware piaware[2204]: *** buffer overflow detected ***: /usr/bin/piaware terminated
Oct 29 12:23:27 PiAware piaware[2271]: creating pidfile /run/piaware/piaware.pid
Oct 29 12:23:27 PiAware piaware[2271]: ****************************************************
Oct 29 12:23:27 PiAware piaware[2271]: piaware version 7.2 is running, process ID 2271
Oct 29 12:23:27 PiAware piaware[2271]: your system info is: Linux PiAware 5.15.74-v7+ #1595 SMP Wed Oct 26 11:03:05 BST 2022 armv7l GNU/Linux
Oct 29 12:23:27 PiAware piaware[2271]: *** buffer overflow detected ***: /usr/bin/piaware terminated
Oct 29 12:23:57 PiAware piaware[2503]: creating pidfile /run/piaware/piaware.pid
Oct 29 12:23:57 PiAware piaware[2503]: ****************************************************
Oct 29 12:23:57 PiAware piaware[2503]: piaware version 7.2 is running, process ID 2503
Oct 29 12:23:57 PiAware piaware[2503]: your system info is: Linux PiAware 5.15.74-v7+ #1595 SMP Wed Oct 26 11:03:05 BST 2022 armv7l GNU/Linux
Oct 29 12:23:57 PiAware piaware[2503]: *** buffer overflow detected ***: /usr/bin/piaware terminated
Oct 29 12:24:28 PiAware piaware[2566]: creating pidfile /run/piaware/piaware.pid
Oct 29 12:24:28 PiAware piaware[2566]: ****************************************************
Oct 29 12:24:28 PiAware piaware[2566]: piaware version 7.2 is running, process ID 2566
Oct 29 12:24:28 PiAware piaware[2566]: your system info is: Linux PiAware 5.15.74-v7+ #1595 SMP Wed Oct 26 11:03:05 BST 2022 armv7l GNU/Linux
Oct 29 12:24:28 PiAware piaware[2566]: *** buffer overflow detected ***: /usr/bin/piaware terminated
Oct 29 12:24:58 PiAware piaware[2805]: creating pidfile /run/piaware/piaware.pid
Oct 29 12:24:58 PiAware piaware[2805]: ****************************************************
Oct 29 12:24:58 PiAware piaware[2805]: piaware version 7.2 is running, process ID 2805
Oct 29 12:24:58 PiAware piaware[2805]: your system info is: Linux PiAware 5.15.74-v7+ #1595 SMP Wed Oct 26 11:03:05 BST 2022 armv7l GNU/Linux
Oct 29 12:24:58 PiAware piaware[2805]: *** buffer overflow detected ***: /usr/bin/piaware terminated
Oct 29 12:25:29 PiAware piaware[2871]: creating pidfile /run/piaware/piaware.pid
Oct 29 12:25:29 PiAware piaware[2871]: ****************************************************
Oct 29 12:25:29 PiAware piaware[2871]: piaware version 7.2 is running, process ID 2871
Oct 29 12:25:29 PiAware piaware[2871]: your system info is: Linux PiAware 5.15.74-v7+ #1595 SMP Wed Oct 26 11:03:05 BST 2022 armv7l GNU/Linux
Oct 29 12:25:29 PiAware piaware[2871]: *** buffer overflow detected ***: /usr/bin/piaware terminated
Oct 29 12:26:00 PiAware piaware[3118]: creating pidfile /run/piaware/piaware.pid
Oct 29 12:26:00 PiAware piaware[3118]: ****************************************************
Oct 29 12:26:00 PiAware piaware[3118]: piaware version 7.2 is running, process ID 3118
Oct 29 12:26:00 PiAware piaware[3118]: your system info is: Linux PiAware 5.15.74-v7+ #1595 SMP Wed Oct 26 11:03:05 BST 2022 armv7l GNU/Linux
Oct 29 12:26:00 PiAware piaware[3118]: *** buffer overflow detected ***: /usr/bin/piaware terminated
Oct 29 12:26:31 PiAware piaware[3181]: creating pidfile /run/piaware/piaware.pid
Oct 29 12:26:31 PiAware piaware[3181]: ****************************************************
Oct 29 12:26:31 PiAware piaware[3181]: piaware version 7.2 is running, process ID 3181
Oct 29 12:26:31 PiAware piaware[3181]: your system info is: Linux PiAware 5.15.74-v7+ #1595 SMP Wed Oct 26 11:03:05 BST 2022 armv7l GNU/Linux
Oct 29 12:26:31 PiAware piaware[3181]: *** buffer overflow detected ***: /usr/bin/piaware terminated
Oct 29 12:27:01 PiAware piaware[3409]: creating pidfile /run/piaware/piaware.pid
Oct 29 12:27:01 PiAware piaware[3409]: ****************************************************
Oct 29 12:27:01 PiAware piaware[3409]: piaware version 7.2 is running, process ID 3409
Oct 29 12:27:01 PiAware piaware[3409]: your system info is: Linux PiAware 5.15.74-v7+ #1595 SMP Wed Oct 26 11:03:05 BST 2022 armv7l GNU/Linux
Oct 29 12:27:01 PiAware piaware[3409]: *** buffer overflow detected ***: /usr/bin/piaware terminated
Oct 29 12:27:32 PiAware piaware[3471]: creating pidfile /run/piaware/piaware.pid
Oct 29 12:27:32 PiAware piaware[3471]: ****************************************************
Oct 29 12:27:32 PiAware piaware[3471]: piaware version 7.2 is running, process ID 3471
Oct 29 12:27:32 PiAware piaware[3471]: your system info is: Linux PiAware 5.15.74-v7+ #1595 SMP Wed Oct 26 11:03:05 BST 2022 armv7l GNU/Linux
Oct 29 12:27:32 PiAware piaware[3471]: *** buffer overflow detected ***: /usr/bin/piaware terminated
Oct 29 12:28:03 PiAware piaware[3716]: creating pidfile /run/piaware/piaware.pid
Oct 29 12:28:03 PiAware piaware[3716]: ****************************************************
Oct 29 12:28:03 PiAware piaware[3716]: piaware version 7.2 is running, process ID 3716
Oct 29 12:28:03 PiAware piaware[3716]: your system info is: Linux PiAware 5.15.74-v7+ #1595 SMP Wed Oct 26 11:03:05 BST 2022 armv7l GNU/Linux
Oct 29 12:28:03 PiAware piaware[3716]: *** buffer overflow detected ***: /usr/bin/piaware terminated
Oct 29 12:28:33 PiAware piaware[3790]: creating pidfile /run/piaware/piaware.pid
Oct 29 12:28:33 PiAware piaware[3790]: ****************************************************
Oct 29 12:28:33 PiAware piaware[3790]: piaware version 7.2 is running, process ID 3790
Oct 29 12:28:33 PiAware piaware[3790]: your system info is: Linux PiAware 5.15.74-v7+ #1595 SMP Wed Oct 26 11:03:05 BST 2022 armv7l GNU/Linux
Oct 29 12:28:33 PiAware piaware[3790]: *** buffer overflow detected ***: /usr/bin/piaware terminated
Oct 29 12:29:04 PiAware piaware[4029]: creating pidfile /run/piaware/piaware.pid
Oct 29 12:29:04 PiAware piaware[4029]: ****************************************************
Oct 29 12:29:04 PiAware piaware[4029]: piaware version 7.2 is running, process ID 4029
Oct 29 12:29:04 PiAware piaware[4029]: your system info is: Linux PiAware 5.15.74-v7+ #1595 SMP Wed Oct 26 11:03:05 BST 2022 armv7l GNU/Linux
Oct 29 12:29:04 PiAware piaware[4029]: *** buffer overflow detected ***: /usr/bin/piaware terminated
Oct 29 12:29:35 PiAware piaware[4113]: creating pidfile /run/piaware/piaware.pid
Oct 29 12:29:35 PiAware piaware[4113]: ****************************************************
Oct 29 12:29:35 PiAware piaware[4113]: piaware version 7.2 is running, process ID 4113
Oct 29 12:29:35 PiAware piaware[4113]: your system info is: Linux PiAware 5.15.74-v7+ #1595 SMP Wed Oct 26 11:03:05 BST 2022 armv7l GNU/Linux
Oct 29 12:29:35 PiAware piaware[4113]: *** buffer overflow detected ***: /usr/bin/piaware terminated
Oct 29 12:30:05 PiAware piaware[4342]: creating pidfile /run/piaware/piaware.pid
Oct 29 12:30:05 PiAware piaware[4342]: ****************************************************
Oct 29 12:30:05 PiAware piaware[4342]: piaware version 7.2 is running, process ID 4342
Oct 29 12:30:05 PiAware piaware[4342]: your system info is: Linux PiAware 5.15.74-v7+ #1595 SMP Wed Oct 26 11:03:05 BST 2022 armv7l GNU/Linux
Oct 29 12:30:05 PiAware piaware[4342]: *** buffer overflow detected ***: /usr/bin/piaware terminated
Oct 29 12:30:36 PiAware piaware[4469]: creating pidfile /run/piaware/piaware.pid
Oct 29 12:30:36 PiAware piaware[4469]: ****************************************************
Oct 29 12:30:36 PiAware piaware[4469]: piaware version 7.2 is running, process ID 4469
Oct 29 12:30:36 PiAware piaware[4469]: your system info is: Linux PiAware 5.15.74-v7+ #1595 SMP Wed Oct 26 11:03:05 BST 2022 armv7l GNU/Linux
Oct 29 12:30:36 PiAware piaware[4469]: *** buffer overflow detected ***: /usr/bin/piaware terminated
Oct 29 12:31:07 PiAware piaware[4646]: creating pidfile /run/piaware/piaware.pid
Oct 29 12:31:07 PiAware piaware[4646]: ****************************************************
Oct 29 12:31:07 PiAware piaware[4646]: piaware version 7.2 is running, process ID 4646
Oct 29 12:31:07 PiAware piaware[4646]: your system info is: Linux PiAware 5.15.74-v7+ #1595 SMP Wed Oct 26 11:03:05 BST 2022 armv7l GNU/Linux
Oct 29 12:31:07 PiAware piaware[4646]: *** buffer overflow detected ***: /usr/bin/piaware terminated
Oct 29 12:31:37 PiAware piaware[4770]: creating pidfile /run/piaware/piaware.pid
Oct 29 12:31:37 PiAware piaware[4770]: ****************************************************
Oct 29 12:31:37 PiAware piaware[4770]: piaware version 7.2 is running, process ID 4770
Oct 29 12:31:37 PiAware piaware[4770]: your system info is: Linux PiAware 5.15.74-v7+ #1595 SMP Wed Oct 26 11:03:05 BST 2022 armv7l GNU/Linux
Oct 29 12:31:37 PiAware piaware[4770]: *** buffer overflow detected ***: /usr/bin/piaware terminated
pi@PiAware:/var/log $

10

Interesting, I had a similar issue yesterday as well with one of my sites. Just in the fwiw and if it helps department.

During the course of the morning, I looked at my stats page to see how the the day was progressing, to find that it was reported that my 1090 feeder (Site: 183579) hadn’t reported in three hours. My 978 feeder (Site: 184474) was reporting fine during the same timeframe, and shares the same internet connectivity. (My first hunch)

I did look at piaware.log (shown below) and syslog, but there isn’t any entries during this time (11:19-14:14 EST).

Graphs1090 showed I was still seeing AC messages:

MessageRate
MessageRate1258×327 52.6 KB

and my bandwidth charts showed continuous activity:
BandwidthUsage

but clearily something wasn’t working properly during this time:
HourlyReports

Unfortunately, I didn’t check the health of dump1090 in the moment, or do any further troubleshooting, as I was in the middle of my work day… I just rebooted the box at 14:14.

Oct 28 10:30:39 ThinAware piaware[522]: mlat-client(1363233): Receiver status: connected
Oct 28 10:30:39 ThinAware piaware[522]: mlat-client(1363233): Server status:   synchronized with 527 nearby receivers
Oct 28 10:30:39 ThinAware piaware[522]: mlat-client(1363233): Receiver: 2045.4 msg/s received      586.7 msg/s processed (29%)
Oct 28 10:30:39 ThinAware piaware[522]: mlat-client(1363233): Server:      0.1 kB/s from server    0.1kB/s TCP to server     4.4kB/s UDP to server
Oct 28 10:30:39 ThinAware piaware[522]: mlat-client(1363233): Results:  30.9 positions/minute
Oct 28 10:30:39 ThinAware piaware[522]: mlat-client(1363233): Aircraft: 37 of 49 Mode S, 113 of 276 ADS-B used
Oct 28 10:33:39 ThinAware piaware[522]: 5712906 msgs recv'd from dump1090-fa (6869 in last 5m); 5712704 msgs sent to FlightAware
Oct 28 10:37:55 ThinAware piaware[522]: mlat-client(1363233): Route MTU changed to 1500
Oct 28 10:38:07 ThinAware piaware[522]: mlat-client(1363233): Route MTU changed to 1476
Oct 28 10:38:39 ThinAware piaware[522]: 5719771 msgs recv'd from dump1090-fa (6865 in last 5m); 5719569 msgs sent to FlightAware
Oct 28 10:43:39 ThinAware piaware[522]: 5726771 msgs recv'd from dump1090-fa (7000 in last 5m); 5726569 msgs sent to FlightAware
Oct 28 10:45:39 ThinAware piaware[522]: mlat-client(1363233): Receiver status: connected
Oct 28 10:45:39 ThinAware piaware[522]: mlat-client(1363233): Server status:   synchronized with 520 nearby receivers
Oct 28 10:45:39 ThinAware piaware[522]: mlat-client(1363233): Receiver: 2068.6 msg/s received      601.0 msg/s processed (29%)
Oct 28 10:45:39 ThinAware piaware[522]: mlat-client(1363233): Server:      0.1 kB/s from server    0.1kB/s TCP to server     4.7kB/s UDP to server
Oct 28 10:45:39 ThinAware piaware[522]: mlat-client(1363233): Results:  26.0 positions/minute
Oct 28 10:45:39 ThinAware piaware[522]: mlat-client(1363233): Aircraft: 25 of 43 Mode S, 120 of 262 ADS-B used
Oct 28 10:48:39 ThinAware piaware[522]: 5733883 msgs recv'd from dump1090-fa (7112 in last 5m); 5733681 msgs sent to FlightAware
Oct 28 10:53:39 ThinAware piaware[522]: 5741006 msgs recv'd from dump1090-fa (7123 in last 5m); 5740804 msgs sent to FlightAware
Oct 28 10:58:09 ThinAware piaware[522]: mlat-client(1363233): Route MTU changed to 1500
Oct 28 10:58:23 ThinAware piaware[522]: mlat-client(1363233): Route MTU changed to 1476
Oct 28 10:58:32 ThinAware piaware[522]: Lost connection to adept server at piaware.flightaware.com/1200: server closed connection
Oct 28 10:58:32 ThinAware piaware[522]: multilateration data no longer required, disabling mlat client
Oct 28 10:58:33 ThinAware piaware[522]: fa-mlat-client exited normally
Oct 28 10:58:33 ThinAware piaware[522]: reconnecting in 5 seconds...
Oct 28 10:58:33 ThinAware piaware[522]: mlat-client(1363233): Disconnecting from localhost:30005: Lost connection to multilateration server, no need for input data
Oct 28 10:58:33 ThinAware piaware[522]: mlat-client(1363233): Exiting on connection loss
Oct 28 10:58:38 ThinAware piaware[522]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Oct 28 10:58:39 ThinAware piaware[522]: 5748413 msgs recv'd from dump1090-fa (7407 in last 5m); 5748057 msgs sent to FlightAware
Oct 28 10:58:39 ThinAware piaware[522]: Connection with adept server at piaware.flightaware.com/1200 established
Oct 28 10:58:39 ThinAware piaware[522]: TLS handshake with adept server at piaware.flightaware.com/1200 completed
Oct 28 10:58:39 ThinAware piaware[522]: FlightAware server certificate validated
Oct 28 10:58:39 ThinAware piaware[522]: encrypted session established with FlightAware
Oct 28 10:58:40 ThinAware piaware[522]: logged in to FlightAware as user cnuwer
Oct 28 10:58:40 ThinAware piaware[522]: my feeder ID is xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Oct 28 10:58:40 ThinAware piaware[522]: site statistics URL: https://flightaware.com/adsb/stats/user/cnuwer#stats-183579
Oct 28 10:58:40 ThinAware piaware[522]: multilateration data requested
Oct 28 10:58:40 ThinAware piaware[522]: Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --results beast,listen,30105 --results ext_basestation,listen,30106 --udp-transport 2620:13d:c000:11::198:19649:3601478145
Oct 28 10:58:40 ThinAware piaware[522]: mlat-client(1829149): fa-mlat-client 0.2.12 starting up
Oct 28 10:58:40 ThinAware piaware[522]: mlat-client(1829149): Using UDP transport to 2620:13d:c000:11::198 port 19649
Oct 28 10:58:40 ThinAware piaware[522]: mlat-client(1829149): Listening for Beast-format results connection on port 30105
Oct 28 10:58:40 ThinAware piaware[522]: mlat-client(1829149): Listening for Extended Basestation-format results connection on port 30106
Oct 28 10:58:40 ThinAware piaware[522]: mlat-client(1829149): Route MTU changed to 1500
Oct 28 10:58:40 ThinAware piaware[522]: mlat-client(1829149): Input connected to localhost:30005
Oct 28 10:58:40 ThinAware piaware[522]: mlat-client(1829149): Input format changed to BEAST, 12MHz clock
Oct 28 10:58:41 ThinAware piaware[522]: mlat-client(1829149): Beast-format results connection with ::1:30104: connection established
Oct 28 10:58:56 ThinAware piaware[522]: mlat-client(1829149): Route MTU changed to 1476
Oct 28 11:03:39 ThinAware piaware[522]: 5756193 msgs recv'd from dump1090-fa (7780 in last 5m); 5755818 msgs sent to FlightAware
Oct 28 11:08:39 ThinAware piaware[522]: 5764031 msgs recv'd from dump1090-fa (7838 in last 5m); 5763656 msgs sent to FlightAware
Oct 28 11:13:39 ThinAware piaware[522]: 5771449 msgs recv'd from dump1090-fa (7418 in last 5m); 5771074 msgs sent to FlightAware
Oct 28 11:13:41 ThinAware piaware[522]: mlat-client(1829149): Receiver status: connected
Oct 28 11:13:41 ThinAware piaware[522]: mlat-client(1829149): Server status:   synchronized with 528 nearby receivers
Oct 28 11:13:41 ThinAware piaware[522]: mlat-client(1829149): Receiver: 1975.0 msg/s received      598.0 msg/s processed (30%)
Oct 28 11:13:41 ThinAware piaware[522]: mlat-client(1829149): Server:      0.1 kB/s from server    0.1kB/s TCP to server     4.4kB/s UDP to server
Oct 28 11:13:41 ThinAware piaware[522]: mlat-client(1829149): Results:  43.6 positions/minute
Oct 28 11:13:41 ThinAware piaware[522]: mlat-client(1829149): Aircraft: 30 of 46 Mode S, 111 of 275 ADS-B used
Oct 28 11:18:39 ThinAware piaware[522]: 5778436 msgs recv'd from dump1090-fa (6987 in last 5m); 5778061 msgs sent to FlightAware
Oct 28 11:18:45 ThinAware piaware[522]: mlat-client(1829149): Route MTU changed to 1500
Oct 28 11:19:12 ThinAware piaware[522]: mlat-client(1829149): Route MTU changed to 1476
Oct 28 11:19:16 ThinAware piaware[522]: Lost connection to adept server at piaware.flightaware.com/1200: server closed connection
Oct 28 14:14:33 ThinAware piaware[513]: creating pidfile /run/piaware/piaware.pid
Oct 28 14:14:33 ThinAware piaware[513]: ****************************************************
Oct 28 14:14:33 ThinAware piaware[513]: piaware version 7.2 is running, process ID 513
Oct 28 14:14:33 ThinAware piaware[513]: your system info is: Linux ThinAware 5.10.0-19-amd64 #1 SMP Debian 5.10.149-2 (2022-10-21) x86_64 GNU/Linux
Oct 28 14:14:34 ThinAware piaware[513]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Oct 28 14:14:34 ThinAware piaware[513]: Connection to adept server at piaware.flightaware.com/1200 failed: couldn't open socket: Temporary failure in name resolution
Oct 28 14:14:34 ThinAware piaware[513]: reconnecting in 5 seconds...
Oct 28 14:14:36 ThinAware piaware[513]: ADS-B data program 'dump1090-fa' is listening on port 30005, so far so good
Oct 28 14:14:36 ThinAware piaware[513]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 39.16x --lon -78.15x
Oct 28 14:14:36 ThinAware piaware[513]: Started faup1090 (pid 664) to connect to dump1090-fa
Oct 28 14:14:36 ThinAware piaware[513]: UAT support disabled by local configuration setting: uat-receiver-type
Oct 28 14:14:39 ThinAware piaware[513]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Oct 28 14:14:40 ThinAware piaware[513]: Connection with adept server at piaware.flightaware.com/1200 established
Oct 28 14:14:40 ThinAware piaware[513]: TLS handshake with adept server at piaware.flightaware.com/1200 completed
Oct 28 14:14:40 ThinAware piaware[513]: FlightAware server certificate validated
Oct 28 14:14:40 ThinAware piaware[513]: encrypted session established with FlightAware
Oct 28 14:14:40 ThinAware piaware[513]: adept reported location: 39.16xxx, -78.15xxx, 746ft AMSL
Oct 28 14:14:40 ThinAware piaware[513]: logged in to FlightAware as user cnuwer
Oct 28 14:14:40 ThinAware piaware[513]: my feeder ID is xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Oct 28 14:14:40 ThinAware piaware[513]: site statistics URL: https://flightaware.com/adsb/stats/user/cnuwer#stats-183579
Oct 28 14:14:40 ThinAware piaware[513]: multilateration data requested
Oct 28 14:14:40 ThinAware piaware[513]: Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --results beast,listen,30105 --results ext_basestation,listen,30106 --udp-transport 2620:13d:c000:11::201:9012:1627360442
Oct 28 14:14:41 ThinAware piaware[513]: mlat-client(784): fa-mlat-client 0.2.12 starting up
Oct 28 14:14:41 ThinAware piaware[513]: mlat-client(784): Using UDP transport to 2620:13d:c000:11::201 port 9012
Oct 28 14:14:41 ThinAware piaware[513]: mlat-client(784): Listening for Beast-format results connection on port 30105
Oct 28 14:14:41 ThinAware piaware[513]: mlat-client(784): Listening for Extended Basestation-format results connection on port 30106
Oct 28 14:14:41 ThinAware piaware[513]: mlat-client(784): Route MTU changed to 1500
Oct 28 14:14:41 ThinAware piaware[513]: mlat-client(784): Input connected to localhost:30005
Oct 28 14:14:41 ThinAware piaware[513]: mlat-client(784): Input format changed to BEAST, 12MHz clock
Oct 28 14:14:42 ThinAware piaware[513]: mlat-client(784): Beast-format results connection with ::1:30104: connection established
Oct 28 14:14:45 ThinAware piaware[513]: piaware received a message from dump1090-fa!
Oct 28 14:14:45 ThinAware piaware[513]: piaware has successfully sent several msgs to FlightAware!
Oct 28 14:15:00 ThinAware piaware[513]: mlat-client(784): Route MTU changed to 1476
Oct 28 14:15:07 ThinAware piaware[513]: 997 msgs recv'd from dump1090-fa; 997 msgs sent to FlightAware
Oct 28 14:20:07 ThinAware piaware[513]: 7443 msgs recv'd from dump1090-fa (6446 in last 5m); 7443 msgs sent to FlightAware
Oct 28 14:25:07 ThinAware piaware[513]: 13910 msgs recv'd from dump1090-fa (6467 in last 5m); 13910 msgs sent to FlightAware
Oct 28 14:29:41 ThinAware piaware[513]: mlat-client(784): Receiver status: connected
Oct 28 14:29:41 ThinAware piaware[513]: mlat-client(784): Server status:   synchronized with 518 nearby receivers
Oct 28 14:29:41 ThinAware piaware[513]: mlat-client(784): Receiver: 1935.1 msg/s received      567.0 msg/s processed (29%)
Oct 28 14:29:41 ThinAware piaware[513]: mlat-client(784): Server:      0.0 kB/s from server    0.1kB/s TCP to server     4.3kB/s UDP to server
Oct 28 14:29:41 ThinAware piaware[513]: mlat-client(784): Results:  7.0 positions/minute
Oct 28 14:29:41 ThinAware piaware[513]: mlat-client(784): Aircraft: 26 of 46 Mode S, 100 of 241 ADS-B used
Oct 28 14:30:07 ThinAware piaware[513]: 20403 msgs recv'd from dump1090-fa (6493 in last 5m); 20403 msgs sent to FlightAware
Oct 28 14:35:07 ThinAware piaware[513]: 26467 msgs recv'd from dump1090-fa (6064 in last 5m); 26467 msgs sent to FlightAware
Oct 28 14:40:07 ThinAware piaware[513]: 33014 msgs recv'd from dump1090-fa (6547 in last 5m); 33014 msgs sent to FlightAware
11

This is usually caused by a tcl ipv6 problem: buffer overflow when IPv6 gets disabled · Issue #51 · flightaware/piaware · GitHub

12

This is likely to be a tcl-tls bug that makes piaware intermittently hang. piaware 8.0 will have a workaround for this.

1 Like
13

As a workaround, remove the IPv6 entry for localhost in /etc/hosts.

This is causing the buffer overflow.

1 Like
15

Thank-you very much for the insight here @obj It takes the mystery out of it for me and I’ll be on the lookout for v8 as time progresses!

17

@tomvdhorst Thanks this worked a treat. All back to normal now.

Dave

1 Like
18

I noticed the same data loss to Flightaware after disabling ipv6 on my R-Pi.
Locally, everything was running fine, but I later got an email from Flightaware that I wasn’t feeding?!
Thank goodness for the email otherwise I might have lost my 7 year streak.

It’s simple to replicate the ‘problem’ - just add “ipv6.disable=1” to the end of /boot/cmdline.txt and reboot.

Good to see Flightaware are on top of it and will have a fix in due course.

Nigel.

19

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