MLAT Error


#1

Hello i have an pi B+ with the last piaware image the Error MLAT works 2min than crash :frowning:

Can me help me?

Greats Nik


#2

You need to describe the problem better. Does the whole Pi hang or reboot? Then it is a power problem.


#3

The MLAT Crash after 2min wenn piaware server works after 2 min no MLAT on VRS. When i piaware restart then works MLAT for 2 min usw.


#4

What do the piaware logs say?
How did you install?


#5

piaware the last version and we can i see the log?


#6

OK, so you installed the piaware sdcard image, or the packages?

Logs are in /tmp/piaware.out

From what I can see on this side you seem to have broken faup1090 somehow.
Did you disable the loopback interface on your Pi? (That seems to be a thing now, I don’t know why)


#7

i have install the piware sd card image

i don´t have the loopback interface on my Pi disable :frowning:

in /tmp/piaware.out say my pi command not found


08/10/2015 18:54:22 piaware received a message from dump1090!
08/10/2015 18:54:22 piaware has successfully sent several msgs to FlightAware!
08/10/2015 18:54:22 mlat(2619): fa-mlat-client 0.2.3 starting up
08/10/2015 18:54:22 mlat(2619): Using UDP transport to 70.42.6.194:5917
08/10/2015 18:54:22 mlat(2619): Listening for Basestation-format results connect                                   ion on port 31003
08/10/2015 18:54:22 mlat(2619): Input connected to localhost:30005
08/10/2015 18:54:23 mlat(2619): Beast-format results connection with localhost:3                                   0004: connection established
08/10/2015 18:54:27 mlat(2619): Accepted Basestation-format results connection f                                   rom 192.168.0.3:60261
08/10/2015 18:54:51 89 msgs recv'd from dump1090; 89 msgs sent to FlightAware
08/10/2015 18:55:21 server is sending alive messages; we will expect them
08/10/2015 18:57:24 piaware (process 2592) is shutting down because it received a shutdown signal (SIGTERM) from the system...
08/10/2015 18:57:24 multilateration data no longer required, disabling mlat client
08/10/2015 18:57:24 removing pidfile /var/run/piaware.pid
08/10/2015 18:57:24 piaware (process 2592) is exiting...
08/10/2015 18:57:27 ****************************************************
08/10/2015 18:57:27 piaware version 2.1-2 is running, process ID 2660
08/10/2015 18:57:27 your system info is: Linux piaware 3.18.11-v7+ #781 SMP PREEMPT Tue Apr 21 18:07:59 BST 2015 armv7l GNU/Linux
08/10/2015 18:57:27 connecting to FlightAware piaware.flightaware.com/1200
08/10/2015 18:57:28 FlightAware server SSL certificate validated
08/10/2015 18:57:28 encrypted session established with FlightAware
08/10/2015 18:57:28 autoUpdate is not set in adept config, looking further...
08/10/2015 18:57:28 autoUpdate in /etc/piaware is enabled, allowing update
08/10/2015 18:57:28 manualUpdate is not set in adept config, looking further...
08/10/2015 18:57:28 manualUpdate in /etc/piaware is enabled, allowing update
08/10/2015 18:57:28 multilateration support enabled (use piaware-config to disable)
08/10/2015 18:57:28 ADS-B data program 'dump1090' is listening on port 30005, so far so good
08/10/2015 18:57:28 Starting faup1090: /usr/bin/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --lat 51.362 --lon 12.185
08/10/2015 18:57:28 Started faup1090 (pid 2685) to connect to dump1090
08/10/2015 18:57:28 logged in to FlightAware as user eagleonenik
08/10/2015 18:57:28 multilateration support enabled (use piaware-config to disable)
08/10/2015 18:57:28 multilateration data requested, enabling mlat client
08/10/2015 18:57:29 Starting multilateration client: /usr/lib/fa-mlat-client/fa-mlat-client --input-connect localhost:30005 --results beast,connect,localhost:30004 --results basestation,listen,31003 --udp-transport 70.42.6.203:5248:3192244585
08/10/2015 18:57:29 piaware received a message from dump1090!
08/10/2015 18:57:29 piaware has successfully sent several msgs to FlightAware!
08/10/2015 18:57:29 mlat(2687): fa-mlat-client 0.2.3 starting up
08/10/2015 18:57:29 mlat(2687): Using UDP transport to 70.42.6.203:5248
08/10/2015 18:57:29 mlat(2687): Listening for Basestation-format results connection on port 31003
08/10/2015 18:57:29 mlat(2687): Input connected to localhost:30005
08/10/2015 18:57:29 mlat(2687): Beast-format results connection with localhost:30004: connection established
08/10/2015 18:57:30 mlat(2687): Accepted Basestation-format results connection from 192.168.0.3:60297



#8

That all looks normal and there’s no evidence of anything crashing there. What is the problem you see exactly?


#9

I can see that MLAT works 2min and than crash. I see it on Virtual Radar by Feed Status


2015-08-11 17:08 CEST] mlat(3488): Receiver connection: ready
[2015-08-11 17:08 CEST] mlat(3488): Server connection: ready
[2015-08-11 17:08 CEST] mlat(3488): Receiver: 401.7 msg/s received 7.4kB/s from receiver
[2015-08-11 17:08 CEST] mlat(3488): Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.0kB/s UDP to server
[2015-08-11 17:08 CEST] mlat(3488): Aircraft: 113 known, 66 requested by server
[2015-08-11 17:08 CEST] 172646 msgs recv'd from dump1090 (1339 in last 5m); 172646 msgs sent to FlightAware
[2015-08-11 17:13 CEST] 173932 msgs recv'd from dump1090 (1286 in last 5m); 173932 msgs sent to FlightAware
[2015-08-11 17:18 CEST] 175262 msgs recv'd from dump1090 (1330 in last 5m); 175262 msgs sent to FlightAware
[2015-08-11 17:20 CEST] piaware (process 3461) is shutting down because it received a shutdown signal (SIGTERM) from the system...
[2015-08-11 17:20 CEST] multilateration data no longer required, disabling mlat client


#10

That log says that everything was running normally for 12 minutes, then you manually stopped piaware.
You stopped it before fa-mlat-client could do its perioidic report that includes the position rate, so I can’t tell if it’s receiving positions or not.
Otherwise, everything looks OK.

You will need to explain what the problem with the feed is more exactly - does VRS stop receiving data entirely, or is it losing the connection, or do the message counts stop increasing, or what? I see nothing wrong from these logs.


#11

i have piaware manually restart for MLAt

VRS stop receiving data for MLAT and then i make an restart of piaware


#12

Leave mlat enabled and don’t restart piaware. When you see the problem wait 15 mins, check it is still happening, check your stats page for any anomaly reports. Then look at the logs.


#13

ok I’m watching the time now


#14

after 30min the same Error MLATs works 2-5min then VRS show not MLAT an this comes from my log

Anomaly report for PiAware feeder with a MAC address of 
    Multilateration has not synchronized with any nearby sites. This may be because of a lack of nearby ADS-B equipped aircraft, or simply a lack of nearby multilateration-capable receivers. It can also be caused by the site location being incorrect.

#15

OK, so this is probably not a problem on your side. You should leave mlat enabled and I will take a look on the server side when I can (probably when I am back from holiday in a couple of weeks)


#16

i think i have the problem resolved with helb. the problem was the firewall on my router LAN-side UDP Flood and now mlat works now :slight_smile: thanks for the help


#17

Aha, that would do it. fa-mlat-client uses UDP to send the mlat data.

On the todo list is to do some checks that UDP sent by the client arrives OK at the server.