I have piaware running on a raspberry pi 4 have not looked at it in some time.
and it seems like i am not getting any data.
the web us is working and running in port 8080
but it is showing
Total Aircraft: 0
With Positions: 0 UAT Message Rate: 0.0/sec
Position History: 0
I remember a process running dump1090 in the past i do not see that process running now.
Anyone have a idea on what to look for or where to look for a answer?
You have two options.
The more comfortable is to access the process using your profile on Flightradar. For this go to your profile, select the gear and in the upcoming box you have parts of the log.
In this window you can either restart your whole device or the processes themselves only.
The second option require that you access your device via SSH
once logged in you can control the status of piaware with the command
sudo systemctl status piaware
In case it does not state “active”, you can restart the service with
sudo systemctl restart piaware
The simplest way is to reboot the whole device and check if it is working again.
sudo shutdown -r now
will do that.
Or
sudo reboot now 
restarting piaware was the first thing i did.
“sudo /etc/init.d/piaware restart”
no change.
and then reboot.
No change.
when I do a status
i@piaware:~ $ 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 Sun 2021-09-19 23:48:01 EDT; 8h ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Main PID: 565 (piaware)
Tasks: 2 (limit: 4915)
CGroup: /system.slice/piaware.service
└─565 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
Sep 20 08:24:10 piaware sudo[30177]: pam_unix(sudo:session): session closed for user root
Sep 20 08:24:10 piaware piaware[565]: no ADS-B data program is serving on port 30005, not starting multilateration client yet
Sep 20 08:25:06 piaware sudo[30232]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/netstat --program --tcp --wide --all --numeric
Sep 20 08:25:06 piaware sudo[30232]: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 20 08:25:06 piaware sudo[30232]: pam_unix(sudo:session): session closed for user root
Sep 20 08:25:06 piaware piaware[565]: no ADS-B data program seen listening on port 30005 for 250 seconds, next check in 60s
Sep 20 08:25:10 piaware sudo[30243]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/netstat --program --tcp --wide --all --numeric
Sep 20 08:25:10 piaware sudo[30243]: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 20 08:25:10 piaware sudo[30243]: pam_unix(sudo:session): session closed for user root
Sep 20 08:25:10 piaware piaware[565]: no ADS-B data program is serving on port 30005, not starting multilateration client yet
what is “no ADS-B data program is serving on port 30005, not starting multilateration client yet” telling me?
That indicates that your dump1090-fa is not running (assuming you’re not using readsb)
Check this one
sudo systemctl status dump1090-fa
That is required, otherwise Piaware cannot get any data and transfer it to FA
pi@piaware:/var/run $ sudo 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: activating (auto-restart) (Result: exit-code) since Mon 2021-09-20 12:17:18 EDT; 6s ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Process: 9552 ExecStart=/usr/share/dump1090-fa/start-dump1090-fa --write-json /run/dump1090-fa (code=exited, status=1/FAILURE)
Main PID: 9552 (code=exited, status=1/FAILURE)
I did note that there is no directory /var/run/dump1090-fa
i do find the /var/run/skyaware978 and /var/run/piaware but /var/run/dump1090-fa is missing
I do a
sudo systemctl stop dump1090-fa
sudo systemctl start dump1090-fa
sudo systemctl status dump1090-fa
still get
● dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Mon 2021-09-20 12:21:05 EDT; 20s ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Process: 9749 ExecStart=/usr/share/dump1090-fa/start-dump1090-fa --write-json /run/dump1090-fa (code=exited, status=1/FAILURE)
Main PID: 9749 (code=exited, status=1/FAILURE)
Robert
pretty likely that dump1090-fa is simply not installed or at least only partially
If you stop and start the service again, that won’t fix it.
perform the following commands, answering with yes if asked:
sudo apt purge dump1090-fa
sudo apt install dump1090-fa
The first command removes dump1090 and the second reinstall it.
The uninstall might be required to make sure that the installer can reinstall it.
Think i found the probem.
lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 086: ID 214b:7250
Bus 001 Device 085: ID 214b:7250
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I have a [LDKCOK USB 2.0 Type A Male to A Female Active Repeater Extension Cable 60ft
This cable has been working fine for 4 months
now I am not seeing the dongle
when I plug the dongle right into the pi and not use the extention cord i get
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 078: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Why was it working for 4 months and now stop working?
crappy cable perhaps ? 
You never know
Cable can be broken or any of the connectors.
I had an issues the other day where my Airspy continued connecting/disconnecting every few minutes.
I then pressed the USB male connector a bit so it fits better to the slot. Since then it’s working
I was having the same issue where the service stopped working. After running the above two commands and a reboot everything started working again.
Thank you, you saved my day!
sudo apt purge dump1090-fa
sudo apt install dump1090-fa
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.