PiAware Stopped reporting?


#1

PiAware stopped reporting and the log posts:
"[2016-10-11 14:29 EDT] no ADS-B data program seen listening on port 30005 for 184 seconds, next check in 60s"
Flashed the SD card to updated to Ver 3, tried three different SDR’s, and different power supplies.

Web page on port8080 has an error box on lower left with:
Problem fetching data from dump1090.
AJAX call failed (error). Maybe dump1090 is no longer running?
The displayed map data will be out of date.

What next?


#2

dump1090 is not running. Try “sudo journalctl -u dump1090-fa” and/or “sudo systemctl status dump1090-fa” and see if there’s anything obvious there. It probably can’t see the dongle.


#3

OK, for a Newbi not fluent in LINUX, how do you send a command to PiAware. The “Send Command” field has pre-configured commands and does not allow other commands to be entered. Looked in FAQs could not find how to do it.


#4

easy way in your rpi perhaps mit ssh run:
cd dump1090
sudo service dump1090.sh reload
if not work post your results from last command

Sent from my SM-N910F using Tapatalk


#5

You will need to log in to the Pi using ssh or by connecting a HDMI monitor and keyboard, and run the commands from the command line. Username pi, password flightaware.


#6

both works

Sent from my SM-N910F using Tapatalk


#7

This will not work on a PiAware 3 image.


#8

OBJ said: “You will need to log in to the Pi using ssh”

As I said, a NEWBI here, please explain how to log in iusing ssh?

Sorry for being ignorant about LINUX, old fart here with MS DOS background.


#9

ssh lets you log in over the network. You will need to run a ssh client on your PC; assuming you’re using Windows, PuTTY is an option: chiark.greenend.org.uk/~sgta … nload.html


#10

Thanks,

Results:
pi@piaware:~ $ sudo systemctl status dump1090-fa
● dump1090-fa.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)

Whats missing?


#11

Just to doublecheck, this is a PiAware 3 sdcard image?

If so it’s broken and I don’t know how it got into that state; the sdcard image includes dump1090-fa, but that command is reporting that the service file doesn’t even exist.
Re-flash the image and try again.


#12

Yes, it was a ver2.xx when it stopped working and I downloaded the new ver 3 and re-flashed the SD card, but it still did not work.

I will re-flash and keep you posted.


#13

No Joy!
But different reply to ssh command:

pi@piaware:~$ sudo systemctl status dump1090-fa
● dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2016-10-13 16 :11:35 UTC; 7s ago
Docs: flightaware.com/adsb/piaware/
Process: 1137 ExecStart=/usr/bin/dump1090-fa $RECEIVER_OPTIONS $DECODER_OPTION S $NET_OPTIONS $JSON_OPTIONS $PIAWARE_DUMP1090_LOCATION_OPTIONS --write-json /ru n/dump1090-fa --quiet (code=exited, status=1/FAILURE)
Main PID: 1137 (code=exited, status=1/FAILURE)

Oct 13 16:11:35 piaware systemd[1]: Unit dump1090-fa.service entered failed…e.
Hint: Some lines were ellipsized, use -l to show in full.


#14

That is more like what I expected to see.
What does the other command give you (“sudo journalctl -u dump1090-fa”)


