Log View Problem

#1
Hello,

I keep getting this message, Failed to parse response from Plane Finder server: HTTP/1.1 200 OK.

It's happening far to often for my liking and if all my data is not being fed to Planefinder then it makes me wonder if i should bother at all.

I'm feeding using an RTL Dongle and a Raspberry Pi using the PF Client software.

Can anyone explain to me what's causing this to happen.

Copy of my Log View,

2016-05-04 16:38:47.738665 [-] Successfully sent 853 aircraft updates across 10 packets (65.00KB)2016-05-04 16:38:35.59681 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK2016-05-04 16:38:05.649751 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK2016-05-04 16:36:14.702705 [-] Successfully sent 951 aircraft updates across 11 packets (72.00KB)2016-05-04 16:36:02.693005 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK2016-05-04 16:34:14.507393 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK2016-05-04 16:33:19.940098 [-] Successfully sent 931 aircraft updates across 10 packets (69.00KB)2016-05-04 16:31:47.374342 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK2016-05-04 16:30:29.133694 [-] Successfully sent 938 aircraft updates across 10 packets (68.00KB)2016-05-04 16:30:01.420343 [!] Failed to parse response from Plane Finder server: HTTP/1.1 400 Bad Request2016-05-04 16:29:44.842273 [!] Failed to parse response from Plane Finder server: HTTP/1.1 400 Bad Request2016-05-04 16:29:29.386996 [!] Failed to parse response from Plane Finder server: HTTP/1.1 400 Bad Request2016-05-04 16:29:11.952161 [!] Data upload failed with error: 'Client not authenticated - local time on client out of limits, suggest setting up NTP locally - for help contact support@planefinder.net'2016-05-04 16:28:21.908720 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK2016-05-04 16:27:45.628309 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK2016-05-04 16:26:57.688282 [-] Successfully sent 889 aircraft updates across 10 packets (67.00KB)2016-05-04 16:26:31.524977 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK2016-05-04 16:25:42.262182 [!] Data upload failed with error: 'Client not authenticated - local time on client out of limits, suggest setting up NTP locally - for help contact support@planefinder.net'2016-05-04 16:24:59.257246 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK2016-05-04 16:24:43.479007 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK2016-05-04 16:24:04.732715 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK2016-05-04 16:23:49.334549 [-] Successfully sent 906 aircraft updates across 10 packets (66.00KB)2016-05-04 16:23:34.167952 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK2016-05-04 16:22:46.483572 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK2016-05-04 16:21:43.164988 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK2016-05-04 16:21:09.619208 [!] Data upload failed with error: 'Client not authenticated - local time on client out of limits, suggest setting up NTP locally - for help contact support@planefinder.net'2016-05-04 16:20:19.240442 [-] Successfully sent 853 aircraft updates across 10 packets (63.00KB)2016-05-04 16:18:11.402259 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK2016-05-04 16:17:55.963958 [-] Successfully sent 806 aircraft updates across 10 packets (59.00KB)2016-05-04 16:16:17.484093 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK2016-05-04 16:15:35.38350 [-] Successfully sent 822 aircraft updates across 10 packets (60.00KB)2016-05-04 16:14:51.795980 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK2016-05-04 16:12:54.71926 [-] Successfully sent 839 aircraft updates across 10 packets (60.00KB)

MTIA

Phil
 

Lee Armstrong

Administrator
Staff member
#2
Hi Phil,

I've had a look and you have 4 share codes allocated to you!

The most recent one uploading is getting to us but the local time on your Pi is off at the moment by about 7 seconds. I would look at setting up NTP on your Pi.

Just had a quick Google around and found this guide but there are many more I would look at following..

Lee
 
#3
Hi Lee,

Still getting the Failed To Parse Error and i'm not sure what to do now as i have NTP installed on the Pi and keep getting the problem, and it's happening more frequently.

