After updating to 3.6.2


#1

Hi all
Getting Mlat problem keeps stopping and restarting

warning i get is
MLAT disabled/not synchronized/Latitude Longitude not set
but they are correct reentered several times

here’s a bit of log

[2018-08-06 08:05 BST] dump1090 start appears to have been successful
[2018-08-06 08:06 BST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2018-08-06 08:06 BST] no ADS-B data program seen listening on port 30005 for 70 seconds, next check in 60s
[2018-08-06 08:06 BST] 536179 msgs recv’d from dump1090-fa (4404 in last 5m); 536178 msgs sent to FlightAware
[2018-08-06 08:07 BST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2018-08-06 08:07 BST] no ADS-B data program seen listening on port 30005 for 130 seconds, next check in 60s
[2018-08-06 08:08 BST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2018-08-06 08:08 BST] no ADS-B data program seen listening on port 30005 for 190 seconds, next check in 60s
[2018-08-06 08:09 BST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2018-08-06 08:09 BST] no ADS-B data program seen listening on port 30005 for 251 seconds, next check in 60s
[2018-08-06 08:10 BST] 0 msgs recv’d from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
[2018-08-06 08:10 BST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2018-08-06 08:10 BST] no ADS-B data program seen listening on port 30005 for 311 seconds, next check in 60s
[2018-08-06 08:11 BST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2018-08-06 08:11 BST] no ADS-B data program seen listening on port 30005 for 371 seconds, trying to start it…
[2018-08-06 08:11 BST] attempting to start dump1090…
[2018-08-06 08:11 BST] attempting to start dump1090-fa using ‘systemctl --no-block restart dump1090-fa.service < /dev/null’…
[2018-08-06 08:11 BST] dump1090 start appears to have been successful
[2018-08-06 08:11 BST] 540412 msgs recv’d from dump1090-fa (4233 in last 5m); 540411 msgs sent to FlightAware
[2018-08-06 08:11 BST] no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s
[2018-08-06 08:12 BST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2018-08-06 08:12 BST] mlat-client(1047): Receiver status: connected
[2018-08-06 08:12 BST] mlat-client(1047): Server status: synchronized with 492 nearby receivers
[2018-08-06 08:12 BST] mlat-client(1047): Receiver: 1502.7 msg/s received 179.0 msg/s processed (12%)
[2018-08-06 08:12 BST] mlat-client(1047): Server: 0.2 kB/s from server 0.1kB/s TCP to server 1.9kB/s UDP to server
[2018-08-06 08:12 BST] mlat-client(1047): Results: 110.8 positions/minute
[2018-08-06 08:12 BST] mlat-client(1047): Aircraft: 21 of 65 Mode S, 83 of 138 ADS-B used
[2018-08-06 08:12 BST] no ADS-B data program seen listening on port 30005 for 70 seconds, next check in 60s
[2018-08-06 08:13 BST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2018-08-06 08:13 BST] no ADS-B data program seen listening on port 30005 for 130 seconds, next check in 60s
[2018-08-06 08:14 BST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2018-08-06 08:14 BST] no ADS-B data program seen listening on port 30005 for 190 seconds, next check in 60s
[2018-08-06 08:15 BST] 0 msgs recv’d from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
[2018-08-06 08:15 BST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2018-08-06 08:15 BST] no ADS-B data program seen listening on port 30005 for 250 seconds, next check in 60s
[2018-08-06 08:16 BST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2018-08-06 08:16 BST] 544312 msgs recv’d from dump1090-fa (3900 in last 5m); 544311 msgs sent to FlightAware
[2018-08-06 08:16 BST] no ADS-B data program seen listening on port 30005 for 310 seconds, next check in 60s
[2018-08-06 08:17 BST] no ADS-B data program is serving on port 30005, not starting multilateration client yet


#2

seems dump1090 is crashing for some reason.

ssh into the pi and do:
sudo journalctl -n 400 --no-pager

Either paste that here or check if there is any indication why dump1090 crashed.

As always most likely problem is the power supply. Or is this an old setup?


#3

Setup 15 months ago 5v 2.5amp psu
result from output short
Aug 06 13:46:58 piaware sudo[12116]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/getent shadow pi
Aug 06 13:46:58 piaware sudo[12116]: pam_unix(sudo:session): session opened for user root by pi(uid=0)
Aug 06 13:46:58 piaware sudo[12116]: pam_unix(sudo:session): session closed for user root
Aug 06 13:47:01 piaware CRON[12141]: pam_unix(cron:session): session opened for user pi by (uid=0)
Aug 06 13:47:01 piaware CRON[12145]: (pi) CMD (/home/pi/360radar/scripts/360r-ch eck.sh > /dev/null)
Aug 06 13:47:01 piaware CRON[12141]: pam_unix(cron:session): session closed for user pi
Aug 06 13:47:38 piaware sudo[12258]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/bin/journalctl -n 400 --no-pager
Aug 06 13:47:38 piaware sudo[12258]: pam_unix(sudo:session): session opened for user root by pi(uid=0)


