Log View in Profile stopped displaying latest entries

FlightAware ADS-B Flight Tracking
1

Hi all,

i’ve noticed that morning that the log shown in my receiver profile differ from the log on my device itself.

The log stopped reporting in the window at 10:18 while the profile says “a few seconds ago”.
Checking the log on my device itself, it is updated.

EDIT:
Looking at the profile log, it’s 10:27. So approx 35 Minutes behind reality.
See below the two different windows. For the second window it’s UTC so screenshot was taken at 10:58 while the profile log stopped at 10:!8

Anyone else with that issue? Pressing the refresh button does not change it.

image
image1215×465 160 KB

EDIT: The log in profile is updating, now showing 10:28, so it is approx. 35 minutes behind reality

2

It seem to be working again. Did you change something?

Below you can see the gap of 45 minutes:

[2021-09-23 11:59 CEST] mlat-client(18431): Route MTU changed to 1492
[2021-09-23 12:00 CEST] mlat-client(18431): Route MTU changed to 1476
[2021-09-23 12:03 CEST] 179174 msgs recv'd from rcd (1550 in last 5m); 179173 msgs sent to FlightAware
[2021-09-23 12:48 CEST] 194345 msgs recv'd from rcd (1955 in last 5m); 194344 msgs sent to FlightAware

EDIT:

Problem is back This is the log in profile from now (18:06)

[2021-09-23 17:36 CEST] mlat-client(11273): Server status: synchronized with 577 nearby receivers
[2021-09-23 17:37 CEST] 50408 msgs recv'd from rcd (1546 in last 5m); 50407 msgs sent to FlightAware
[2021-09-23 17:40 CEST] mlat-client(11273): Route MTU changed to 1492
[2021-09-23 17:41 CEST] mlat-client(11273): Route MTU changed to 1476
[2021-09-23 17:42 CEST] 51901 msgs recv'd from rcd (1493 in last 5m); 51900 msgs sent to FlightAware
3

Any update on this?

The issue still persist after 12 hours waiting time

4

Seeing a similar discrepency here on some of my receivers

Currently 1946 EAST (local Australian Eastern Standard time)

0946 UTC

Site number 25403

Sep 24 09:36:00 Pi1 piaware[7875]: 1002245 msgs recv'd from dump1090-fa (169 in last 5m); 998416 msgs sent to FlightAware
Sep 24 09:40:25 Pi1 piaware[7875]: mlat-client(28154): Receiver status: connected
Sep 24 09:40:25 Pi1 piaware[7875]: mlat-client(28154): Server status:   synchronized with 93 nearby receivers
Sep 24 09:40:25 Pi1 piaware[7875]: mlat-client(28154): Receiver:   23.6 msg/s received       15.1 msg/s processed (64%)
Sep 24 09:40:25 Pi1 piaware[7875]: mlat-client(28154): Server:      0.0 kB/s from server    0.0kB/s TCP to server     0.2kB/s UDP to server
Sep 24 09:40:25 Pi1 piaware[7875]: mlat-client(28154): Results:  8.1 positions/minute
Sep 24 09:40:25 Pi1 piaware[7875]: mlat-client(28154): Aircraft: 1 of 2 Mode S, 5 of 5 ADS-B used
Sep 24 09:41:00 Pi1 piaware[7875]: 1002447 msgs recv'd from dump1090-fa (202 in last 5m); 998618 msgs sent to FlightAware
Sep 24 09:46:00 Pi1 piaware[7875]: 1002725 msgs recv'd from dump1090-fa (278 in last 5m); 998896 msgs sent to FlightAware
Sep 24 09:51:00 Pi1 piaware[7875]: 1002941 msgs recv'd from dump1090-fa (216 in last 5m); 999112 msgs sent to FlightAware

and from the Stats page for the same receiver

