apt-cache policy piaware
piaware:
Installed: 3.7.2~ubuntu1804+1
Candidate: 3.7.2~ubuntu1804+1
Version table:
*** 3.7.2~ubuntu1804+1 100
100 /var/lib/dpkg/status
(1) Check if package piaware_3.8.0~dev_amd64.deb is available in folder piaware_builder
(2) If yes, did you install it by sudo dpkg -i command?
abcd@ubuntu19:~/piaware_builder$ ls
bionic common package-buster piaware_3.8.0~dev_amd64.deb sensible-build.sh xenial
buster Jenkinsfile piaware_3.8.0~dev_amd64.buildinfo piaware-dbgsym_3.8.0~dev_amd64.ddeb stretch
changelog jessie piaware_3.8.0~dev_amd64.changes README.md
sudo dpkg -i piaware_3.8.0~dev_amd64.deb
abcd@ubuntu19:~$ apt-cache policy piaware
piaware:
Installed: 3.8.0~dev
Candidate: 3.8.0~dev
Version table:
*** 3.8.0~dev 100
100 /var/lib/dpkg/status
1 Like
Aha, that was it!
sorin@Ubuntu-Latitude-E6420:~/piaware_builder$ apt-cache policy piaware
piaware:
Installed: 3.8.0~dev
Candidate: 3.8.0~dev
Version table:
*** 3.8.0~dev 100
100 /var/lib/dpkg/status
Version 3.8.0~dev_amd64
abcd@ubuntu19:~$ sudo systemctl status piaware
● piaware.service - FlightAware ADS-B uploader
Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2019-11-27 12:05:31 EST; 15min ago
Docs: https://flightaware.com/adsb/piaware/
Main PID: 6431 (piaware)
Tasks: 4 (limit: 4659)
Memory: 14.6M
CGroup: /system.slice/piaware.service
├─6431 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
├─6575 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,
└─6579 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 43.xxx --lon -79.xxx
Nov 27 12:07:36 ubuntu19 piaware[6431]: mlat-client(6575): Listening for Beast-format results connection on port 30105
Nov 27 12:07:36 ubuntu19 piaware[6431]: mlat-client(6575): Listening for Extended Basestation-format results connection on port 30106
Nov 27 12:07:36 ubuntu19 piaware[6431]: mlat-client(6575): Route MTU changed to 1500
Nov 27 12:07:36 ubuntu19 piaware[6431]: mlat-client(6575): Input connected to localhost:30005
Nov 27 12:07:36 ubuntu19 piaware[6431]: mlat-client(6575): Input format changed to BEAST, 12MHz clock
Nov 27 12:07:37 ubuntu19 piaware[6431]: mlat-client(6575): Beast-format results connection with 127.0.0.1:30104: connection established
Nov 27 12:07:40 ubuntu19 piaware[6431]: piaware received a message from dump1090-fa!
Nov 27 12:07:52 ubuntu19 piaware[6431]: piaware has successfully sent several msgs to FlightAware!
Nov 27 12:11:06 ubuntu19 piaware[6431]: 171 msgs recv'd from dump1090-fa (171 in last 5m); 171 msgs sent to FlightAware
Nov 27 12:16:06 ubuntu19 piaware[6431]: 340 msgs recv'd from dump1090-fa (169 in last 5m); 340 msgs sent to FlightAware
1 Like
sorin@Ubuntu-Latitude-E6420:~/piaware_builder$ sudo systemctl status piaware piaware.service - FlightAware ADS-B uploader Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2019-11-27 12:17:57 EST; 15min ago Docs: https://flightaware.com/adsb/piaware/ Main PID: 7527 (piaware) Tasks: 4 (limit: 4512) Memory: 17.5M CGroup: /system.slice/piaware.service ├─7527 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status. ├─7582 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type du └─7586 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdou Nov 27 12:18:10 Ubuntu-Latitude-E6420 piaware[7527]: piaware has successfully sent several msgs to Flight Nov 27 12:18:32 Ubuntu-Latitude-E6420 piaware[7527]: 497 msgs recv'd from dump1090-fa; 497 msgs sent to F Nov 27 12:23:32 Ubuntu-Latitude-E6420 piaware[7527]: 3579 msgs recv'd from dump1090-fa (3082 in last 5m); Nov 27 12:28:32 Ubuntu-Latitude-E6420 piaware[7527]: 6627 msgs recv'd from dump1090-fa (3048 in last 5m); Nov 27 12:32:59 Ubuntu-Latitude-E6420 piaware[7527]: mlat-client(7582): Receiver status: connected Nov 27 12:32:59 Ubuntu-Latitude-E6420 piaware[7527]: mlat-client(7582): Server status: synchronized wit Nov 27 12:32:59 Ubuntu-Latitude-E6420 piaware[7527]: mlat-client(7582): Receiver: 1153.9 msg/s received Nov 27 12:32:59 Ubuntu-Latitude-E6420 piaware[7527]: mlat-client(7582): Server: 0.1 kB/s from server Nov 27 12:32:59 Ubuntu-Latitude-E6420 piaware[7527]: mlat-client(7582): Results: 40.7 positions/minute Nov 27 12:32:59 Ubuntu-Latitude-E6420 piaware[7527]: mlat-client(7582): Aircraft: 13 of 25 Mode S, 77 of lines 1-22/22 (END)
It seems that it did the trick! Thanks!
And thanks to @abcd567 for his help!
LE: It’s still working. Great!
[2019-11-27 13:23 EST] 43697 msgs recv’d from dump1090-fa (3333 in last 5m); 43697 msgs sent to FlightAware
[2019-11-27 13:33 EST] mlat-client(7582): Receiver: 1228.5 msg/s received 366.5 msg/s processed (30%)
[2019-11-27 13:33 EST] mlat-client(7582): Server status: synchronized with 248 nearby receivers
[2019-11-27 13:33 EST] mlat-client(7582): Aircraft: 18 of 37 Mode S, 81 of 138 ADS-B used
[2019-11-27 13:33 EST] mlat-client(7582): Receiver status: connected
[2019-11-27 13:33 EST] mlat-client(7582): Server: 0.1 kB/s from server 0.1kB/s TCP to server 3.1kB/s UDP to server
[2019-11-27 13:33 EST] 50333 msgs recv’d from dump1090-fa (3195 in last 5m); 50333 msgs sent to FlightAware
Thanks for testing. I added a rule to sensible-build.sh for disco.
2 Likes
I’ve read and searched for a couple of hours to fix the error:
gpg: skipped “Eric Tran eric.tran@flightaware.com”: No secret key
for the 2nd (or 3rd) time cut/paste the recipe
cd package-bionic
sudo dpkg-buildpackage -b
tks …
…jay
Ubuntu 18.04.3 LTS
on a Dell XPS 13 7390 …
Not really an error.
You are not Mr. Tran, so you can’t sign the build.
But you don’t need to sign it, just install it.
1 Like
I have the same problem on Ubuntu 18.04.03 LTS:
"…
dpkg-buildpackage: info: binary-only upload (no source included)
signfile dump1090-fa_3.7.2_arm64.buildinfo
gpg: WARNING: unsafe ownership on homedir ‘/home/julian/.gnupg’
gpg: skipped “Eric Tran eric.tran@flightaware.com”: No secret key
gpg: dpkg-sign.7E8GIcFG/dump1090-fa_3.7.2_arm64.buildinfo: clear-sign failed: No secret key
dpkg-buildpackage: error: failed to sign .buildinfo file
…"
Unfortunately this is done during execution of “sudo dpkg-buildpackage -b”.
As a relative noob to package building, I have no idea how to remove this stage.
Please could you advise, as I have now spent almost a week struggling to do this?
Thanks in advance.
Ignore the signing error. The package has still been built. Go on to the next step.
Alternatively, you can pass --no-sign to dpkg-buildpackage to skip the signing step.
Thanks… back on track.
…jay
Thanks. All good now.
Thank you abcd567,
Last night I used your very well documented procedures in the first post above for a PiAware 3.7.2 install on native Ubuntu 18.04. Of course I reviewed the entire thread first, and for 18.04 the only other detail that was “good to know” was to ignore the digital signature error message. The install was very smooth and works perfectly.
dan@Acer-722:~$ apt-cache policy piaware
piaware:
Installed: 3.7.2~ubuntu1804+1
Candidate: 3.7.2~ubuntu1804+1
Version table:
*** 3.7.2~ubuntu1804+1 100
100 /var/lib/dpkg/status
The only thing I noticed which is not an issue (and not worth changing) is when visiting the IP of the device. No, I’m not asking for a solution to this. Just pointing it out in case it confuses others.
IP/ goes to generic Lighttpd placeholder page
IP:8080/ goes to PiAware SkyAware
IP/dump1090-fa/ goes to PiAware SkyAware
I have also installed dump978-fa in a similar way to your dump1090-fa directions above and am also giving that a try.
Thank you,
-Dan
Build & Install dump978-fa ver 3.7.2 on Ubuntu 18.04 (Bionic)
1 - Install build tools & dependencies
sudo apt install build-essential debhelper dh-systemd
sudo apt install libboost-system-dev libboost-program-options-dev
sudo apt install libboost-regex-dev libboost-filesystem-dev libsoapysdr-dev 2. Clone source-code, build package, and install package
git clone https://github.com/flightaware/dump978.git
cd dump978
sudo dpkg-buildpackage -b
cd ../
sudo dpkg -i dump978-fa_*_*.deb3 - Configure
3.1 - Serialize dongles: (CLICK HERE)
3.2 - configure dump1090 and dump978
sudo piaware-config uat-receiver-type sdr
sudo sed -i 's/--device-index 0/--device-index 00001090/' /etc/default/dump1090-fa
sudo sed -i 's/driver=rtlsdr/driver=rtlsdr,serial=00000978/' /etc/default/dump978-fa
# Reboot Pi to implement configuration settings
sudo reboot
4 - Check Status
abcd@ubuntu-18:~$ sudo systemctl status dump978-fa
● dump978-fa.service - dump978 ADS-B UAT receiver
Loaded: loaded (/lib/systemd/system/dump978-fa.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2019-12-22 17:16:47 EST; 2min 59s ago
Docs: https://flightaware.com/adsb/piaware/
Main PID: 14697 (dump978-fa)
Tasks: 4 (limit: 4675)
CGroup: /system.slice/dump978-fa.service
└─14697 /usr/bin/dump978-fa --sdr driver=rtlsdr --format CS8 --raw-port 30978 --json-port 30979
Dec 22 17:16:47 ubuntu-18 dump978-fa[14697]: linux; GNU C++ version 7.3.0; Boost_106501; UHD_003.010.003.000
Dec 22 17:16:47 ubuntu-18 dump978-fa[14697]: Detached kernel driver
Dec 22 17:16:48 ubuntu-18 dump978-fa[14697]: Found Rafael Micro R820T tuner
Dec 22 17:16:49 ubuntu-18 dump978-fa[14697]: Reattached kernel driver
Dec 22 17:16:49 ubuntu-18 dump978-fa[14697]: Detached kernel driver
Dec 22 17:16:50 ubuntu-18 dump978-fa[14697]: Found Rafael Micro R820T tuner
Dec 22 17:16:51 ubuntu-18 dump978-fa[14697]: Exact sample rate is: 2083333.135571 Hz
Dec 22 17:16:51 ubuntu-18 dump978-fa[14697]: [R82XX] PLL not locked!
Dec 22 17:16:51 ubuntu-18 dump978-fa[14697]: SoapySDR: using maximum manual gain 49.6 dB
Dec 22 17:16:51 ubuntu-18 dump978-fa[14697]: SoapySDR: using stream setting buffsize=262144
2 Likes
This post is ONLY about an issue with faup978 while running dump978-fa. The original #1 post above is still working perfectly for faup1090 and dump1090-fa.
Hi ABCD567,
I’m getting closer and believe I’ve narrowed my problem down to faup978 not running because it is not available in /usr/lib/piaware/helpers to be started. I have been looking at this yesterday and today and didn’t want to just post “tons of data” until I narrowed it down a bit. I enjoy learning new things and didn’t want you to just give me the answer! (grin)
Observations:
- I am testing with a single RTL device.
- All indications are good using defaults, decoding 1090, and uploading 1090 data.
- After disabling 1090, dump978-fa correctly starts. All local indications look good. Dump978-fa is running fine, online stats page shows 978 link so it knows I’m 978, local 978 page opens fine. I understand 978 data is very limited and am currently receiving none. That’s not the problem. I have previously decoded 978 UAT data using the original dump978.
- While PiAware is correctly syncing with FA servers, I suspect that data would not actually be uploaded since faup978 is not running.
Additional info:
dan@Acer-722:/etc$ sudo cat /etc/piaware.conf
feeder-id xxxx-edit-xxxx...
receiver-type rtlsdr
uat-receiver-type sdr
dan@Acer-722:/etc/default$ cat dump1090-fa
# dump1090-fa configuration
# dump1090-fa won't automatically start unless ENABLED=yes
ENABLED=no
RECEIVER_OPTIONS="--device-index 0 --gain -10 --ppm 0 --net-bo-port 30005"
DECODER_OPTIONS="--max-range 360"
NET_OPTIONS="--net --net-heartbeat 60 --net-ro-size 1000 --net-ro-interval 1 --net-ri-port 0 --net-ro-port 30002 --net-sbs-port 30003 --net-bi-port 30004,30104 --net-bo-port 30005"
JSON_OPTIONS="--json-location-accuracy 1"
dan@Acer-722:/etc/default$ cat dump978-fa
# dump978-fa configuration
# dump978-fa won't automatically start unless ENABLED=yes
ENABLED=yes
RECEIVER_OPTIONS="--sdr driver=rtlsdr --format CS8"
DECODER_OPTIONS=""
NET_OPTIONS="--raw-port 30978 --json-port 30979"
Everything looks good below (for single RTL 978) except for faup978 not running. While it indicates that “dump978 is NOT producing data on localhost:30978.” that is correct because I am not receiving data. 30978 is available for connections and I can connect to it using VRS.
dan@Acer-722:/usr/lib/piaware/helpers$ sudo piaware-status
PiAware master process (piaware) is running with pid 968.
PiAware ADS-B client (faup1090) is not running.
PiAware ADS-B UAT client (faup978) is not running.
PiAware mlat client (fa-mlat-client) is not running.
Local ADS-B receiver (dump1090) is not running.
Local ADS-B UAT receiver (dump978-fa) is running with pid 872.
no program appears to be listening for ES connections on port 30005.
dump978-fa (pid 872) is listening for UAT connections on port 30978.
faup1090 is NOT connected to the ADS-B receiver.
faup978 is NOT connected to the ADS-B UAT receiver.
piaware is connected to FlightAware.
got 'couldn't open socket: connection refused'
dump1090 is NOT producing data on localhost:30005.
dump978 is NOT producing data on localhost:30978.
dan@Acer-722:~$ sudo systemctl status dump978-fa
dump978-fa.service - dump978 ADS-B UAT receiver
Loaded: loaded (/lib/systemd/system/dump978-fa.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2019-12-23 14:15:48 CST; 8min ago
Docs: https://flightaware.com/adsb/piaware/
Main PID: 868 (dump978-fa)
Tasks: 4 (limit: 4344)
CGroup: /system.slice/dump978-fa.service
└─868 /usr/bin/dump978-fa --sdr driver=rtlsdr --format CS8 --raw-port 30978 --json-port 30979
Dec 23 14:16:04 Acer-722 dump978-fa[868]: Reattached kernel driver
Dec 23 14:16:04 Acer-722 dump978-fa[868]: Detached kernel driver
Dec 23 14:16:04 Acer-722 dump978-fa[868]: Found Rafael Micro R820T tuner
Dec 23 14:16:04 Acer-722 dump978-fa[868]: Exact sample rate is: 2083333.135571 Hz
Dec 23 14:16:04 Acer-722 dump978-fa[868]: [R82XX] PLL not locked!
Dec 23 14:16:04 Acer-722 dump978-fa[868]: SoapySDR: using maximum manual gain 49.6 dB
Dec 23 14:16:04 Acer-722 dump978-fa[868]: SoapySDR: using stream setting buffsize=262144
Dec 23 14:16:04 Acer-722 dump978-fa[868]: 0.0.0.0:30978: accepted a connection from 127.0.0.1:41736
Dec 23 14:21:10 Acer-722 dump978-fa[868]: 0.0.0.0:30978: accepted a connection from 127.0.0.1:33431
Dec 23 14:21:20 Acer-722 dump978-fa[868]: 127.0.0.1:33431: connection closed
dan@Acer-722:~$ whereis faup1090
faup1090: /usr/share/man/man1/faup1090.1.gz
dan@Acer-722:~$ whereis faup978
faup978: (*** indicates not found)
dan@Acer-722:~$ ls -ls /usr/lib/piaware/helpers
total 4708
12 -rwxr-xr-x 1 root root 10224 Dec 21 16:54 fa-mlat-client
108 -rwxr-xr-x 1 root root 108696 Dec 21 16:54 faup1090
4 -rw-r--r-- 1 root root 1155 Dec 21 16:54 flightaware-archive-keyring.gpg
4 drwxr-xr-x 15 root root 4096 Dec 21 16:59 lib
4576 -rw-r--r-- 1 root root 4683728 Dec 21 16:54 libpython3.6m.so.1.0
4 -rwxr-xr-x 1 root root 2466 Dec 21 16:54 run-apt-get
From /usr/lib/piaware/faup978.tcl
proc connect_uat_via_faup978 {} {
set receiverType [piawareConfig get uat-receiver-type]
# is 978 enabled?
if {$receiverType eq "none"} {
logger "UAT support disabled by local configuration setting: uat-receiver-type"
return
}
# path to faup978
set path [auto_execok "/usr/lib/piaware/helpers/faup978"]
if {$path eq ""} {
logger "No faup978 found at $path, UAT support disabled"
return
}
So, I believe faup978 is the problem. I suspect faup1090 is likely installed by piaware (or perhaps dump1090-fa). However, it looks like faup978 is NOT correctly installed by piaware (or perhaps dump978-fa.
I really did not want to clutter up this thread, but I think I’m ready for your opinion on what I have tracked down so far.
Thanks,
-Dan
You compiled piaware, yes?
Which ./sensible-build.sh parameter did you use?
I’d always recommend using stretch or now buster for the later Ubuntu versions.
The build targets for Ubuntu aren’t really tested, so probably faup978 was just not being built.
Recompile piaware using ./sensible-build.sh stretch … then try again.
1 Like
Yes.
I compiled using this from the directions in post #1 above.
./sensible-build.sh bionic
Will recompile using stretch as a test.
-Dan
Bingo! Recompiling by replacing bionic with stretch each time did the trick and correctly created the needed faup978.
Below shows good results now for a single RTL used for 978 on Ubuntu 18.04 (Bionic) with the PiAware being compiled using stretch.
dan@Acer-722:/$ ps -ea | grep faup978
1158 ? 00:00:00 faup978
dan@Acer-722:/$ sudo piaware-status
PiAware master process (piaware) is running with pid 1093.
PiAware ADS-B client (faup1090) is not running (disabled by configuration settings)
PiAware ADS-B UAT client (faup978) is running with pid 1158.
PiAware mlat client (fa-mlat-client) is not running.
Local ADS-B UAT receiver (dump978-fa) is running with pid 851.dump978-fa (pid 851) is listening for UAT connections on port 30978.
faup978 is connected to the ADS-B UAT receiver.
piaware is connected to FlightAware.dump978 is NOT producing data on localhost:30978.
This looks good at first glance. I’ll take a closer look and dig around some more. The “dump978 is NOT producing data on localhost:30978” is due to no current reception of 978.
Thank you both for your help.
-Dan