Trouble installing - bad package?

FlightAware ADS-B Flight Tracking
1

I’m having trouble with the install instructions. Following the step-by-step on the website when I try to install piaware I get:

The following packages have unmet dependencies:
piaware : Depends: libboost-regex1.74.0-icu67 but it is not installable
Depends: libc6 (>= 2.29) but 2.28-10+rpt2+rpi1 is to be installed
Depends: libffi7 (>= 3.3~20180313) but it is not installable
Depends: libgcc-s1 (>= 3.5) but it is not installable
Depends: libmpdec3 but it is not installable
Depends: libreadline8 (>= 7.0~beta) but it is not installable
Depends: libstdc++6 (>= 9) but 8.3.0-6+rpi1 is to be installed
E: Unable to correct problems, you have held broken packages.

Any thoughts?

2

Possibly the wrong repository installed for your OS version.
Try the FA part here: https://github.com/wiedehopf/adsb-wiki/wiki/Raspbian-Lite:-ADS-B-receiver

3

I did pick the one for my distribution, just concerning that it’s not complete. And thanks for the links, but that just kind of muddied the water a bit. Hopefully I’ll get some other insights.

4

If you give more info about your distribution, it will make it easy for others to help you.

(1) Which model of Pi you are using?
(2) Please post output of following commands:

uname -a

lsb_release -a

apt-cache policy piaware

 

5

I’m trying to load the FA software on a Pi-Star hotspot running on a Raspberry Pi Zero. Unfortunately, the Pi-Star software is only available as a complete image, so I have to use it has the base. Here is the other info: (I’m going to assume the absence of lsb modules is likely at the core of my problem?)

pi-star@pi-star(rw):~$ uname -a
Linux pi-star 5.10.63+ #1459 Wed Oct 6 16:40:27 BST 2021 armv6l GNU/Linux
pi-star@pi-star(ro):~$ lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 10 (buster)
Release: 10
Codename: buster
pi-star@pi-star(ro):~$ apt-cache policy piaware
piaware:
Installed: (none)
Candidate: 7.2
Version table:
7.2 500
500 http://flightaware.com/adsb/piaware/files/packages bullseye/piaware armhf Packages
7.2~bpo10+1 500
500 http://flightaware.com/adsb/piaware/files/packages buster/piaware armhf Packages

1 Like
6

 

Above output shows hat you have installed flightaware’s TWO repositories, one for buster other for bullseye. This is what is causing the problem.

STEP-1: Issue command below to remove Flightaware’s BOTH repositories from /etc/apt/sources.list.d

sudo dpkg --purge piaware-repository

STEP-2: Install Flightaware repository only for BUSTER

The first command is very long and its right half may not be directly visible
Please scroll right to see and copy the long command in full

wget https://flightaware.com/adsb/piaware/files/packages/pool/piaware/p/piaware-support/piaware-repository_7.2~bpo10+1_all.deb     

sudo dpkg -i piaware-repository_7.2~bpo10+1_all.deb    

sudo apt update

 

STEP-3: Install Piaware & Dump1090-fa

sudo apt install piaware    

sudo apt install dump1090-fa  

sudo reboot
7

Well, there you go. I thought I installed the other version (which I got by mistake) but apparently I did not!

The installation appears to have worked, now I only need to get it claimed. Still working on that issue. It doesn’t want to connect automatically and the other application (pi-star) takes over the website access on port 80 - so I can’t see the link to claim manually. Trying to find the unique ID.

But thanks for the help - a stupid mistake on my part.

Jon

8 
pi@orangepipc:~$ sudo journalctl -u piaware -b | grep "feeder ID"

Jul 18 12:44:46 orangepipc piaware[1657]: my feeder ID is xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
9

Tried it - returns blank. No ID. The real question is, where does one get a Feeder-ID. Since the web page cannot find my system automatically, I need to link it manually. But where does one get an ID?

I’ve chatted with support - and they don’t know either!! Looking for any other answers before I just give up. :frowning:

10

Dont try to claim from Pi’s browser if you have problem.

Instead, try following address from another computer (Desktop/Laptop/Phone) on same local netwrok (LAN/router) as the Pi is. You must login to your flightaware account from the Laptop/Desktop/Phone from which you are going to the claims page.

https://flightaware.com/adsb/piaware/claim

 