#15

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Thu Oct 13 17:12:16 2016 from 192.168.2.22
pi@piaware:~$ sudo journalctl -u dump1090-fa
– Logs begin at Thu 2016-10-13 19:17:01 UTC, end at Thu 2016-10-13 20:02:15 UTC. –
Oct 13 19:17:10 piaware systemd[1]: Starting dump1090 ADS-B receiver (FlightAware customization)…
Oct 13 19:17:10 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Oct 13 19:17:10 piaware dump1090-fa[437]: Thu Oct 13 19:17:10 2016 UTC dump1090-fa v3.1.0 starting up.
Oct 13 19:17:10 piaware dump1090-fa[437]: Using sample converter: UC8, integer/table path
Oct 13 19:17:10 piaware dump1090-fa[437]: No supported devices found.
Oct 13 19:17:10 piaware systemd[1]: dump1090-fa.service: main process exited, code=exited, status=1/FAILURE
Oct 13 19:17:10 piaware systemd[1]: Unit dump1090-fa.service entered failed state.
Oct 13 19:57:27 piaware systemd[1]: Stopping dump1090 ADS-B receiver (FlightAware customization)…
Oct 13 19:57:27 piaware systemd[1]: Starting dump1090 ADS-B receiver (FlightAware customization)…
Oct 13 19:57:27 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Oct 13 19:57:27 piaware dump1090-fa[621]: Thu Oct 13 19:57:27 2016 UTC dump1090-fa v3.1.0 starting up.
Oct 13 19:57:27 piaware dump1090-fa[621]: Using sample converter: UC8, integer/table path
Oct 13 19:57:27 piaware dump1090-fa[621]: No supported devices found.
Oct 13 19:57:27 piaware systemd[1]: dump1090-fa.service: main process exited, code=exited, status=1/FAILURE
Oct 13 19:57:27 piaware systemd[1]: Unit dump1090-fa.service entered failed state.
Oct 13 19:57:58 piaware systemd[1]: dump1090-fa.service holdoff time over, scheduling restart.
Oct 13 19:57:58 piaware systemd[1]: Stopping dump1090 ADS-B receiver (FlightAware customization)…
Oct 13 19:57:58 piaware systemd[1]: Starting dump1090 ADS-B receiver (FlightAware customization)…
Oct 13 19:57:58 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Oct 13 19:57:58 piaware dump1090-fa[638]: Thu Oct 13 19:57:58 2016 UTC dump1090-fa v3.1.0 starting up.
Oct 13 19:57:58 piaware dump1090-fa[638]: Using sample converter: UC8, integer/table path
Oct 13 19:57:58 piaware dump1090-fa[638]: No supported devices found.
Oct 13 19:57:58 piaware systemd[1]: dump1090-fa.service: main process exited, code=exited, status=1/FAILURE
Oct 13 19:57:58 piaware systemd[1]: Unit dump1090-fa.service entered failed state.
Oct 13 19:58:28 piaware systemd[1]: dump1090-fa.service holdoff time over, scheduling restart.
Oct 13 19:58:28 piaware systemd[1]: Stopping dump1090 ADS-B receiver (FlightAware customization)…
Oct 13 19:58:29 piaware systemd[1]: Starting dump1090 ADS-B receiver (FlightAware customization)…
Oct 13 19:58:29 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Oct 13 19:58:29 piaware dump1090-fa[644]: Thu Oct 13 19:58:29 2016 UTC dump1090-fa v3.1.0 starting up.
Oct 13 19:58:29 piaware dump1090-fa[644]: Using sample converter: UC8, integer/table path
Oct 13 19:58:29 piaware dump1090-fa[644]: No supported devices found.
Oct 13 19:58:29 piaware systemd[1]: dump1090-fa.service: main process exited, code=exited, status=1/FAILURE
Oct 13 19:58:29 piaware systemd[1]: Unit dump1090-fa.service entered failed state.
Oct 13 19:58:59 piaware systemd[1]: dump1090-fa.service holdoff time over, scheduling restart.
Oct 13 19:58:59 piaware systemd[1]: Stopping dump1090 ADS-B receiver (FlightAware customization)…
lines 1-36

Is it possible that all four USB ports shit the bed? I started swaping SDRs and trying different USB ports and it appears they are all dead. Is there a way to trouble shoot the USB ports? I’ll try hooking up the Pi to the TV with a basic Pi load SC card to see what it does.


#16

If you’re getting it with multiple different dongles then it does sound like the Pi’s USB bus might be hosed.

Try “lsusb -t” and see if the dongle shows up there.


#17

Not exactly sure what this is telling me, but:
PiAware on working Pi
pi@piaware:~ lsusb -t /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/5p, 480M |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=smsc95xx, 4 80M |__ Port 5: Dev 4, If 0, Class=Vendor Specific Class, Driver=usbfs, 480M pi@piaware:~

Non-working Pi
pi@piaware:~ lsusb -t /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/5p, 480M |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=smsc95xx, 480M pi@piaware:~

Hooked up to the TV with a basic Raspberry PI SD card and it powered up, but the USB keyboard and Mouse did not work.

Looking at this from a hardware standpoint I plugged in a USB to 5V barrel plug cable and took a voltage reading on the plug. The working Pi had the 5V on the barrel plug the non woorking Pi had 0V on the plug.

So, thank you for all your help. Only question remaining is: What can I use a Raspberry Pi for when the USB ports are dead?


#18

Hi, Newbie here. My PiAware was working fine for 14 days (although it didn’t have the range), and then the other day I got the following message: •Anomaly report for PiAware feeder with a MAC address of b8:27:eb:d5:55:b5:
1.This feeder last checked in several hours ago.

So, what does this mean (besides it’s not working) and how do I fix it. And I know nothing about Linux.
Thanks.


#19

This means it is not connected to the FlightAware servers.
Either you have a network problem or the Pi has crashed.
Check your network and power. You can probably recover by rebooting the Pi.


#20

Thanks…it’s working now. I rebooted the thing, shut it down, unplugged it for about 3 hours, then started it up again. Now to figure out why I don’t get the good range.