[2021-09-24 17:55 AEST] mlat-client(28154): Server status: synchronized with 132 nearby receivers
[2021-09-24 17:55 AEST] mlat-client(28154): Aircraft: 1 of 1 Mode S, 6 of 6 ADS-B used
[2021-09-24 17:55 AEST] mlat-client(28154): Receiver: 17.9 msg/s received 11.0 msg/s processed (61%)
[2021-09-24 17:55 AEST] mlat-client(28154): Receiver status: connected
[2021-09-24 17:55 AEST] 998717 msgs recv'd from dump1090-fa (148 in last 5m); 994888 msgs sent to FlightAware
[2021-09-24 18:00 AEST] 998913 msgs recv'd from dump1090-fa (196 in last 5m); 995084 msgs sent to FlightAware
[2021-09-24 18:10 AEST] mlat-client(28154): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.3kB/s UDP to server
[2021-09-24 18:10 AEST] mlat-client(28154): Aircraft: 2 of 2 Mode S, 5 of 6 ADS-B used
[2021-09-24 18:10 AEST] mlat-client(28154): Receiver status: connected
[2021-09-24 18:21 AEST] 999909 msgs recv'd from dump1090-fa (281 in last 5m); 996080 msgs sent to FlightAware
[2021-09-24 18:25 AEST] mlat-client(28154): Aircraft: 1 of 1 Mode S, 3 of 3 ADS-B used
[2021-09-24 18:25 AEST] mlat-client(28154): Receiver: 21.5 msg/s received 13.1 msg/s processed (61%)
[2021-09-24 18:25 AEST] mlat-client(28154): Server status: synchronized with 101 nearby receivers
[2021-09-24 18:25 AEST] mlat-client(28154): Receiver status: connected
[2021-09-24 18:26 AEST] 1000077 msgs recv'd from dump1090-fa (168 in last 5m); 996248 msgs sent to FlightAware
[2021-09-24 18:31 AEST] 1000160 msgs recv'd from dump1090-fa (83 in last 5m); 996331 msgs sent to FlightAware
[2021-09-24 18:36 AEST] 1000251 msgs recv'd from dump1090-fa (91 in last 5m); 996422 msgs sent to FlightAware
[2021-09-24 18:40 AEST] mlat-client(28154): Receiver: 8.2 msg/s received 5.2 msg/s processed (64%)
[2021-09-24 18:40 AEST] mlat-client(28154): Aircraft: 0 of 0 Mode S, 3 of 3 ADS-B used
[2021-09-24 18:40 AEST] mlat-client(28154): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.1kB/s UDP to server
[2021-09-24 18:46 AEST] 1000491 msgs recv'd from dump1090-fa (131 in last 5m); 996662 msgs sent to FlightAware
[2021-09-24 18:51 AEST] 1000629 msgs recv'd from dump1090-fa (138 in last 5m); 996800 msgs sent to FlightAware
[2021-09-24 18:55 AEST] mlat-client(28154): Receiver status: connected
[2021-09-24 18:55 AEST] mlat-client(28154): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.2kB/s UDP to server
[2021-09-24 18:55 AEST] mlat-client(28154): Aircraft: 0 of 0 Mode S, 4 of 4 ADS-B used
[2021-09-24 18:55 AEST] mlat-client(28154): Server status: synchronized with 117 nearby receivers
[2021-09-24 18:56 AEST] 1000781 msgs recv'd from dump1090-fa (152 in last 5m); 996952 msgs sent to FlightAware
[2021-09-24 19:01 AEST] 1000879 msgs recv'd from dump1090-fa (98 in last 5m); 997050 msgs sent to FlightAware
[2021-09-24 19:06 AEST] 1001015 msgs recv'd from dump1090-fa (136 in last 5m); 997186 msgs sent to FlightAware
[2021-09-24 19:10 AEST] mlat-client(28154): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.1kB/s UDP to server
[2021-09-24 19:10 AEST] mlat-client(28154): Server status: synchronized with 121 nearby receivers
[2021-09-24 19:10 AEST] mlat-client(28154): Receiver status: connected
[2021-09-24 19:10 AEST] mlat-client(28154): Aircraft: 0 of 0 Mode S, 5 of 5 ADS-B used
[2021-09-24 19:11 AEST] 1001205 msgs recv'd from dump1090-fa (190 in last 5m); 997376 msgs sent to FlightAware```
1 Like
5

Likewise here even after refreshing the logfile.

[2021-09-24 17:28 PST] 22250 msgs recv'd from dump1090-fa (45 in last 5m); 22250 msgs sent to FlightAware:

Current time: 18:14 PST (Philippine Standard Time.)

