FlightAware Discussions

Faup978 not currently running?

I’m a little confused below. My Pi definitely IS producing data, but when I check the status is says it is not. Am I missing something?

Thanks.

pi@Raspberrypi3ADSB:~ $ piaware-status
PiAware master process (piaware) is running with pid 683.
PiAware ADS-B client (faup1090) is running with pid 937.
PiAware ADS-B UAT client (faup978) is not running (disabled by configuration settings)
PiAware mlat client (fa-mlat-client) is running with pid 8900.
Local ADS-B receiver (dump1090-fa) is running with pid 479.

dump1090-fa (pid 479) 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.

You have two sites; one does not have UAT configured. I assume that’s the site shown above. faup978 only runs on UAT receivers.

Thanks - you had me second guessing that I was looking at the wrong Pi. “Raspberrypi3ADSB” is my Pi with both 1090 and 978 receivers. I think I found the difference though. Sudo. When I use sudo, it reports normally. Otherwise, it says it’s NOT running.

pi@Raspberrypi3ADSB:~ $ sudo piaware-status
PiAware master process (piaware) is running with pid 683.
PiAware ADS-B client (faup1090) is running with pid 937.
PiAware ADS-B UAT client (faup978) is running with pid 2708.
PiAware mlat client (fa-mlat-client) is running with pid 8900.
Local ADS-B receiver (dump1090-fa) is running with pid 479.
Local ADS-B UAT receiver (dump978-fa) is running with pid 2648.

dump1090-fa (pid 479) is listening for ES connections on port 30005.
dump978-fa (pid 2648) is listening for UAT connections on port 30978.
faup1090 is connected to the ADS-B receiver.
faup978 is connected to the ADS-B UAT receiver.
piaware is connected to FlightAware.

dump978 is producing data on localhost:30978.
dump1090 is producing data on localhost:30005.

Sounds like the pi user can’t read the piaware config file (permissions?)

You could try running piaware-config and sudo piaware-config and comparing the output to check if it’s a problem reading a specific config file.

Yes, that’s what those outputs are.

sudo piaware-config
vs.
piaware-config

If there is a permission issue, is it a problem? Everything seems to work. I just need “sudo” when checking the status.

piaware-config not piaware-status

Ah, silly me. Yes, “piaware-config” results in permission denied:

pi@Raspberrypi3ADSB:~ $ piaware-config
warning: /etc/piaware.conf: failed to read config file: couldn't open "/etc/piaware.conf": permission denied
pi@Raspberrypi3ADSB:~ $ sudo piaware-config
allow-auto-updates             yes                            # value set at /etc/piaware.conf:7
allow-manual-updates           yes                            # value set at /etc/piaware.conf:8
receiver-type                  rtlsdr                         # value set at /etc/piaware.conf:12
rtlsdr-device-index            00001090                       # value set at /etc/piaware.conf:10
uat-receiver-type              sdr                            # value set at /etc/piaware.conf:9
uat-sdr-device                 driver=rtlsdr,serial=00000978  # value set at /etc/piaware.conf:11

I also learned that if you have a standard package install (not doing anything really custom), but with 1090 and 978. Running piaware-status vs sudo piaware-status will result in a different output. It was messing with my head for quite a bit…

The original reason for having /etc/piaware.conf not world readable was that it could contain sensitive info (username/password). Since we’ve moved away from that now, making it world-readable is probably the simple fix here.