Help on Log errors

FlightAware ADS-B Flight Tracking
1

I’ve got a Raspberry Pi 3B with a current NOOBS OS, a current PiAware 3.5, and a current FR24.
PiAware and FR24 appear to be feeding Ok - except the on-line PiAware log shows an “Errno 111” for “Beast-format results connections”.

I don’t have a clue as to what that means or how to fix it.

Any help would be appreciated.

…also what is the complete terminal command line to access and edit the PiAware config file??

I’m including samples of the log with it’s errors and a copy of my PiAware config file.

Thanks.

[2017-04-26 21:47 PDT] mlat-client(23661): Server: 0.7 kB/s from server 0.0kB/s TCP to server 1.3kB/s UDP to server
[2017-04-26 21:47 PDT] mlat-client(23661): Results: 325.0 positions/minute
[2017-04-26 21:47 PDT] mlat-client(23661): Aircraft: 10 of 22 Mode S, 21 of 26 ADS-B used
[2017-04-26 21:47 PDT] mlat-client(23661): Beast-format results connection with ::1:30104: [Errno 111] Connection refused
[2017-04-26 21:48 PDT] mlat-client(23661): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
[2017-04-26 21:48 PDT] mlat-client(23661): Beast-format results connection with ::1:30104: [Errno 111] Connection refused
[2017-04-26 21:49 PDT] mlat-client(23661): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
[2017-04-26 21:49 PDT] mlat-client(23661): Beast-format results connection with ::1:30104: [Errno 111] Connection refused
[2017-04-26 21:50 PDT] mlat-client(23661): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
[2017-04-26 21:50 PDT] mlat-client(23661): Beast-format results connection with ::1:30104: [Errno 111] Connection refused

[2017-04-26 21:49 PDT] mlat-client(23661): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
[2017-04-26 21:49 PDT] mlat-client(23661): Beast-format results connection with ::1:30104: [Errno 111] Connection refused
[2017-04-26 21:50 PDT] mlat-client(23661): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
[2017-04-26 21:50 PDT] mlat-client(23661): Beast-format results connection with ::1:30104: [Errno 111] Connection refused
[2017-04-26 21:51 PDT] mlat-client(23661): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
[2017-04-26 21:51 PDT] 2838117 msgs recv’d from dump1090-mutabi (1568 in last 5m); 2835381 msgs sent to FlightAware
[2017-04-26 21:51 PDT] mlat-client(23661): Beast-format results connection with ::1:30104: [Errno 111] Connection refused
[2017-04-26 21:52 PDT] mlat-client(23661): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
[2017-04-26 21:52 PDT] mlat-client(23661): Beast-format results connection with ::1:30104: [Errno 111] Connection refused
[2017-04-26 21:53 PDT] mlat-client(23661): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused

pi@raspberrypi:~ $ sudo piaware-config -showall
#adept-serverhosts “piaware.flightaware.com piaware.flightaware.com 70.42.6.197 70.42.6.198 70.42.6.191” # using default value
#adept-serverport 1200 # using default value
allow-auto-updates yes # value set at /etc/piaware.conf:7
#allow-dhcp-duid yes # using default value
allow-manual-updates yes # value set at /etc/piaware.conf:8
#allow-mlat yes # using default value
#allow-modeac yes # using default value
#beast-baudrate # no value set and no default value
#feeder-id # no value set and no default value
#flightaware-password # no value set and no default value
#flightaware-user # no value set and no default value
#force-macaddress # no value set and no default value
#http-proxy-host # no value set and no default value
#http-proxy-password # no value set and no default value
#http-proxy-port # no value set and no default value
#http-proxy-user # no value set and no default value
#image-type # no value set and no default value
#manage-config no # using default value
#mlat-results yes # using default value
#mlat-results-anon yes # using default value
#mlat-results-format “beast,connect,localhost:30104 beast,listen,30105 ext_basestation,listen,30106” # using default value
#priority # no value set and no default value
#radarcape-host # no value set and no default value
#receiver-host # no value set and no default value
#receiver-port 30005 # using default value
#receiver-type rtlsdr # using default value
#rfkill no # using default value
#rtlsdr-device-index 0 # using default value
#rtlsdr-gain -10 # using default value
#rtlsdr-ppm 0 # using default value
#wired-address # no value set and no default value
#wired-broadcast # no value set and no default value
#wired-gateway # no value set and no default value
#wired-nameservers “8.8.8.8 8.8.4.4” # using default value
#wired-netmask # no value set and no default value
#wired-network yes # using default value
#wired-type dhcp # using default value
#wireless-address # no value set and no default value
#wireless-broadcast # no value set and no default value
#wireless-gateway # no value set and no default value
#wireless-nameservers “8.8.8.8 8.8.4.4” # using default value
#wireless-netmask # no value set and no default value
#wireless-network no # using default value
#wireless-password # no value set and no default value
#wireless-ssid # no value set and no default value
#wireless-type dhcp # using default value
pi@raspberrypi:~ $

2

That means that piaware is trying to connect to your local dump1090 to return mlat results, but dump1090 is not listening for them.
It’s harmless in terms of data feeding, though obviously it also means that mlat results will not be visible to you on your local map.

You need a dump1090 version that is mlat-aware to display the results. dump1090-fa and dump1090-mutability are mlat-aware.

3

Oh, I forgot to say that I also have 1090-mutability installed.

How do I get mutability-dump1090 to listen?
and what is the terminal command line to access and edit the piaware configuration file?

Thanks again

1 Like
4

Hi all
Could you help me check logs 24hrs
just need to sus why my pi crashes once a day
am i pushing it to much or is my dns server doing it im not sure
pi4/2gb dietpi 64bit piaware /readsb

john

5

that would work only if the reason for a crash is documented in the logs right before the crash.
In many cases even the logging stopped and the next thing you see in the logs will be the reboot.

You can try it to find the position in the logs with uptime. Then scroll back to that time or a few minutes before.

And if DietPC is using log2ram technology to reduce writes, the chance is almost zero.
So you might need to change the logging method first

6

Oh dear i should have realised my mistake and checked that out first sorry bout that
my memory dont work well these days
and the obvious dont click in my head
i got it sorted and thankyou for your time
john

1 Like