2016-05-15 18:33:50.381 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:32:50.871230 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:32:04.704103 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:31:46.285445 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:31:17.417213 [-] Successfully sent 1129 aircraft updates across 14 packets (86.00KB)
2016-05-15 18:31:00.834414 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:30:37.156675 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:30:21.691550 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:30:05.281853 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:29:09.831388 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:28:54.373037 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:28:35.69300 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:28:17.640536 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:27:06.739649 [-] Successfully sent 786 aircraft updates across 10 packets (60.00KB)
2016-05-15 18:26:51.737571 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:26:36.92854 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:25:51.365388 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:25:34.917144 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:25:06.869815 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:24:36.382616 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:24:20.931254 [-] Successfully sent 725 aircraft updates across 10 packets (56.00KB)
2016-05-15 18:24:00.391593 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:21:52.629216 [-] Successfully sent 702 aircraft updates across 10 packets (55.00KB)
2016-05-15 18:19:48.508621 [-] Successfully sent 737 aircraft updates across 10 packets (56.00KB)
2016-05-15 18:18:43.999503 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:17:37.929325 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:17:06.827160 [-] Successfully sent 785 aircraft updates across 10 packets (59.00KB)
2016-05-15 18:16:51.263255 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:16:24.320862 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:16:08.865085 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:15:27.805121 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:12:15.992375 [-] Successfully sent 796 aircraft updates across 10 packets (59.00KB)
2016-05-15 18:11:25.113593 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:10:43.799625 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:10:12.56358 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:09:48.699627 [-] Successfully sent 811 aircraft updates across 10 packets (60.00KB)
2016-05-15 18:08:48.428352 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:08:21.387013 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:07:39.915561 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:07:24.461169 [-] Successfully sent 789 aircraft updates across 10 packets (61.00KB)
2016-05-15 18:06:54.270954 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:05:30.869104 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:04:52.507340 [-] Successfully sent 802 aircraft updates across 10 packets (63.00KB)
2016-05-15 18:04:13.959344 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:03:22.359353 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:02:45.802627 [-] Successfully sent 821 aircraft updates across 11 packets (61.00KB)
2016-05-15 18:02:35.340763 [!] Failed to parse response from Plane Finder server: HTTP/1.1 200 OK
2016-05-15 18:00:40.20225 [-] User location has been verified.2016-05-15 18:00:33.982279 [-] Echo port is now listening on: 192.168.0.27:300542016-05-15 18:00:33.971890 [-] Web server is now listening on: http://192.168.0.27:300532016-05-15 18:00:33.968554 [-] TCP connection established: 127.0.0.1:300052016-05-15 18:00:33.945797 [-] user_longitude = -3.0067002016-05-15 18:00:33.945725 [-] user_latitude = 53.4872802016-05-15 18:00:33.945618 [-] web_server_port = 300532016-05-15 18:00:33.945559 [-] select_timeout = 102016-05-15 18:00:33.945497 [-] aircraft_timeout = 302016-05-15 18:00:33.945427 [-] data_format = 12016-05-15 18:00:33.945370 [-] tcp_port = 300052016-05-15 18:00:33.945303 [-] tcp_address = 127.0.0.12016-05-15 18:00:33.945173 [-] connection_type = 12016-05-15 18:00:33.942971 [-] pfclient (3.4.30 armhf) started with the following options:2016-05-15 18:00:15.446175 [-] Data proxy is shutting down2016-05-15 18:00:06.605070 [-] Web server is shutting down2016-05-15 18:00:01.826686 [-] Echo port is shutting down2016-05-15 18:00:01.800148 [-] Shutting down workers...2016-05-15 18:00:01.799966 [-] Closed TCP connection: 127.0.0.1:30005


Regards

Phil
 

Lee Armstrong

Administrator
Staff member
#4
Thanks Phil,

We will take a look. Rest assured the data is getting to the server ok and the message in essence is wrong!

We'll see if we can get it resolved though!

Lee
 

Lee Armstrong

Administrator
Staff member
#5
Hi Phil,

I have set up some logging on the server end for this issue. From 0930 BST can you let me know when it happens again please?

One thing I notice is that the time on your Pi is jumping around a LOT. I wonder if the Pi is an older Pi running at 100% CPU and is simply doing far too much!

What else does your Pi have installed on it?