Pi stops communicating to FA


#1

Running the latest version of Piaware on a B+ and it runs great, right up until around 7 pm local (midnight UTC). Around that time, it stops talking to Flightaware for some reason, which I notice when I check my stats page. I work evenings, so I’m not home to reset it till after 10 pm. Once I reset it, it seems to return to normal until about the same time the next evening. Has anyone else experienced this? The only thing I know to do is set a cron job to reboot around 7 or so every night.

Ken


#2

I connected to the Pi via ssh when I got home and ran checked netstat. Everything looks normal except perhaps the large Recv-Q for piaware.

pi@piaware ~ $ sudo netstat -antp
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 1826/dump1090
tcp 0 0 0.0.0.0:10001 0.0.0.0:* LISTEN 1826/dump1090
tcp 0 0 0.0.0.0:30001 0.0.0.0:* LISTEN 1826/dump1090
tcp 0 0 0.0.0.0:30002 0.0.0.0:* LISTEN 1826/dump1090
tcp 0 0 0.0.0.0:30003 0.0.0.0:* LISTEN 1826/dump1090
tcp 0 0 0.0.0.0:30004 0.0.0.0:* LISTEN 1826/dump1090
tcp 0 0 0.0.0.0:30005 0.0.0.0:* LISTEN 1826/dump1090
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 2118/sshd
tcp 0 0 192.168.2.25:8080 192.168.2.19:41363 CLOSE_WAIT 1826/dump1090
tcp 0 0 192.168.2.25:8080 192.168.2.19:41365 CLOSE_WAIT 1826/dump1090
tcp 175063 0 127.0.0.1:35511 127.0.0.1:10001 ESTABLISHED 2081/piaware
tcp 0 94902 127.0.0.1:10001 127.0.0.1:35511 ESTABLISHED 1826/dump1090
tcp 0 0 192.168.2.25:60527 70.42.6.203:1200 ESTABLISHED 2081/piaware
tcp 0 0 192.168.2.25:8080 192.168.2.19:41364 CLOSE_WAIT 1826/dump1090
tcp 0 0 192.168.2.25:22 192.168.2.19:58430 ESTABLISHED 2526/sshd: pi priv


#3

Can you send the output of /tmp/piaware.out and/or /tmp/piaware.out.yesterday during the problem period?


#4

The yesterday file is no longer there. The current .out file started when I rebooted the Pi last night and it is pasted below:

