About 2 weeks ago, my feeder stopped working. It still says connected to Flightaware

FlightAware ADS-B Flight Tracking
1

Below is what i get when I issue a piaware-status.

Any idea what may be going on?

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

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

got ‘couldn’t open socket: connection refused’
dump1090 is NOT producing data on localhost:30005.

2

Does lsusb show your RTL dongle?

3

Piaware is one component, a decoder is the other. Piaware is looking for a connection but there is nothing.

Check if dump1090 is running by using
sudo systemctl status dump1090-fa
(assuming you’re running dump1090 and not a different decoder like readsb)

For more details use
sudo journalctl -xe | grep dump1090

4

Here is what I got:

sudo systemctl status dump1090-fa

dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
Loaded: loaded (/lib/systemd/system/dump1090-fa.service; disabled; vendor preset: enabled)
Active: inactive (dead)
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware

pi@piaware:~ $ sudo journalctl -xe | grep dump1090
Jan 30 08:52:36 piaware piaware[471]: attempting to start dump1090…
Jan 30 08:52:36 piaware piaware[471]: can’t start dump1090, no services that look like dump1090 found
Jan 30 08:54:35 piaware piaware[471]: 0 msgs recv’d from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
Jan 30 08:58:47 piaware piaware[471]: attempting to start dump1090…
Jan 30 08:58:47 piaware piaware[471]: can’t start dump1090, no services that look like dump1090 found
Jan 30 08:59:35 piaware piaware[471]: 0 msgs recv’d from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
Jan 30 09:04:35 piaware piaware[471]: 0 msgs recv’d from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
Jan 30 09:04:59 piaware piaware[471]: attempting to start dump1090…
Jan 30 09:04:59 piaware piaware[471]: can’t start dump1090, no services that look like dump1090 found
Jan 30 09:05:21 piaware sudo[5981]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/systemctl status dump1090-fa

5

Seem to be that dump1090 is gone

try
sudo journalctl -xe | grep dump1090-fa

and post the results here.

What do you get if you simply try to run

sudo apt install dump1090-fa

6

thanks for the awesome information.

7

Here is what I got…
pi@piaware:~ $ sudo journalctl -xe | grep dump1090-fa
pi@piaware:~ $
pi@piaware:~ $ sudo apt install dump1090-fa
Reading package lists… Done
Building dependency tree
Reading state information… Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
dump1090-fa : Depends: libbladerf2 (>= 0.2019.07) but it is not installable
Depends: libc6 (>= 2.29) but 2.28-10+rpi1 is to be installed
Depends: liblimesuite20.10-1 (>= 20.10.0+dfsg) but it is not installable
Depends: librtlsdr0 (>= 0.6.0) but 0.6-1+rpt1 is to be installed
E: Unable to correct problems, you have held broken packages.

8

Try fixing it with

sudo apt install -f

That forces to fix broken dependencies

9

The piaware name implies this is a piaware image.

If you didn’t remove dump1090-fa … something is completely broken.
Start over with a fresh image.

1 Like
10

The root of the problem was a bad raspberry pi device. Thanks everybody for your suggestions and assistance

EDIT: It was not the raspberry PI, it was the FA Data Receiver.

2 Likes
11

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