#4

Yep, this is not a mlat problem, it’s an entire-data-feed problem; possibly the dongle is resetting or wedging due to a voltage drop.

If you have a spare power supply, I’d try swapping that out - 80% of problems are power related, and power supplies can go bad over time.

(FWIW, if you use a Stretch-based install, the newer kernels available with Stretch will log about undervoltage problems)


#5

Ok that is not an interesting part.

Let’s try
sudo journalctl -n 400 --no-pager -u dump1090-fa

And please copy at least the entire page after making the command window full screen.


#6

pi@piaware:~$ sudo journalctl -n 400 --no-pager -u dump1090-fa
– Logs begin at Sun 2018-08-05 13:41:00 UTC, end at Mon 2018-08-06 16:46:44 UTC. –
Aug 05 13:41:10 piaware systemd[1]: Starting dump1090 ADS-B receiver (FlightAware customization)…
Aug 05 13:41:10 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Aug 05 13:41:10 piaware dump1090-fa[534]: Sun Aug 5 13:41:10 2018 UTC dump1090-fa 3.6.2~bpo8+1 starting up.
Aug 05 13:41:10 piaware dump1090-fa[534]: rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000001)
Aug 05 13:41:11 piaware dump1090-fa[534]: Found Rafael Micro R820T tuner
Aug 05 13:41:11 piaware dump1090-fa[534]: rtlsdr: tuner gain set to 36.4 dB
Aug 05 13:42:50 piaware systemd[1]: Stopping dump1090 ADS-B receiver (FlightAware customization)…
Aug 05 13:42:50 piaware dump1090-fa[534]: Sun Aug 5 13:42:50 2018 UTC Caught SIGTERM, shutting down…
Aug 05 13:42:50 piaware dump1090-fa[534]: Sun Aug 5 13:42:50 2018 UTC Waiting for receive thread termination
Aug 05 13:42:50 piaware dump1090-fa[534]: Sun Aug 5 13:42:50 2018 UTC Normal exit.
Aug 05 13:42:50 piaware systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Aug 05 13:42:53 piaware systemd[1]: Starting dump1090 ADS-B receiver (FlightAware customization)…
Aug 05 13:42:53 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Aug 05 13:42:53 piaware dump1090-fa[1264]: Sun Aug 5 13:42:53 2018 UTC dump1090-fa 3.6.2~bpo8+1 starting up.
Aug 05 13:42:53 piaware dump1090-fa[1264]: rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000001)
Aug 05 13:42:53 piaware dump1090-fa[1264]: Found Rafael Micro R820T tuner
Aug 05 13:42:53 piaware dump1090-fa[1264]: rtlsdr: tuner gain set to 36.4 dB


#7

Ok ive changed the psu 5.1v 2.5 for another in loft
fans still doing its job all looks well
waits


#8

Actually on closer inspection there’s something a bit weird going on here; piaware thinks that both there is and isn’t a mlat client and dump1090 running. What is this install based on? Have you made any local changes? Do you have more than one receiver?

edit: you have two connections with the same feeder ID, different local IP addresses, and different MAC addresses. Please ensure that you use a different feeder ID for each physical device.


#9

I have several pi’s running
main 1pi in loft to sdrrtl v3 dongle, into triple filter and adsb 1090 filter to antenna
5.1v 2.5a spu
usb fan with seperate psu for it cooling things down


#10

i think you hit nail on the head i fired up second pi with adsb install maybe with same id will stop it now


#11

ok Stopped the pi 71 still got the problem

red mlat box

MLAT disabled/not synchronized/Latitude Longitude not set


#12

pi 71 offline

