Dump978-fa crashing

FlightAware ADS-B Flight Tracking
1

Are others having to restart dump978-fa regularly? This morning 3 UATs appeared after rebooting through FA/My ADS-B.

image
image2318×1252 614 KB

2

Is this dump978 or dump978-fa? I run both. The older dump978 did this,it just stopped working, It was still running, just no data. I have a cron job running to restart it every two hours.
You should also post the version you are running.

2 Likes
3

The modification to the service file probably won’t help as systemd should already kill it in case it fails to restart.
But it doesn’t hurt either.

1 Like
4

Trying a shorter USB power cord. Power supply issue would be a great and simple cure.

5

Given that systemd will already auto-restart it, this isn’t “dump978-fa crashing” (I’m not aware of any bugs in dump978-fa that would cause it to crash), but rather “dump978-fa isn’t giving me the data I expect it to give me”.

Things to check (before rebooting):

  • is the Pi still accessible?
  • is dump978-fa still consuming CPU?
  • do you have any undervoltage events reported?
  • is there anything reported in dmesg or the dump978-fa logs?
6

piaware-status
PiAware master process (piaware) is running with pid 621.
PiAware ADS-B client (faup1090) is not running.
PiAware ADS-B UAT client (faup978) is not running.
PiAware mlat client (fa-mlat-client) is not running.
Local ADS-B UAT receiver (dump978-maint.s) is running with pid 636.
Local ADS-B UAT receiver (dump978) is running with pid 1402.
Local ADS-B UAT receiver (dump978-maint.s) is running with pid 1405.

no program appears to be listening for connections on port 30005.
no program appears to be listening for connections on port 30978.
faup1090 is NOT connected to the ADS-B receiver.
faup978 is NOT connected to the ADS-B UAT receiver.
piaware is connected to FlightAware.

7

What is “dump978-maint”, and why is piaware-status reporting that you are running dump978 not dump978-fa? Also, you didn’t answer the questions above.

8

It looks like Joe’s adsb receiver project setup for the old version of dump978. This is the version that I have to restart every two hours.
It has faup978 too, which is odd.

1 Like
9

Seems to be better now after removing some items from rc.local
pi@piawaredump978:~ $ sudo piaware-status
PiAware master process (piaware) is running with pid 619.
PiAware ADS-B client (faup1090) is not running.
PiAware ADS-B UAT client (faup978) is running with pid 2921.
PiAware mlat client (fa-mlat-client) is not running.
Local ADS-B UAT receiver (dump978-fa) is running with pid 1940.

no program appears to be listening for connections on port 30005.
dump978-fa (pid 1940) is listening for connections on port 30978.
faup1090 is NOT connected to the ADS-B receiver.
faup978 is connected to the ADS-B UAT receiver.
piaware is connected to FlightAware.

got ‘couldn’t open socket: connection refused’

Standard Pi power supplies (Pro-Elec 5.25V 2.4A Microusb) seemed to be worse than a samsung phone charger that outputs 5.18 V

Need examples to run for the questions you ask as I am a Noob for linux.
FA 3.7.1 image was the only one I could get to work as a 978 only feeder. What’s a sanctioned way of feeding other sites?

10

Maybe the topic title could be changed to something more appropriate.

Things to check (before rebooting):

is the Pi still accessible?  Y    With the pro-elec supplies it seemed more flaky than with the samsung.
is dump978-fa still consuming CPU?   dump 978 was running all the time., and dump978-fa would popup
do you have any undervoltage events reported?    possible. didn't know how to run dmesg, and no monitor connected to pi.   Not sure if realvnc screen gets the voltage lightning bolts.
is there anything reported in dmesg or the dump978-fa logs?  please provide commands to get the data.

Thanks for your help!

11

Other sites don’t understand the protocol given by dump978-fa.

If you don’t understand how things work and install random stuff, it’s not gonna work.
That’s exactly what happened.
dump978-fa wasn’t even running, you were using an old version of dump978, or they were fighting over the dongle.

So you don’t know how to type dmesg into the console?

Anyway appropriate commands for logs can be found here:
Debug commands ¡ wiedehopf/adsb-wiki Wiki ¡ GitHub

If other feed sites don’t support UAT on port 30978, i don’t see a particular reason to help them get the data.
Anyway this post could help you, if you are able to figure out how to make it work:
UAT Translation from Dump978-fa - #9 by KC1IUC

The problem is, i don’t even know if other sites want the data in that form.
Or people could feed the translated data to FA.
Also it’s FA developing dump978, so i don’t see a reason to make it easy to feed other services with that data. As i said if they are interested, they should grab the data themselves.

1 Like
12

I suggest you just use that sdcard image then and don’t try to install extra 978 stuff; as you’ve discovered, it interferes (it sounds like you’ve installed additional older software that’s not aware of or compatible with the 3.7.1 image)

1 Like