pi@piaware:~ $ sudo systemctl status piaware
● piaware.service - FlightAware ADS-B uploader
   Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2021-09-23 23:08:08 UTC; 11h ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 9770 (piaware)
    Tasks: 4 (limit: 2059)
   CGroup: /system.slice/piaware.service
           ├─4870 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --
           ├─9770 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/st
           └─9797 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-ty

Sep 24 10:06:01 piaware piaware[9770]: mlat-client(9797): Input format changed to BEAST, 12MHz clock
Sep 24 10:06:08 piaware piaware[9770]: adept server faup request received: faup_adjust_upload_rate
Sep 24 10:06:08 piaware piaware[9770]: faup1090(4870): handleFaupCommand(): Adjusting message rate t
Sep 24 10:08:32 piaware piaware[9770]: mlat-client(9797): Receiver status: connected
Sep 24 10:08:32 piaware piaware[9770]: mlat-client(9797): Server status:   synchronized with 7 nearb
Sep 24 10:08:32 piaware piaware[9770]: mlat-client(9797): Receiver:    7.7 msg/s received        4.8
Sep 24 10:08:32 piaware piaware[9770]: mlat-client(9797): Server:      0.0 kB/s from server    0.0kB
Sep 24 10:08:32 piaware piaware[9770]: mlat-client(9797): Aircraft: 0 of 0 Mode S, 2 of 2 ADS-B used
Sep 24 10:08:43 piaware piaware[9770]: 22651 msgs recv'd from dump1090-fa (136 in last 5m); 22651 ms
Sep 24 10:13:43 piaware piaware[9770]: 22762 msgs recv'd from dump1090-fa (111 in last 5m); 22762 ms

PiAware uses UTC so it’s current. It’s the log pane at the bottom of the stats page’s settings (the gear icon) that’s off.

1 Like
6

It’s also not stable on my end. Here again the time drop of 45 Minutes where nothing has been logged, but the device was running all the time without gaps in data stream:

Gabp is between 12:15 and 13:00
That’s exactly the 45 Minutes where the two logs differ from each other

[2021-09-24 12:09 CEST] mlat-client(28833): Route MTU changed to 1476
[2021-09-24 12:10 CEST] 148457 msgs recv'd from rcd (1637 in last 5m); 148456 msgs sent to FlightAware
[2021-09-24 12:15 CEST] 149947 msgs recv'd from rcd (1490 in last 5m); 149946 msgs sent to FlightAware
[2021-09-24 13:00 CEST] mlat-client(28833): Route MTU changed to 1492
[2021-09-24 13:00 CEST] mlat-client(28833): Route MTU changed to 1476
[2021-09-24 13:00 CEST] 164321 msgs recv'd from rcd (1701 in last 5m); 164320 msgs sent to FlightAware
[2021-09-24 13:05 CEST] mlat-client(28833): Server status: synchronized with 597 nearby receivers
[2021-09-24 13:05 CEST] mlat-client(28833): Server: 0.1 kB/s from server 0.0kB/s TCP to server 2.4kB/s UDP to server
[2021-09-24 13:05 CEST] mlat-client(28833): Receiver status: connected
[2021-09-24 13:05 CEST] mlat-client(28833): Results: 52.3 positions/minute
[2021-09-24 13:05 CEST] mlat-client(28833): Aircraft: 17 of 27 Mode S, 71 of 83 ADS-B used
[2021-09-24 13:05 CEST] mlat-client(28833): Receiver: 1251.3 msg/s received 199.5 msg/s processed (16%)
[2021-09-24 13:05 CEST] 166281 msgs recv'd from rcd (1960 in last 5m); 166280 msgs sent to FlightAware
[2021-09-24 13:10 CEST] mlat-client(28833): Route MTU changed to 1492
[2021-09-24 13:10 CEST] mlat-client(28833): Route MTU changed to 1476
[2021-09-24 13:10 CEST] 168095 msgs recv'd from rcd (1814 in last 5m); 168094 msgs sent to FlightAware

Currently the time in the profile matches

7

There’s an internal ticket open to look into this.

1 Like
8

Can you please give me the ticket number?

Oh, sorry. I am working in IT support and have forgotten that this has nothing to do with my companies ticket system :rofl: :rofl:

9

Should be back on track now.

edit: it was BCK-6375 if you really want to know :wink:

1 Like
10

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