Did you confirm your feed is up and running? Any stats come up? Your user page shows:
No Active FlightAware ADS-B Sites For This User (JerrytheK)
Although FA recognizes the receiver, still no data being sent and/or received:
PiAware - Claim and Link a Brand New PiAware Ground Station
Unfortunately, FlightAware hasn’t found a new, unclaimed PiAware connection yet from your IP (75.71.43.253 or 2601:283:4401:65ab:1515:c428:ecba:d283). Either your device has not yet connected (it takes a few minutes to start) or you are on a different IP address.
FlightAware searches for PiAware connections on the same global IP (75.71.43.253 or 2601:283:4401:65ab:1515:c428:ecba:d283) as your connection. If you are on the same LAN as the PiAware device, then we should be able to find the receiver and claim it for you. You should wait a few minutes after plugging in your PiAware device before expecting it to be connected to FlightAware. Try checking cable connections, waiting a few moments, and trying again.
Check Again for my PiAware Setup Manually with HDMI display + keyboard (advanced)
Linked PiAware Receivers (JerrytheK)
Great news! Your account is associated with the following PiAware receivers and you can view your statistics here:
b8:27:eb:93:8f:bd: PiAware (Debian Package Add-on) 2.1 added Monday, March 21, 2016 (75.71.43.253 / 10.0.1.65)
It’s now set up in the attic. I’m going to see what happens overnight.
It shows up on my local network and as working.
Any suggestions (as always) are greatly appreciated.
If you have access to it via ssh or otherwise, you can run the command
sudo piaware-status
And it will give a snapshot of whether it’s running properly, like the following…
pi@raspberrypi:~ $ sudo piaware-status
dump1090 is not running.
faup1090 is running.
piaware is running.
dump1090-mutabi is listening for connections on port 30005.
faup1090 is connected to port 30005.
piaware is connected to FlightAware.
dump1090-mutabi is producing data on port 30005.
Thanks.
I’m still trying to figure out SSH.
I’ll get it down from the attic in the morning, and hook it up to a monitor, etc., and run that command and report in with the results.
Thanks for the help!
Sorted out SSH!!
Here’s what I get:
pi@raspberrypi:~ $ sudo piaware-status
dump1090 is not running.
faup1090 is not running.
piaware is not running.
no program appears to be listening for connections on port 30005.
faup1090 is NOT connected to port 30005.
piaware is NOT connected to FlightAware.
got ‘couldn’t open socket: connection refused’
maybe dump1090 is NOT producing data on port 30005.
Clearly need to restart it and try to check it’s status again.
Time to get some sleep though.
REALLY appreciate your help!
Yup reboot and see if it gets up and going…
sudo reboot
OR
sudo shutdown -r now
Good night!
Just did a remote reboot, ran status and got the same messages as before.
Time to call it for me.
I’ll get it hard-wire connected in the morning, repower it and see what happens and report back.
If you can ssh into it, you can leave it up there while you rejigger. Piaware should have started on boot automatically. You can try to manually restart it via:
sudo /etc/init.d/piaware restart
Then check status again after a minute. Though I suspect something may have gone wrong during setup.
pi@raspberrypi:~ $ sudo piaware-status
dump1090 is not running.
faup1090 is not running.
piaware is not running.
no program appears to be listening for connections on port 30005.
faup1090 is NOT connected to port 30005.
piaware is NOT connected to FlightAware.
got ‘couldn’t open socket: connection refused’
maybe dump1090 is NOT producing data on port 30005.
It sounds like dump1090 is not running.
Did you install it using these instructions?
flightaware.com/adsb/piaware/install
what is the out of the command
dump1090
or
netstat -an | grep 30
Yes, I installed Noobs, and then used the instructions in the link you just posted.
I have another SD card that I loaded with the FA software without using Noobs and am going to try that, as well as some other strategies with the system currently in the Pi.
I’ll keep you (and others) updated on progress.
Thanks
I today first use the Noobs set up and downloaded the flightaware software from its website.
That didn’t work.
I then created a new SD card file using jprochazka “ADS-B Receiver Image March 7th, 2016” and then went through the install process.
That also didn’t work.
Here’s what I’m getting when I run sudo piaware-status
pi@raspberrypi:~ $ sudo piaware-status
dump1090 is not running.
faup1090 is not running.
piaware is not running.
dump1090-mutabi is listening for connections on port 30005.
faup1090 is NOT connected to port 30005.
piaware is NOT connected to FlightAware.
dump1090-mutabi is producing data on port 30005.
pi@raspberrypi:~ $
I’m now wondering if the problem is that I’m using a R Pi 3, rather than a 2.
If anyone thinks that’s the issue, I’ll buy a 2 and try installing on that.
I thought I needed the built-in wireless of the 3, but I forgot I have a switch in the attic, so I can go hard wired, rather than wireless.
Any thoughts will be greatly appreciated!!
Thanks in advance.
I think there is a pi-3-supporting piaware sdcard image on its way in the next few days, so it might be simplest to wait for that.
Anything reported in the PiAware log file?
The log file should be in the /tmp directory.
How do I access the /tmp directory?
And if I don’t get this sorted out quickly, I’ll wait for the P 3 version.
cat /tmp/piaware.out
Very odd. I ran the pi 2, upgraded to the pi 3 last week, running NOOBS. Everything’s up and running just fine. Don’t think it’s a compatibility issue.
We need an IRC chat for this board so we can live-support each other 
03/22/2016 16:08:13 ****************************************************
03/22/2016 16:08:13 piaware version 2.1-5 is running, process ID 730
03/22/2016 16:08:13 your system info is: Linux raspberrypi 4.1.19-v7+ #858 SMP Tue Mar 15 15:56:00 GMT 2016 armv7l GNU/Linux
03/22/2016 16:08:13 Connecting to FlightAware adept server at piaware.flightaware.com/1200
03/22/2016 16:08:13 Connection to adept server at piaware.flightaware.com/1200 failed: couldn’t open socket: network is unreachable
03/22/2016 16:08:13 reconnecting in 95 seconds…
03/22/2016 16:08:13 ADS-B data program ‘dump1090-mutabi’ is listening on port 30005, so far so good
03/22/2016 16:08:13 Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout
03/22/2016 16:08:13 Started faup1090 (pid 818) to connect to dump1090-mutabi
03/22/2016 16:08:14 piaware received a message from dump1090-mutabi!
03/22/2016 16:08:43 26 msgs recv’d from dump1090-mutabi; 0 msgs sent to FlightAware
03/22/2016 16:09:48 Connecting to FlightAware adept server at piaware.flightaware.com/1200
03/22/2016 16:09:48 Connection with adept server at piaware.flightaware.com/1200 established
03/22/2016 16:09:49 FlightAware server SSL certificate validated
03/22/2016 16:09:49 encrypted session established with FlightAware
03/22/2016 16:09:49 autoUpdate is not configured in /etc/piaware or by piaware-config
03/22/2016 16:09:49 manualUpdate is not configured in /etc/piaware or by piaware-config
03/22/2016 16:09:49 multilateration support enabled (use piaware-config to disable)
03/22/2016 16:09:49 *******************************************
03/22/2016 16:09:49 LOGIN FAILED: status ‘error’: reason ‘incorrect password’
03/22/2016 16:09:49 please correct this, possibly using piaware-config
03/22/2016 16:09:49 to set valid Flightaware user name and password.
03/22/2016 16:09:49 piaware will now exit.
03/22/2016 16:09:49 You can start it up again using ‘sudo /etc/init.d/piaware start’
03/22/2016 16:09:49 TLS alert: close notify
The issue appears to be an incorrect password.
I’ve tried resetting that using sudo piaware-config -user JerrytheK -password, which hasn’t seemed to work.
I’m now rerunning jp…'s install script to see if I can sort out the password issue.
When you run –
sudo piaware-config -user JerrytheK -password
Does it prompt you for password?
ETA – BOOM. Looks like you’re up and running:
Success!!!
pi@raspberrypi:~ $ cat /tmp/piaware.out
03/22/2016 17:17:12 ****************************************************
03/22/2016 17:17:12 piaware version 2.1-5 is running, process ID 726
03/22/2016 17:17:12 your system info is: Linux raspberrypi 4.1.19-v7+ #858 SMP Tue Mar 15 15:56:00 GMT 2016 armv7l GNU/Linux
03/22/2016 17:17:12 Connecting to FlightAware adept server at piaware.flightaware.com/1200
03/22/2016 17:17:12 ADS-B data program ‘dump1090-mutabi’ is listening on port 30005, so far so good
03/22/2016 17:17:12 Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout
03/22/2016 17:17:12 Started faup1090 (pid 915) to connect to dump1090-mutabi
03/22/2016 17:17:12 Connection with adept server at piaware.flightaware.com/1200 established
03/22/2016 17:17:12 FlightAware server SSL certificate validated
03/22/2016 17:17:12 encrypted session established with FlightAware
03/22/2016 17:17:12 autoUpdate is not configured in /etc/piaware or by piaware-config
03/22/2016 17:17:12 manualUpdate is not configured in /etc/piaware or by piaware-config
03/22/2016 17:17:12 multilateration support enabled (use piaware-config to disable)
03/22/2016 17:17:13 logged in to FlightAware as user JerrytheK
03/22/2016 17:17:13 piaware received a message from dump1090-mutabi!
03/22/2016 17:17:14 piaware has successfully sent several msgs to FlightAware!
03/22/2016 17:35:53 15 msgs recv’d from dump1090-mutabi; 15 msgs sent to FlightAware
03/22/2016 17:35:53 timed out waiting for alive message from FlightAware, reconnecting…
03/22/2016 17:35:53 TLS alert: close notify
03/22/2016 17:35:53 reconnecting in 68 seconds…
03/22/2016 17:36:23 42 msgs recv’d from dump1090-mutabi (27 in last 1m); 15 msgs sent to FlightAware
03/22/2016 17:37:01 Connecting to FlightAware adept server at piaware.flightaware.com/1200
03/22/2016 17:37:01 Connection with adept server at piaware.flightaware.com/1200 established
03/22/2016 17:37:01 FlightAware server SSL certificate validated
03/22/2016 17:37:01 encrypted session established with FlightAware
03/22/2016 17:37:01 autoUpdate is not configured in /etc/piaware or by piaware-config
03/22/2016 17:37:01 manualUpdate is not configured in /etc/piaware or by piaware-config
03/22/2016 17:37:01 multilateration support enabled (use piaware-config to disable)
03/22/2016 17:37:01 logged in to FlightAware as user JerrytheK
03/22/2016 17:38:43 piaware (process 726) is shutting down because it received a shutdown signal (SIGTERM) from the system…
03/22/2016 17:38:43 removing pidfile /var/run/piaware.pid
03/22/2016 17:38:43 piaware (process 726) is exiting…
03/22/2016 17:38:43 TLS alert: close notify
03/22/2016 17:38:43 ****************************************************
03/22/2016 17:38:43 piaware version 2.1-5 is running, process ID 998
03/22/2016 17:38:43 your system info is: Linux raspberrypi 4.1.19-v7+ #858 SMP Tue Mar 15 15:56:00 GMT 2016 armv7l GNU/Linux
03/22/2016 17:38:43 Connecting to FlightAware adept server at piaware.flightaware.com/1200
03/22/2016 17:38:43 ADS-B data program ‘dump1090-mutabi’ is listening on port 30005, so far so good
03/22/2016 17:38:43 Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout
03/22/2016 17:38:43 Started faup1090 (pid 1040) to connect to dump1090-mutabi
03/22/2016 17:38:43 Connection with adept server at piaware.flightaware.com/1200 established
03/22/2016 17:38:43 FlightAware server SSL certificate validated
03/22/2016 17:38:43 encrypted session established with FlightAware
03/22/2016 17:38:44 autoUpdate is not configured in /etc/piaware or by piaware-config
03/22/2016 17:38:44 manualUpdate is not configured in /etc/piaware or by piaware-config
03/22/2016 17:38:44 multilateration support enabled (use piaware-config to disable)
03/22/2016 17:38:44 logged in to FlightAware as user JerrytheK
03/22/2016 17:38:44 piaware received a message from dump1090-mutabi!
03/22/2016 17:38:45 piaware has successfully sent several msgs to FlightAware!
03/22/2016 17:39:13 31 msgs recv’d from dump1090-mutabi; 31 msgs sent to FlightAware
pi@raspberrypi:~ $
And:
Dear Jerry Kashinski,
Good news! We are now receiving and processing live data from your PiAware (b8:27:eb:93:8f:bd).
You can view your receiver’s statistics & rankings, plus you should set your exact location and nearest airport here:
flightaware.com/adsb/stats/user/JerrytheK
It is important that your location be set precisely on that page in order for multilateration (MLAT) to work.
Going forward, as long as your Raspberry Pi is running, it should continue to feed FlightAware automatically without any further effort.
From your local network, you can access the live PiAware web interface here: 10.0.1.63:8080/
Remember that the signals from aircraft are not designed to penetrate objects, so the antenna should be located “line of sight” to the sky with no obstructions. The most optimal installations, which are installed outdoors and on a roof, have a range of over 250mi/400km.
Thanks for your participation and have fun! Please spread the word to friends so that we can work together to improve coverage around the world!
FlightAware ADS-B Team
adsbsupport@flightaware.com
Thanks to all.
With all of your help, this has been a rewarding learning experience.
Cheers!
Last thing you may need to do at some point, since it looks like you’re not receiving MLAT positions, is change a port in your config. You’ll track more planes this way…
If you’re using Mutability:
sudo nano /etc/default/dump1090-mutability
Change the Beast Input line below to be port 30104, if it isn’t already:
BEAST_INPUT_PORT="30104"
Save the changes and exit.
Then restart dump1090…