FlightAware Discussions

Anyone working with the new x86 Raspbian

If you see my first post of today (Post # 215), you will find that I have already installed following packages before issuing the "dpkg-buildpackage" command

  • systemd_229
  • python3-venv_3.5.1-3
  • python3-dev_3.5.1-3_i386.deb

EDIT:
I have now installed this package also

  • systemd-sysv_229

You are still missing the program py3versions.
Maybe you only installed the development package for python3, dev packages don’t necessarily contain all the stuff …
Quick google shows in xenial py3versions is provided by python3-minimal
(maybe provided by python3 as well)

Thanks, I also found same thing before seeing your post, checked PPM, not available, then found and installed :

Gave command "dpkg-buildpackage -b -d". It got past the stage where it has got stuck initially, but now it got stuck with Cx-Freez

... ... ...

building 'cx_Freeze.util' extension
creating build/temp.linux-i686-3.5
creating build/temp.linux-i686-3.5/source
i686-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -g -O2 -fPIC -I/root/piaware_builder/package-xenial/debian/venv/include -I/usr/include/python3.5m -c source/util.c -o build/temp.linux-i686-3.5/source/util.o
source/util.c:6:20: fatal error: Python.h: No such file or directory
compilation terminated.
error: command 'i686-linux-gnu-gcc' failed with exit status 1
debian/rules:60: recipe for target 'build_cxfreeze' failed
make[1]: *** [build_cxfreeze] Error 1
make[1]: Leaving directory '/root/piaware_builder/package-xenial'
debian/rules:88: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

can you log out and log in and try again?

It’s not finding the <python.h> which should be somewhere with the one of the dev versions of the libraries.
Maybe it didn’t refresh the path properly when you installed it.

[strike] Apart from that i’m mostly out of ideas :frowning: [/strike]

Do this:
sudo find / -name Python.h

It should be in
/usr/include/python3.5m
otherwise the compile won’t work :confused:

If you ever get this to work you better provide the debian packages for that image so people don’t need to compile them themselves :stuck_out_tongue:
Anyway i guess you need to install a truckload of stuff before you can even install those packages.

Bad news: the USB flash, on which Xenialpup’s image was written, suddenly died. With it my steps & observations which I was noting on Xenialpup’s notepad also vanished.

Good news: I have posted all the steps on FA forum, which is now backup for me.

NEXT
Start with a new USB flash and fresh install of everything.

.
CLICK ON SCREENSHOT TO SEE LARGER SIZE

SUCCESS With Another Puppy-Linux:

BionicDog (Forked from DebianDog)

Xnialpup lacks lot of infrastructure, and requires lots of workarounds and loads of packages to be added, and still no success as systemd still does not work properly, and also Piaware builder got stuck at cx_freez.

I landed into another version of Puppy-Linux, the BionicDog (forked from DebianDog). It is Ubuntu Bionic, but "pupped". It is fast and lightweigt (405 Mb), as well as has all the necessary infrastructure out of the box (i.e. firmware, systemd, apt, dpkg etc etc).

https://debiandog.github.io/doglinux/zz06-zbionicdog.html

1 - Installation of OS on USB Flash Stick / Pendrive

1.1 - From above page download:

BionicDog32_2018-06-04-firmware_all.iso (Size: 405MB)

1.2 - Burn above .iso to a DVD. I have used a USB Flash instead, and burned image by Win32Disk imager. I will call it USB#1

1.3 - Boot PC using USB#1 (or DVD)

1.4 - Plugg-in 2nd USB Flash Stick / Pendrive on which the BionicDog Full install will be done. Call it USB#2

1.4 - Click menu -> System -> BionicDog-Full-Install

1.5 - Choose USB#2 as drive on which BionicDog will be installed (sdc1 in screenshot below, but it may be a different partition number on your computer)

1.6 - Click Install button

.

1.7 - Click “YES” button

install-3

.

install-4
.

1.8 - Click OK button

install-5

.
1.9 - Click OK button
install-6

.
1.10 - Congratulations, BionicDog is installed on USB#2 (sdc1 in this examle). Shutdown computer. When asked to “Save”, click “Quit” button.

install-7

.

2 - Remove Installation media (DVD or USB#1) and boot from USB#2.

NOTE:
(a) Booting from USB#2 takes about 2 ~ 3 minutes depending on speed of USB and CPU.

(b) During boot, at one stage, the display does not show any progress for a while. This gives the impression that computer has hanged/froze. Please be patient, it will automatically move-on after a while.

3 - Installation of dump1090-fa

.
3.1 - Update system

root@live:~# apt update

.

3.2 - Install packages necessary to build and to fulfil dependencies

root@live:~# apt install -y git curl build-essential debhelper pkg-config 

root@live:~# apt install -y rtl-sdr librtlsdr-dev libusb-1.0-0 libusb-1.0-0-dev   

root@live:~# apt install -y cron lighttpd fakeroot dh-systemd libncurses5-dev  
   

.
.

3.3 - Clone source-code from github

root@live:~# git clone https://github.com/flightaware/dump1090.git   

.

3.4 - Enter Cloned directory “dump1090”, and remove bladeRF entries from 2 files as shown in 2.4.1 & 2.4.2

root@live:~# cd dump1090

3.4.1. Edit file debian/control and remove bladeRF

root@live:~# cd dump1090

root@live:~/dump1090# nano debian/control

  • Scroll down till you find the first lines below.
  • Scroll down further to find second line.
  • Delete libbladerf in both lines as shown in red below.

.

3.4.2 - Edit file debian/rules and change BLADERF=yes to BLADERF=no

root@live:~# cd dump1090

root@live:~/dump1090# nano debian/rules
  • Scroll down till you find the line shown below.
  • Change BLADERF=yes to BLADERF=no as shown in red below.

.

3.5 - Build the dump1090-fa package

root@live:~# cd dump1090

root@live:~/dump1090# sudo dpkg-buildpackage -b

.

3.6 - After package building is completed, go out of dump1090 directory and check if the package is actually built:

root@live:~/dump1090# cd ../

root@live:~# ls

2019-01-26-163236_222x119_scrot.png  dump1090-fa_3.6.3_i386.deb 
Desktop                              dump1090-fa-dbgsym_3.6.3_i386.ddeb  
Downloads                            my-documents 
dump1090                             Startup 
dump1090_3.6.3_all.deb               tint2launchers 
dump1090-fa_3.6.3_i386.buildinfo     txt2svg 
dump1090-fa_3.6.3_i386.changes 

.

3.7 - Install dump1090-fa

root@live:~# sudo dpkg -i dump1090-fa_*.deb

root@live:~# sudo reboot

.

3.8 - Check after Reboot

root@live:~# systemctl status dump1090-fa
● dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
   Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2019-01-27 02:26:15 EST; 27s ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 21362 (dump1090-fa)
    Tasks: 3 (limit: 4915)
   CGroup: /system.slice/dump1090-fa.service
           └─21362 /usr/bin/dump1090-fa --device-index 0 --gain -10 --ppm 0 --net-bo-port 300

Jan 27 02:26:15 live systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Jan 27 02:26:15 live dump1090-fa[21362]: Sun Jan 27 02:26:15 2019 EST  dump1090-fa 3.6.3 star
Jan 27 02:26:15 live dump1090-fa[21362]: rtlsdr: using device #0: Generic RTL2832U (Realtek, 
Jan 27 02:26:15 live dump1090-fa[21362]: Detached kernel driver
Jan 27 02:26:15 live dump1090-fa[21362]: Found Rafael Micro R820T tuner
Jan 27 02:26:15 live dump1090-fa[21362]: rtlsdr: enabling tuner AGC

.
NOTE:
1 - Using mag-mount antenna inside room
2 - VERY FEW FLIGHTS AT THIS HOUR OF NIGHT

CLICK ON SCREENSHOT TO SEE LARGER SIZE

.

4 - Installation of Piaware data feeder

.
4.1 - Update system

root@live:~# apt update

.
4.2 - Install packages necessary to build and to fulfil dependencies

root@live:~# apt install -y git devscripts build-essential debhelper  

root@live:~# apt install -y tcl8.6-dev autoconf python3-dev python3-venv  

root@live:~# apt install -y virtualenv dh-systemd zlib1g-dev tclx8.4  

root@live:~# apt install -y tcllib tcl-tls itcl3 net-tools 


.

4.3 - Clone source-code and build Piaware package

root@live:~# git clone https://github.com/flightaware/piaware_builder.git  

root@live:~# cd  piaware_builder  

root@live:~/piaware_builder# CODENAME=(`lsb_release -sc`)  

root@live:~/piaware_builder# echo ${CODENAME}  

root@live:~/piaware_builder# ./sensible-build.sh ${CODENAME}  

root@live:~/piaware_builder# cd  package-${CODENAME}  

root@live:~/piaware_builder/package-bionic# dpkg-buildpackage -b  

.
4.4 - Check if the package is actually built

root@live:~/piaware_builder/package-bionic# cd ../   

root@live:~/piaware_builder# ls  

bionic       package-bionic                               README.md
changelog    piaware_3.6.3~ubuntu1804+1_i386.buildinfo    sensible-build.sh
common       piaware_3.6.3~ubuntu1804+1_i386.changes      stretch
Jenkinsfile  piaware_3.6.3~ubuntu1804+1_i386.deb          wheezy
jessie       piaware-dbgsym_3.6.3~ubuntu1804+1_i386.ddeb  xenial

.
4.5 - Install Piaware

root@live:~/piaware_builder# sudo dpkg -i piaware_*.deb  

.

4.6 - CONFIGURE PIAWARE


root@live:~/piaware_builder# cd 

root@live:~# piaware-config feeder-id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

root@live:~# piaware-config allow-auto-updates yes
root@live:~# piaware-config allow-manual-updates yes

root@live:~#  systemctl restart piaware

.
4.7 - Check Status

root@live:~# systemctl status piaware

● piaware.service - FlightAware ADS-B uploader
   Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2019-01-27 03:46:17 EST; 7min ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 32197 (piaware)
    Tasks: 4 (limit: 4915)
   CGroup: /system.slice/piaware.service
           ├─32197 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
           ├─32218 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,
           └─32704 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 43.xxx --lon -79.xxx

Jan 27 03:46:52 live piaware[32197]: 0 msgs recv'd from dump1090; 0 msgs sent to FlightAware
Jan 27 03:47:21 live sudo[32702]:  piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp --wide --all --numeri
Jan 27 03:47:21 live sudo[32702]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jan 27 03:47:21 live sudo[32702]: pam_unix(sudo:session): session closed for user root
Jan 27 03:47:21 live piaware[32197]: ADS-B data program 'dump1090-fa' is listening on port 30005, so far so good
Jan 27 03:47:21 live piaware[32197]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 -
Jan 27 03:47:21 live piaware[32197]: Started faup1090 (pid 32704) to connect to dump1090-fa
Jan 27 03:47:21 live piaware[32197]: piaware received a message from dump1090-fa!
Jan 27 03:48:32 live piaware[32197]: piaware has successfully sent several msgs to FlightAware!
Jan 27 03:51:52 live piaware[32197]: 16 msgs recv'd from dump1090-fa (16 in last 5m); 16 msgs sent to FlightAware

ENJOY :slight_smile:

2 Likes

Found Another Dog, the StretchDog.

.
CLICK ON SCREENSGHOT TO SEE LARGER SIZE


.

https://debiandog.github.io/doglinux/zz02stretchdog.html

Downloaded OS: StretchDog32-openbox_xfce-jwm-2017-10-10.iso
Size: 242MB
.

The procedure to install OS is almost same as that of BionicDog, except for few minor differences:

(1) In step 1.6 for BionicDog, one does not need to point to the location of the downloaded .iso. For StretchDog, the location of the downloaded .iso is required to be pointed to.

(2) After full-install is completed and the computer is booted by USB#2, at boot menu, following options are presented:

  • Boot with systemvinit (default)
  • Boot with systemd

One has to manually change from default sysvinit to systemd option at every boot/reboot. A better option is to modify Boot Config / Grub to change default to systemd.

How to change default from sysvinit to systemd

Open file /menu.lst for editing

root@live:~# nano /menu.lst

The above command will open following file
.

# menu.lst produced by grub4dosconfig-v1.7
color white/blue black/cyan white/black cyan/black
timeout 10
default 0 


title DDog - sysvinit
 uuid f13dfcc6-bf90-4c64-894e-44a472e9973d
 kernel /boot/vmlinuz1 root=UUID=f13dfcc6-bf90-4c64-894e-44a472e9973d ro
 initrd /boot/initrd.img

title DDog - systemd
 uuid f13dfcc6-bf90-4c64-894e-44a472e9973d
 kernel /boot/vmlinuz1 root=UUID=f13dfcc6-bf90-4c64-894e-44a472e9973d init=/bin$
 initrd /boot/initrd.img

title Reboot computer
  reboot

.

In this file change 4th line
default 0
to
default 1

(0 represents first entry which is sysvinit, and 1 represents second entry which is systemd)

Save file and reboot
.
(3) After full installation of OS on USB#2 is completed and PC is booted by USB#2 (i.e. after Step 2 of BionicDog), one has to download file “61-DEVX-Stretch_1386.squashfs” from:
https://github.com/fredx181/StretchDog/releases/v2.1.

After download, right-click on downloaded file and in the pop-up menu select “load-sfs-chroot full install” .

The procedure to install dump1090-fa and Piaware is identical to that of BionicDog, except in step 4.3 as shown below:

The distro codename stretch is not returned by command lsb_release -sc. hence following revise item 4.3 is given below:

4.3 - Clone source-code and build Piaware package

root@live:~# git clone https://github.com/flightaware/piaware_builder.git  

root@live:~# cd  piaware_builder  


root@live:~/piaware_builder# ./sensible-build.sh stretch  

root@live:~/piaware_builder# cd  package-stretch  

root@live:~/piaware_builder/package-stretch# dpkg-buildpackage -b  

#Move to directory where piawarepackage is built
root@live:~/piaware_builder/package-stretch# cd ../ 

#Install piaware package
root@live:~/piaware_builder# sudo dpkg -i piaware_*.deb

.

CHECK

root@live:~# systemctl status piaware
● piaware.service - FlightAware ADS-B uploader
   Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2019-01-27 20:48:53 UTC; 49s ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 7873 (piaware)
    Tasks: 4 (limit: 4915)
   CGroup: /system.slice/piaware.service
           ├─7873 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run
           ├─7910 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005
           └─7917 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-po

Jan 27 20:48:56 live piaware[7873]: mlat-client(7910): Input format changed to BEAST, 12M
Jan 27 20:48:57 live sudo[7915]:  piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bi
Jan 27 20:48:57 live sudo[7915]: pam_unix(sudo:session): session opened for user root by 
Jan 27 20:48:57 live piaware[7873]: ADS-B data program 'dump1090-fa' is listening on port
Jan 27 20:48:57 live piaware[7873]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 
Jan 27 20:48:57 live piaware[7873]: Started faup1090 (pid 7917) to connect to dump1090-fa
Jan 27 20:48:57 live piaware[7873]: mlat-client(7910): Beast-format results connection wi
Jan 27 20:48:57 live piaware[7873]: piaware received a message from dump1090-fa!
Jan 27 20:48:59 live piaware[7873]: piaware has successfully sent several msgs to FlightA
Jan 27 20:49:28 live piaware[7873]: 83 msgs recv'd from dump1090-fa; 83 msgs sent to Flig
1 Like

Hi, abcd567
Sorry to revive this topic but, just to thank you !
I’ve installed piaware on Ubuntu 19.04 and everything works fine.
Was just necessary to replace codname “disco” to codname “bionic”.
Regards
vsqz44

1 Like

@vsqz44
:+1: :+1: :+1:

1 Like

Hi,
I thought that everything was OK but, now I realized that, despite the aircraft are show on the map, there are nothing send to Flightware.
Below, my piaware-status

$ sudo piaware-status
PiAware master process (piaware) is running with pid 1322.
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-fa) is running with pid 4870.

dump1090-fa (pid 4870) is listening for ES connections on port 30005.
faup1090 is NOT connected to the ADS-B receiver.
piaware is connected to FlightAware.

dump1090 is producing data on localhost:30005.

Any help ?
Thanks in advanced

vsqz44

Show the output of:

sudo piaware-config

sudo journalctl --no-pager -u piaware

1 Like

Hi, wiedehopf

allow-auto-updates yes # value set at /etc/piaware.conf:8
allow-manual-updates yes # value set at /etc/piaware.conf:9
feeder-id xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx # value set at /etc/piaware.conf:7
flightaware-password # value set at /etc/piaware.conf:11
flightaware-user # value set at /etc/piaware.conf:10

set 29 09:09:53 eu-Aspire-VX5-591G systemd[1]: Started FlightAware ADS-B uploader.
set 29 09:09:53 eu-Aspire-VX5-591G piaware[1541]: creating pidfile /run/piaware/piaware.pid
set 29 09:09:53 eu-Aspire-VX5-591G piaware[1541]: ****************************************************
set 29 09:09:53 eu-Aspire-VX5-591G piaware[1541]: piaware version 3.7.2 is running, process ID 1541
set 29 09:09:53 eu-Aspire-VX5-591G piaware[1541]: your system info is: Linux eu-Aspire-VX5-591G 5.0.0-29-generic #31-Ubuntu SMP Thu Sep 12 13:05:32 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
set 29 09:09:54 eu-Aspire-VX5-591G piaware[1541]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
set 29 09:09:54 eu-Aspire-VX5-591G piaware[1541]: Connection with adept server at piaware.flightaware.com/1200 established
set 29 09:09:55 eu-Aspire-VX5-591G piaware[1541]: TLS handshake with adept server at piaware.flightaware.com/1200 completed
set 29 09:09:56 eu-Aspire-VX5-591G piaware[1541]: FlightAware server certificate validated
set 29 09:09:56 eu-Aspire-VX5-591G piaware[1541]: encrypted session established with FlightAware
set 29 09:09:56 eu-Aspire-VX5-591G sudo[1598]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=list /usr/bin/netstat --program --tcp --wide --all --numeric
set 29 09:09:56 eu-Aspire-VX5-591G sudo[1599]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/netstat --program --tcp --wide --all --numeric
set 29 09:09:56 eu-Aspire-VX5-591G sudo[1599]: pam_unix(sudo:session): session opened for user root by (uid=0)
set 29 09:09:56 eu-Aspire-VX5-591G sudo[1599]: pam_unix(sudo:session): session closed for user root
set 29 09:09:56 eu-Aspire-VX5-591G sudo[1605]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/netstat --program --tcp --wide --all --numeric
set 29 09:09:56 eu-Aspire-VX5-591G sudo[1605]: pam_unix(sudo:session): session opened for user root by (uid=0)
set 29 09:09:56 eu-Aspire-VX5-591G sudo[1605]: pam_unix(sudo:session): session closed for user root
set 29 09:09:56 eu-Aspire-VX5-591G piaware[1541]: no ADS-B data program seen listening on port 30005 for 3 seconds, next check in 60s
set 29 09:09:56 eu-Aspire-VX5-591G piaware[1541]: UAT support disabled by local configuration setting: uat-receiver-type
set 29 09:09:56 eu-Aspire-VX5-591G piaware[1541]: adept reported location: -22.95821, -43.19639, 182ft AMSL
set 29 09:09:56 eu-Aspire-VX5-591G piaware[1541]: logged in to FlightAware as user vsqz44
set 29 09:09:56 eu-Aspire-VX5-591G piaware[1541]: my feeder ID is xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
set 29 09:09:56 eu-Aspire-VX5-591G piaware[1541]: site statistics URL: https://flightaware.com/adsb/stats/user/vsqz44#stats-xxxxx
set 29 09:09:56 eu-Aspire-VX5-591G piaware[1541]: multilateration data requested
set 29 09:09:56 eu-Aspire-VX5-591G sudo[1607]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/netstat --program --tcp --wide --all --numeric
set 29 09:09:56 eu-Aspire-VX5-591G sudo[1607]: pam_unix(sudo:session): session opened for user root by (uid=0)
set 29 09:09:56 eu-Aspire-VX5-591G sudo[1607]: pam_unix(sudo:session): session closed for user root
set 29 09:09:56 eu-Aspire-VX5-591G piaware[1541]: no ADS-B data program is serving on port 30005, not starting multilateration client yet
set 29 09:10:27 eu-Aspire-VX5-591G piaware[1541]: 0 msgs recv’d from dump1090; 0 msgs sent to FlightAware
set 29 09:10:56 eu-Aspire-VX5-591G sudo[2317]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/netstat --program --tcp --wide --all --numeric
set 29 09:10:56 eu-Aspire-VX5-591G sudo[2317]: pam_unix(sudo:session): session opened for user root by (uid=0)
set 29 09:10:56 eu-Aspire-VX5-591G sudo[2317]: pam_unix(sudo:session): session closed for user root
set 29 09:10:56 eu-Aspire-VX5-591G piaware[1541]: no ADS-B data program seen listening on port 30005 for 63 seconds, next check in 60s
set 29 09:10:56 eu-Aspire-VX5-591G sudo[2319]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/netstat --program --tcp --wide --all --numeric
set 29 09:10:56 eu-Aspire-VX5-591G sudo[2319]: pam_unix(sudo:session): session opened for user root by (uid=0)
set 29 09:10:56 eu-Aspire-VX5-591G sudo[2319]: pam_unix(sudo:session): session closed for user root
set 29 09:10:56 eu-Aspire-VX5-591G piaware[1541]: no ADS-B data program is serving on port 30005, not starting multilateration client yet
set 29 09:11:56 eu-Aspire-VX5-591G sudo[2950]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/netstat --program --tcp --wide --all --numeric
set 29 09:11:56 eu-Aspire-VX5-591G sudo[2950]: pam_unix(sudo:session): session opened for user root by (uid=0)
set 29 09:11:56 eu-Aspire-VX5-591G sudo[2950]: pam_unix(sudo:session): session closed for user root
set 29 09:11:56 eu-Aspire-VX5-591G piaware[1541]: no ADS-B data program seen listening on port 30005 for 123 seconds, next check in 60s
set 29 09:11:56 eu-Aspire-VX5-591G sudo[2952]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/netstat --program --tcp --wide --all --numeric
set 29 09:11:56 eu-Aspire-VX5-591G sudo[2952]: pam_unix(sudo:session): session opened for user root by (uid=0)

That’s contrary to the piaware-status output.

Check if there is data:

nc localhost 30005

There should be strange symbols flashing over the screen.
Interrupt with Ctrl-C

If there is no output, then dump1090-fa isn’t really running.
Have you tried rebooting?

Let’s also check the dump1090-fa command line:

pgrep -a dump1090
sudo netstat --program --tcp --wide --all --numeric | grep LISTEN | grep 30005
1 Like
nc localhost 30005 - strange symbols

$ pgrep -a dump1090
4244 /usr/bin/dump1090-fa --device-index 0 --gain -10 --lat -23.9643 --lon -43.2037 --ppm 0 --net-bo-port 30005 --max-range 360 --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-location-accuracy 1 --lat -22.95945 --lon -43.19731 --write-json /run/dump1090-fa --quiet

I have airplanes on the map localhost:8080 and I’m feeding FR24 successfully

Thanks

Do the last command as well.

Seems piaware is confused and not detecting that there is output on localhost:30005

1 Like
sudo netstat --program --tcp --wide --all --numeric | grep LISTEN | grep 30005

Gets nothing

Just this part then.

1 Like

sudo netstat --program --tcp --wide --all --numeric
Conexões Internet Ativas (servidores e estabelecidas)
Proto Recv-Q Send-Q Endereço Local Endereço Remoto Estado PID/Program name
tcp 0 0 0.0.0.0:30104 0.0.0.0:* OUÇA 4452/dump1090-fa
tcp 0 0 0.0.0.0:30334 0.0.0.0:* OUÇA 1561/fr24feed
tcp 0 0 0.0.0.0:8080 0.0.0.0:* OUÇA 1567/lighttpd
tcp 0 0 0.0.0.0:80 0.0.0.0:* OUÇA 1567/lighttpd
tcp 0 0 0.0.0.0:30002 0.0.0.0:* OUÇA 4452/dump1090-fa
tcp 0 0 0.0.0.0:8754 0.0.0.0:* OUÇA 1561/fr24feed
tcp 0 0 0.0.0.0:30003 0.0.0.0:* OUÇA 4452/dump1090-fa
tcp 0 0 0.0.0.0:30004 0.0.0.0:* OUÇA 4452/dump1090-fa
tcp 0 0 0.0.0.0:30005 0.0.0.0:* OUÇA 4452/dump1090-fa
tcp 0 0 127.0.0.53:53 0.0.0.0:* OUÇA 929/systemd-resolve
tcp 0 0 127.0.0.1:631 0.0.0.0:* OUÇA 1015/cupsd
tcp 0 0 192.168.0.77:8080 192.168.0.77:45354 TIME_WAIT -
tcp 0 0 192.168.0.77:42003 70.42.6.191:1200 ESTABELECIDA 1541/piaware
tcp 0 0 192.168.0.77:8080 192.168.0.77:45366 ESTABELECIDA 1567/lighttpd
tcp 0 0 127.0.0.1:30005 127.0.0.1:49468 ESTABELECIDA 4452/dump1090-fa
tcp 0 0 192.168.0.77:35858 200.236.31.207:443 TIME_WAIT -
tcp 0 0 192.168.0.77:45366 192.168.0.77:8080 ESTABELECIDA 2345/firefox
tcp 0 0 192.168.0.77:35862 200.236.31.207:443 TIME_WAIT -
tcp 0 1 192.168.0.77:54214 35.222.85.5:80 SYN_ENVIADO 1014/NetworkManager
tcp 0 0 127.0.0.1:49468 127.0.0.1:30005 ESTABELECIDA 1561/fr24feed
tcp 0 0 192.168.0.77:50976 52.43.174.132:443 ESTABELECIDA 2345/firefox
tcp6 0 0 :::30104 :::* OUÇA 4452/dump1090-fa
tcp6 0 0 :::30002 :::* OUÇA 4452/dump1090-fa
tcp6 0 0 :::30003 :::* OUÇA 4452/dump1090-fa
tcp6 0 0 :::30004 :::* OUÇA 4452/dump1090-fa
tcp6 0 0 :::30005 :::* OUÇA 4452/dump1090-fa
tcp6 0 0 ::1:631 :::* OUÇA 1015/cupsd
tcp6 0 0 2804:14d:5c51:9503:7dd2:3472:38f2:79b:59912 2600:1fa0:406c:1141:34da:ed39:::443 TIME_WAIT -
tcp6 0 0 2804:14d:5c51:9503:7dd2:3472:38f2:79b:48526 2800:3f0:4004:809::200e:443 ESTABELECIDA 2345/firefox
tcp6 0 0 2804:14d:5c51:9503:7dd2:3472:38f2:79b:43498 2800:3f0:4004:800::200a:443 TIME_WAIT -
tcp6 0 0 2804:14d:5c51:9503:7dd2:3472:38f2:79b:44546 2001:470:1:791::11:443 ESTABELECIDA 2345/firefox

I see the problem, it’s not made for other languages i guess.

Can you turn the system language to English?
Otherwise you’ll have to change the piaware source code to ignore that check.

1 Like

See it checks the output for “LISTEN”, but it’s not there because the language is different.

1 Like