Plane Finder Client Beta2 (3.0.1435)

Status
Not open for further replies.
Lee Armstrong

Lee Armstrong

Administrator
Staff member
Hello everyone,

Thank you all for installing the last beta and a special thanks to those that we worked with directly on a couple of issues.

The latest version is 3.0.1435 and can be found here along with a change log which we will keep updated there too.

For those who want the commands for the update it is simply..
Code: 
wget http://client.planefinder.net/pfclient_3.0.1435_armhf.deb
sudo dpkg -i pfclient_3.0.1435_armhf.deb

Hopefully CPU should be a bit lower than before for those that saw it higher than we did in our testing. Not a huge amount of new stuff for Pi users just some increased stability.

What is new though is a native build that can be installed directly on the Radarcape unit. This is a slightly different build and is designed at the moment for the default Angstrom with soft float support. To install it is simply a case of ssh'ing to the unit and running.
Code: 
opkg install http://client.planefinder.net/pfclient_3.0.1435_armel.opk

If you need help with the SSH part we suggest you look at http://wiki.modesbeast.com

Once installed follow the same instructions as a Pi for setup by visiting http://<ip of unit>:30053. Obvious differences are to set the "Format" to "Radarcape" and to also set it to "127.0.0.1" and "10006" for the IP and port.
 
Thanks , Updated,

CPU loads is lower :)
Running on raspberry pi 2

Screen Shot 2015-04-23 at 16.06.38.png
 
My client had stopped again. I started it just to get current reading of CPU:
1929 dump1090 15 -5 16996 8252 1940 R 39.8 1.9 551:15.05 dump1090-mutabi
3778 root 20 0 28200 2592 2312 S 2.6 0.6 0:02.59 pfclient
2012 root 20 0 72256 14m 8116 S 1.0 3.2 2:38.96 collectd
2137 root 20 0 73792 6256 3232 S 1.0 1.4 11:34.66 fr24feed

Installed version 3.0.1435 and CPU has gone down:
1929 dump1090 15 -5 16996 8252 1940 R 40.1 1.9 553:09.42 dump1090-mutabi
4052 pi 20 0 4672 2448 2080 R 1.3 0.6 0:01.57 top
2137 root 20 0 73792 6256 3232 S 0.7 1.4 11:37.00 fr24feed
4031 root 20 0 36216 2440 2132 S 0.7 0.5 0:00.42 pfclient

Please let us know which log we should watch for any issues. Thanks!
 
Good that is much lower. The log that you need should show up in the "Log Viewer" of the web interface.

Also if it crashes I'm hoping it should now write something to /var/log/pfclient/error.log

Also the config would be handy to see too.

Glad to see CPU down too
 
Beta2 not yet installed, will do soon. Meanwhile Beta1 failed to connect to server shortly after crash of dump1090-mut: sympathetic crash! . Log file (pfclient log.txt) attached.
 

Attachments

  • pfclient log.txt
    247.9 KB · Views: 37
Last edited:
hmmm , poll timeout occurred, restarting...

Nothing in error.log /var/log/pfclient/

