My stats page is hanging again

FlightAware ADS-B Flight Tracking
1

Since this morning, European time, my stats page is hanging again, but the RasPi seems to run fine and also is still feeding to FR24.

Data Feed: Today - vor etwa einer Stunde
Feeder Check-in: Today - vor etwa einer Stunde

But this time, Positions reported and Aircraft seen are also not increasing. Last time they did, but Data Feed and Feeder Check-in was hanging only.

Did you do an overnight (US time) update again?

I am worried now that my data is lost and this will affect my stats. :open_mouth: :confused: :cry:

Can you please have a look at it? Thanks!

Regards,

Kabuse

2

You are not alone. I’ve just had to restart my FF box, no data feed for 11 hours, but feeder checked in 29 minutes ago. It’s also messed up my ‘longest streak’, a perfect record since I installed it 344 days ago. :confused:

3

Yes, that’s kind of annoying!

I hope, they can fix this issue finally completely.

Kabuse

4

Data Feed: Today - vor 9 Stunden
Feeder Check-in: Today - vor 9 Stunden

Still hanging, 9 hours now… :frowning:

Kabuse

5

Can you try restarting your devices?

6

Ok, after restart, using putty, my stats page gets updated again.

Anyway, dump1090 webserver was running, piaware-status said that everything was ok, FA24-feed was working perfectly.

Damn, already fallen down in the stats… :unamused:

Kabuse

7

Can you paste the logs for when it wasn’t working? That would be extremely helpful.

8

I will have a closer look at it at home and post it, if it is possible.

I just restarted by using the Android version of putty on my phone. Here at work, all other ports than 80 seem to be closed.

Kabuse

9

Some people with FF boxes from FA have also been reporting similar issues of stats not updating.

10

Ok, like promised, here is what I could extract from the log.

After reboot, I also did a manual update of piaware and dump1090, I think this is shown at the end.

Not sure about the time. Is this UTC? I think, I did reboot at about 16:00, so it seems to have a difference of 2 hours.

I hope this will help.

Kabuse