10/22/2014 06:58:00 ****************************************************
10/22/2014 06:58:00 piaware version 1.15 is running, process ID 2075
10/22/2014 06:58:00 your system info is: Linux piaware 3.12.29+ #714 PREEMPT Wed Oct 1 23:11:38 BST 2014 armv6l GNU/Linux
10/22/2014 06:58:00 connecting to FlightAware eyes.flightaware.com/1200
10/22/2014 06:58:03 FlightAware server SSL certificate validated
10/22/2014 06:58:03 encrypted session established with FlightAware
10/22/2014 06:58:03 ADS-B data program ‘dump1090’ is listening on port 30005, so far so good
10/22/2014 06:58:03 i see dump1090 serving on port 10001
10/22/2014 06:58:03 connecting to dump1090 on port 10001…
10/22/2014 06:58:03 piaware is connected to dump1090 on port 10001
10/22/2014 06:58:03 dump1090 is listening for connections on FA-style port 10001
10/22/2014 06:58:03 piaware received a message from the ADS-B source!
10/22/2014 06:58:04 logged in to FlightAware as user KPryor
10/22/2014 06:58:33 2 msgs recv’d from dump1090; 1 msgs sent to FlightAware
10/22/2014 06:59:14 piaware has successfully sent several msgs to FlightAware!
10/22/2014 06:59:19 server is sending alive messages; we will expect them
10/22/2014 07:03:33 33 msgs recv’d from dump1090 (31 in last 5m); 33 msgs sent to FlightAware
10/22/2014 07:08:33 43 msgs recv’d from dump1090 (10 in last 5m); 44 msgs sent to FlightAware
10/22/2014 07:13:33 51 msgs recv’d from dump1090 (8 in last 5m); 53 msgs sent to FlightAware
10/22/2014 07:18:03 dump1090 is listening for connections on FA-style port 10001
10/22/2014 07:18:33 53 msgs recv’d from dump1090 (2 in last 5m); 56 msgs sent to FlightAware
10/22/2014 07:23:33 63 msgs recv’d from dump1090 (10 in last 5m); 67 msgs sent to FlightAware
10/22/2014 07:28:03 dump1090 is listening for connections on FA-style port 10001
10/22/2014 07:28:33 63 msgs recv’d from dump1090 (0 in last 5m); 68 msgs sent to FlightAware
10/22/2014 07:33:03 dump1090 is listening for connections on FA-style port 10001
10/22/2014 07:33:33 63 msgs recv’d from dump1090 (0 in last 5m); 69 msgs sent to FlightAware
10/22/2014 07:38:03 dump1090 is listening for connections on FA-style port 10001
10/22/2014 07:38:33 63 msgs recv’d from dump1090 (0 in last 5m); 70 msgs sent to FlightAware
10/22/2014 07:43:03 dump1090 is listening for connections on FA-style port 10001
10/22/2014 07:43:33 63 msgs recv’d from dump1090 (0 in last 5m); 71 msgs sent to FlightAware
10/22/2014 07:48:33 65 msgs recv’d from dump1090 (2 in last 5m); 74 msgs sent to FlightAware
10/22/2014 07:53:33 83 msgs recv’d from dump1090 (18 in last 5m); 94 msgs sent to FlightAware
10/22/2014 07:58:33 145 msgs recv’d from dump1090 (62 in last 5m); 156 msgs sent to FlightAware
10/22/2014 08:03:33 217 msgs recv’d from dump1090 (72 in last 5m); 229 msgs sent to FlightAware
10/22/2014 08:08:33 289 msgs recv’d from dump1090 (72 in last 5m); 302 msgs sent to FlightAware
10/22/2014 08:13:33 365 msgs recv’d from dump1090 (76 in last 5m); 379 msgs sent to FlightAware
10/22/2014 08:18:33 467 msgs recv’d from dump1090 (102 in last 5m); 482 msgs sent to FlightAware
10/22/2014 08:23:33 555 msgs recv’d from dump1090 (88 in last 5m); 571 msgs sent to FlightAware
10/22/2014 08:28:33 636 msgs recv’d from dump1090 (81 in last 5m); 653 msgs sent to FlightAware
10/22/2014 08:33:33 685 msgs recv’d from dump1090 (49 in last 5m); 703 msgs sent to FlightAware
10/22/2014 08:38:33 740 msgs recv’d from dump1090 (55 in last 5m); 759 msgs sent to FlightAware
10/22/2014 08:43:33 801 msgs recv’d from dump1090 (61 in last 5m); 821 msgs sent to FlightAware
10/22/2014 08:48:33 862 msgs recv’d from dump1090 (61 in last 5m); 883 msgs sent to FlightAware
10/22/2014 08:53:33 969 msgs recv’d from dump1090 (107 in last 5m); 991 msgs sent to FlightAware
10/22/2014 08:58:33 1057 msgs recv’d from dump1090 (88 in last 5m); 1080 msgs sent to FlightAware
10/22/2014 09:03:33 1137 msgs recv’d from dump1090 (80 in last 5m); 1161 msgs sent to FlightAware
10/22/2014 09:08:33 1209 msgs recv’d from dump1090 (72 in last 5m); 1234 msgs sent to FlightAware
10/22/2014 09:13:33 1276 msgs recv’d from dump1090 (67 in last 5m); 1303 msgs sent to FlightAware
10/22/2014 09:18:33 1378 msgs recv’d from dump1090 (102 in last 5m); 1405 msgs sent to FlightAware
10/22/2014 09:23:33 1476 msgs recv’d from dump1090 (98 in last 5m); 1504 msgs sent to FlightAware
10/22/2014 09:28:33 1557 msgs recv’d from dump1090 (81 in last 5m); 1586 msgs sent to FlightAware
10/22/2014 09:33:33 1630 msgs recv’d from dump1090 (73 in last 5m); 1660 msgs sent to FlightAware
10/22/2014 09:38:33 1681 msgs recv’d from dump1090 (51 in last 5m); 1712 msgs sent to FlightAware
10/22/2014 09:43:33 1691 msgs recv’d from dump1090 (10 in last 5m); 1724 msgs sent to FlightAware
10/22/2014 09:48:33 1694 msgs recv’d from dump1090 (3 in last 5m); 1727 msgs sent to FlightAware
10/22/2014 09:53:33 1700 msgs recv’d from dump1090 (6 in last 5m); 1734 msgs sent to FlightAware
10/22/2014 09:58:33 1730 msgs recv’d from dump1090 (30 in last 5m); 1765 msgs sent to FlightAware
10/22/2014 10:03:33 1745 msgs recv’d from dump1090 (15 in last 5m); 1781 msgs sent to FlightAware
10/22/2014 10:08:33 1764 msgs recv’d from dump1090 (19 in last 5m); 1801 msgs sent to FlightAware
10/22/2014 10:13:33 1793 msgs recv’d from dump1090 (29 in last 5m); 1831 msgs sent to FlightAware
10/22/2014 10:18:33 1838 msgs recv’d from dump1090 (45 in last 5m); 1877 msgs sent to FlightAware
10/22/2014 10:23:33 1891 msgs recv’d from dump1090 (53 in last 5m); 1931 msgs sent to FlightAware
10/22/2014 10:28:33 1917 msgs recv’d from dump1090 (26 in last 5m); 1958 msgs sent to FlightAware
10/22/2014 10:33:33 1942 msgs recv’d from dump1090 (25 in last 5m); 1984 msgs sent to FlightAware
10/22/2014 10:38:33 1956 msgs recv’d from dump1090 (14 in last 5m); 1999 msgs sent to FlightAware
10/22/2014 10:43:33 1985 msgs recv’d from dump1090 (29 in last 5m); 2029 msgs sent to FlightAware
10/22/2014 10:48:33 2046 msgs recv’d from dump1090 (61 in last 5m); 2091 msgs sent to FlightAware
10/22/2014 10:53:33 2111 msgs recv’d from dump1090 (65 in last 5m); 2157 msgs sent to FlightAware
10/22/2014 10:58:33 2155 msgs recv’d from dump1090 (44 in last 5m); 2202 msgs sent to FlightAware
10/22/2014 11:03:33 2191 msgs recv’d from dump1090 (36 in last 5m); 2239 msgs sent to FlightAware
10/22/2014 11:08:33 2207 msgs recv’d from dump1090 (16 in last 5m); 2256 msgs sent to FlightAware
10/22/2014 11:13:33 2245 msgs recv’d from dump1090 (38 in last 5m); 2295 msgs sent to FlightAware
10/22/2014 11:18:33 2319 msgs recv’d from dump1090 (74 in last 5m); 2370 msgs sent to FlightAware
10/22/2014 11:23:33 2409 msgs recv’d from dump1090 (90 in last 5m); 2461 msgs sent to FlightAware
10/22/2014 11:28:33 2508 msgs recv’d from dump1090 (99 in last 5m); 2561 msgs sent to FlightAware
10/22/2014 11:33:33 2594 msgs recv’d from dump1090 (86 in last 5m); 2648 msgs sent to FlightAware
10/22/2014 11:38:33 2735 msgs recv’d from dump1090 (141 in last 5m); 2790 msgs sent to FlightAware
10/22/2014 11:42:36 lost connection to FlightAware, reconnecting…
10/22/2014 11:42:36 connecting to FlightAware 70.42.6.203/1200
10/22/2014 11:44:04 FlightAware server SSL certificate validated
10/22/2014 11:44:04 encrypted session established with FlightAware
10/22/2014 11:44:04 connecting to FlightAware eyes.flightaware.com/1200
10/22/2014 11:44:08 FlightAware server SSL certificate validated
10/22/2014 11:44:08 encrypted session established with FlightAware
10/22/2014 11:44:09 logged in to FlightAware as user KPryor
10/22/2014 11:44:14 data isn’t making it to FlightAware, reconnecting…
10/22/2014 11:44:14 connecting to FlightAware 70.42.6.203/1200
10/22/2014 11:44:16 FlightAware server SSL certificate validated
10/22/2014 11:44:16 encrypted session established with FlightAware
10/22/2014 11:44:17 logged in to FlightAware as user KPryor
10/22/2014 11:44:34 2930 msgs recv’d from dump1090 (195 in last 6m); 2933 msgs sent to FlightAware
10/22/2014 11:45:16 server is sending alive messages; we will expect them
10/22/2014 11:49:34 3086 msgs recv’d from dump1090 (156 in last 5m); 3090 msgs sent to FlightAware
10/22/2014 11:54:34 3200 msgs recv’d from dump1090 (114 in last 5m); 3205 msgs sent to FlightAware
10/22/2014 11:59:34 3324 msgs recv’d from dump1090 (124 in last 5m); 3330 msgs sent to FlightAware
10/22/2014 12:04:34 3420 msgs recv’d from dump1090 (96 in last 5m); 3427 msgs sent to FlightAware
10/22/2014 12:09:34 3542 msgs recv’d from dump1090 (122 in last 5m); 3550 msgs sent to FlightAware
10/22/2014 12:14:34 3673 msgs recv’d from dump1090 (131 in last 5m); 3682 msgs sent to FlightAware
10/22/2014 12:19:34 3785 msgs recv’d from dump1090 (112 in last 5m); 3795 msgs sent to FlightAware
10/22/2014 12:24:34 3941 msgs recv’d from dump1090 (156 in last 5m); 3952 msgs sent to FlightAware
10/22/2014 12:29:34 4141 msgs recv’d from dump1090 (200 in last 5m); 4153 msgs sent to FlightAware
10/22/2014 12:34:34 4346 msgs recv’d from dump1090 (205 in last 5m); 4359 msgs sent to FlightAware
10/22/2014 12:39:34 4533 msgs recv’d from dump1090 (187 in last 5m); 4547 msgs sent to FlightAware
10/22/2014 12:44:34 4713 msgs recv’d from dump1090 (180 in last 5m); 4728 msgs sent to FlightAware
10/22/2014 12:49:34 4907 msgs recv’d from dump1090 (194 in last 5m); 4923 msgs sent to FlightAware
10/22/2014 12:54:34 5073 msgs recv’d from dump1090 (166 in last 5m); 5090 msgs sent to FlightAware
10/22/2014 12:59:34 5239 msgs recv’d from dump1090 (166 in last 5m); 5257 msgs sent to FlightAware
10/22/2014 13:04:34 5426 msgs recv’d from dump1090 (187 in last 5m); 5445 msgs sent to FlightAware
10/22/2014 13:09:34 5608 msgs recv’d from dump1090 (182 in last 5m); 5628 msgs sent to FlightAware
10/22/2014 13:14:35 5788 msgs recv’d from dump1090 (180 in last 5m); 5809 msgs sent to FlightAware
10/22/2014 13:19:34 5959 msgs recv’d from dump1090 (171 in last 5m); 5981 msgs sent to FlightAware
10/22/2014 13:24:34 6060 msgs recv’d from dump1090 (101 in last 5m); 6083 msgs sent to FlightAware
10/22/2014 13:29:34 6144 msgs recv’d from dump1090 (84 in last 5m); 6168 msgs sent to FlightAware
10/22/2014 13:34:34 6303 msgs recv’d from dump1090 (159 in last 5m); 6328 msgs sent to FlightAware
10/22/2014 13:39:34 6571 msgs recv’d from dump1090 (268 in last 5m); 6597 msgs sent to FlightAware
10/22/2014 13:44:34 6882 msgs recv’d from dump1090 (311 in last 5m); 6909 msgs sent to FlightAware
10/22/2014 13:49:34 7192 msgs recv’d from dump1090 (310 in last 5m); 7220 msgs sent to FlightAware
10/22/2014 13:54:34 7521 msgs recv’d from dump1090 (329 in last 5m); 7550 msgs sent to FlightAware
10/22/2014 13:59:34 7793 msgs recv’d from dump1090 (272 in last 5m); 7823 msgs sent to FlightAware
10/22/2014 14:04:34 8126 msgs recv’d from dump1090 (333 in last 5m); 8157 msgs sent to FlightAware
10/22/2014 14:09:34 8466 msgs recv’d from dump1090 (340 in last 5m); 8498 msgs sent to FlightAware
10/22/2014 14:14:34 8762 msgs recv’d from dump1090 (296 in last 5m); 8795 msgs sent to FlightAware
10/22/2014 14:19:34 9012 msgs recv’d from dump1090 (250 in last 5m); 9046 msgs sent to FlightAware
10/22/2014 14:24:34 9274 msgs recv’d from dump1090 (262 in last 5m); 9309 msgs sent to FlightAware
10/22/2014 14:29:34 9583 msgs recv’d from dump1090 (309 in last 5m); 9619 msgs sent to FlightAware
10/22/2014 14:34:34 9857 msgs recv’d from dump1090 (274 in last 5m); 9894 msgs sent to FlightAware
10/22/2014 14:39:34 10129 msgs recv’d from dump1090 (272 in last 5m); 10167 msgs sent to FlightAware
10/22/2014 14:44:34 10438 msgs recv’d from dump1090 (309 in last 5m); 10477 msgs sent to FlightAware
10/22/2014 14:49:34 10684 msgs recv’d from dump1090 (246 in last 5m); 10724 msgs sent to FlightAware
10/22/2014 14:54:34 10888 msgs recv’d from dump1090 (204 in last 5m); 10929 msgs sent to FlightAware
10/22/2014 14:59:34 11104 msgs recv’d from dump1090 (216 in last 5m); 11146 msgs sent to FlightAware
10/22/2014 15:04:34 11326 msgs recv’d from dump1090 (222 in last 5m); 11369 msgs sent to FlightAware
10/22/2014 15:09:34 11554 msgs recv’d from dump1090 (228 in last 5m); 11598 msgs sent to FlightAware
10/22/2014 15:14:34 11824 msgs recv’d from dump1090 (270 in last 5m); 11869 msgs sent to FlightAware
10/22/2014 15:19:34 12098 msgs recv’d from dump1090 (274 in last 5m); 12144 msgs sent to FlightAware
10/22/2014 15:24:34 12335 msgs recv’d from dump1090 (237 in last 5m); 12382 msgs sent to FlightAware
10/22/2014 15:29:34 12507 msgs recv’d from dump1090 (172 in last 5m); 12555 msgs sent to FlightAware
10/22/2014 15:34:34 12683 msgs recv’d from dump1090 (176 in last 5m); 12732 msgs sent to FlightAware
10/22/2014 15:39:34 12859 msgs recv’d from dump1090 (176 in last 5m); 12909 msgs sent to FlightAware
10/22/2014 15:44:34 13010 msgs recv’d from dump1090 (151 in last 5m); 13061 msgs sent to FlightAware


