FlightAware Discussions

Enhancements to Dump978 (UAT decoder)

Please show the output of these commands:

cd /var/lib/collectd/rrd/localhost/dump1090-localhost
ls -l *978*
sudo /usr/share/graphs1090/graphs1090.sh
cd /var/lib/collectd/rrd/localhost/dump1090-localhost
ls -l *978*

pi@piaware:/var/lib/collectd/rrd/localhost/dump1090-localhost $ ls -l *978*
-rw-r--r-- 1 root root 515256 Aug 14 14:35 dump1090_aircraft-recent_978.rrd
-rw-r--r-- 1 root root 129316 Aug 14 14:35 dump1090_dbfs-median_978.rrd
-rw-r--r-- 1 root root 129316 Aug 14 14:35 dump1090_dbfs-min_signal_978.rrd
-rw-r--r-- 1 root root 129316 Aug 14 14:35 dump1090_dbfs-peak_signal_978.rrd
-rw-r--r-- 1 root root 129316 Aug 14 14:35 dump1090_dbfs-quart1_978.rrd
-rw-r--r-- 1 root root 129316 Aug 14 14:35 dump1090_dbfs-quart3_978.rrd
-rw-r--r-- 1 root root 258272 Aug 14 14:35 dump1090_gps-recent_978.rrd
-rw-r--r-- 1 root root 387228 Aug 14 14:35 dump1090_messages-messages_978.rrd
-rw-r--r-- 1 root root 387228 Aug 14 14:35 dump1090_range-max_range_978.rrd
-rw-r--r-- 1 root root 129316 Aug 14 14:35 dump1090_range-median_978.rrd
-rw-r--r-- 1 root root 129316 Aug 14 14:35 dump1090_range-minimum_978.rrd
-rw-r--r-- 1 root root 129316 Aug 14 14:35 dump1090_range-quart1_978.rrd
-rw-r--r-- 1 root root 129316 Aug 14 14:35 dump1090_range-quart3_978.rrd
-rw-r--r-- 1 root root 258272 Aug 14 14:35 dump1090_tisb-recent_978.rrd

… and …

sudo /usr/share/graphs1090/graphs1090.sh
10559 (process ID) old priority 0, new priority 19
702x362
702x362
702x362
702x362
702x362
1423x371
702x362
702x362
702x362
702x362
702x362
702x362
1423x371
702x362
702x362
702x362
702x362
702x362
702x362

That makes no sense, all the graphs where created, try refreshing the page or clicking on the link where the graph should be.

Ok. I had to force my browser to reload the page from the server, just a regular refresh kept showing the image I posted above. All good now.

I’ve added some cache busting that hopefully fixes the problem for other people before it becomes a problem.
(Though the problem is only existent for people updating from a version that didn’t have that graph)

1 Like

press F5 to reload the webpage.

Is there any advice on how to detect when dump978 is broken and restarting dump978 or rebooting the pi? Have a dedicated pi for 978. After noticing little activity this morning, and it picked up 2 978 planes after a reboot. Are there any better ways to detect dump978-fa is misbehaving? Would sudo system restart dump978-fa possibly be faster than a reboot?
Is an orange Piaware Dongle usable for 978 MHz?

piaware will attempt to restart dump978-fa anyway.

Can you show your logs:

sudo journalctl -u piaware --no-pager
sudo journalctl -u dump978-fa --no-pager

And if possible, don’t photograph your screen with a camera.
You should be able to select the text in putty (select automaticlaly copies) and paste it here or on pastebin with Ctrl-V.

If piaware emits a message to the journal when dump978-fa is not giving data (which is normally the case), then you can listen for that and reboot the pi or forcibly restart dump978-fa
sudo pkill -9 dump978-fa; sleep .5; sudo systemctl restart dump978-fa

For dump1090-fa i’ve used this script before:

#!/bin/bash
#exec &>>/var/feed/wedge
sleep 20

journalctl -b -0 -f -n0 | grep 'No data received from the SDR for a long time' --line-buffered | {
	while read line
	do
		date
		systemctl kill -s 9 dump1090-fa
		sleep .3
		systemctl restart dump1090-fa
	done
}

Then you open crontab with sudo crontab -e and add this line

@reboot	/root/.wedge.sh

Assuming you saved the above script to /root/.wedge.sh

On a Mac a forced reload is command-shift-R

Aug 24 19:20:56 piawaredump978 piaware[605]: 1796 msgs recv’d from dump978-fa (0 in last 5m); 1785 msgs sent to FlightAware
Aug 24 19:25:26 piawaredump978 piaware[605]: no new messages received in 3608 seconds, it might just be that there haven’t been any aircraft nearby but I’m going to try to restart everything, just in case…
Aug 24 19:25:27 piawaredump978 piaware[605]: faup978 exited with SIG SIGHUP
Aug 24 19:25:27 piawaredump978 piaware[605]: attempting to restart dump978…

