FlightAware Discussions

False "feeder offline" messages?

Hi,
In the last few days I had more often an error message that the feeder x minutes was no longer online. But the other field (arrow) says that he was online a few seconds ago. Is this a known error? In the picture the top error message says he was not online for 13 minutes and the other says he was online a few seconds ago.

Thank you
olli

1 Like

Same here, and to prove there is a connection, I open the map and it’s updating as normal.

What is your log saying when you access it using the gear icon on top right beside the “Anomalien anzeigen”?

It’s happening just as I write this. Map is updating normally, log shows that data was sent 5 minute ago, while home page says that it has been offline longer than 5 minute.

Edit: It cleared. The condition does not seem to last more than 15 minutes at a time.

Saw the same thing on my site just now too.

Reverted to “three green” in the time it took me to check the piaware log. (Which showed no problems and I was also getting MLAT results)

Maybe this is a FlightAware server issue?

I have the same issue here as well

Checked my piaware logs and found “timed out waiting for alive message from FlightAware, reconnecting…” which occurs at an indeterminate frequency but definitely causes the processes to all reconnect which will give the “red” buttons.

 Count Month-Day-Hour (CST)
     1 Feb-20-00
     3 Feb-20-07
     6 Feb-20-12
     4 Feb-20-13
     1 Feb-20-14
     1 Feb-20-15
     1 Feb-21-11
     4 Feb-21-12
     3 Feb-21-14
     2 Feb-21-15
     1 Feb-22-05
     2 Feb-22-06
     1 Feb-22-07
     1 Feb-22-13
     1 Feb-22-16
     3 Feb-22-17

Thanks for the suggestion. Just checked my log for that message.

Only found one instance - one minute after last reboot four plus days ago (which I think is expected behaviour during the piaware start sequence.)

I’ve seen a subsequent “three red” since my last post - which again cleared, but everything seems to be running OK.

Doesn’t seem to be a major issue.

Yes - the one on reboot is expected, it happens because piaware starts trying to connect before time synchronization is complete, and when time sync does complete the system clock steps forward.

Seen the same with my sites as well.

I raised an internal issue for the web team to take a look at this one.

2 Likes

Hey all, if anyone continues to come across this issue, please report it here.

What information do you want? Time and site ID? Will be on the lookout.

Site 71443 has been the repeat offender for me.

@eric1tran saw this issue again yesterday evening (my time = UTC + 11) This screen shot at 19:42:06

The condition cleared itself while I was looking at the logs. This screen shot at 19:45:45

Here is at the piaware log snippet for the period:

Feb 25 19:04:40 raspi4 piaware[654]: 1328701 msgs recv'd from dump1090-fa (523 in last 5m); 1328290 msgs sent to FlightAware
Feb 25 19:09:40 raspi4 piaware[654]: 1329133 msgs recv'd from dump1090-fa (432 in last 5m); 1328722 msgs sent to FlightAware
Feb 25 19:14:40 raspi4 piaware[654]: 1329660 msgs recv'd from dump1090-fa (527 in last 5m); 1329249 msgs sent to FlightAware
Feb 25 19:18:25 raspi4 piaware[654]: mlat-client(27850): Receiver status: connected
Feb 25 19:18:25 raspi4 piaware[654]: mlat-client(27850): Server status:   synchronized with 163 nearby receivers
Feb 25 19:18:25 raspi4 piaware[654]: mlat-client(27850): Receiver:  110.7 msg/s received       67.0 msg/s processed (61%)
Feb 25 19:18:25 raspi4 piaware[654]: mlat-client(27850): Server:      0.0 kB/s from server    0.0kB/s TCP to server     1.0kB/s UDP to server
Feb 25 19:18:25 raspi4 piaware[654]: mlat-client(27850): Results:  1.9 positions/minute
Feb 25 19:18:25 raspi4 piaware[654]: mlat-client(27850): Aircraft: 2 of 2 Mode S, 15 of 16 ADS-B used
Feb 25 19:19:40 raspi4 piaware[654]: 1330078 msgs recv'd from dump1090-fa (418 in last 5m); 1329667 msgs sent to FlightAware
Feb 25 19:24:40 raspi4 piaware[654]: 1330471 msgs recv'd from dump1090-fa (393 in last 5m); 1330060 msgs sent to FlightAware
Feb 25 19:29:40 raspi4 piaware[654]: 1330931 msgs recv'd from dump1090-fa (460 in last 5m); 1330520 msgs sent to FlightAware
Feb 25 19:33:25 raspi4 piaware[654]: mlat-client(27850): Receiver status: connected
Feb 25 19:33:25 raspi4 piaware[654]: mlat-client(27850): Server status:   synchronized with 121 nearby receivers
Feb 25 19:33:25 raspi4 piaware[654]: mlat-client(27850): Receiver:  112.9 msg/s received       65.0 msg/s processed (58%)
Feb 25 19:33:25 raspi4 piaware[654]: mlat-client(27850): Server:      0.0 kB/s from server    0.0kB/s TCP to server     1.0kB/s UDP to server
Feb 25 19:33:25 raspi4 piaware[654]: mlat-client(27850): Results:  4.7 positions/minute
Feb 25 19:33:25 raspi4 piaware[654]: mlat-client(27850): Aircraft: 1 of 1 Mode S, 13 of 13 ADS-B used
Feb 25 19:34:40 raspi4 piaware[654]: 1331317 msgs recv'd from dump1090-fa (386 in last 5m); 1330906 msgs sent to FlightAware
Feb 25 19:39:35 raspi4 piaware[654]: timed out waiting for alive message from FlightAware, reconnecting...
Feb 25 19:39:35 raspi4 piaware[654]: multilateration data no longer required, disabling mlat client
Feb 25 19:39:36 raspi4 piaware[654]: fa-mlat-client exited normally
Feb 25 19:39:36 raspi4 piaware[654]: reconnecting in 6 seconds...
Feb 25 19:39:36 raspi4 piaware[654]: mlat-client(27850): Disconnecting from localhost:30005: Lost connection to multilateration server, no need for input data
Feb 25 19:39:36 raspi4 piaware[654]: mlat-client(27850): Exiting on connection loss
Feb 25 19:39:40 raspi4 piaware[654]: 1331711 msgs recv'd from dump1090-fa (394 in last 5m); 1331294 msgs sent to FlightAware
Feb 25 19:39:42 raspi4 piaware[654]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Feb 25 19:39:57 raspi4 piaware[654]: Connection attempt with adept server at piaware.flightaware.com/1200 timed out
Feb 25 19:39:57 raspi4 piaware[654]: reconnecting in 5 seconds...
Feb 25 19:40:02 raspi4 piaware[654]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Feb 25 19:40:17 raspi4 piaware[654]: Connection attempt with adept server at piaware.flightaware.com/1200 timed out
Feb 25 19:40:17 raspi4 piaware[654]: reconnecting in 5 seconds...
Feb 25 19:40:22 raspi4 piaware[654]: Connecting to FlightAware adept server at 70.42.6.156/1200
Feb 25 19:40:24 raspi4 piaware[654]: Connection with adept server at 70.42.6.156/1200 established
Feb 25 19:40:24 raspi4 piaware[654]: TLS handshake with adept server at 70.42.6.156/1200 completed
Feb 25 19:40:24 raspi4 piaware[654]: FlightAware server certificate validated
Feb 25 19:40:24 raspi4 piaware[654]: encrypted session established with FlightAware
Feb 25 19:40:24 raspi4 sudo[31225]:  piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp --wide --all --numeric
Feb 25 19:40:24 raspi4 sudo[31225]: pam_unix(sudo:session): session opened for user root by (uid=0)
Feb 25 19:40:24 raspi4 sudo[31225]: pam_unix(sudo:session): session closed for user root
Feb 25 19:40:25 raspi4 piaware[654]: logged in to FlightAware as user JRG1956
Feb 25 19:40:25 raspi4 piaware[654]: my feeder ID is c43cc4bc-7b47-4b03-968b-568b94f4b18f
Feb 25 19:40:25 raspi4 piaware[654]: site statistics URL: https://flightaware.com/adsb/stats/user/JRG1956#stats-123363
Feb 25 19:40:25 raspi4 piaware[654]: multilateration data requested
Feb 25 19:40:25 raspi4 sudo[31231]:  piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp --wide --all --numeric
Feb 25 19:40:25 raspi4 sudo[31231]: pam_unix(sudo:session): session opened for user root by (uid=0)
Feb 25 19:40:25 raspi4 sudo[31231]: pam_unix(sudo:session): session closed for user root
Feb 25 19:40:25 raspi4 piaware[654]: 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 70.42.6.156:10310:3859518743
Feb 25 19:40:25 raspi4 piaware[654]: mlat-client(31233): fa-mlat-client 0.2.11 starting up
Feb 25 19:40:25 raspi4 piaware[654]: mlat-client(31233): Using UDP transport to 70.42.6.156 port 10310
Feb 25 19:40:25 raspi4 piaware[654]: mlat-client(31233): Listening for Beast-format results connection on port 30105
Feb 25 19:40:25 raspi4 piaware[654]: mlat-client(31233): Listening for Extended Basestation-format results connection on port 30106
Feb 25 19:40:25 raspi4 piaware[654]: mlat-client(31233): Route MTU changed to 1500
Feb 25 19:40:25 raspi4 piaware[654]: mlat-client(31233): Input connected to localhost:30005
Feb 25 19:40:25 raspi4 piaware[654]: mlat-client(31233): Input format changed to BEAST, 12MHz clock
Feb 25 19:40:26 raspi4 piaware[654]: mlat-client(31233): Beast-format results connection with ::1:30104: connection established
Feb 25 19:44:40 raspi4 piaware[654]: 1332049 msgs recv'd from dump1090-fa (338 in last 5m); 1331579 msgs sent to FlightAware
Feb 25 19:49:40 raspi4 piaware[654]: 1332408 msgs recv'd from dump1090-fa (359 in last 5m); 1331938 msgs sent to FlightAware
Feb 25 19:54:40 raspi4 piaware[654]: 1332744 msgs recv'd from dump1090-fa (336 in last 5m); 1332274 msgs sent to FlightAware
Feb 25 19:55:26 raspi4 piaware[654]: mlat-client(31233): Receiver status: connected
Feb 25 19:55:26 raspi4 piaware[654]: mlat-client(31233): Server status:   synchronized with 126 nearby receivers
Feb 25 19:55:26 raspi4 piaware[654]: mlat-client(31233): Receiver:   84.5 msg/s received       50.0 msg/s processed (59%)
Feb 25 19:55:26 raspi4 piaware[654]: mlat-client(31233): Server:      0.0 kB/s from server    0.0kB/s TCP to server     0.8kB/s UDP to server
Feb 25 19:55:26 raspi4 piaware[654]: mlat-client(31233): Aircraft: 0 of 0 Mode S, 9 of 9 ADS-B used
Feb 25 19:59:40 raspi4 piaware[654]: 1333069 msgs recv'd from dump1090-fa (325 in last 5m); 1332599 msgs sent to FlightAware
Feb 25 20:04:40 raspi4 piaware[654]: 1333358 msgs recv'd from dump1090-fa (289 in last 5m); 1332888 msgs sent to FlightAware
Feb 25 20:09:40 raspi4 piaware[654]: 1333581 msgs recv'd from dump1090-fa (223 in last 5m); 1333111 msgs sent to FlightAware
Feb 25 20:10:26 raspi4 piaware[654]: mlat-client(31233): Receiver status: connected
Feb 25 20:10:26 raspi4 piaware[654]: mlat-client(31233): Server status:   synchronized with 112 nearby receivers
Feb 25 20:10:26 raspi4 piaware[654]: mlat-client(31233): Receiver:   71.3 msg/s received       40.1 msg/s processed (56%)
Feb 25 20:10:26 raspi4 piaware[654]: mlat-client(31233): Server:      0.0 kB/s from server    0.0kB/s TCP to server     0.7kB/s UDP to server
Feb 25 20:10:26 raspi4 piaware[654]: mlat-client(31233): Aircraft: 1 of 1 Mode S, 7 of 7 ADS-B used

Looking more closely at the log, I see that I had the “timed out waiting for alive message from FlightAware, reconnecting…” message four times February 22nd (apologies to @johnb0 - I forgot to use --no-pager to see the full log before searching), and three times on Feb 25th - none since the last documented in this post.

Note that only the instances on the 25th also had the “Connection attempt with adept server at piaware.flightaware.com/1200 timed out” line(s) as well.

Of potential interest, I also saw the same issue on February 23rd, but there is nothing in the log indicating a timeout around the time of the screenshot I took.

Let me know if you want the full log or any further detail.

1 Like