#5

Hi. I don’t think anything in this paste indicates a problem. Here’s my guess: Remember, the times are in UTC aka GMT. You appear to be in Missouri so it’s UTC-6:00 so 7:00 UTC is 1 AM Central. Seeing as how the progression of message counts reported at five minute intervals goes 31, 10, 8, 2, 10, 0, 0, 0, 0, 2, 18, 62 I think there just wasn’t an aircraft in range from around 1:28 AM until about 1:48 AM, the wee hours of the morning.


#6

I’m in Illinois. The actual problem usually occurs around 7pm local time, although it didn’t do it tonight. I know it’s then because I check my stats from time to time while I’m at work and after 7 local time, FA will say my Piaware was last seen a number of hours earlier before finally showing an anomaly.


#7

The same problem started again tonight around 8pm local time. I’ve rebooted and even shutdown and restarted, but my stat page reports my receiver was last seen 2 hours ago, as of the time I’m typing this. I looked at the live page on my Pi and there are plenty of aircraft being detected by it, but FA is still showing the anomaly.

Ken


#8

And, of course, a few minutes after I typed the last message things returned to normal. Weird.


#9

Hate to bring this post up again, but the problem still exists. I am away from home at the moment and checking my stats I see that my unit was last seen 14 hours ago. I’m not there to reboot it, so it’ll have to wait till I get back. No idea why this keeps happening.