Aug 24 19:25:27 piawaredump978 piaware[605]: attempting to restart dump978-fa using ‘systemctl --no-block try-restart dump978-fa.service < /dev/null’…
Aug 24 19:25:27 piawaredump978 sudo[21222]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl --no-block try-restart dump978-fa.service

pi@piawaredump978:~ $ cat jrl_piaware.txt
– Logs begin at Sat 2019-08-24 09:10:09 EDT, end at Sat 2019-08-24 21:27:42 EDT. –
Aug 24 09:10:19 piawaredump978 systemd[1]: Started FlightAware ADS-B uploader.
Aug 24 09:10:21 piawaredump978 piaware[605]: creating pidfile /run/piaware/piaware.pid
Aug 24 09:10:21 piawaredump978 piaware[605]: ****************************************************
Aug 24 09:10:21 piawaredump978 piaware[605]: piaware version 3.7.1 is running, process ID 605
Aug 24 09:10:21 piawaredump978 piaware[605]: your system info is: Linux piawaredump978 4.19.58-v7+ #1245 SMP Fri Jul 12 17:25:51 BST 2019 armv7l GNU/Linux
Aug 24 09:10:23 piawaredump978 piaware[605]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Aug 24 09:10:23 piawaredump978 piaware[605]: Connection with adept server at piaware.flightaware.com/1200 established
Aug 24 09:10:23 piawaredump978 piaware[605]: TLS handshake with adept server at piaware.flightaware.com/1200 completed
Aug 24 09:10:24 piawaredump978 piaware[605]: FlightAware server certificate validated
Aug 24 09:10:24 piawaredump978 piaware[605]: encrypted session established with FlightAware
Aug 24 09:10:24 piawaredump978 sudo[955]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp --wide --all --numeric
Aug 24 09:10:24 piawaredump978 sudo[955]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 24 09:10:24 piawaredump978 sudo[955]: pam_unix(sudo:session): session closed for user root
Aug 24 09:10:25 piawaredump978 piaware[605]: 1090ES support disabled by local configuration setting: receiver-type
Aug 24 09:10:25 piawaredump978 sudo[972]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp --wide --all --numeric
Aug 24 09:10:25 piawaredump978 sudo[972]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 24 09:10:25 piawaredump978 sudo[972]: pam_unix(sudo:session): session closed for user root
Aug 24 09:10:25 piawaredump978 piaware[605]: ADS-B data program ‘dump978-fa’ is listening on port 30978, so far so good
Aug 24 09:10:25 piawaredump978 piaware[605]: Starting faup978: /usr/lib/piaware/helpers/faup978 --connect localhost:30978
Aug 24 09:10:25 piawaredump978 piaware[605]: Started faup978 (pid 982) to connect to dump978-fa
Aug 24 09:10:25 piawaredump978 piaware[605]: faup978(982): Connecting to localhost:30978
Aug 24 09:10:25 piawaredump978 piaware[605]: faup978(982): Connected to [::1]:30978
Aug 24 09:10:25 piawaredump978 piaware[605]: adept reported location: xx.xxxxx, -xx.xxxxx, xx ft AMSL
Aug 24 09:10:25 piawaredump978 piaware[605]: logged in to FlightAware as user xxx
Aug 24 09:10:25 piawaredump978 piaware[605]: my feeder ID is xxx
Aug 24 09:10:25 piawaredump978 piaware[605]: site statistics URL: https://flightaware.com/adsb/stats/user/xxx
Aug 24 09:10:25 piawaredump978 piaware[605]: multilateration data requested
Aug 24 09:10:25 piawaredump978 piaware[605]: multilateration support disabled by local configuration (ADS-B receiver-type not configured)
Aug 24 09:10:26 piawaredump978 piaware[605]: piaware received a message from dump978-fa!
Aug 24 09:10:47 piawaredump978 piaware[605]: piaware has successfully sent several msgs to FlightAware!
Aug 24 09:10:56 piawaredump978 piaware[605]: 10 msgs recv’d from dump978-fa; 10 msgs sent to FlightAware
Aug 24 09:11:37 piawaredump978 piaware[605]: timed out waiting for alive message from FlightAware, reconnecting…
Aug 24 09:11:37 piawaredump978 piaware[605]: reconnecting in 55 seconds…
Aug 24 09:12:32 piawaredump978 piaware[605]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Aug 24 09:12:32 piawaredump978 piaware[605]: Connection with adept server at piaware.flightaware.com/1200 established
Aug 24 09:12:33 piawaredump978 piaware[605]: TLS handshake with adept server at piaware.flightaware.com/1200 completed
Aug 24 09:12:33 piawaredump978 piaware[605]: FlightAware server certificate validated
Aug 24 09:12:33 piawaredump978 piaware[605]: encrypted session established with FlightAware
Aug 24 09:12:33 piawaredump978 sudo[3155]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp --wide --all --numeric
Aug 24 09:12:33 piawaredump978 sudo[3155]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 24 09:12:33 piawaredump978 sudo[3155]: pam_unix(sudo:session): session closed for user root
Aug 24 09:12:34 piawaredump978 piaware[605]: logged in to FlightAware as user xxx
Aug 24 09:12:34 piawaredump978 piaware[605]: my feeder ID is
Aug 24 09:12:34 piawaredump978 piaware[605]: site statistics URL: xxx
Aug 24 09:12:34 piawaredump978 piaware[605]: multilateration data requested
Aug 24 09:12:34 piawaredump978 piaware[605]: multilateration support disabled by local configuration (ADS-B receiver-type not configured)
Aug 24 09:15:56 piawaredump978 piaware[605]: 63 msgs recv’d from dump978-fa (53 in last 5m); 52 msgs sent to FlightAware
Aug 24 13:35:56 piawaredump978 piaware[605]: 1042 msgs recv’d from dump978-fa (0 in last 5m); 1031 msgs sent to FlightAware
Aug 24 14:20:26 piawaredump978 piaware[605]: no new messages received in 3840 seconds, it might just be that there haven’t been any aircraft nearby but I’m going to try to restart everything, just in case…
Aug 24 14:20:27 piawaredump978 piaware[605]: faup978 exited with SIG SIGHUP
Aug 24 14:20:27 piawaredump978 piaware[605]: attempting to restart dump978…
Aug 24 14:20:27 piawaredump978 sudo[29324]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/invoke-rc.d --query dump978-fa restart
Aug 24 14:20:27 piawaredump978 sudo[29324]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 24 14:20:27 piawaredump978 sudo[29324]: pam_unix(sudo:session): session closed for user root
Aug 24 14:20:27 piawaredump978 piaware[605]: attempting to restart dump978-fa using ‘systemctl --no-block try-restart dump978-fa.service < /dev/null’…
Aug 24 14:20:27 piawaredump978 sudo[29336]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl --no-block try-restart dump978-fa.service
Aug 24 14:20:27 piawaredump978 sudo[29336]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 24 14:20:27 piawaredump978 sudo[29336]: pam_unix(sudo:session): session closed for user root
Aug 24 14:20:27 piawaredump978 piaware[605]: dump978 restart appears to have been successful
Aug 24 14:20:37 piawaredump978 sudo[29416]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp --wide --all --numeric
Aug 24 14:20:37 piawaredump978 sudo[29416]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 24 14:20:37 piawaredump978 sudo[29416]: pam_unix(sudo:session): session closed for user root
Aug 24 14:20:37 piawaredump978 piaware[605]: ADS-B data program ‘dump978-fa’ is listening on port 30978, so far so good
Aug 24 14:20:37 piawaredump978 piaware[605]: Starting faup978: /usr/lib/piaware/helpers/faup978 --connect localhost:30978
Aug 24 14:20:37 piawaredump978 piaware[605]: Started faup978 (pid 29424) to connect to dump978-fa
Aug 24 14:20:37 piawaredump978 piaware[605]: faup978(29424): Connecting to localhost:30978
Aug 24 14:20:37 piawaredump978 piaware[605]: faup978(29424): Connected to [::1]:30978
Aug 24 14:20:57 piawaredump978 piaware[605]: 1042 msgs recv’d from dump978-fa (0 in last 5m); 1031 msgs sent to FlightAware
Aug 24 15:35:56 piawaredump978 piaware[605]: 1044 msgs recv’d from dump978-fa (1 in last 5m); 1033 msgs sent to FlightAware

