Seen this a few times this week “Sorry, we were unable to fetch the log for this site. Please try again later.” in the Log window on the user control panel.
Sometimes I get to see the log and sometimes I get that.
PiAware and PC are both hardwired to the same router.
My Piaware recently corrupted after the last “Upgrade Everything” command so I had to re-image the SD card but this issue still persists (it was doing it before also).
Any idea what might be causing it ?
It’s an issue on the FA server side with the bit of software that maintains a list of recent log entries / nearby flights, not with your piaware.
OK thanks, it’s just coincidental that it started happening this week around the time my SD card corrupted during the “Upgrade All” activity.
A reflash of the SD card fixed the other issues.
I have been getting this message a LOT, I would say 80% of the time, perhaps more.
While we are on the subject, the auto refresh time is annoyingly short. Please consider either making it longer (60 sec?) or options to toggle it on / off.
Often I want to scroll back and read the log file and just about when I get to what I want to read it auto refreshes, arrgh. Stop it please! iPads are expensive and this makes me want to toss to to the other side of the room!
I concur, control panel states “15 second refresh” but in fact, it is only 9.47 seconds until it refreshes the page 
+1. For at least a “Pause” option, please.
I am able to see back about 3 hours on the log.
I’m using Chrome on Win 7.
On “My ADS-B” page open the log.
Click anywhere on the page and CTRL-A, then CTRL-C.
Open text editor, (notepad) and paste (CTRL-V).
This pastes all the page of course but it includes the hidden part of the log.
Mode S Multilateration (MLAT) Send non-ADS-B data for Multilateration (MLAT).
Send command to device Send command This PiAware device has manual updates disabled. More info
Log
Note: this log pane refreshes itself automatically every 15 seconds. Refresh log contents →
[2015-12-20 06:04 CET] 178497 msgs recv’d from dump1090-mutabi (21 in last 5m); 178362 msgs sent to FlightAware
[2015-12-20 06:05 CET] mlat(10515): Receiver status: connected
[2015-12-20 06:05 CET] mlat(10515): Server status: synchronized with 2 nearby receivers
[2015-12-20 06:05 CET] mlat(10515): Receiver: 12.0 msg/s received 0.2kB/s from receiver
[2015-12-20 06:05 CET] mlat(10515): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.1kB/s UDP to server
[2015-12-20 06:05 CET] mlat(10515): Aircraft: 0 of 1 Mode S, 1 of 2 ADS-B used
[2015-12-20 06:09 CET] 178540 msgs recv’d from dump1090-mutabi (43 in last 5m); 178405 msgs sent to FlightAware
[2015-12-20 06:14 CET] 178586 msgs recv’d from dump1090-mutabi (46 in last 5m); 178451 msgs sent to FlightAware
[2015-12-20 06:19 CET] 178642 msgs recv’d from dump1090-mutabi (56 in last 5m); 178507 msgs sent to FlightAware
[2015-12-20 06:20 CET] mlat(10515): Receiver status: connected
[2015-12-20 06:20 CET] mlat(10515): Server status: synchronized with 2 nearby receivers
[2015-12-20 06:20 CET] mlat(10515): Receiver: 24.9 msg/s received 0.5kB/s from receiver
[2015-12-20 06:20 CET] mlat(10515): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.2kB/s UDP to server
[2015-12-20 06:20 CET] mlat(10515): Aircraft: 1 of 2 Mode S, 2 of 4 ADS-B used
[2015-12-20 06:24 CET] 178715 msgs recv’d from dump1090-mutabi (73 in last 5m); 178580 msgs sent to FlightAware
[2015-12-20 06:29 CET] 178803 msgs recv’d from dump1090-mutabi (88 in last 5m); 178668 msgs sent to FlightAware
[2015-12-20 06:34 CET] 178867 msgs recv’d from dump1090-mutabi (64 in last 5m); 178732 msgs sent to FlightAware
[2015-12-20 06:35 CET] mlat(10515): Receiver status: connected
[2015-12-20 06:35 CET] mlat(10515): Server status: synchronized with 1 nearby receivers
[2015-12-20 06:35 CET] mlat(10515): Receiver: 45.9 msg/s received 0.9kB/s from receiver
[2015-12-20 06:35 CET] mlat(10515): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.2kB/s UDP to server
[2015-12-20 06:35 CET] mlat(10515): Aircraft: 1 of 3 Mode S, 1 of 2 ADS-B used
[2015-12-20 06:39 CET] 178925 msgs recv’d from dump1090-mutabi (58 in last 5m); 178790 msgs sent to FlightAware
[2015-12-20 06:44 CET] 178960 msgs recv’d from dump1090-mutabi (35 in last 5m); 178825 msgs sent to FlightAware
[2015-12-20 06:49 CET] 179021 msgs recv’d from dump1090-mutabi (61 in last 5m); 178886 msgs sent to FlightAware
[2015-12-20 06:50 CET] mlat(10515): Receiver status: connected
[2015-12-20 06:50 CET] mlat(10515): Server status: synchronized with 1 nearby receivers
[2015-12-20 06:50 CET] mlat(10515): Receiver: 12.8 msg/s received 0.3kB/s from receiver
[2015-12-20 06:50 CET] mlat(10515): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server
[2015-12-20 06:50 CET] mlat(10515): Aircraft: 0 of 3 Mode S, 1 of 3 ADS-B used
[2015-12-20 06:54 CET] 179088 msgs recv’d from dump1090-mutabi (67 in last 5m); 178953 msgs sent to FlightAware
[2015-12-20 06:59 CET] 179166 msgs recv’d from dump1090-mutabi (78 in last 5m); 179031 msgs sent to FlightAware
[2015-12-20 07:04 CET] 179210 msgs recv’d from dump1090-mutabi (44 in last 5m); 179075 msgs sent to FlightAware
[2015-12-20 07:05 CET] mlat(10515): Receiver status: connected
[2015-12-20 07:05 CET] mlat(10515): Server status: synchronized with 1 nearby receivers
[2015-12-20 07:05 CET] mlat(10515): Receiver: 19.4 msg/s received 0.4kB/s from receiver
[2015-12-20 07:05 CET] mlat(10515): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.1kB/s UDP to server
[2015-12-20 07:05 CET] mlat(10515): Aircraft: 0 of 2 Mode S, 2 of 4 ADS-B used
[2015-12-20 07:09 CET] 179266 msgs recv’d from dump1090-mutabi (56 in last 5m); 179131 msgs sent to FlightAware
[2015-12-20 07:14 CET] 179321 msgs recv’d from dump1090-mutabi (55 in last 5m); 179186 msgs sent to FlightAware
[2015-12-20 07:19 CET] 179453 msgs recv’d from dump1090-mutabi (132 in last 5m); 179318 msgs sent to FlightAware
[2015-12-20 07:20 CET] mlat(10515): Receiver status: connected
[2015-12-20 07:20 CET] mlat(10515): Server status: synchronized with 2 nearby receivers
[2015-12-20 07:20 CET] mlat(10515): Receiver: 35.1 msg/s received 0.7kB/s from receiver
[2015-12-20 07:20 CET] mlat(10515): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.2kB/s UDP to server
[2015-12-20 07:20 CET] mlat(10515): Aircraft: 1 of 1 Mode S, 2 of 6 ADS-B used
[2015-12-20 07:24 CET] 179572 msgs recv’d from dump1090-mutabi (119 in last 5m); 179437 msgs sent to FlightAware
[2015-12-20 07:29 CET] 179714 msgs recv’d from dump1090-mutabi (142 in last 5m); 179579 msgs sent to FlightAware
[2015-12-20 07:34 CET] 179774 msgs recv’d from dump1090-mutabi (60 in last 5m); 179639 msgs sent to FlightAware
[2015-12-20 07:35 CET] mlat(10515): Receiver status: connected
[2015-12-20 07:35 CET] mlat(10515): Server status: synchronized with 2 nearby receivers
[2015-12-20 07:35 CET] mlat(10515): Receiver: 21.9 msg/s received 0.4kB/s from receiver
[2015-12-20 07:35 CET] mlat(10515): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.1kB/s UDP to server
[2015-12-20 07:35 CET] mlat(10515): Aircraft: 0 of 1 Mode S, 1 of 4 ADS-B used
[2015-12-20 07:39 CET] 179817 msgs recv’d from dump1090-mutabi (43 in last 5m); 179682 msgs sent to FlightAware
[2015-12-20 07:44 CET] 179884 msgs recv’d from dump1090-mutabi (67 in last 5m); 179749 msgs sent to FlightAware
[2015-12-20 07:49 CET] 179994 msgs recv’d from dump1090-mutabi (110 in last 5m); 179859 msgs sent to
…
Hope this helps,
Phill
Well Phill,
So dgates is using an Ipad.
And I’m usually on an Android device.
So thanks for your input, but no. It doesn’t solve the issue.
Hadn’t thought of the copy/past technique, good idea! But right, doesn’t really address the issue either, merely a work around for the problem.