Code: 
2015-04-24 14:08:11.311840 Successfully sent 483 aircraft updates over the past minute (32.00kb)
2015-04-24 14:07:07.321123 Successfully sent 1 aircraft updates over the past minute (2.00kb)
2015-04-24 14:06:26.901094 TCP connection established: 127.0.0.1:30005
2015-04-24 14:06:26.900438 Client restarted successfully
2015-04-24 14:06:26.900344 Closed TCP connection
2015-04-24 14:06:26.899977 poll timeout occurred, restarting...
2015-04-24 14:06:16.891187 TCP connection established: 127.0.0.1:30005
2015-04-24 14:06:16.890479 Client restarted successfully
2015-04-24 14:06:16.890384 Closed TCP connection
2015-04-24 14:06:16.889978 poll timeout occurred, restarting...
2015-04-24 14:06:06.883540 TCP connection established: 127.0.0.1:30005
2015-04-24 14:06:06.882957 Client restarted successfully
2015-04-24 14:06:06.882886 Closed TCP connection
2015-04-24 14:06:06.882535 poll timeout occurred, restarting...
2015-04-24 14:05:56.872380 TCP connection established: 127.0.0.1:30005
2015-04-24 14:05:56.871681 Client restarted successfully
2015-04-24 14:05:56.871581 Closed TCP connection
2015-04-24 14:05:56.871153 poll timeout occurred, restarting...
2015-04-24 14:05:46.860977 TCP connection established: 127.0.0.1:30005
2015-04-24 14:05:46.860264 Client restarted successfully
2015-04-24 14:05:46.860143 Closed TCP connection
2015-04-24 14:05:46.859665 poll timeout occurred, restarting...
2015-04-24 14:05:32.681330 TCP connection established: 127.0.0.1:30005
2015-04-24 14:05:32.680807 Client restarted successfully
2015-04-24 14:05:32.680735 Closed TCP connection
2015-04-24 14:05:32.680388 poll timeout occurred, restarting...
2015-04-24 14:05:22.670174 TCP connection established: 127.0.0.1:30005
2015-04-24 14:05:22.669159 Client restarted successfully
2015-04-24 14:05:22.668922 Closed TCP connection
2015-04-24 14:05:16.661490 poll timeout occurred, restarting...
2015-04-24 14:05:06.292932 Successfully sent 145 aircraft updates over the past minute (10.00kb)
2015-04-24 14:04:57.279152 TCP connection established: 127.0.0.1:30005
2015-04-24 14:04:57.278360 Client restarted successfully
2015-04-24 14:04:57.278165 Closed TCP connection
2015-04-24 14:04:57.276146 poll timeout occurred, restarting...
2015-04-24 14:04:29.661560 TCP connection established: 127.0.0.1:30005
2015-04-24 14:04:29.660547 Client restarted successfully
2015-04-24 14:04:29.660371 Closed TCP connection
2015-04-24 14:04:27.237244 poll timeout occurred, restarting...
2015-04-24 14:04:04.955381 Successfully sent 612 aircraft updates over the past minute (39.00kb)
2015-04-24 14:02:59.975448 Successfully sent 584 aircraft updates over the past minute (38.00kb)
2015-04-24 14:01:55.221985 Successfully sent 586 aircraft updates over the past minute (37.00kb)
 
bramj said:
hmmm , poll timeout occurred, restarting...

Nothing in error.log /var/log/pfclient/

