Today, this happened:
[2015-06-16 12:27 CEST] 561090 msgs recv’d from dump1090 (1355 in last 5m); 557519 msgs sent to FlightAware
[2015-06-16 12:32 CEST] 562465 msgs recv’d from dump1090 (1375 in last 5m); 558894 msgs sent to FlightAware
[2015-06-16 12:37 CEST] 563996 msgs recv’d from dump1090 (1531 in last 5m); 560425 msgs sent to FlightAware
[2015-06-16 12:40 CEST] lost connection to faup1090, reconnecting…
[2015-06-16 12:40 CEST] no ADS-B data program is serving on port 30005, next check in 60s
[2015-06-16 12:41 CEST] no ADS-B data program is serving on port 30005, next check in 60s
[2015-06-16 12:42 CEST] no ADS-B data program is serving on port 30005, next check in 60s
[2015-06-16 12:42 CEST] no ADS-B producer program seen for 300 seconds (or since piaware started), will attempt to start it next check after 360 seconds…
[2015-06-16 12:42 CEST] no ADS-B producer (dump1090, modesmixer, etc) appears to be running or is not listening for connections on port 30005, next check in 5m
[2015-06-16 12:42 CEST] 564686 msgs recv’d from dump1090 (690 in last 5m); 561115 msgs sent to FlightAware
[2015-06-16 12:43 CEST] no ADS-B data program is serving on port 30005, next check in 60s
[2015-06-16 12:44 CEST] no ADS-B data program is serving on port 30005, next check in 60s
[2015-06-16 12:45 CEST] no ADS-B data program is serving on port 30005, next check in 60s
[2015-06-16 12:46 CEST] no ADS-B data program is serving on port 30005, next check in 60s
Here, I’ve restarted PiAware and dump1090 manually, then everything was fine again.
What was the reason for it, what did crash in particularly? dump1090 or PiAware?
Kabuse