Hello all:
setting up my second piaware: new RP3, new pro stick, filter, antenna.
As I follow the setup instructions, I successfully load “piaware-sd-card-3.0.4” onto the SD card, boot up the RP, but alas the :8080 shows me a generic map with the statement:
“Problem fetching data from dump1090.
AJAX call failed (error: Not Found). Maybe dump1090 is no longer running?
The displayed map data will be out of date.”
Have re-started it multiple times, to no avail.
the pro stick is inserted at the time of the attempt:
Any hints most welcome: I am a noob when it comes to linux troubleshooting…
Port 8080 will not work when accessing your system from the Internet IP if using piaware 3
If you are on your local net, your internal IP like 192.168.1.XX:80 or 8080 will work.
My solution was to forward a port(any number like 2020) to port 80 or 8080 on your internal IP, so now your_ext_IP:2020 is a go.
tried to connect, from the same subnet, to 192.168.7.148/dump1090-fa/, and I get the same aforementioned result.
i get a map centered on Milan, and the note: "
Problem fetching data from dump1090.
AJAX call failed (error: Not Found). Maybe dump1090 is no longer running?
The displayed map data will be out of date."
This tells me:
I am connecting to the Pi
but somehow, the Pi is not running 1090? (not sure here)…
I saw some posts about replacing dump1090 with dump1090-mutability → but since I just installed using the very latest image available on flight aware, I presume that whatever s/w packages needed to be in there ARE indeed in there…
Appreciate all the help. I can SSH into the unit, and will gladly run any suggested “show” commands to see what process are running - its just I am not sure what to run to see if all is OK on the Pi.
Piaware 3.0.4 image has built-in dump1090-fa (Flightaware’s repackaged version of dump1090-mutability).
Try
sudo service dump1090-fa status -l
and post the output.
If the output contains your actual latitude & longitude, while posting in forum, replace these by xxxxx for privacy reasons.
I expect you will see errors about “no supported devices found” as that’s the most likely cause for dump1090 to fail to start. If so that means the Pi is not seeing your dongle, either you have a bad connection, a bad connector, or a bad dongle.
I think you found it:
^Cpi@piaware:~$ sudo journalctl -f _SYSTEMD_UNIT=dump1090-fa.service
– Logs begin at Fri 2016-08-19 14:20:19 UTC. –
Sep 06 23:46:13 piaware dump1090-fa[4878]: No supported devices found.
Sep 06 23:46:43 piaware dump1090-fa[4885]: Tue Sep 6 23:46:43 2016 UTC dump1090-fa v3.0.3 starting up.
Sep 06 23:46:43 piaware dump1090-fa[4885]: Using sample converter: UC8, integer/table path
Sep 06 23:46:43 piaware dump1090-fa[4885]: No supported devices found.
Sep 06 23:47:14 piaware dump1090-fa[4896]: Tue Sep 6 23:47:14 2016 UTC dump1090-fa v3.0.3 starting up.
Sep 06 23:47:14 piaware dump1090-fa[4896]: Using sample converter: UC8, integer/table path
Sep 06 23:47:14 piaware dump1090-fa[4896]: No supported devices found.
Sep 06 23:47:44 piaware dump1090-fa[4907]: Tue Sep 6 23:47:44 2016 UTC dump1090-fa v3.0.3 starting up.
Sep 06 23:47:44 piaware dump1090-fa[4907]: Using sample converter: UC8, integer/table path
Sep 06 23:47:44 piaware dump1090-fa[4907]: No supported devices found.
Sep 06 23:48:15 piaware dump1090-fa[4929]: Tue Sep 6 23:48:15 2016 UTC dump1090-fa v3.0.3 starting up.
Sep 06 23:48:15 piaware dump1090-fa[4929]: Using sample converter: UC8, integer/table path
Sep 06 23:48:15 piaware dump1090-fa[4929]: No supported devices found.
^Cpi@piaware:~$
Any way to “test” the dongle with a PC or a mac? Something that would let me see if it is alive at all? I see the amber LED on it, but no other proof of life at all.
Can’t speak for Windows, but you can try lsusb on the Pi itself (or any Linux machine) to see if it is at least enumerating, it should look something like this:
pi@piaware:~$ lsusb
Bus 001 Device 006: ID 0bda:2832 Realtek Semiconductor Corp. RTL2832U DVB-T <--- this is what you want to see
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
You said this was your second piaware, can you try the new dongle in your old Pi to eliminate the Pi itself as the cause of the problem?
current pi:
Bus 001 Device 005: ID 045e:007d Microsoft Corp. Notebook Optical Mouse
Bus 001 Device 006: ID 05ac:020b Apple, Inc. Pro Keyboard [Mitsumi, A1048/US layout]
Bus 001 Device 004: ID 05ac:1003 Apple, Inc. Hub in Pro Keyboard [Mitsumi, A1048]
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
so highly unlikely that it is not the dongle.
just ordered a replacement on Amazon.
Thank you for your expertise: I was re-installing the firmware, and loosing too much time figuring it out.
Appreciate your willingness to help a lowly Habs fan (taking the risk of revealing my true colors to a likely Leafs fan, abcd567 being a YYZ kind a guy )
)