#10

Are you able to communicate with the raspberry pi (ie does it respond to pings from other computers on the same network). Wireless network issues are somewhat common with the raspberry pi. I believe the problem stems from the bad USB stack. You may want to follow the instructions listed here: post152153.html#p152153 to automatically reboot the raspberry pi if you have network issues.


#11

I’m not home to do it right now and cannot connect from here. Usually, I can connect via ssh from another computer on my network, but sometimes I’m not even able to do that, so I have to just unplug it. I’ve had this problem with it using the wireless dongle and when I used the wired network, too. I’ll take a look at the link you provided, thanks!

KP


#12

I had the same ‘no response’ from my RPi on my wireless network. Turns out the wifi adapter was going into sleep mode. This fixed it: raspberrypi.org/forums/viewt … 5&p=479174

Don’t know if it’ll work for you since you’re seeing it while hard-wired.


#13

Enter the following command, if it returns a “1” then it would be a good idea to try the that fix. Once you create the file, then just simply reboot the raspberry pi. Confim that it is working by re-tunning the command below and it should now return a “0”.


cat /sys/module/8192cu/parameters/rtw_power_mgnt


#14

My system had no stats for the first time ever tonight. I have no problem viewing the local web page and it shows planes being seen fine, so I know the RX and wifi are working . Is there anything I should be looking for when this happens? I rebooted and after a bit it was sending data to FA again.


