No MLAT connection

For 2-3 weeks I have had no MLAT connection when checking /myip and MLAT sync stats (5A) though I've had a little connection for some days a week or two back.
I'm not among the banned MLAT feeders and my MLAT sync health has always been around 90-95 percent.

I have tried to restart my MLAT client but to no avail.

I haven't registred any under-voltage and I am using the official Pi power supply on a pretty standard set-up.
Also when checking status of the client on my Pi it says the client is active:

● mlat-client.service - LSB: Multilateration client
Loaded: loaded (/etc/init.d/mlat-client; generated)
Active: active (exited) since Mon 2020-01-20 05:41:54 GMT; 1 weeks 3 days ago
Docs: man:systemd-sysv-generator(8)
Process: 321 ExecStart=/etc/init.d/mlat-client start (code=exited, status=0/SUCCESS)

Any suggestions, anyone?

 

Obv if exiting it's crashing.

Check your config.

What else did you install recently?

 

We should make a /home/pi sub-directory and just compile executables in that.

Tired of these sites and their shitty code breaking things.

People going to install theses commercial sites just to jerk off to obfuscated fake data, and that screws up getting real data to ADSBx when they break things.

 

Thanks for the suggestions.

I'm running Pi with the feeder installed (not Adsbx image) - it's on Buster Lite and running dump1090-fa 3.8.0.
I am feeding a custom port 51251 at Adsbx.

I didn't install anything recently (except dump1090-fa 3.8.0); have tried out RB24 for a short while but as far back as I remember, I have a clean install with only Adsbx, Flightaware, FR24 and Wiedehopf's graphs - and the Pi is running nothing else.

I didn't know that the MLAT client I was checking wasn't Adsbx - I am not feeding MLAT data to Flightaware or FR24 so their MLAT clients shouldn't be running.
Any suggenstions on what that might be?

I'm not super technical inclined but I get the basics and know how to follow a how-to without screwing up.

I'm not sure how to check my config though unfortunately, James - and I am not jerking off to obfuscated fake data (yet)

But I really would like to contribute with MLAT data on Adsbx - and Adsbx only.

 

https://github.com/adsbxchange/adsbexchange-stats


Step 1 and Step 2

If you are lucky if will fix what other sites broke ...

 

Thanks James and Wiedehopf for the answers.
I made a re-install of the ADSBx script and now I'm feeding MLAT data.

Weird thing is that I got a "permission denied" when trying to run rm -rf adsb-exchange but I made a new install nonetheless.
And I still have no clue what mlat-client.service I have (had been) running.

I will make a clean install at some point.
Thanks again!

 

I did use sudo the second time I tried
But still persmission denied. Very weird.

 

Compilation worked. So I absolutly agree - makes no sense.
I usually run a tight ship when it comes to my Raspberry Pi but something here is not right - which is why I will make a clean install at some point soon.

 

Hmm...my MLAT client seems to disconnect.
The client seems to be running - but not connected.
If I manually restarts the MLAT client it reconnects. Anybody has any thoughts on this?

Code:

● adsbexchange-mlat.service - adsbexchange-mlat
Loaded: loaded (/lib/systemd/system/adsbexchange-mlat.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2020-02-05 06:42:31 GMT; 1 day 13h ago
Main PID: 752 (mlat-client)
Tasks: 1 (limit: 2200)
Memory: 9.0M
CGroup: /system.slice/adsbexchange-mlat.service
└─752 /usr/bin/python3.7 /usr/bin/mlat-client --input-type dump1090 --no-udp --input-connect 127.0.0.1:3000

Feb 06 19:44:53 raspberrypi adsbexchange-mlat[752]: Thu Feb  6 19:44:53 2020 Server status:   disconnected
Feb 06 19:44:53 raspberrypi adsbexchange-mlat[752]: Thu Feb  6 19:44:53 2020 Receiver:    0.0 msg/s received        0.
Feb 06 19:44:53 raspberrypi adsbexchange-mlat[752]: Thu Feb  6 19:44:53 2020 Server:      0.0 kB/s from server    0.0k
Feb 06 19:44:53 raspberrypi adsbexchange-mlat[752]: Thu Feb  6 19:44:53 2020 Aircraft: 0 of 0 Mode S, 0 of 0 ADS-B use
Feb 06 19:45:17 raspberrypi adsbexchange-mlat[752]: Thu Feb  6 19:45:17 2020 Connection to feed.adsbexchange.com:31090
Feb 06 19:45:17 raspberrypi adsbexchange-mlat[752]: Thu Feb  6 19:45:17 2020 Reconnecting in 14.0 seconds
Feb 06 19:45:41 raspberrypi adsbexchange-mlat[752]: Thu Feb  6 19:45:41 2020 Connection to feed.adsbexchange.com:31090
Feb 06 19:45:41 raspberrypi adsbexchange-mlat[752]: Thu Feb  6 19:45:41 2020 Reconnecting in 14.0 seconds
Feb 06 19:46:05 raspberrypi adsbexchange-mlat[752]: Thu Feb  6 19:46:05 2020 Connection to feed.adsbexchange.com:31090
Feb 06 19:46:05 raspberrypi adsbexchange-mlat[752]: Thu Feb  6 19:46:05 2020 Reconnecting in 14.0 seconds

 

any other feeders installed?

 

ADSBx, Flightaware, FR24 and Wiedehopf's graphs - and the Pi is running nothing else.
And not feeding MLAT to FlightAware or FR24 - their MLAT clients are off.

 

Hmmm . hard to say .....

 

Thank's for helping out, Wiedehopf.

Code:

10803 /usr/bin/python3.7 /usr/bin/mlat-client --input-type dump1090 --no-udp --input-connect 127.0.0.1:30005 --server feed.adsbexchange.com:31090 --user Rubiconic --lat 55.67065 --lon 12.5606 --alt 20 --results beast,connect,localhost:30104 --results basestation,listen,31003