A screenshot after changing desktop color settings

See here, piaware restarted dump978-fa and it worked.

(You never know if it’s just that there were no messages for an hour or if dump978-fa actually stopped working.)

Sometimes that restarting won’t work.
One can listen for that line and forcibly kill dump978-fa or even reboot.
Rebooting is of course problematic if you have no UAT traffic an night because the pi will reboot every hour at night.

1 Like

Interesting, i was wondering how that could happen :slight_smile:
The graphs were readable, i was just a little confused how that might happen.

1 Like

Can we NOT post long txt logs here directly? The junk from above, copy/pasted in word, resulted in 6900 words and 18 pages.
This thread was about Enhancements to UAT decoder, not troubleshooting one installation.

Makes this thread useless for everyone else. Attach the logs as files or PM if you need customized troubleshooting.

I should probably ask people to open a thread about their problem.

But people could just do that themselves instead of hijacking threads -.-
Oh well ¯\(ツ)

1 Like

sorry, didn’t think. will edit. good thing it only allows 32000 char posts!

Thanks again for your help!

I am first to admit that I am guilty of that too. And thankfull when someone pulls me away when I do that.
Sometimes there is merit for a small off-topic, brings fresh ideas. Sometimes just messes up good threads.

So it goes.

Still the wrong thread, why don’t you open a new one with an appropriate name.

dump978-fa crashing or something.

Anyhow, try if these commands improve your situation:

sudo sed -i -e 's/User=dump978/\0\nTimeoutStopSec=5\nSendSIGHUP=yes/' /lib/systemd/system/dump978-fa.service
sudo reboot

One of the common problems with dongles stopping to work is an insufficient power supply.

3 Likes