Dump978-fa.service

FlightAware ADS-B Flight Tracking
1

Hi,
I started two days ago with 3.8.1 and raspberry. I’m impressive by the work. and the capacity to receive information from planes as far as 230 km. Thank you to the team.
I have a question about dump978 and skyaware978

I understand that dump978 is for UAT and this is different from dump1090.
The result of command $ piaware-status indicates in bold hereunder:
PiAware master process (piaware) is running with pid 725.
PiAware ADS-B client (faup1090) is running with pid 19114.
PiAware ADS-B UAT client (faup978) is not running (disabled by configuration settings)
PiAware mlat client (fa-mlat-client) is running with pid 19147.
Local ADS-B receiver (dump1090-fa) is running with pid 19083.

dump1090-fa (pid 19083) is listening for ES connections on port 30005.
faup1090 is connected to the ADS-B receiver.
piaware is connected to FlightAware.

dump1090 is producing data on localhost:30005.

Your feeder ID is d7b15c75-xxxx-xxxx-xxxx-xxxxxxxxx (from /var/cache/piaware/feeder_id)

so why there are such messages in /var/log/syslog file?

Apr 17 18:25:51 localhost skyaware978[19070]: Connecting to localhost:30978
Apr 17 18:25:51 localhost skyaware978[19070]: connection to [::1]:30978 failed: Connection refused
Apr 17 18:25:51 localhost skyaware978[19070]: connection to 127.0.0.1:30978 failed: Connection refused
Apr 17 18:25:51 localhost skyaware978[19070]: Connection failed: Connection refused
Apr 17 18:26:17 localhost systemd[1]: dump978-fa.service: Service RestartSec=30s expired, scheduling restart.
Apr 17 18:26:17 localhost systemd[1]: dump978-fa.service: Scheduled restart job, restart counter is at 4941.
Apr 17 18:26:17 localhost systemd[1]: Stopped dump978 ADS-B UAT receiver.
Apr 17 18:26:17 localhost systemd[1]: Started dump978 ADS-B UAT receiver.
Apr 17 18:26:17 localhost dump978-fa[29310]: raw-port: listening for connections on 0.0.0.0:30978
Apr 17 18:26:17 localhost dump978-fa[29310]: raw-port: listening for connections on [::]:30978
Apr 17 18:26:17 localhost dump978-fa[29310]: json-port: listening for connections on 0.0.0.0:30979
Apr 17 18:26:17 localhost dump978-fa[29310]: json-port: listening for connections on [::]:30979
Apr 17 18:26:17 localhost dump978-fa[29310]: usb_claim_interface error -6
Apr 17 18:26:17 localhost dump978-fa[29310]: usb_claim_interface error -6
Apr 17 18:26:17 localhost dump978-fa[29310]: SoapySDR: using maximum manual gain 0.0 dB
Apr 17 18:26:17 localhost dump978-fa[29310]: SoapySDR: using stream setting buffsize=262144
Apr 17 18:26:21 localhost skyaware978[19070]: Connecting to localhost:30978
Apr 17 18:26:21 localhost skyaware978[19070]: Connected to [::1]:30978
Apr 17 18:26:21 localhost dump978-fa[29310]: [::]:30978: accepted a connection from [::1]:35524
Apr 17 18:26:22 localhost dump978-fa[29310]: Message source reports error: TIMEOUT
Apr 17 18:26:22 localhost dump978-fa[29310]: Abnormal exit
Apr 17 18:26:22 localhost skyaware978[19070]: Connection failed: End of file
Apr 17 18:26:22 localhost systemd[1]: dump978-fa.service: Main process exited, code=exited, status=1/FAILURE
Apr 17 18:26:22 localhost systemd[1]: dump978-fa.service: Failed with result ‘exit-code’.
Apr 17 18:26:52 localhost skyaware978[19070]: Connecting to localhost:30978
Apr 17 18:26:52 localhost skyaware978[19070]: connection to [::1]:30978 failed: Connection refused
Apr 17 18:26:52 localhost skyaware978[19070]: connection to 127.0.0.1:30978 failed: Connection refused
Apr 17 18:26:52 localhost skyaware978[19070]: Connection failed: Connection refused
Apr 17 18:26:52 localhost systemd[1]: dump978-fa.service: Service RestartSec=30s expired, scheduling restart.
Apr 17 18:26:52 localhost systemd[1]: dump978-fa.service: Scheduled restart job, restart counter is at 4942.
Apr 17 18:26:52 localhost systemd[1]: Stopped dump978 ADS-B UAT receiver.
Apr 17 18:26:52 localhost systemd[1]: Started dump978 ADS-B UAT receiver.
Apr 17 18:26:53 localhost dump978-fa[29332]: raw-port: listening for connections on 0.0.0.0:30978
Apr 17 18:26:53 localhost dump978-fa[29332]: raw-port: listening for connections on [::]:30978
Apr 17 18:26:53 localhost dump978-fa[29332]: json-port: listening for connections on 0.0.0.0:30979
Apr 17 18:26:53 localhost dump978-fa[29332]: json-port: listening for connections on [::]:30979
Apr 17 18:26:53 localhost dump978-fa[29332]: usb_claim_interface error -6
Apr 17 18:26:53 localhost dump978-fa[29332]: usb_claim_interface error -6
Apr 17 18:26:53 localhost dump978-fa[29332]: SoapySDR: using maximum manual gain 0.0 dB
Apr 17 18:26:53 localhost dump978-fa[29332]: SoapySDR: using stream setting buffsize=262144
Apr 17 18:26:58 localhost dump978-fa[29332]: Message source reports error: TIMEOUT
Apr 17 18:26:58 localhost dump978-fa[29332]: Abnormal exit
Apr 17 18:26:58 localhost systemd[1]: dump978-fa.service: Main process exited, code=exited, status=1/FAILURE
Apr 17 18:26:58 localhost systemd[1]: dump978-fa.service: Failed with result ‘exit-code’.

What is wrong and how I can correct ?
Thank you for your help
Phil

2

You shouldn’t install it if you don’t need it.

The piaware-config is only for piaware sd-card images.
As such piaware-status is misleading.

Uninstall it …

3

The Piaware SD card image has both the dump978-fa and skyaware978 pre-installed, but disabled by default.

If you dont want them in sys log, dont use piaware sd card image. Instead write Raspbian Lite image to your microSD card, then install only piaware and dump1090-fa by package install.

4

As his piaware status shows … it’s disabled in the piaware config.
Thus it running means he is on a non piaware Raspbian already.

That syslog is not how the piaware sd-card with 978 disabled looks …

5

For completeness, this means that piaware is not even trying to connect to dump978 because you have told it (via the piaware config) that you’re not providing 978 data.

If you are actually running dump978 successfully and want to feed data from it, then you need to tell piaware that. (Piaware sdcard images sort this out automatically - both the 978 data feed and whether dump978-fa itself is started are controlled by the same config option on that sdcard image)

6

Hi, Thank you for your answers

I understand the reason why.
I follow all the steps indicated on webpage PiAware - dump1090 ADS-B integration with FlightAware - FlightAware
and make an installation on an existing raspberry, so I didn’t use a piaware sd-card images.
However the step number 4 should not have been done as in Europe UAT is not there.
So

apt-get remove dump978-fa

and

apt-get remove skyaware978

no more error in syslog file. seems good.
Thank you all
Phil

2 Likes
7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.