#15

Do you know how to connect to it and view /tmp/piaware.out ? If not, we’ll soon be adding a web interface for viewing the logs.


#16

Nice feature. Consider adding a ‘button’ for:

  • check piware version
    - update piaware
  • check dump1090 version
    - update dump1090

Maybe also a hot link button to the forums.


#17

I am experiencing a similar problem where my PiAware setup (1.16) stopped sending data to FA. It still shows live data in the local browser, but the piaware.out log file only reports the following in the last lines:

11/15/2014 10:59:29 data isn’t making it to FlightAware, reconnecting…
11/15/2014 10:59:29 connecting to FlightAware eyes.flightaware.com/1200
11/15/2014 10:59:50 got ‘couldn’t open socket: no such device or address (Tempor
ary failure in name resolution)’ to adept server at eyes.flightaware.com/1200, w
ill try again soon…
11/15/2014 11:00:29 connecting to FlightAware 70.42.6.203/1200

Any idea how to fix this? Thx!

(edit: i just did a “sudo reboot” via ssh and this fixed the issue for the moment, but as far as I see it this has happened before + wasn’t version 1.16 optimized to fix this issue where a failed connection also means that it will not reconnect?)


#18

It looks like you might have a local network problem. Can you post more lines of the piaware.out?

Might be worth a restart too.


#19

Yes, I just did a reboot via ssh and it is working now. Thx!
This network problem (DNS resolving?) - is there any way I can prevent this in future?


#20

My connection to flightaware keeps dying. It still shows local output, but when doing a piaware-status, it will show not connected to piaware. I just implemented the fix listed on this page to disallow the wifi device sleeping and had previously entered the auto reboot on not network connectivity fix. Problem is, it need to reboot when it loses its connection to flightaware!