Errno 111


#1

Hey guys,
since around 4PM my position reports plunged to 0.
According to Site info I’m online, feeding and mlat is enabled.

Data Feed: Live - less than a minute ago
Feeder Check-in: Live - less than a minute ago
Joined: 26-Nov-2014
Current Streak: 26 days (05-Oct-2015 - Today)
Longest Streak: 211 days (26-Nov-2014 - 24-Jun-2015)
Feeder Type: PiAware (Debian Package Add-on) 2.1-3
Multilateration (MLAT): Supported / Enabled (synchronized with 43 nearby receivers)

My log looks like this:
[2015-10-30 18:12 CET] mlat(2828): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
[2015-10-30 18:12 CET] mlat(2828): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
[2015-10-30 18:13 CET] mlat(2828): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
[2015-10-30 18:13 CET] 1696 msgs recv’d from dump1090-mutab (1549 in last 5m); 1696 msgs sent to FlightAware
[2015-10-30 18:13 CET] mlat(2828): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
[2015-10-30 18:14 CET] mlat(2828): Beast-format results connection with localhost:30104: [Errno 111] Connection refused

Any ideas?


#2

Stats have been regularly 2-3 hours behind over the last few days. Ignore the most recent 2-3 hours in the hourly stats graph, they will fix themselves as stats works through the backlog of data.

The errors connecting to port 30104 are piaware attempting (and failing) to connect to your local dump1090 to return mlat positions. See the piaware 2.1-3 announcement topic for more details.