pi@piaware:~ sudo journalctl -n 400 --no-pager -u dump1090-fa -- Logs begin at Mon 2018-08-06 16:17:01 UTC, end at Mon 2018-08-06 17:34:30 UTC. -- Aug 06 16:17:11 piaware systemd[1]: Starting dump1090 ADS-B receiver (FlightAware customization)... Aug 06 16:17:11 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization). Aug 06 16:17:12 piaware dump1090-fa[538]: Mon Aug 6 16:17:12 2018 UTC dump1090-fa 3.6.2~bpo8+1 starting up. Aug 06 16:17:12 piaware dump1090-fa[538]: rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000001) Aug 06 16:17:12 piaware dump1090-fa[538]: Found Rafael Micro R820T tuner Aug 06 16:17:12 piaware dump1090-fa[538]: rtlsdr: tuner gain set to 36.4 dB Aug 06 17:18:18 piaware systemd[1]: Stopping dump1090 ADS-B receiver (FlightAware customization)... Aug 06 17:18:18 piaware dump1090-fa[538]: Mon Aug 6 17:18:18 2018 UTC Caught SIGTERM, shutting down.. Aug 06 17:18:18 piaware dump1090-fa[538]: Mon Aug 6 17:18:18 2018 UTC Waiting for receive thread termination Aug 06 17:18:18 piaware dump1090-fa[538]: Mon Aug 6 17:18:18 2018 UTC Normal exit. Aug 06 17:18:19 piaware systemd[1]: Starting dump1090 ADS-B receiver (FlightAware customization)... Aug 06 17:18:19 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization). Aug 06 17:18:19 piaware dump1090-fa[4833]: Mon Aug 6 17:18:19 2018 UTC dump1090-fa 3.6.2~bpo8+1 starting up. Aug 06 17:18:19 piaware dump1090-fa[4833]: rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000001) Aug 06 17:18:19 piaware dump1090-fa[4833]: Found Rafael Micro R820T tuner Aug 06 17:18:19 piaware dump1090-fa[4833]: rtlsdr: tuner gain set to 36.4 dB Aug 06 17:24:40 piaware systemd[1]: Stopping dump1090 ADS-B receiver (FlightAware customization)... Aug 06 17:24:40 piaware dump1090-fa[4833]: Mon Aug 6 17:24:40 2018 UTC Caught SIGTERM, shutting down.. Aug 06 17:24:40 piaware dump1090-fa[4833]: Mon Aug 6 17:24:40 2018 UTC Waiting for receive thread termination Aug 06 17:24:40 piaware dump1090-fa[4833]: Mon Aug 6 17:24:40 2018 UTC Normal exit. Aug 06 17:24:41 piaware systemd[1]: Starting dump1090 ADS-B receiver (FlightAware customization)... Aug 06 17:24:41 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization). Aug 06 17:24:41 piaware dump1090-fa[6342]: Mon Aug 6 17:24:41 2018 UTC dump1090-fa 3.6.2~bpo8+1 starting up. Aug 06 17:24:41 piaware dump1090-fa[6342]: rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000001) Aug 06 17:24:41 piaware dump1090-fa[6342]: Found Rafael Micro R820T tuner Aug 06 17:24:41 piaware dump1090-fa[6342]: rtlsdr: tuner gain set to 36.4 dB Aug 06 17:26:03 piaware systemd[1]: Stopping dump1090 ADS-B receiver (FlightAware customization)... Aug 06 17:26:03 piaware dump1090-fa[6342]: Mon Aug 6 17:26:03 2018 UTC Caught SIGTERM, shutting down.. Aug 06 17:26:03 piaware dump1090-fa[6342]: Mon Aug 6 17:26:03 2018 UTC Waiting for receive thread termination Aug 06 17:26:03 piaware dump1090-fa[6342]: Mon Aug 6 17:26:03 2018 UTC Normal exit. Aug 06 17:26:03 piaware systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization). Aug 06 17:26:07 piaware systemd[1]: Starting dump1090 ADS-B receiver (FlightAware customization)... Aug 06 17:26:07 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization). Aug 06 17:26:07 piaware dump1090-fa[6931]: Mon Aug 6 17:26:07 2018 UTC dump1090-fa 3.6.2~bpo8+1 starting up. Aug 06 17:26:07 piaware dump1090-fa[6931]: rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000001) Aug 06 17:26:07 piaware dump1090-fa[6931]: Found Rafael Micro R820T tuner Aug 06 17:26:07 piaware dump1090-fa[6931]: rtlsdr: tuner gain set to 36.4 dB pi@piaware:~


#13

3 Greens yesss
unable to find fault now
all working strange


#14

There is some feed-back system to restart things when no data is received.

That system is completely screwed up if you try to feed from two installations under one feeder-id as it will probably disconnect the working system when the “new” system comes up.
One system detects it’s not working properly restarts everything to try to get it working … then they change places … it’s ugly.

So it’s not so strange that it’s working now.
Just remove the feeder-id from one of your systems and the system will get a new id automatically.
Then you can claim that id and have them both running. There are threads on the subject if you need further advice just google “piaware feeder-id” and it should bring up relevant documents.