Checking my stats to day I see a sharp decline in the number of positions reported on 3 of my seven feeders.
While the aircraft numbers remain roughly the same, the number of postions is declining with 50%.
Now I know that when running Skyaware Anywhere increases the number of reported positions I’m wondering if there’s a relation between the recieivng server and the reporting station to be found somewhere ?
Skywaware Anywhere is running 24/7 on a seperate machine connected to a screen displaying the combined 7 feeders so that hasn’t been switched on or of, it is always there. So that shouldn’t be a factor.
Reason for the question is that the other 4 recievers are running as usual with a quite steady number of postions and the other 3 had increased number for a month now.
All 3 started to report lower numbers at the same time so it seems that something changed at the serverside of things since this morning.
Checking the Piaware log I don’t see anything out of the ordinary, reports are sent regularly and there’s also no indication of a reconnection towards the receiving server.
Maybe the origin of this is to be found in the receiving server ? Has there been a redistribution due to serverload maybe ? If so, that’s fine but I would expect to see a reconnect in the piaware logs.
The time the decline started was between 09:00 and 10:00 CET and nothing is showing in the piaware log during that time ?
May 18 09:02:14 orangepi19 piaware[1663]: mlat-client(26343): Receiver status: connected
May 18 09:02:14 orangepi19 piaware[1663]: mlat-client(26343): Server status: synchronized with 382 nearby receivers
May 18 09:02:14 orangepi19 piaware[1663]: mlat-client(26343): Receiver: 592.3 msg/s received 117.8 msg/s processed (20%)
May 18 09:02:14 orangepi19 piaware[1663]: mlat-client(26343): Server: 0.1 kB/s from server 0.0kB/s TCP to server 1.1kB/s UDP to server
May 18 09:02:14 orangepi19 piaware[1663]: mlat-client(26343): Results: 35.9 positions/minute
May 18 09:02:14 orangepi19 piaware[1663]: mlat-client(26343): Aircraft: 20 of 32 Mode S, 39 of 56 ADS-B used
May 18 09:03:33 orangepi19 piaware[1663]: 25173343 msgs recv'd from dump1090-fa (3653 in last 5m); 25172951 msgs sent to FlightAware
May 18 09:04:02 orangepi19 piaware[1663]: mlat-client(26343): Route MTU changed to 1500
May 18 09:04:35 orangepi19 piaware[1663]: mlat-client(26343): Route MTU changed to 1476
May 18 09:08:33 orangepi19 piaware[1663]: 25176639 msgs recv'd from dump1090-fa (3296 in last 5m); 25176247 msgs sent to FlightAware
May 18 09:13:33 orangepi19 piaware[1663]: 25179667 msgs recv'd from dump1090-fa (3028 in last 5m); 25179275 msgs sent to FlightAware
May 18 09:14:53 orangepi19 piaware[1663]: mlat-client(26343): Route MTU changed to 1500
May 18 09:16:38 orangepi19 piaware[1663]: mlat-client(26343): Route MTU changed to 1476
May 18 09:17:14 orangepi19 piaware[1663]: mlat-client(26343): Receiver status: connected
May 18 09:17:14 orangepi19 piaware[1663]: mlat-client(26343): Server status: synchronized with 382 nearby receivers
May 18 09:17:14 orangepi19 piaware[1663]: mlat-client(26343): Receiver: 504.3 msg/s received 95.1 msg/s processed (19%)
May 18 09:17:14 orangepi19 piaware[1663]: mlat-client(26343): Server: 0.1 kB/s from server 0.0kB/s TCP to server 1.0kB/s UDP to server
May 18 09:17:14 orangepi19 piaware[1663]: mlat-client(26343): Results: 25.5 positions/minute
May 18 09:17:14 orangepi19 piaware[1663]: mlat-client(26343): Aircraft: 9 of 23 Mode S, 38 of 45 ADS-B used
May 18 09:18:33 orangepi19 piaware[1663]: 25182321 msgs recv'd from dump1090-fa (2654 in last 5m); 25181929 msgs sent to FlightAware
May 18 09:23:33 orangepi19 piaware[1663]: 25184818 msgs recv'd from dump1090-fa (2497 in last 5m); 25184426 msgs sent to FlightAware
May 18 09:26:29 orangepi19 piaware[1663]: mlat-client(26343): Route MTU changed to 1500
May 18 09:28:33 orangepi19 piaware[1663]: 25187190 msgs recv'd from dump1090-fa (2372 in last 5m); 25186798 msgs sent to FlightAware
May 18 09:28:43 orangepi19 piaware[1663]: mlat-client(26343): Route MTU changed to 1476
May 18 09:32:14 orangepi19 piaware[1663]: mlat-client(26343): Receiver status: connected
May 18 09:32:14 orangepi19 piaware[1663]: mlat-client(26343): Server status: synchronized with 444 nearby receivers
May 18 09:32:14 orangepi19 piaware[1663]: mlat-client(26343): Receiver: 440.9 msg/s received 78.7 msg/s processed (18%)
May 18 09:32:14 orangepi19 piaware[1663]: mlat-client(26343): Server: 0.1 kB/s from server 0.0kB/s TCP to server 0.8kB/s UDP to server
May 18 09:32:14 orangepi19 piaware[1663]: mlat-client(26343): Results: 33.1 positions/minute
May 18 09:32:14 orangepi19 piaware[1663]: mlat-client(26343): Aircraft: 17 of 34 Mode S, 32 of 40 ADS-B used
May 18 09:33:33 orangepi19 piaware[1663]: 25189775 msgs recv'd from dump1090-fa (2585 in last 5m); 25189383 msgs sent to FlightAware
May 18 09:38:33 orangepi19 piaware[1663]: 25192607 msgs recv'd from dump1090-fa (2832 in last 5m); 25192215 msgs sent to FlightAware
May 18 09:38:40 orangepi19 piaware[1663]: mlat-client(26343): Route MTU changed to 1500
May 18 09:39:14 orangepi19 piaware[1663]: mlat-client(26343): Route MTU changed to 1476
May 18 09:43:33 orangepi19 piaware[1663]: 25195301 msgs recv'd from dump1090-fa (2694 in last 5m); 25194909 msgs sent to FlightAware
May 18 09:47:14 orangepi19 piaware[1663]: mlat-client(26343): Receiver status: connected
May 18 09:47:14 orangepi19 piaware[1663]: mlat-client(26343): Server status: synchronized with 418 nearby receivers
May 18 09:47:14 orangepi19 piaware[1663]: mlat-client(26343): Receiver: 479.8 msg/s received 86.6 msg/s processed (18%)
May 18 09:47:14 orangepi19 piaware[1663]: mlat-client(26343): Server: 0.1 kB/s from server 0.0kB/s TCP to server 0.9kB/s UDP to server
May 18 09:47:14 orangepi19 piaware[1663]: mlat-client(26343): Results: 36.9 positions/minute
May 18 09:47:14 orangepi19 piaware[1663]: mlat-client(26343): Aircraft: 14 of 30 Mode S, 34 of 46 ADS-B used
May 18 09:48:33 orangepi19 piaware[1663]: 25198069 msgs recv'd from dump1090-fa (2768 in last 5m); 25197677 msgs sent to FlightAware
May 18 09:49:03 orangepi19 piaware[1663]: mlat-client(26343): Route MTU changed to 1500
May 18 09:49:35 orangepi19 piaware[1663]: mlat-client(26343): Route MTU changed to 1476
May 18 09:53:33 orangepi19 piaware[1663]: 25201184 msgs recv'd from dump1090-fa (3115 in last 5m); 25200792 msgs sent to FlightAware
May 18 09:58:33 orangepi19 piaware[1663]: 25204529 msgs recv'd from dump1090-fa (3345 in last 5m); 25204137 msgs sent to FlightAware
May 18 09:59:19 orangepi19 piaware[1663]: mlat-client(26343): Route MTU changed to 1500
May 18 09:59:52 orangepi19 piaware[1663]: mlat-client(26343): Route MTU changed to 1476
Maybe someone tell me if I can find a relation with the receiving server somewhere ? Not Much I can do about that side of things but it made me wonder…
