Plane Finder Client Beta2 (3.0.1435)

Status
Not open for further replies.
zahidulhasan said:
Dear Sir,

I have attached a file from the PC. Please check and advice me how to install PFClient in that PC.

Thanks & Regards,
Zahidul Hasan.
Click to expand...
We should have a version that works on that.

Can you tell me what you get when you run
Code: 
dpkg --print-architecture
 
Lee Armstrong said:
Thanks. At this time we don't have one for that architecture until out of beta. If you were to update to a 64-bit release I can provide a version for you.
Click to expand...

Dear Sir,

Older PFClient will not run on this? actually today my RPI burn out in thunderstorm, then i changed it to a better hardware. I am just pissed-off in RPI. ID 6290 was running on that RPI. I was not aware about the issue about the x86 or 64 OS. Now OS change is not possible. If any PFClient don't work on x86 OS, then this feeder will be out of service.

Thanks,
Zahidul Hasan.
 
You can always install the NodeJS version but this is not the thread for this. The 32-bit version will be out soon.

This is a beta thread for the Pi
 
Just FYI: I'm seeing "poll timeout occurred, restarting..." messages when things are quiet overnight with no traffic. So this looks like normal behaviour: it always reconnects and sends updates when and if there is something to report.

UPDATE:
It looks like the client is restarting 6 times in quick succession when "supply" dries up. It then just sits there (without restarting or logging anything else) and waits for the next positions to arrive.
 
Last edited:
mgunther said:
Just FYI: I'm seeing "poll timeout occurred, restarting..." messages when things are quiet overnight with no traffic. So this looks like normal behaviour: it always reconnects and sends updates when and if there is something to report.

UPDATE:
It looks like the client is restarting 6 times in quick succession when "supply" dries up. It then just sits there (without restarting or logging anything else) and waits for the next positions to arrive.
Click to expand...
Thanks. Sort of expected behaviour. The client isn't restarting. Just the TCP connection to the data source.
 
mgunther said:
Just FYI: I'm seeing "poll timeout occurred, restarting..." messages when things are quiet overnight with no traffic. So this looks like normal behaviour: it always reconnects and sends updates when and if there is something to report.

UPDATE:
It looks like the client is restarting 6 times in quick succession when "supply" dries up. It then just sits there (without restarting or logging anything else) and waits for the next positions to arrive.
Click to expand...
We are going to do some work around the reconnections I think but it sounds like this is the only issue for people and otherwise a pretty stable release!?
 
Just started with Planefinder today. I installed the client alongside FR24 and Flightaware and it runs fine. It is a very easy install and didn't upset any other settings. Running now for about 3 hours and has produced more than 80,000 positions. No errors in the log.
 
rogjack said:
Just started with Planefinder today. I installed the client alongside FR24 and Flightaware and it runs fine. It is a very easy install and didn't upset any other settings. Running now for about 3 hours and has produced more than 80,000 positions. No errors in the log.
Click to expand...
Great news, yes on the Raspbian Hard Float systems we try and use as little as possible!
 
Hi PF team,
New rpi feeder 3.0.1435 release has much lower cpu % & its running happily since I installed it around 8 hrs ago.;)
Thanks.
Mike.
 
guys got a problem. the software lags like hell... the old plans are not deleted.

log:

2015-04-28 13:13:13.555183 Failed to read web server request (7)
2015-04-28 13:10:08.870747 Successfully sent 39 aircraft updates over the past minute (5.00kb)
2015-04-28 13:07:17.873085 Successfully sent 51 aircraft updates over the past minute (5.00kb)
2015-04-28 13:05:43.856826 Failed to establish a data proxy connection. Receiver data cannot be sent!
2015-04-28 13:05:43.856513 Failed to resolve remote address 'dataupload.planefinder.net' (errno: -3)
2015-04-28 13:04:30.463249 Successfully sent 35 aircraft updates over the past minute (4.00kb)
2015-04-28 13:04:00.664690 Failed to establish a data proxy connection. Receiver data cannot be sent!
2015-04-28 13:04:00.664386 Failed to resolve remote address 'dataupload.planefinder.net' (errno: -2)
2015-04-28 13:01:33.34300 Failed to read web server request (7)
2015-04-28 13:01:21.617686 Successfully sent 44 aircraft updates over the past minute (5.00kb)
2015-04-28 13:00:43.345072 User location has been verified.
2015-04-28 13:00:01.11486 Failed to establish a data proxy connection. Receiver data cannot be sent!
2015-04-28 13:00:01.11206 Failed to resolve remote address 'dataupload.planefinder.net' (errno: -3)
2015-04-28 12:59:30.978580 Failed to establish a data proxy connection. Receiver data cannot be sent!
2015-04-28 12:59:30.978195 Failed to resolve remote address 'dataupload.planefinder.net' (errno: -2)
2015-04-28 12:58:51.504257 Successfully sent 28 aircraft updates over the past minute (4.00kb)
 

Attachments

  • 1.png
    1.png
    356 KB · Views: 30
  • 2.png
    2.png
    75.2 KB · Views: 28
2015-04-28 12:28:08.758809 Failed connection to all provided addresses
2015-04-28 12:28:08.754305 Failed to open connection to socket: Connection refused (errno: 111)
2015-04-28 12:28:03.752983 Failed connection to all provided addresses
2015-04-28 12:28:03.749126 Failed to open connection to socket: Connection refused (errno: 111)
2015-04-28 12:27:58.747769 Failed connection to all provided addresses
2015-04-28 12:27:58.738905 Failed to open connection to socket: Connection refused (errno: 111)
2015-04-28 12:27:53.737824 Failed connection to all provided addresses
2015-04-28 12:27:53.737596 Failed to open connection to socket: Connection refused (errno: 111)
2015-04-28 12:27:53.736596 Client restarted successfully
2015-04-28 12:27:53.736412 Closed TCP connection
 
Status
Not open for further replies.
Back
Top