11

That is what I have been doing. The Pi is running headless, I have only SSH access.

12

What is output of following commands?

ping -c 3 google.com   

ping -c 3 flightaware.com

 

13

Both pings are successful.

14

You automatically get an ID once you feed data successfully.
It will be in the piaware log.

sudo journalctl -u piaware -e
15

@fajg22 says he already tried it, but no harm in trying again, this time with @wiedehopf 's command.

May also try my command again, but this time without -b 

sudo journalctl -u piaware  | grep "feeder ID"
16

Well the log will say something for piaware, if you don’t look specifically for the ID you might actually find useful info.

17

Nothing shows up for feeder id. As I think I noted before, when I run “piaware-config -showall” it reports that the Feeder-ID is “”

18

Curiosity - (a) if I don’t have a Feeder-ID, how does it feed data? and (b) if the system requires manual association, where does one get a Feeder-ID for a new feeder station?

19

FYI - the output of piaware-config -showall

#adaptive-burst no # using default value
#adaptive-dynamic-range yes # using default value
#adaptive-dynamic-range-target # no value set and no default value
#adaptive-max-gain # no value set and no default value
#adaptive-min-gain # no value set and no default value
#adept-serverhosts “piaware.flightaware.com piaware.flightaware.com {206.253.80.196 206.253.80.197 206.253.80.198 206.253.80.199 206.253.80.200 206.253.80.201} {206.253.84.193 206.253.84.194 206.253.84.195 206.253.84.196 206.253.84.197 206.253.84.198}” # using default value
#adept-serverport 1200 # using default value
allow-auto-updates yes # value set at /etc/piaware.conf:7
#allow-ble-setup auto # using default value
#allow-dhcp-duid yes # using default value
allow-manual-updates yes # value set at /etc/piaware.conf:8
#allow-mlat yes # using default value
#allow-modeac yes # using default value
#beast-baudrate # no value set and no default value
#enable-firehose no # using default value
#feeder-id # no value set and no default value
#force-macaddress # no value set and no default value
#http-proxy-host # no value set and no default value
#http-proxy-password # no value set and no default value
#http-proxy-port # no value set and no default value
#http-proxy-user # no value set and no default value
#image-type # no value set and no default value
#manage-config no # using default value
#mlat-results yes # using default value
#mlat-results-anon yes # using default value
#mlat-results-format “beast,connect,localhost:30104 beast,listen,30105 ext_basestation,listen,30106” # using default value
#network-config-style buster # using default value
#priority # no value set and no default value
#radarcape-host # no value set and no default value
#receiver-host # no value set and no default value
#receiver-port 30005 # using default value
#receiver-type rtlsdr # using default value
#rfkill no # using default value
#rtlsdr-device-index 0 # using default value
#rtlsdr-gain max # using default value
#rtlsdr-ppm 0 # using default value
#slow-cpu auto # using default value
#uat-receiver-host # no value set and no default value
#uat-receiver-port 30978 # using default value
#uat-receiver-type none # using default value
#uat-sdr-device driver=rtlsdr # using default value
#uat-sdr-gain max # using default value
#uat-sdr-ppm 0 # using default value
#use-gpsd yes # using default value
#wired-address # no value set and no default value
#wired-broadcast # no value set and no default value
#wired-gateway # no value set and no default value
#wired-nameservers “8.8.8.8 8.8.4.4” # using default value
#wired-netmask # no value set and no default value
#wired-network yes # using default value
#wired-type dhcp # using default value
#wireless-address # no value set and no default value
#wireless-broadcast # no value set and no default value
#wireless-country 00 # using default value
#wireless-gateway # no value set and no default value
#wireless-nameservers “8.8.8.8 8.8.4.4” # using default value
#wireless-netmask # no value set and no default value
#wireless-network no # using default value
#wireless-password # no value set and no default value
#wireless-ssid # no value set and no default value
#wireless-type dhcp # using default value

20

Please post output of following command. It will output piaware log which will help in finding what went wrong.

sudo journalctl -u piaware -e

 

NOTE:
To properly format and make it easy to read, please type [code] above the first line you copy-paste, and [/code] below the last line of code you copy-paste. Like below

[code]
Output line 1
Output line 2
Output line 3
…
…
Output line n
[/code]