Code: 
2015-04-24 14:08:11.311840 Successfully sent 483 aircraft updates over the past minute (32.00kb)
2015-04-24 14:07:07.321123 Successfully sent 1 aircraft updates over the past minute (2.00kb)
2015-04-24 14:06:26.901094 TCP connection established: 127.0.0.1:30005
2015-04-24 14:06:26.900438 Client restarted successfully
2015-04-24 14:06:26.900344 Closed TCP connection
2015-04-24 14:06:26.899977 poll timeout occurred, restarting...
2015-04-24 14:06:16.891187 TCP connection established: 127.0.0.1:30005
2015-04-24 14:06:16.890479 Client restarted successfully
2015-04-24 14:06:16.890384 Closed TCP connection
2015-04-24 14:06:16.889978 poll timeout occurred, restarting...
2015-04-24 14:06:06.883540 TCP connection established: 127.0.0.1:30005
2015-04-24 14:06:06.882957 Client restarted successfully
2015-04-24 14:06:06.882886 Closed TCP connection
2015-04-24 14:06:06.882535 poll timeout occurred, restarting...
2015-04-24 14:05:56.872380 TCP connection established: 127.0.0.1:30005
2015-04-24 14:05:56.871681 Client restarted successfully
2015-04-24 14:05:56.871581 Closed TCP connection
2015-04-24 14:05:56.871153 poll timeout occurred, restarting...
2015-04-24 14:05:46.860977 TCP connection established: 127.0.0.1:30005
2015-04-24 14:05:46.860264 Client restarted successfully
2015-04-24 14:05:46.860143 Closed TCP connection
2015-04-24 14:05:46.859665 poll timeout occurred, restarting...
2015-04-24 14:05:32.681330 TCP connection established: 127.0.0.1:30005
2015-04-24 14:05:32.680807 Client restarted successfully
2015-04-24 14:05:32.680735 Closed TCP connection
2015-04-24 14:05:32.680388 poll timeout occurred, restarting...
2015-04-24 14:05:22.670174 TCP connection established: 127.0.0.1:30005
2015-04-24 14:05:22.669159 Client restarted successfully
2015-04-24 14:05:22.668922 Closed TCP connection
2015-04-24 14:05:16.661490 poll timeout occurred, restarting...
2015-04-24 14:05:06.292932 Successfully sent 145 aircraft updates over the past minute (10.00kb)
2015-04-24 14:04:57.279152 TCP connection established: 127.0.0.1:30005
2015-04-24 14:04:57.278360 Client restarted successfully
2015-04-24 14:04:57.278165 Closed TCP connection
2015-04-24 14:04:57.276146 poll timeout occurred, restarting...
2015-04-24 14:04:29.661560 TCP connection established: 127.0.0.1:30005
2015-04-24 14:04:29.660547 Client restarted successfully
2015-04-24 14:04:29.660371 Closed TCP connection
2015-04-24 14:04:27.237244 poll timeout occurred, restarting...
2015-04-24 14:04:04.955381 Successfully sent 612 aircraft updates over the past minute (39.00kb)
2015-04-24 14:02:59.975448 Successfully sent 584 aircraft updates over the past minute (38.00kb)
2015-04-24 14:01:55.221985 Successfully sent 586 aircraft updates over the past minute (37.00kb)
Click to expand...

error.log will only be populated on a crash, everything else in this log.

It looks like whatever we connected to refused our connection for a few minutes and then it rectified itself. Other clients may have had this issue too but we report it :)
 
CPU usage has dropped. Nice release.
Code: 
  1  [|||||                           12.8%]     Tasks: 53, 41 thr; 1 running
  2  [|||||||||                       23.2%]     Load average: 0.51 0.45 0.42
  Mem[||||||||||||||||||||||||||||143/874MB]     Uptime: 29 days, 06:14:53
  Swp[                               0/99MB]

  PID USER      PRI  NI  VIRT   RES   SHR S CPU% MEM%   TIME+  Command
 1915 dumpuser   15  -5 20948 10336  1120 S 27.0  1.2     185h /usr/bin/dump1090-mutability --
 2041 dumpuser   15  -5 20948 10336  1120 S  5.0  1.2 31h17:07 /usr/bin/dump1090-mutability --
 2042 bananapi   20   0 13180  2640  2196 S  4.0  0.3 30h31:59 ./modesmixer2 --inConnect 192.1
14587 bananapi   20   0  4884  1688  1236 R  3.0  0.2  0:01.28 htop
 2072 root       20   0 82080  5300  1996 S  1.0  0.6 10h11:13 /usr/bin/fr24feed -- --monitor-
30459 root       20   0 79204  3248  1692 S  0.0  0.4 19:06.33 /usr/bin/pfclient -d -i /var/ru
 2128 root       20   0 17360  6468  3024 S  0.0  0.7  3h25:35 /usr/bin/piaware -p /var/run/pi
 2812 root       39  19 19120  7208  1564 S  0.0  0.8  3h01:15 /usr/bin/perl /usr/bin/rpimonit
30461 root       20   0 79204  3248  1692 S  0.0  0.4  3:03.87 /usr/bin/pfclient -d -i /var/ru
 2986 root       20   0 82080  5300  1996 S  0.0  0.6  5h55:55 /usr/bin/fr24feed -- --monitor-
 
