FlightAware Discussions

Issue with new install

I recently receive a second PiAware to add to my site.
Old Site: Site 117510
New Site: Site 140133

Old site is working fine. After getting new site up I was trying to add Flightware (https://pt.flightaware.com/adsb/piaware/install). After doing:


I am now getting:
pi@piaware:~ sudo apt-get update Hit:1 http://flightaware.com/mirror/raspbian/raspbian stretch InRelease Hit:2 http://flightaware.com/adsb/piaware/files/packages buster InRelease Hit:3 http://flightaware.com/adsb/piaware/files/packages stretch InRelease Hit:4 http://flightaware.com/mirror/raspberrypi/debian stretch InRelease Reading package lists... Done pi@piaware:~ sudo apt-get upgrade
Reading package lists… Done
Building dependency tree
Reading state information… Done
You might want to run ‘apt --fix-broken install’ to correct these.
The following packages have unmet dependencies:
piaware-release : Depends: piaware-support (= 4.0~bpo9+1) but 3.6.3 is installed
Depends: piaware (= 4.0~bpo9+1) but 3.6.3 is installed
Depends: beast-splitter (= 4.0~bpo9+1) but 3.6.3 is installed
Depends: dump1090-fa (= 4.0~bpo9+1) but 3.6.3 is installed
Depends: dump978-fa (= 4.0~bpo9+1) but it is not installed
Depends: skyaware978 (= 4.0~bpo9+1) but it is not installed
Depends: piaware-web (= 4.0~bpo9+1) but 3.6.3 is installed
E: Unmet dependencies. Try ‘apt --fix-broken install’ with no packages (or specify a solution).

any assistants will be greatly appreciated.

Your new site 140133 seems to be up and running fine on a 4.0 SD card install (although not receiving aircraft at the moment)

Are you still having issues? Those instructions you pasted are for package installers so those don’t apply to you.

I have gotten past the “fix” issues, but it still appears that it is not sending data for some reason.

Looks like it is not sending data:

pi@PiAware2:~ $ piaware-status
PiAware master process (piaware) is running with pid 480.
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.

Your feeder ID is 367449fb-664d-4775-a0ed-80fa473244e3 (from /var/cache/piaware/feeder_id)

Check on your radio. If everything seems ok, try using a different USB port.

Looks like I have messed up my configuration. The SYSLOG keeps getting:
Oct 31 20:20:03 PiAware2 adsbexchange-mlat[486]: Could not connect to 127.0.0.1:30005, retry in 30 seconds.
Oct 31 20:20:03 PiAware2 adsbexchange-feed[472]: Could not connect to 127.0.0.1:30005, retry in 30 seconds.
Oct 31 20:20:27 PiAware2 systemd[1]: dump1090-fa.service: Service hold-off time over, scheduling restart.
Oct 31 20:20:27 PiAware2 systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Oct 31 20:20:27 PiAware2 systemd[1]: Starting Generate receiver configuration…
Oct 31 20:20:27 PiAware2 generate-receiver-config[1705]: Updating /etc/default/dump978-fa …
Oct 31 20:20:27 PiAware2 generate-receiver-config[1705]: Updating /etc/default/skyaware978 …
Oct 31 20:20:27 PiAware2 generate-receiver-config[1705]: Updating /etc/default/beast-splitter …
Oct 31 20:20:27 PiAware2 generate-receiver-config[1705]: Updating /etc/default/dump1090-fa …
Oct 31 20:20:27 PiAware2 systemd[1]: Started Generate receiver configuration.
Oct 31 20:20:27 PiAware2 systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Oct 31 20:20:27 PiAware2 dump1090-fa[1708]: Sat Oct 31 20:20:27 2020 UTC dump1090-fa 4.0~bpo9+1 starting up.
Oct 31 20:20:27 PiAware2 dump1090-fa[1708]: rtlsdr: no supported devices found.
Oct 31 20:20:27 PiAware2 systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
Oct 31 20:20:27 PiAware2 systemd[1]: dump1090-fa.service: Unit entered failed state.
Oct 31 20:20:27 PiAware2 systemd[1]: dump1090-fa.service: Failed with result ‘exit-code’.
Oct 31 20:20:33 PiAware2 adsbexchange-mlat[486]: Could not connect to 127.0.0.1:30005, retry in 30 seconds.
Oct 31 20:20:33 PiAware2 adsbexchange-feed[472]: Could not connect to 127.0.0.1:30005, retry in 30 seconds.
Oct 31 20:20:57 PiAware2 systemd[1]: dump1090-fa.service: Service hold-off time over, scheduling restart.
Oct 31 20:20:57 PiAware2 systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Oct 31 20:20:57 PiAware2 systemd[1]: Starting Generate receiver configuration…
Oct 31 20:20:57 PiAware2 generate-receiver-config[1719]: Updating /etc/default/dump978-fa …
Oct 31 20:20:57 PiAware2 generate-receiver-config[1719]: Updating /etc/default/skyaware978 …
Oct 31 20:20:57 PiAware2 generate-receiver-config[1719]: Updating /etc/default/beast-splitter …
Oct 31 20:20:57 PiAware2 generate-receiver-config[1719]: Updating /etc/default/dump1090-fa …
Oct 31 20:20:57 PiAware2 systemd[1]: Started Generate receiver configuration.
Oct 31 20:20:57 PiAware2 systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Oct 31 20:20:57 PiAware2 dump1090-fa[1721]: Sat Oct 31 20:20:57 2020 UTC dump1090-fa 4.0~bpo9+1 starting up.
Oct 31 20:20:57 PiAware2 dump1090-fa[1721]: rtlsdr: no supported devices found.
Oct 31 20:20:57 PiAware2 systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
Oct 31 20:20:57 PiAware2 systemd[1]: dump1090-fa.service: Unit entered failed state.
Oct 31 20:20:57 PiAware2 systemd[1]: dump1090-fa.service: Failed with result ‘exit-code’.

I noticed my “feeder-id” in piaware-config.dat file so I have added that, but it looks like some of the things I have done to try to fix it might have hosed the software/configuration. At this point If I could “recreate” the SD card that was sent and start with that it might fix the issue.

Doesn’t seem to be recognizing a radio connected. Did you check on that? You can try the radio from your other PiAware if convenient

I swapped them a number of times and at this time I am getting numbers on both of them! Looking at the pages:


They are both showing some planes the same and some different, but “last seen” are both within saying seen less than 10 minutes ago. Will leave them both as they are for the next 24 hours and see how it goes.