pi@piaware /tmp $ cat piaware.out
06/11/2015 13:52:05 ****************************************************
06/11/2015 13:52:05 piaware version 2.0 is running, process ID 2146
06/11/2015 13:52:05 your system info is: Linux piaware 3.18.7-v7+ #755 SMP PREEMPT Thu Feb 12 17:20:48 GMT 2015 armv7l GNU/Linux
06/11/2015 13:52:05 connecting to FlightAware piaware.flightaware.com/1200
06/11/2015 13:52:06 FlightAware server SSL certificate validated
06/11/2015 13:52:06 encrypted session established with FlightAware
06/11/2015 13:52:06 autoUpdate is not set in adept config, looking further…
06/11/2015 13:52:06 autoUpdate in /etc/piaware is enabled, allowing update
06/11/2015 13:52:06 manualUpdate is not set in adept config, looking further…
06/11/2015 13:52:06 manualUpdate in /etc/piaware is enabled, allowing update
06/11/2015 13:52:06 multilateration support enabled (use piaware-config to disable)
06/11/2015 13:52:06 ADS-B data program ‘dump1090’ is listening on port 30005, so far so good
06/11/2015 13:52:06 i see dump1090 serving on port 10001
06/11/2015 13:52:06 connecting to dump1090 on port 10001…
06/11/2015 13:52:06 piaware is connected to dump1090 on port 10001
06/11/2015 13:52:06 dump1090 is listening for connections on FA-style port 10001
06/11/2015 13:52:06 piaware received a message from the ADS-B source!
06/11/2015 13:52:06 logged in to FlightAware as user Kabuse
06/11/2015 13:52:06 multilateration support enabled (use piaware-config to disable)
06/11/2015 13:52:06 multilateration data requested, enabling mlat client
06/11/2015 13:52:07 mlat: fa-mlat-client 0.1.14.2 starting up
06/11/2015 13:52:07 mlat: Using UDP transport to 70.42.6.194:7774
06/11/2015 13:52:07 mlat: Input connected to localhost:30005
06/11/2015 13:52:11 piaware has successfully sent several msgs to FlightAware!
06/11/2015 13:52:36 101 msgs recv’d from dump1090; 44 msgs sent to FlightAware
06/11/2015 13:53:29 server is sending alive messages; we will expect them
06/11/2015 13:55:31 manual update (user-initiated via their flightaware control page) requested by adept server
06/11/2015 13:55:31 manualUpdate is not set in adept config, looking further…
06/11/2015 13:55:31 manualUpdate in /etc/piaware is enabled, allowing update
06/11/2015 13:55:31 performing manual update, action: piaware
06/11/2015 13:55:32 got status ok trying to fetch flightaware.com/adsb/piaware/files/latest
06/11/2015 13:55:32 considering upgrading piaware from flightaware.com/adsb/piaware/fi … rmhf.deb….
06/11/2015 13:55:32 fetching latest piaware version from flightaware.com/adsb/piaware/fi … _armhf.deb
06/11/2015 13:55:38 installing piaware…
06/11/2015 13:55:38 *** running command ‘dpkg --force-confnew -i /tmp/piaware_2.0-4_armhf.deb’ and logging output
06/11/2015 13:55:39 > (Reading database … 71540 files and directories currently installed.)
06/11/2015 13:55:39 > Preparing to replace piaware 2.0-3 (using /tmp/piaware_2.0-4_armhf.deb) …
06/11/2015 13:55:39 > Unpacking replacement piaware …
06/11/2015 13:55:40 > Setting up piaware (2.0-4) …
06/11/2015 13:55:41 > Starting piaware server: piaware/usr/bin/piaware already running.
06/11/2015 13:55:41 > .
06/11/2015 13:55:41 > Processing triggers for man-db …
06/11/2015 13:55:45 installing any required dependencies
06/11/2015 13:55:45 *** running command ‘apt-get install -fy’ and logging output
06/11/2015 13:55:48 > Reading package lists…
06/11/2015 13:55:49 > Building dependency tree…
06/11/2015 13:55:49 > Reading state information…
06/11/2015 13:55:50 > The following packages were automatically installed and are no longer required:
06/11/2015 13:55:50 > libfam0 spawn-fcgi
06/11/2015 13:55:50 > Use ‘apt-get autoremove’ to remove them.
06/11/2015 13:55:50 > 0 upgraded, 0 newly installed, 0 to remove and 21 not upgraded.
06/11/2015 13:55:50 upgrade of piaware complete.
06/11/2015 13:55:50 update request complete
06/11/2015 13:55:50 restarting piaware. hopefully i’ll be right back…
Stopping piaware server: piaware.
Starting piaware server: piaware.
06/11/2015 13:55:52 ****************************************************
06/11/2015 13:55:52 piaware version 2.0 is running, process ID 2675
06/11/2015 13:55:52 your system info is: Linux piaware 3.18.7-v7+ #755 SMP PREEMPT Thu Feb 12 17:20:48 GMT 2015 armv7l GNU/Linux
06/11/2015 13:55:52 connecting to FlightAware piaware.flightaware.com/1200
06/11/2015 13:55:54 FlightAware server SSL certificate validated
06/11/2015 13:55:54 encrypted session established with FlightAware
06/11/2015 13:55:54 autoUpdate is not set in adept config, looking further…
06/11/2015 13:55:54 autoUpdate in /etc/piaware is enabled, allowing update
06/11/2015 13:55:54 manualUpdate is not set in adept config, looking further…
06/11/2015 13:55:54 manualUpdate in /etc/piaware is enabled, allowing update
06/11/2015 13:55:54 multilateration support enabled (use piaware-config to disable)
06/11/2015 13:55:54 ADS-B data program ‘dump1090’ is listening on port 30005, so far so good
06/11/2015 13:55:54 i see dump1090 serving on port 10001
06/11/2015 13:55:54 connecting to dump1090 on port 10001…
06/11/2015 13:55:54 piaware is connected to dump1090 on port 10001
06/11/2015 13:55:54 dump1090 is listening for connections on FA-style port 10001
06/11/2015 13:55:54 logged in to FlightAware as user Kabuse
06/11/2015 13:55:54 multilateration support enabled (use piaware-config to disable)
06/11/2015 13:55:54 multilateration data requested, enabling mlat client
06/11/2015 13:55:55 mlat: fa-mlat-client 0.1.14.2 starting up
06/11/2015 13:55:55 mlat: Using UDP transport to 70.42.6.194:7778
06/11/2015 13:55:55 mlat: Input connected to localhost:30005
06/11/2015 13:55:59 piaware received a message from the ADS-B source!
06/11/2015 13:55:59 piaware has successfully sent several msgs to FlightAware!
06/11/2015 13:56:00 piaware (process 2146) is shutting down because it received a shutdown signal (SIGTERM) from the system…
06/11/2015 13:56:00 stop_faup1090: no need to stop faup1090, it’s not running
06/11/2015 13:56:00 multilateration data no longer required, disabling mlat client
06/11/2015 13:56:00 removing pidfile /var/run/piaware.pid
06/11/2015 13:56:00 piaware (process 2146) is exiting…
06/11/2015 13:56:24 166 msgs recv’d from dump1090; 166 msgs sent to FlightAware
06/11/2015 13:56:53 server is sending alive messages; we will expect them
06/11/2015 13:57:02 manual update (user-initiated via their flightaware control page) requested by adept server
06/11/2015 13:57:02 manualUpdate is not set in adept config, looking further…
06/11/2015 13:57:03 manualUpdate in /etc/piaware is enabled, allowing update
06/11/2015 13:57:03 performing manual update, action: piaware
06/11/2015 13:57:04 got status ok trying to fetch flightaware.com/adsb/piaware/files/latest
06/11/2015 13:57:04 considering upgrading piaware from flightaware.com/adsb/piaware/fi … rmhf.deb….
06/11/2015 13:57:04 fetching latest piaware version from flightaware.com/adsb/piaware/fi … _armhf.deb
06/11/2015 13:57:10 installing piaware…
06/11/2015 13:57:10 *** running command ‘dpkg --force-confnew -i /tmp/piaware_2.0-4_armhf.deb’ and logging output
06/11/2015 13:57:10 > (Reading database … 71540 files and directories currently installed.)
06/11/2015 13:57:10 > Preparing to replace piaware 2.0-4 (using /tmp/piaware_2.0-4_armhf.deb) …
06/11/2015 13:57:10 > Unpacking replacement piaware …
06/11/2015 13:57:12 > Setting up piaware (2.0-4) …
06/11/2015 13:57:12 > Starting piaware server: piaware.
06/11/2015 13:57:12 > Processing triggers for man-db …
06/11/2015 13:57:13 ****************************************************
06/11/2015 13:57:13 piaware version 2.0 is running, process ID 2734
06/11/2015 13:57:13 your system info is: Linux piaware 3.18.7-v7+ #755 SMP PREEMPT Thu Feb 12 17:20:48 GMT 2015 armv7l GNU/Linux
06/11/2015 13:57:13 connecting to FlightAware piaware.flightaware.com/1200
06/11/2015 13:57:14 FlightAware server SSL certificate validated
06/11/2015 13:57:14 encrypted session established with FlightAware
06/11/2015 13:57:14 autoUpdate is not set in adept config, looking further…
06/11/2015 13:57:14 autoUpdate in /etc/piaware is enabled, allowing update
06/11/2015 13:57:14 manualUpdate is not set in adept config, looking further…
06/11/2015 13:57:14 manualUpdate in /etc/piaware is enabled, allowing update
06/11/2015 13:57:14 multilateration support enabled (use piaware-config to disable)
06/11/2015 13:57:14 ADS-B data program ‘dump1090’ is listening on port 30005, so far so good
06/11/2015 13:57:14 i see dump1090 serving on port 10001
06/11/2015 13:57:14 connecting to dump1090 on port 10001…
06/11/2015 13:57:14 piaware is connected to dump1090 on port 10001
06/11/2015 13:57:14 dump1090 is listening for connections on FA-style port 10001
06/11/2015 13:57:14 logged in to FlightAware as user Kabuse
06/11/2015 13:57:14 multilateration support enabled (use piaware-config to disable)
06/11/2015 13:57:14 multilateration data requested, enabling mlat client
06/11/2015 13:57:15 mlat: fa-mlat-client 0.1.14.2 starting up
06/11/2015 13:57:15 mlat: Using UDP transport to 70.42.6.194:7781
06/11/2015 13:57:15 mlat: Input connected to localhost:30005
06/11/2015 13:57:19 installing any required dependencies
06/11/2015 13:57:19 *** running command ‘apt-get install -fy’ and logging output
06/11/2015 13:57:19 piaware received a message from the ADS-B source!
06/11/2015 13:57:19 piaware has successfully sent several msgs to FlightAware!
06/11/2015 13:57:21 > Reading package lists…
06/11/2015 13:57:22 > Building dependency tree…
06/11/2015 13:57:22 > Reading state information…
06/11/2015 13:57:23 > The following packages were automatically installed and are no longer required:
06/11/2015 13:57:23 > libfam0 spawn-fcgi
06/11/2015 13:57:23 > Use ‘apt-get autoremove’ to remove them.
06/11/2015 13:57:23 > 0 upgraded, 0 newly installed, 0 to remove and 21 not upgraded.
06/11/2015 13:57:23 upgrade of piaware complete.
06/11/2015 13:57:23 update request complete
06/11/2015 13:57:23 restarting piaware. hopefully i’ll be right back…
Stopping piaware server: piaware06/11/2015 13:57:23 piaware (process 2734) is shutting down because it received a shutdown signal (SIGTERM) from the system…
.
06/11/2015 13:57:23 stop_faup1090: no need to stop faup1090, it’s not running
06/11/2015 13:57:23 multilateration data no longer required, disabling mlat client
06/11/2015 13:57:23 removing pidfile /var/run/piaware.pid
06/11/2015 13:57:23 piaware (process 2734) is exiting…
Starting piaware server: piaware.
06/11/2015 13:57:26 ****************************************************
06/11/2015 13:57:26 piaware version 2.0 is running, process ID 3053
06/11/2015 13:57:26 your system info is: Linux piaware 3.18.7-v7+ #755 SMP PREEMPT Thu Feb 12 17:20:48 GMT 2015 armv7l GNU/Linux
06/11/2015 13:57:26 connecting to FlightAware piaware.flightaware.com/1200
06/11/2015 13:57:27 FlightAware server SSL certificate validated
06/11/2015 13:57:27 encrypted session established with FlightAware
06/11/2015 13:57:27 autoUpdate is not set in adept config, looking further…
06/11/2015 13:57:27 autoUpdate in /etc/piaware is enabled, allowing update
06/11/2015 13:57:27 manualUpdate is not set in adept config, looking further…
06/11/2015 13:57:27 manualUpdate in /etc/piaware is enabled, allowing update
06/11/2015 13:57:27 multilateration support enabled (use piaware-config to disable)
06/11/2015 13:57:27 ADS-B data program ‘dump1090’ is listening on port 30005, so far so good
06/11/2015 13:57:27 i see dump1090 serving on port 10001
06/11/2015 13:57:27 connecting to dump1090 on port 10001…
06/11/2015 13:57:27 piaware is connected to dump1090 on port 10001
06/11/2015 13:57:27 dump1090 is listening for connections on FA-style port 10001
06/11/2015 13:57:27 logged in to FlightAware as user Kabuse
06/11/2015 13:57:27 multilateration support enabled (use piaware-config to disable)
06/11/2015 13:57:27 multilateration data requested, enabling mlat client
06/11/2015 13:57:28 mlat: fa-mlat-client 0.1.14.2 starting up
06/11/2015 13:57:28 mlat: Using UDP transport to 70.42.6.194:7782
06/11/2015 13:57:28 mlat: Input connected to localhost:30005
06/11/2015 13:57:29 piaware received a message from the ADS-B source!
06/11/2015 13:57:29 piaware has successfully sent several msgs to FlightAware!
06/11/2015 13:57:33 piaware failed to die, pid 2675, that’s me, i’m gonna kill myself
06/11/2015 13:57:57 174 msgs recv’d from dump1090; 174 msgs sent to FlightAware
06/11/2015 13:58:27 server is sending alive messages; we will expect them
06/11/2015 14:00:43 manual update (user-initiated via their flightaware control page) requested by adept server
06/11/2015 14:00:43 manualUpdate is not set in adept config, looking further…
06/11/2015 14:00:43 manualUpdate in /etc/piaware is enabled, allowing update
06/11/2015 14:00:43 performing manual update, action: dump1090
06/11/2015 14:00:43 upgrade of dump1090 requested
06/11/2015 14:00:44 got status ok trying to fetch flightaware.com/adsb/piaware/fi … t_dump1090
06/11/2015 14:00:44 considering upgrading dump1090 from flightaware.com/adsb/piaware/fi … rmhf.deb….
06/11/2015 14:00:44 fetching latest dump1090 version from flightaware.com/adsb/piaware/fi … _armhf.deb
06/11/2015 14:00:46 installing dump1090…
06/11/2015 14:00:46 *** running command ‘dpkg --force-confnew -i /tmp/dump1090_1.1-1_armhf.deb’ and logging output
06/11/2015 14:00:46 > (Reading database … 71540 files and directories currently installed.)
06/11/2015 14:00:46 > Preparing to replace dump1090 1.1-1 (using /tmp/dump1090_1.1-1_armhf.deb) …
06/11/2015 14:00:46 > Unpacking replacement dump1090 …
06/11/2015 14:00:47 > Setting up dump1090 (1.1-1) …
06/11/2015 14:00:48 > Processing triggers for man-db …
06/11/2015 14:00:53 installing any required dependencies
06/11/2015 14:00:53 *** running command ‘apt-get install -fy’ and logging output
06/11/2015 14:00:56 > Reading package lists…
06/11/2015 14:00:56 > Building dependency tree…
06/11/2015 14:00:56 > Reading state information…
06/11/2015 14:00:57 > The following packages were automatically installed and are no longer required:
06/11/2015 14:00:57 > libfam0 spawn-fcgi
06/11/2015 14:00:57 > Use ‘apt-get autoremove’ to remove them.
06/11/2015 14:00:58 > 0 upgraded, 0 newly installed, 0 to remove and 21 not upgraded.
06/11/2015 14:00:58 upgrade of dump1090 complete.
06/11/2015 14:00:58 attempting to restart dump1090 using ‘/etc/init.d/fadump1090.sh restart’…
Stopping dump1090 server: dump1090.
Starting dump1090 server: dump1090006/11/2015 14:01:00 dump1090 restart appears to have been successful
06/11/2015 14:01:00 update request complete
06/11/2015 14:00:58 mlat: Lost connection to localhost:30005
06/11/2015 14:00:58 mlat: Reconnecting in 30.0 seconds
06/11/2015 14:01:00 lost connection to faup1090, reconnecting…
06/11/2015 14:01:00 no ADS-B data program is serving on port 30005, next check in 60s
06/11/2015 14:01:28 mlat: Input connected to localhost:30005
06/11/2015 14:02:00 ADS-B data program ‘dump1090’ is listening on port 30005, so far so good
06/11/2015 14:02:00 i see dump1090 serving on port 10001
06/11/2015 14:02:00 connecting to dump1090 on port 10001…
06/11/2015 14:02:00 piaware is connected to dump1090 on port 10001
06/11/2015 14:02:57 1507 msgs recv’d from dump1090 (1333 in last 5m); 1507 msgs sent to FlightAware
06/11/2015 14:07:57 3368 msgs recv’d from dump1090 (1861 in last 5m); 3368 msgs sent to FlightAware
06/11/2015 14:12:28 mlat: Receiver connection: ready
06/11/2015 14:12:28 mlat: Server connection: ready
06/11/2015 14:12:28 mlat: Receiver: 478.6 msg/s received 8.4kB/s from receiver
06/11/2015 14:12:28 mlat: Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.4kB/s UDP to server
06/11/2015 14:12:28 mlat: Aircraft: 143 known, 80 requested by server
06/11/2015 14:12:57 5317 msgs recv’d from dump1090 (1949 in last 5m); 5317 msgs sent to FlightAware
06/11/2015 14:17:57 7188 msgs recv’d from dump1090 (1871 in last 5m); 7188 msgs sent to FlightAware
06/11/2015 14:22:57 9117 msgs recv’d from dump1090 (1929 in last 5m); 9117 msgs sent to FlightAware
06/11/2015 14:27:28 mlat: Receiver connection: ready
06/11/2015 14:27:28 mlat: Server connection: ready
06/11/2015 14:27:28 mlat: Receiver: 505.3 msg/s received 8.8kB/s from receiver
06/11/2015 14:27:28 mlat: Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.2kB/s UDP to server
06/11/2015 14:27:28 mlat: Aircraft: 142 known, 72 requested by server
06/11/2015 14:27:57 10918 msgs recv’d from dump1090 (1801 in last 5m); 10918 msgs sent to FlightAware
06/11/2015 14:32:57 12768 msgs recv’d from dump1090 (1850 in last 5m); 12768 msgs sent to FlightAware
06/11/2015 14:37:57 14661 msgs recv’d from dump1090 (1893 in last 5m); 14661 msgs sent to FlightAware
06/11/2015 14:42:28 mlat: Receiver connection: ready
06/11/2015 14:42:28 mlat: Server connection: ready
06/11/2015 14:42:28 mlat: Receiver: 500.5 msg/s received 8.7kB/s from receiver
06/11/2015 14:42:28 mlat: Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.7kB/s UDP to server
06/11/2015 14:42:28 mlat: Aircraft: 133 known, 80 requested by server
06/11/2015 14:42:57 16576 msgs recv’d from dump1090 (1915 in last 5m); 16576 msgs sent to FlightAware
06/11/2015 14:47:57 18293 msgs recv’d from dump1090 (1717 in last 5m); 18293 msgs sent to FlightAware
06/11/2015 14:52:57 20035 msgs recv’d from dump1090 (1742 in last 5m); 20035 msgs sent to FlightAware
06/11/2015 14:57:28 mlat: Receiver connection: ready
06/11/2015 14:57:28 mlat: Server connection: ready
06/11/2015 14:57:28 mlat: Receiver: 480.9 msg/s received 8.4kB/s from receiver
06/11/2015 14:57:28 mlat: Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.8kB/s UDP to server
06/11/2015 14:57:28 mlat: Aircraft: 114 known, 70 requested by server
06/11/2015 14:57:57 21582 msgs recv’d from dump1090 (1547 in last 5m); 21582 msgs sent to FlightAware
06/11/2015 15:02:57 22990 msgs recv’d from dump1090 (1408 in last 5m); 22990 msgs sent to FlightAware
06/11/2015 15:07:57 24437 msgs recv’d from dump1090 (1447 in last 5m); 24437 msgs sent to FlightAware
06/11/2015 15:12:29 mlat: Receiver connection: ready
06/11/2015 15:12:29 mlat: Server connection: ready
06/11/2015 15:12:29 mlat: Receiver: 472.3 msg/s received 8.2kB/s from receiver
06/11/2015 15:12:29 mlat: Server: 0.0 kB/s from server 0.0kB/s TCP to server 2.3kB/s UDP to server
06/11/2015 15:12:29 mlat: Aircraft: 120 known, 68 requested by server
06/11/2015 15:12:57 25924 msgs recv’d from dump1090 (1487 in last 5m); 25924 msgs sent to FlightAware
06/11/2015 15:17:57 27522 msgs recv’d from dump1090 (1598 in last 5m); 27522 msgs sent to FlightAware
06/11/2015 15:22:57 29162 msgs recv’d from dump1090 (1640 in last 5m); 29162 msgs sent to FlightAware
06/11/2015 15:27:29 mlat: Receiver connection: ready
06/11/2015 15:27:29 mlat: Server connection: ready
06/11/2015 15:27:29 mlat: Receiver: 523.2 msg/s received 9.2kB/s from receiver
06/11/2015 15:27:29 mlat: Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.8kB/s UDP to server
06/11/2015 15:27:29 mlat: Aircraft: 134 known, 71 requested by server
06/11/2015 15:27:57 30846 msgs recv’d from dump1090 (1684 in last 5m); 30846 msgs sent to FlightAware
06/11/2015 15:32:57 32520 msgs recv’d from dump1090 (1674 in last 5m); 32520 msgs sent to FlightAware
06/11/2015 15:37:57 34160 msgs recv’d from dump1090 (1640 in last 5m); 34160 msgs sent to FlightAware
06/11/2015 15:42:29 mlat: Receiver connection: ready
06/11/2015 15:42:29 mlat: Server connection: ready
06/11/2015 15:42:29 mlat: Receiver: 491.0 msg/s received 8.6kB/s from receiver
06/11/2015 15:42:29 mlat: Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.6kB/s UDP to server
06/11/2015 15:42:29 mlat: Aircraft: 120 known, 79 requested by server
06/11/2015 15:42:57 35767 msgs recv’d from dump1090 (1607 in last 5m); 35767 msgs sent to FlightAware
06/11/2015 15:47:57 37388 msgs recv’d from dump1090 (1621 in last 5m); 37388 msgs sent to FlightAware
06/11/2015 15:52:57 39170 msgs recv’d from dump1090 (1782 in last 5m); 39170 msgs sent to FlightAware
06/11/2015 15:57:29 mlat: Receiver connection: ready
06/11/2015 15:57:29 mlat: Server connection: ready
06/11/2015 15:57:29 mlat: Receiver: 509.9 msg/s received 9.0kB/s from receiver
06/11/2015 15:57:29 mlat: Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.6kB/s UDP to server
06/11/2015 15:57:29 mlat: Aircraft: 129 known, 73 requested by server
06/11/2015 15:57:57 40956 msgs recv’d from dump1090 (1786 in last 5m); 40956 msgs sent to FlightAware
06/11/2015 16:02:57 42849 msgs recv’d from dump1090 (1893 in last 5m); 42849 msgs sent to FlightAware
06/11/2015 16:07:57 44593 msgs recv’d from dump1090 (1744 in last 5m); 44593 msgs sent to FlightAware
06/11/2015 16:12:29 mlat: Receiver connection: ready
06/11/2015 16:12:29 mlat: Server connection: ready
06/11/2015 16:12:29 mlat: Receiver: 474.5 msg/s received 8.3kB/s from receiver
06/11/2015 16:12:29 mlat: Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.5kB/s UDP to server
06/11/2015 16:12:29 mlat: Aircraft: 134 known, 77 requested by server
06/11/2015 16:12:57 46461 msgs recv’d from dump1090 (1868 in last 5m); 46461 msgs sent to FlightAware
06/11/2015 16:17:57 48254 msgs recv’d from dump1090 (1793 in last 5m); 48254 msgs sent to FlightAware
06/11/2015 16:22:57 50088 msgs recv’d from dump1090 (1834 in last 5m); 50088 msgs sent to FlightAware
06/11/2015 16:27:30 mlat: Receiver connection: ready
06/11/2015 16:27:30 mlat: Server connection: ready
06/11/2015 16:27:30 mlat: Receiver: 494.2 msg/s received 8.7kB/s from receiver
06/11/2015 16:27:30 mlat: Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.8kB/s UDP to server
06/11/2015 16:27:30 mlat: Aircraft: 126 known, 74 requested by server
06/11/2015 16:27:57 51740 msgs recv’d from dump1090 (1652 in last 5m); 51740 msgs sent to FlightAware
06/11/2015 16:32:57 53348 msgs recv’d from dump1090 (1608 in last 5m); 53348 msgs sent to FlightAware
06/11/2015 16:37:57 54995 msgs recv’d from dump1090 (1647 in last 5m); 54995 msgs sent to FlightAware
pi@piaware /tmp $

11

Many thanks to the tech who restored my perfect run of 344 days ‘longest streak’ after my FF box hung up last night!