Hello, something has happened to my Piaware in the last few days, it is no longer reporting to Flightaware. It is still collecting data, and you can access the maps with no problem. I have restarted the device multiple times remotely. I have not pulled the power for a reset, its in the attic and will if it’s needed.
My setup has worked for years, and I haven’t made any changes for some time.
Any ideas?
Thanks
Richard Minton
Maybe you can show some snippets of the logging ? That will give a clue why it isn’t reporting properly
Ok, if you are referring to the log window on the site configuration page, it is blank. Is there way to SSH into the unit and get it?
Did you enable SSH when you installed the OS image?
If not then you have to do it now.
It can be done
that empty text file named ssh would have to be created in the /boot directory on the SD card.
When in Windows File explore, the drive letter of the microSD card is double clicked, it automatically opens the /boot directory. The /boot directory is the only directory visible in Windows.
Yes, I have SSH enabled, and I am logged on to it, where would the log file be kept?
piaware log
sudo journalctl -u piaware -e
dump1090-fa log
sudo journalctl -u dump1090-fa -e
All seems OK here 
Are you sure you are looking at correct Site number on My ADSB page?
You can get the site number by this command:
grep site /var/log/piaware.log
Trying to find the point where it stopped in the logs stand by
The output of this command will give your Pi’s Site number
(Scroll to right. Site number is at extreme right)
grep site /var/log/piaware.log
Ok, It looks like it went down on June 7th for awhile, here is the log for that time period.
Jun 07 08:02:51 piaware piaware[534]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Jun 07 08:03:01 piaware piaware[534]: Connection to adept server at piaware.flightaware.com/1200 failed: couldn’t open socket: Temporary failure in name resolution
Jun 07 08:03:01 piaware piaware[534]: reconnecting in 6 seconds…
Jun 07 08:03:07 piaware piaware[534]: Connecting to FlightAware adept server at 206.253.80.198/1200
Jun 07 08:03:22 piaware piaware[534]: Connection attempt with adept server at 206.253.80.198/1200 timed out
Jun 07 08:03:22 piaware piaware[534]: reconnecting in 6 seconds…
Jun 07 08:03:28 piaware piaware[534]: Connecting to FlightAware adept server at 206.253.84.198/1200
Jun 07 08:03:43 piaware piaware[534]: Connection attempt with adept server at 206.253.84.198/1200 timed out
Jun 07 08:03:43 piaware piaware[534]: reconnecting in 69 seconds…
Jun 07 08:04:52 piaware piaware[534]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Jun 07 08:05:02 piaware piaware[534]: Connection to adept server at piaware.flightaware.com/1200 failed: couldn’t open socket: Temporary failure in name resolution
Jun 07 08:05:02 piaware piaware[534]: reconnecting in 6 seconds…
Jun 07 08:05:08 piaware piaware[534]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Jun 07 08:05:18 piaware piaware[534]: Connection to adept server at piaware.flightaware.com/1200 failed: couldn’t open socket: Temporary failure in name resolution
Jun 07 08:05:18 piaware piaware[534]: reconnecting in 5 seconds…
Jun 07 08:05:23 piaware piaware[534]: Connecting to FlightAware adept server at 206.253.80.196/1200
Jun 07 08:05:38 piaware piaware[534]: Connection attempt with adept server at 206.253.80.196/1200 timed out
Jun 07 08:05:38 piaware piaware[534]: reconnecting in 4 seconds…
Jun 07 08:05:42 piaware piaware[534]: Connecting to FlightAware adept server at 206.253.84.194/1200
Jun 07 08:05:57 piaware piaware[534]: Connection attempt with adept server at 206.253.84.194/1200 timed out
Jun 07 08:05:57 piaware piaware[534]: reconnecting in 66 seconds…
Jun 07 08:06:44 piaware piaware[534]: 34610237 msgs recv’d from dump1090-fa (225 in last 5m); 34586925 msgs sent to FlightAware
Jun 07 08:06:44 piaware piaware[534]: 427782 msgs recv’d from dump978-fa (0 in last 5m); 427770 msgs sent to FlightAware
Jun 07 08:07:03 piaware piaware[534]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Jun 07 08:07:13 piaware piaware[534]: Connection to adept server at piaware.flightaware.com/1200 failed: couldn’t open socket: Temporary failure in name resolution
Jun 07 08:07:13 piaware piaware[534]: reconnecting in 6 seconds…
Jun 07 08:07:19 piaware piaware[534]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Jun 07 08:07:29 piaware piaware[534]: Connection to adept server at piaware.flightaware.com/1200 failed: couldn’t open socket: Temporary failure in name resolution
Jun 07 08:07:29 piaware piaware[534]: reconnecting in 5 seconds…
Jun 07 08:07:34 piaware piaware[534]: Connecting to FlightAware adept server at 206.253.80.201/1200
Jun 07 08:07:49 piaware piaware[534]: Connection attempt with adept server at 206.253.80.201/1200 timed out
Jun 07 08:07:49 piaware piaware[534]: reconnecting in 5 seconds…
Jun 07 08:07:54 piaware piaware[534]: Connecting to FlightAware adept server at 206.253.84.195/1200
Jun 07 08:08:09 piaware piaware[534]: Connection attempt with adept server at 206.253.84.195/1200 timed out
Jun 07 08:08:09 piaware piaware[534]: reconnecting in 51 seconds…
Jun 07 08:09:00 piaware piaware[534]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Jun 07 08:09:10 piaware piaware[534]: Connection to adept server at piaware.flightaware.com/1200 failed: couldn’t open socket: Temporary failure in name resolution
Jun 07 08:09:10 piaware piaware[534]: reconnecting in 5 seconds…
Jun 07 08:09:15 piaware piaware[534]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Jun 07 08:09:25 piaware piaware[534]: Connection to adept server at piaware.flightaware.com/1200 failed: couldn’t open socket: Temporary failure in name resolution
Jun 07 08:09:25 piaware piaware[534]: reconnecting in 6 seconds…
Jun 07 08:09:31 piaware piaware[534]: Connecting to FlightAware adept server at 206.253.80.199/1200
Jun 07 08:09:46 piaware piaware[534]: Connection attempt with adept server at 206.253.80.199/1200 timed out
Jun 07 08:09:46 piaware piaware[534]: reconnecting in 6 seconds…
Jun 07 08:09:52 piaware piaware[534]: Connecting to FlightAware adept server at 206.253.84.196/1200
…skipping…
Jun 07 08:26:29 piaware piaware[534]: mlat-client(14927): Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.1kB/s UDP to server
Jun 07 08:26:29 piaware piaware[534]: mlat-client(14927): Aircraft: 4 of 5 Mode S, 25 of 26 ADS-B used
Jun 07 08:26:52 piaware piaware[534]: 34611657 msgs recv’d from dump1090-fa (436 in last 5m); 34588089 msgs sent to FlightAware
Jun 07 08:26:52 piaware piaware[534]: 427782 msgs recv’d from dump978-fa (0 in last 5m); 427770 msgs sent to FlightAware
Jun 07 08:31:52 piaware piaware[534]: 34612115 msgs recv’d from dump1090-fa (458 in last 5m); 34588547 msgs sent to FlightAware
Jun 07 08:31:52 piaware piaware[534]: 427782 msgs recv’d from dump978-fa (0 in last 5m); 427770 msgs sent to FlightAware
Jun 07 08:36:52 piaware piaware[534]: 34612698 msgs recv’d from dump1090-fa (583 in last 5m); 34589130 msgs sent to FlightAware
Jun 07 08:36:52 piaware piaware[534]: 427782 msgs recv’d from dump978-fa (0 in last 5m); 427770 msgs sent to FlightAware
Jun 07 08:41:29 piaware piaware[534]: mlat-client(14927): Receiver status: connected
Jun 07 08:41:29 piaware piaware[534]: mlat-client(14927): Server status: synchronized with 237 nearby receivers
Jun 07 08:41:29 piaware piaware[534]: mlat-client(14927): Receiver: 236.6 msg/s received 112.1 msg/s processed (47%)
Jun 07 08:41:29 piaware piaware[534]: mlat-client(14927): Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.5kB/s UDP to server
Jun 07 08:41:29 piaware piaware[534]: mlat-client(14927): Aircraft: 2 of 3 Mode S, 32 of 35 ADS-B used
Jun 07 08:41:52 piaware piaware[534]: 34613290 msgs recv’d from dump1090-fa (592 in last 5m); 34589722 msgs sent to FlightAware
Jun 07 08:41:52 piaware piaware[534]: 427782 msgs recv’d from dump978-fa (0 in last 5m); 427770 msgs sent to FlightAware
Jun 07 08:46:52 piaware piaware[534]: 34613923 msgs recv’d from dump1090-fa (633 in last 5m); 34590355 msgs sent to FlightAware
Jun 07 08:46:52 piaware piaware[534]: 427782 msgs recv’d from dump978-fa (0 in last 5m); 427770 msgs sent to FlightAware
Jun 07 08:51:52 piaware piaware[534]: 34614696 msgs recv’d from dump1090-fa (773 in last 5m); 34591128 msgs sent to FlightAware
Jun 07 08:51:52 piaware piaware[534]: 427782 msgs recv’d from dump978-fa (0 in last 5m); 427770 msgs sent to FlightAware
Jun 07 08:56:29 piaware piaware[534]: mlat-client(14927): Receiver status: connected
Jun 07 08:56:29 piaware piaware[534]: mlat-client(14927): Server status: synchronized with 227 nearby receivers
Jun 07 08:56:29 piaware piaware[534]: mlat-client(14927): Receiver: 268.4 msg/s received 129.2 msg/s processed (48%)
Jun 07 08:56:29 piaware piaware[534]: mlat-client(14927): Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.7kB/s UDP to server
Jun 07 08:56:29 piaware piaware[534]: mlat-client(14927): Results: 7.2 positions/minute
Jun 07 08:56:29 piaware piaware[534]: mlat-client(14927): Aircraft: 4 of 6 Mode S, 39 of 43 ADS-B used
Jun 07 08:56:52 piaware piaware[534]: 34615537 msgs recv’d from dump1090-fa (841 in last 5m); 34591969 msgs sent to FlightAware
Jun 07 08:56:52 piaware piaware[534]: 427782 msgs recv’d from dump978-fa (0 in last 5m); 427770 msgs sent to FlightAware
Jun 07 09:01:52 piaware piaware[534]: 34616221 msgs recv’d from dump1090-fa (684 in last 5m); 34592653 msgs sent to FlightAware
You have a network problem - on your PiAware, DNS is broken and there’s apparently no internet connectivity. This usually means there’s a problem with your router.
Im using that same router to respond to these messages. On the config file for piaware my network nameserver is Google at 8.8.8.8 I wonder if something has happened there. I can change it to another DNS.
Looks like you lost your Internet connection for around 30 minutes that morning. I wouldn’t worry about it. That happens sometimes: maybe your ISP was doing something. If it keeps happening, and if while it’s happening you can verify that you have Internet connectivity from your computer, then it’s time to investigate why the Pi lost its connection.
That fixed it. For some reason Google’s DNS have lost Flightaware. I pulled the card and changed the DNS entry to my Internet providers DNS and it came right up.
I have it going again. It actually had been down for days, I just posted the data from earlier.
My router lets me configure three DNS servers. I use one from Google, one from Cloudflare and one from OpenDNS.
Yeah Ive used Google for years on hundreds of different applications, I had it entered into the config file, go figure.