I don't know if it was something on my end or server related, but I report it anyway:
Code: 
2015-04-24 23:37:39.912656 TCP connection established: 192.168.*.*:30002
2015-04-24 23:37:39.912004 Client restarted successfully
2015-04-24 23:37:39.911906 Closed TCP connection
2015-04-24 23:37:39.911444 poll timeout occurred, restarting...
2015-04-24 23:37:33.823144 Successfully sent 4 aircraft updates over the past minute (2.00kb)
2015-04-24 23:37:29.902449 TCP connection established: 192.168.*.*:30002
2015-04-24 23:37:29.901874 Client restarted successfully
2015-04-24 23:37:29.901784 Closed TCP connection
2015-04-24 23:37:29.901409 poll timeout occurred, restarting...
2015-04-24 23:37:19.897760 TCP connection established: 192.168.*.*:30002
2015-04-24 23:37:19.897125 Client restarted successfully
2015-04-24 23:37:19.897030 Closed TCP connection
2015-04-24 23:37:19.896659 poll timeout occurred, restarting...
 
Thanks. It looks like Dump1090 refused our connection for a bit. I've seen this happen so nothing to worry about (as long as we reconnected ok)

Also if Dump1090 is on the same machine I would use 127.0.0.1 as the IP to avoid the networking stack
 
loplo said:
I don't know if it was something on my end or server related, but I report it anyway:
Code: 
2015-04-24 23:37:39.912656 TCP connection established: 192.168.*.*:30002
2015-04-24 23:37:39.912004 Client restarted successfully
2015-04-24 23:37:39.911906 Closed TCP connection
2015-04-24 23:37:39.911444 poll timeout occurred, restarting...
2015-04-24 23:37:33.823144 Successfully sent 4 aircraft updates over the past minute (2.00kb)
2015-04-24 23:37:29.902449 TCP connection established: 192.168.*.*:30002
2015-04-24 23:37:29.901874 Client restarted successfully
2015-04-24 23:37:29.901784 Closed TCP connection
2015-04-24 23:37:29.901409 poll timeout occurred, restarting...
2015-04-24 23:37:19.897760 TCP connection established: 192.168.*.*:30002
2015-04-24 23:37:19.897125 Client restarted successfully
2015-04-24 23:37:19.897030 Closed TCP connection
2015-04-24 23:37:19.896659 poll timeout occurred, restarting...
Click to expand...
Just thinking actually as not sure where you are located. Could it have been a time of no traffic or very little? We reconnect just in case there was an actual error. Either way nothing to worry about as it reconnected and did what I expected.
 
I'm located a few (8km) from EDDK. It's one of the few airports without the night flight ban in Germany, so "no traffic" it's excluded.
I'll check the log tomorrow in the morning for similar disconnections, and I'll report back.
 
Just updated to the new version. CPU load on my Pi B+ is now lower, averaging between 2.0 and 3.3, usually below 3. Great job!
And I like the more detailed logging with a count of data sent.
 
loplo said:
No disruptions during last night.
Click to expand...
That's great. I think my suspicions were correct as it can happen here in the South of the UK too.

zahidulhasan said:
Hi,

Will this client will work on INTEL based processor ?

Thanks,
Zahidul Hasan.
Click to expand...

Linux amd64??

Jayant said:
Just updated to the new version. CPU load on my Pi B+ is now lower, averaging between 2.0 and 3.3, usually below 3. Great job!
And I like the more detailed logging with a count of data sent.
Click to expand...
Thanks!
 
Lee Armstrong said:
That's great. I think my suspicions were correct as it can happen here in the South of the UK too.



Linux amd64??


Thanks!
Click to expand...

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.
 

Attachments

  • PC Configuration.txt
    5.4 KB · Views: 42
Status
Not open for further replies.
Back
Top