that’s not a problem, should probably suppress that error.
the airspy-conf script doesn’t care about the directory you run it from.
that’s not a problem, should probably suppress that error.
the airspy-conf script doesn’t care about the directory you run it from.
So as it stands now, I have gone through all scripts, How can we check what is installed/working
sudo journalctl -eu airspy_adsb
sudo journalctl -eu dump1090-fa
sudo journalctl -eu piaware
Or just check the local dump1090-fa map?
And please learn how to post logs/code:
Debug commands · wiedehopf/adsb-wiki Wiki · GitHub
It’s really hard to read garbled logs.
‘’’
Sep 19 07:09:47 odroid airspy_adsb[13043]: airspy_open() failed: AIRSPY_ERROR_NOT_FOUND (-5)
‘’’
That’s the airspy not plugged in.
Also you might need to copy the back-ticks if you aren’t using a US keyboard.
The backtick is missing on quite a few keyboard layouts.
```
odroid@odroid:~$ sudo journalctl -eu dump1090-fa
[sudo] password for odroid:
Sep 19 06:51:11 odroid dump1090-fa[12643]: rtlsdr: no supported devices found.
Sep 19 06:51:11 odroid systemd[1]: dump1090-fa.service: Main process exited, cod
Sep 19 06:51:11 odroid systemd[1]: dump1090-fa.service: Failed with result 'exit
Sep 19 06:51:42 odroid systemd[1]: dump1090-fa.service: Service hold-off time ov
Sep 19 06:51:42 odroid systemd[1]: dump1090-fa.service: Scheduled restart job, r
Sep 19 06:51:42 odroid systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware
Sep 19 06:51:42 odroid systemd[1]: Started dump1090 ADS-B receiver (FlightAware
Sep 19 06:51:42 odroid dump1090-fa[12961]: Thu Sep 19 06:51:42 2019 UTC dump109
Sep 19 06:51:42 odroid dump1090-fa[12961]: rtlsdr: no supported devices found.
Sep 19 06:51:42 odroid systemd[1]: dump1090-fa.service: Main process exited, cod
Sep 19 06:51:42 odroid systemd[1]: dump1090-fa.service: Failed with result 'exit
Sep 19 06:52:12 odroid systemd[1]: dump1090-fa.service: Service hold-off time ov
Sep 19 06:52:12 odroid systemd[1]: dump1090-fa.service: Scheduled restart job, r
Sep 19 06:52:12 odroid systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware
Sep 19 06:52:12 odroid systemd[1]: Started dump1090 ADS-B receiver (FlightAware
Sep 19 06:52:12 odroid dump1090-fa[12976]: Thu Sep 19 06:52:12 2019 UTC dump109
Sep 19 06:52:12 odroid dump1090-fa[12976]: rtlsdr: no supported devices found.
Sep 19 06:52:12 odroid systemd[1]: dump1090-fa.service: Main process exited, cod
Sep 19 06:52:12 odroid systemd[1]: dump1090-fa.service: Failed with result 'exit
Sep 19 06:52:19 odroid systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware
Sep 19 06:52:19 odroid systemd[1]: Started dump1090 ADS-B receiver (FlightAware
Sep 19 06:52:19 odroid dump1090-fa[13052]: Thu Sep 19 06:52:19 2019 UTC dump109
Sep 19 06:52:19 odroid dump1090-fa[13052]: Net-only mode, no SDR device or file
lines 172-194/194 (END)
Sep 19 06:51:11 odroid dump1090-fa[12643]: rtlsdr: no supported devices found.
Sep 19 06:51:11 odroid systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
Sep 19 06:51:11 odroid systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.
Sep 19 06:51:42 odroid systemd[1]: dump1090-fa.service: Service hold-off time over, scheduling restart.
Sep 19 06:51:42 odroid systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is at 22.
Sep 19 06:51:42 odroid systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Sep 19 06:51:42 odroid systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Sep 19 06:51:42 odroid dump1090-fa[12961]: Thu Sep 19 06:51:42 2019 UTC dump1090-fa 3.7.1 starting up.
Sep 19 06:51:42 odroid dump1090-fa[12961]: rtlsdr: no supported devices found.
Sep 19 06:51:42 odroid systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
Sep 19 06:51:42 odroid systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.
Sep 19 06:52:12 odroid systemd[1]: dump1090-fa.service: Service hold-off time over, scheduling restart.
Sep 19 06:52:12 odroid systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is at 23.
Sep 19 06:52:12 odroid systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Sep 19 06:52:12 odroid systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Sep 19 06:52:12 odroid dump1090-fa[12976]: Thu Sep 19 06:52:12 2019 UTC dump1090-fa 3.7.1 starting up.
Sep 19 06:52:12 odroid dump1090-fa[12976]: rtlsdr: no supported devices found.
Sep 19 06:52:12 odroid systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
Sep 19 06:52:12 odroid systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.
Sep 19 06:52:19 odroid systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Sep 19 06:52:19 odroid systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Sep 19 06:52:19 odroid dump1090-fa[13052]: Thu Sep 19 06:52:19 2019 UTC dump1090-fa 3.7.1 starting up.
Sep 19 06:52:19 odroid dump1090-fa[13052]: Net-only mode, no SDR device or file open.
lines 172-194/194 (END)
Sep 19 06:51:11 odroid dump1090-fa[12643]: rtlsdr: no supported devices found.
Sep 19 06:51:11 odroid systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
Sep 19 06:51:11 odroid systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.
Sep 19 06:51:42 odroid systemd[1]: dump1090-fa.service: Service hold-off time over, scheduling restart.
Sep 19 06:51:42 odroid systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is at 22.
Sep 19 06:51:42 odroid systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Sep 19 06:51:42 odroid systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Sep 19 06:51:42 odroid dump1090-fa[12961]: Thu Sep 19 06:51:42 2019 UTC dump1090-fa 3.7.1 starting up.
Sep 19 06:51:42 odroid dump1090-fa[12961]: rtlsdr: no supported devices found.
Sep 19 06:51:42 odroid systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
Sep 19 06:51:42 odroid systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.
Sep 19 06:52:12 odroid systemd[1]: dump1090-fa.service: Service hold-off time over, scheduling restart.
Sep 19 06:52:12 odroid systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is at 23.
Sep 19 06:52:12 odroid systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Sep 19 06:52:12 odroid systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Sep 19 06:52:12 odroid dump1090-fa[12976]: Thu Sep 19 06:52:12 2019 UTC dump1090-fa 3.7.1 starting up.
Sep 19 06:52:12 odroid dump1090-fa[12976]: rtlsdr: no supported devices found.
Sep 19 06:52:12 odroid systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
Sep 19 06:52:12 odroid systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.
Sep 19 06:52:19 odroid systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Sep 19 06:52:19 odroid systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Sep 19 06:52:19 odroid dump1090-fa[13052]: Thu Sep 19 06:52:19 2019 UTC dump1090-fa 3.7.1 starting up.
Sep 19 06:52:19 odroid dump1090-fa[13052]: Net-only mode, no SDR device or file open.
lines 172-194/194 (END)
So I figure FA not working either
dump1090-fa is running fine.
The log just still shows its failure to run before you ran airspy-conf.
But at the bottom:
Shows a successful start.
If you just plugged in the airspy, you need to restart airspy_adsb.
You might want to do this to avoid typing passwords by the way:
su -l
Then you can also leave out all the sudo i add to the commands.
Restarting airspy_adsb as root or with sudo in front:
systemctl restart airspy_adsb
Then check if it works now the Airspy is hopefully plugged in.
Well it might be working
Might be?
You’ll probably need this: For Beginners - How to Get Back Existing Station Number in A Fresh Install
Sep 19 07:32:44 odroid airspy_adsb[13043]: Push client connected to localhost:30004 (beast)
So, is it feeding and does the local map work?
Might as well go ahead and try out my improved interface: GitHub - wiedehopf/tar1090: Provides an improved webinterface for use with ADS-B decoders readsb / dump1090-fa
And you want graphs i would guess? GitHub - wiedehopf/graphs1090: Graphs for readsb / dump1090-fa / dump1090 (based on dump1090-tools by mutability)
odroid@odroid:~$ sudo journalctl -eu dump1090-fa
Sep 19 06:51:42 odroid dump1090-fa[12961]: Thu Sep 19 06:51:42 2019 UTC dump1090-fa 3.7.1 starti
Sep 19 06:51:42 odroid dump1090-fa[12961]: rtlsdr: no supported devices found.
Sep 19 06:51:42 odroid systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=
Sep 19 06:51:42 odroid systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.
Sep 19 06:52:12 odroid systemd[1]: dump1090-fa.service: Service hold-off time over, scheduling re
Sep 19 06:52:12 odroid systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is
Sep 19 06:52:12 odroid systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Sep 19 06:52:12 odroid systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Sep 19 06:52:12 odroid dump1090-fa[12976]: Thu Sep 19 06:52:12 2019 UTC dump1090-fa 3.7.1 starti
Sep 19 06:52:12 odroid dump1090-fa[12976]: rtlsdr: no supported devices found.
Sep 19 06:52:12 odroid systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=
Sep 19 06:52:12 odroid systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.
Sep 19 06:52:19 odroid systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Sep 19 06:52:19 odroid systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Sep 19 06:52:19 odroid dump1090-fa[13052]: Thu Sep 19 06:52:19 2019 UTC dump1090-fa 3.7.1 starti
Sep 19 06:52:19 odroid dump1090-fa[13052]: Net-only mode, no SDR device or file open.
Sep 19 07:32:31 odroid systemd[1]: Stopping dump1090 ADS-B receiver (FlightAware customization)..
Sep 19 07:32:31 odroid dump1090-fa[13052]: Thu Sep 19 07:32:31 2019 UTC Caught SIGTERM, shutting
Sep 19 07:32:31 odroid dump1090-fa[13052]: Thu Sep 19 07:32:31 2019 UTC Normal exit.
Sep 19 07:32:31 odroid systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Sep 19 07:32:31 odroid systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Sep 19 07:32:31 odroid dump1090-fa[15478]: Thu Sep 19 07:32:31 2019 UTC dump1090-fa 3.7.1 starti
Sep 19 07:32:31 odroid dump1090-fa[15478]: Net-only mode, no SDR device or file open.
lines 179-201/201 (END)
Sep 19 06:51:42 odroid dump1090-fa[12961]: Thu Sep 19 06:51:42 2019 UTC dump1090-fa 3.7.1 starting up.
Sep 19 06:51:42 odroid dump1090-fa[12961]: rtlsdr: no supported devices found.
Sep 19 06:51:42 odroid systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
Sep 19 06:51:42 odroid systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.
Sep 19 06:52:12 odroid systemd[1]: dump1090-fa.service: Service hold-off time over, scheduling restart.
Sep 19 06:52:12 odroid systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is at 23.
Sep 19 06:52:12 odroid systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Sep 19 06:52:12 odroid systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Sep 19 06:52:12 odroid dump1090-fa[12976]: Thu Sep 19 06:52:12 2019 UTC dump1090-fa 3.7.1 starting up.
Sep 19 06:52:12 odroid dump1090-fa[12976]: rtlsdr: no supported devices found.
Sep 19 06:52:12 odroid systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
Sep 19 06:52:12 odroid systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.
Sep 19 06:52:19 odroid systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Sep 19 06:52:19 odroid systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Sep 19 06:52:19 odroid dump1090-fa[13052]: Thu Sep 19 06:52:19 2019 UTC dump1090-fa 3.7.1 starting up.
Sep 19 06:52:19 odroid dump1090-fa[13052]: Net-only mode, no SDR device or file open.
Sep 19 07:32:31 odroid systemd[1]: Stopping dump1090 ADS-B receiver (FlightAware customization)...
Sep 19 07:32:31 odroid dump1090-fa[13052]: Thu Sep 19 07:32:31 2019 UTC Caught SIGTERM, shutting down..
Sep 19 07:32:31 odroid dump1090-fa[13052]: Thu Sep 19 07:32:31 2019 UTC Normal exit.
Sep 19 07:32:31 odroid systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Sep 19 07:32:31 odroid systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Sep 19 07:32:31 odroid dump1090-fa[15478]: Thu Sep 19 07:32:31 2019 UTC dump1090-fa 3.7.1 starting up.
Sep 19 07:32:31 odroid dump1090-fa[15478]: Net-only mode, no SDR device or file open.
The fa check, it is working but it doesnt look right
that’s all old log messages.
The last start is fine at the bottom.
Sep 19 07:32:31 odroid systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Sep 19 07:32:31 odroid dump1090-fa[15478]: Thu Sep 19 07:32:31 2019 UTC dump1090-fa 3.7.1 starting up.
Sep 19 07:32:31 odroid dump1090-fa[15478]: Net-only mode, no SDR device or file open
Right it is up and running but cant to a piaware config to check options, get this warning:
warning: /etc/piaware.conf: failed to read config file: couldn't open "/etc/piaware.conf": permission denied
use sudo or become root before using the command.
to make yourself root
either
su -l
(and root pw)
or
sudo su -l
and whatever pw you need for sudo.
Or just prepend the piaware-config command with a sudo:
sudo piaware-config
no good any option, still cant bring up config file
you’re telling me the console says you are root?
After using su -l
do this:
whoami
It should say root
root@pi:~# whoami
root
something strange happened, can’t access local data either by skyview or the updated viewer
So check lighttpd if the complete web page doesn’t load:
Debug commands · wiedehopf/adsb-wiki Wiki · GitHub
If the local map just doesn’t show any data, show airspy_adsb and dump1090-fa logs.