New Plane Finder Sharing Client - Beta Thread

Status
Not open for further replies.

Dave Blake

New Member
Hi Dave,

No there is an data view on the client itself, I can see everything on the server too. If it happens again I would like to see what is in that list.

See my data view.

View attachment 1664

It's the last seen column I am most interested in. You can click the header to sort and I would love to see the oldest one in the list!

A fresh log next time too would be great also.
Lee, I just sent you the URL to my client data so you can keep an eye on it should the issue happen again.
 

ab cd

Senior Member
I have updated to latest version:
Code:
wget http://client.planefinder.net/pfclient_3.0.450_armhf.deb
sudo dpkg -i pfclient_3.0.450_armhf.deb
 
Last edited:

caius

Member
I had a client crash earlier today. This was the previous version, not .450:

Code:
Apr 18 11:57:18 alarmpi pfclient[12733]: 2015-04-18 11:54:02.464520 Successfu
Apr 18 11:57:18 alarmpi systemd[1]: pfclient.service: main process exited, code=killed, status=11/SEGV
Apr 18 11:57:18 alarmpi systemd[1]: Unit pfclient.service entered failed state.
Apr 18 11:57:18 alarmpi systemd[1]: pfclient.service failed.

Until that time, everything seemed to be running OK, and there were other obvious signs in the logs. Memory usage and CPU were consistent to the point of the crash.
 

Lee Armstrong

Administrator
Staff member
I had a client crash earlier today. This was the previous version, not .450:

Code:
Apr 18 11:57:18 alarmpi pfclient[12733]: 2015-04-18 11:54:02.464520 Successfu
Apr 18 11:57:18 alarmpi systemd[1]: pfclient.service: main process exited, code=killed, status=11/SEGV
Apr 18 11:57:18 alarmpi systemd[1]: Unit pfclient.service entered failed state.
Apr 18 11:57:18 alarmpi systemd[1]: pfclient.service failed.

Until that time, everything seemed to be running OK, and there were other obvious signs in the logs. Memory usage and CPU were consistent to the point of the crash.
Ok thanks. Hopefully later this week we'll have a new version out that has this fixed.
 

caius

Member
I updated to .450 today, and had another crash. There was more information in the log this time:

Code:
Apr 19 22:53:28 alarmpi pfclient[1969]: *** Error in `/usr/bin/pfclient': double free or corruption (!prev): 0x00d99450 ***
Apr 19 22:53:28 alarmpi pfclient[1969]: ======= Backtrace: =========
Apr 19 22:53:28 alarmpi pfclient[1969]: /usr/lib/libc.so.6(+0x6870c)[0x76d9770c]
Apr 19 22:53:28 alarmpi pfclient[1969]: /usr/lib/libc.so.6(+0x6e384)[0x76d9d384]
Apr 19 22:53:28 alarmpi pfclient[1969]: /usr/lib/libc.so.6(+0x6ed2c)[0x76d9dd2c]
Apr 19 22:53:28 alarmpi pfclient[1969]: /usr/lib/libc.so.6(fclose+0x118)[0x76d8ce64]
Apr 19 22:53:28 alarmpi pfclient[1969]: ======= Memory map: ========
Apr 19 22:53:28 alarmpi pfclient[1969]: 00010000-00085000 r-xp 00000000 b3:02 1208742     /usr/bin/pfclient
Apr 19 22:53:28 alarmpi pfclient[1969]: 00095000-0012b000 rw-p 00075000 b3:02 1208742     /usr/bin/pfclient
Apr 19 22:53:28 alarmpi pfclient[1969]: 00d99000-010cb000 rw-p 00000000 00:00 0           [heap]
Apr 19 22:53:28 alarmpi pfclient[1969]: 71c00000-71c23000 rw-p 00000000 00:00 0
Apr 19 22:53:28 alarmpi pfclient[1969]: 71c23000-71d00000 ---p 00000000 00:00 0
Apr 19 22:53:28 alarmpi pfclient[1969]: 71d00000-71d23000 rw-p 00000000 00:00 0
Apr 19 22:53:28 alarmpi pfclient[1969]: 71d23000-71e00000 ---p 00000000 00:00 0
Apr 19 22:53:28 alarmpi pfclient[1969]: 71f00000-71f01000 ---p 00000000 00:00 0
Apr 19 22:53:28 alarmpi pfclient[1969]: 71f01000-72700000 rw-p 00000000 00:00 0
Apr 19 22:53:28 alarmpi pfclient[1969]: 72700000-72701000 ---p 00000000 00:00 0
Apr 19 22:53:28 alarmpi pfclient[1969]: 72701000-72f00000 rw-p 00000000 00:00 0
Apr 19 22:53:28 alarmpi pfclient[1969]: 72f00000-72f01000 ---p 00000000 00:00 0
Apr 19 22:53:28 alarmpi pfclient[1969]: 72f01000-73700000 rw-p 00000000 00:00 0
Apr 19 22:53:28 alarmpi pfclient[1969]: 73700000-73701000 ---p 00000000 00:00 0
Apr 19 22:53:28 alarmpi pfclient[1969]: 73701000-73f00000 rw-p 00000000 00:00 0
Apr 19 22:53:28 alarmpi pfclient[1969]: 73f00000-73f23000 rw-p 00000000 00:00 0
Apr 19 22:53:28 alarmpi pfclient[1969]: 73f23000-74000000 ---p 00000000 00:00 0
Apr 19 22:53:28 alarmpi pfclient[1969]: 74000000-74023000 rw-p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 74023000-74100000 ---p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 74100000-74101000 ---p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 74101000-74900000 rw-p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 74900000-74923000 rw-p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 74923000-74a00000 ---p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 74a00000-74a62000 rw-p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 74a62000-74b00000 ---p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 74ba6000-74bb9000 r-xp 00000000 b3:02 1195599     /usr/lib/libresolv-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 74bb9000-74bc8000 ---p 00013000 b3:02 1195599     /usr/lib/libresolv-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 74bc8000-74bc9000 r--p 00012000 b3:02 1195599     /usr/lib/libresolv-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 74bc9000-74bca000 rw-p 00013000 b3:02 1195599     /usr/lib/libresolv-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 74bca000-74bcc000 rw-p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 74bcc000-74bd2000 r-xp 00000000 b3:02 1195368     /usr/lib/libnss_dns-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 74bd2000-74be1000 ---p 00006000 b3:02 1195368     /usr/lib/libnss_dns-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 74be1000-74be2000 r--p 00005000 b3:02 1195368     /usr/lib/libnss_dns-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 74be2000-74be3000 rw-p 00006000 b3:02 1195368     /usr/lib/libnss_dns-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 74be3000-74bef000 r-xp 00000000 b3:02 1195615     /usr/lib/libnss_files-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 74bef000-74bfe000 ---p 0000c000 b3:02 1195615     /usr/lib/libnss_files-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 74bfe000-74bff000 r--p 0000b000 b3:02 1195615     /usr/lib/libnss_files-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 74bff000-74c00000 rw-p 0000c000 b3:02 1195615     /usr/lib/libnss_files-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 75400000-75422000 rw-p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 75422000-75500000 ---p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 75502000-7551e000 r-xp 00000000 b3:02 1195436     /usr/lib/libgcc_s.so.1
Apr 19 22:53:29 alarmpi pfclient[1969]: 7551e000-7552e000 ---p 0001c000 b3:02 1195436     /usr/lib/libgcc_s.so.1
Apr 19 22:53:29 alarmpi pfclient[1969]: 7552e000-7552f000 rw-p 0001c000 b3:02 1195436     /usr/lib/libgcc_s.so.1
Apr 19 22:53:29 alarmpi pfclient[1969]: 7552f000-75530000 ---p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 75530000-75d2f000 rw-p 00000000 00:00 0           [stack:1972]
Apr 19 22:53:29 alarmpi pfclient[1969]: 75d2f000-75d30000 ---p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 75d30000-7652f000 rw-p 00000000 00:00 0           [stack:1971]
Apr 19 22:53:29 alarmpi pfclient[1969]: 7652f000-76530000 ---p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 76530000-76d2f000 rw-p 00000000 00:00 0           [stack:1970]
Apr 19 22:53:29 alarmpi pfclient[1969]: 76d2f000-76e58000 r-xp 00000000 b3:02 1195427     /usr/lib/libc-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76e58000-76e68000 ---p 00129000 b3:02 1195427     /usr/lib/libc-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76e68000-76e6a000 r--p 00129000 b3:02 1195427     /usr/lib/libc-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76e6a000-76e6b000 rw-p 0012b000 b3:02 1195427     /usr/lib/libc-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76e6b000-76e6e000 rw-p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 76e6e000-76e74000 r-xp 00000000 b3:02 1195304     /usr/lib/librt-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76e74000-76e83000 ---p 00006000 b3:02 1195304     /usr/lib/librt-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76e83000-76e84000 r--p 00005000 b3:02 1195304     /usr/lib/librt-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76e84000-76e85000 rw-p 00006000 b3:02 1195304     /usr/lib/librt-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76e85000-76ef2000 r-xp 00000000 b3:02 1195391     /usr/lib/libm-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76ef2000-76f01000 ---p 0006d000 b3:02 1195391     /usr/lib/libm-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76f01000-76f02000 r--p 0006c000 b3:02 1195391     /usr/lib/libm-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76f02000-76f03000 rw-p 0006d000 b3:02 1195391     /usr/lib/libm-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76f03000-76f18000 r-xp 00000000 b3:02 1195276     /usr/lib/libpthread-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76f18000-76f27000 ---p 00015000 b3:02 1195276     /usr/lib/libpthread-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76f27000-76f28000 r--p 00014000 b3:02 1195276     /usr/lib/libpthread-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76f28000-76f29000 rw-p 00015000 b3:02 1195276     /usr/lib/libpthread-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76f29000-76f2b000 rw-p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 76f3e000-76f5e000 r-xp 00000000 b3:02 1195399     /usr/lib/ld-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76f68000-76f6d000 rw-p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 76f6d000-76f6e000 r--p 0001f000 b3:02 1195399     /usr/lib/ld-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76f6e000-76f6f000 rw-p 00020000 b3:02 1195399     /usr/lib/ld-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 7e9ef000-7ea10000 rw-p 00000000 00:00 0           [stack]
Apr 19 22:53:29 alarmpi pfclient[1969]: 7efec000-7efed000 r-xp 00000000 00:00 0           [sigpage]
Apr 19 22:53:29 alarmpi pfclient[1969]: ffff0000-ffff1000 r-xp 00000000 00:00 0           [vectors]

Systemd succesfully restarted it once and it looks like it uploaded a bunch of cached data, but then the journal is full of similar crash messages until it gave up. I restarted it manually when I noticed and it's running OK again.

This is on a RPi 2, running arch linux.
 

Lee Armstrong

Administrator
Staff member
I updated to .450 today, and had another crash. There was more information in the log this time:

Code:
Apr 19 22:53:28 alarmpi pfclient[1969]: *** Error in `/usr/bin/pfclient': double free or corruption (!prev): 0x00d99450 ***
Apr 19 22:53:28 alarmpi pfclient[1969]: ======= Backtrace: =========
Apr 19 22:53:28 alarmpi pfclient[1969]: /usr/lib/libc.so.6(+0x6870c)[0x76d9770c]
Apr 19 22:53:28 alarmpi pfclient[1969]: /usr/lib/libc.so.6(+0x6e384)[0x76d9d384]
Apr 19 22:53:28 alarmpi pfclient[1969]: /usr/lib/libc.so.6(+0x6ed2c)[0x76d9dd2c]
Apr 19 22:53:28 alarmpi pfclient[1969]: /usr/lib/libc.so.6(fclose+0x118)[0x76d8ce64]
Apr 19 22:53:28 alarmpi pfclient[1969]: ======= Memory map: ========
Apr 19 22:53:28 alarmpi pfclient[1969]: 00010000-00085000 r-xp 00000000 b3:02 1208742     /usr/bin/pfclient
Apr 19 22:53:28 alarmpi pfclient[1969]: 00095000-0012b000 rw-p 00075000 b3:02 1208742     /usr/bin/pfclient
Apr 19 22:53:28 alarmpi pfclient[1969]: 00d99000-010cb000 rw-p 00000000 00:00 0           [heap]
Apr 19 22:53:28 alarmpi pfclient[1969]: 71c00000-71c23000 rw-p 00000000 00:00 0
Apr 19 22:53:28 alarmpi pfclient[1969]: 71c23000-71d00000 ---p 00000000 00:00 0
Apr 19 22:53:28 alarmpi pfclient[1969]: 71d00000-71d23000 rw-p 00000000 00:00 0
Apr 19 22:53:28 alarmpi pfclient[1969]: 71d23000-71e00000 ---p 00000000 00:00 0
Apr 19 22:53:28 alarmpi pfclient[1969]: 71f00000-71f01000 ---p 00000000 00:00 0
Apr 19 22:53:28 alarmpi pfclient[1969]: 71f01000-72700000 rw-p 00000000 00:00 0
Apr 19 22:53:28 alarmpi pfclient[1969]: 72700000-72701000 ---p 00000000 00:00 0
Apr 19 22:53:28 alarmpi pfclient[1969]: 72701000-72f00000 rw-p 00000000 00:00 0
Apr 19 22:53:28 alarmpi pfclient[1969]: 72f00000-72f01000 ---p 00000000 00:00 0
Apr 19 22:53:28 alarmpi pfclient[1969]: 72f01000-73700000 rw-p 00000000 00:00 0
Apr 19 22:53:28 alarmpi pfclient[1969]: 73700000-73701000 ---p 00000000 00:00 0
Apr 19 22:53:28 alarmpi pfclient[1969]: 73701000-73f00000 rw-p 00000000 00:00 0
Apr 19 22:53:28 alarmpi pfclient[1969]: 73f00000-73f23000 rw-p 00000000 00:00 0
Apr 19 22:53:28 alarmpi pfclient[1969]: 73f23000-74000000 ---p 00000000 00:00 0
Apr 19 22:53:28 alarmpi pfclient[1969]: 74000000-74023000 rw-p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 74023000-74100000 ---p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 74100000-74101000 ---p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 74101000-74900000 rw-p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 74900000-74923000 rw-p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 74923000-74a00000 ---p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 74a00000-74a62000 rw-p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 74a62000-74b00000 ---p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 74ba6000-74bb9000 r-xp 00000000 b3:02 1195599     /usr/lib/libresolv-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 74bb9000-74bc8000 ---p 00013000 b3:02 1195599     /usr/lib/libresolv-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 74bc8000-74bc9000 r--p 00012000 b3:02 1195599     /usr/lib/libresolv-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 74bc9000-74bca000 rw-p 00013000 b3:02 1195599     /usr/lib/libresolv-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 74bca000-74bcc000 rw-p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 74bcc000-74bd2000 r-xp 00000000 b3:02 1195368     /usr/lib/libnss_dns-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 74bd2000-74be1000 ---p 00006000 b3:02 1195368     /usr/lib/libnss_dns-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 74be1000-74be2000 r--p 00005000 b3:02 1195368     /usr/lib/libnss_dns-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 74be2000-74be3000 rw-p 00006000 b3:02 1195368     /usr/lib/libnss_dns-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 74be3000-74bef000 r-xp 00000000 b3:02 1195615     /usr/lib/libnss_files-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 74bef000-74bfe000 ---p 0000c000 b3:02 1195615     /usr/lib/libnss_files-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 74bfe000-74bff000 r--p 0000b000 b3:02 1195615     /usr/lib/libnss_files-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 74bff000-74c00000 rw-p 0000c000 b3:02 1195615     /usr/lib/libnss_files-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 75400000-75422000 rw-p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 75422000-75500000 ---p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 75502000-7551e000 r-xp 00000000 b3:02 1195436     /usr/lib/libgcc_s.so.1
Apr 19 22:53:29 alarmpi pfclient[1969]: 7551e000-7552e000 ---p 0001c000 b3:02 1195436     /usr/lib/libgcc_s.so.1
Apr 19 22:53:29 alarmpi pfclient[1969]: 7552e000-7552f000 rw-p 0001c000 b3:02 1195436     /usr/lib/libgcc_s.so.1
Apr 19 22:53:29 alarmpi pfclient[1969]: 7552f000-75530000 ---p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 75530000-75d2f000 rw-p 00000000 00:00 0           [stack:1972]
Apr 19 22:53:29 alarmpi pfclient[1969]: 75d2f000-75d30000 ---p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 75d30000-7652f000 rw-p 00000000 00:00 0           [stack:1971]
Apr 19 22:53:29 alarmpi pfclient[1969]: 7652f000-76530000 ---p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 76530000-76d2f000 rw-p 00000000 00:00 0           [stack:1970]
Apr 19 22:53:29 alarmpi pfclient[1969]: 76d2f000-76e58000 r-xp 00000000 b3:02 1195427     /usr/lib/libc-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76e58000-76e68000 ---p 00129000 b3:02 1195427     /usr/lib/libc-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76e68000-76e6a000 r--p 00129000 b3:02 1195427     /usr/lib/libc-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76e6a000-76e6b000 rw-p 0012b000 b3:02 1195427     /usr/lib/libc-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76e6b000-76e6e000 rw-p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 76e6e000-76e74000 r-xp 00000000 b3:02 1195304     /usr/lib/librt-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76e74000-76e83000 ---p 00006000 b3:02 1195304     /usr/lib/librt-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76e83000-76e84000 r--p 00005000 b3:02 1195304     /usr/lib/librt-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76e84000-76e85000 rw-p 00006000 b3:02 1195304     /usr/lib/librt-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76e85000-76ef2000 r-xp 00000000 b3:02 1195391     /usr/lib/libm-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76ef2000-76f01000 ---p 0006d000 b3:02 1195391     /usr/lib/libm-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76f01000-76f02000 r--p 0006c000 b3:02 1195391     /usr/lib/libm-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76f02000-76f03000 rw-p 0006d000 b3:02 1195391     /usr/lib/libm-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76f03000-76f18000 r-xp 00000000 b3:02 1195276     /usr/lib/libpthread-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76f18000-76f27000 ---p 00015000 b3:02 1195276     /usr/lib/libpthread-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76f27000-76f28000 r--p 00014000 b3:02 1195276     /usr/lib/libpthread-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76f28000-76f29000 rw-p 00015000 b3:02 1195276     /usr/lib/libpthread-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76f29000-76f2b000 rw-p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 76f3e000-76f5e000 r-xp 00000000 b3:02 1195399     /usr/lib/ld-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76f68000-76f6d000 rw-p 00000000 00:00 0
Apr 19 22:53:29 alarmpi pfclient[1969]: 76f6d000-76f6e000 r--p 0001f000 b3:02 1195399     /usr/lib/ld-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 76f6e000-76f6f000 rw-p 00020000 b3:02 1195399     /usr/lib/ld-2.20.so
Apr 19 22:53:29 alarmpi pfclient[1969]: 7e9ef000-7ea10000 rw-p 00000000 00:00 0           [stack]
Apr 19 22:53:29 alarmpi pfclient[1969]: 7efec000-7efed000 r-xp 00000000 00:00 0           [sigpage]
Apr 19 22:53:29 alarmpi pfclient[1969]: ffff0000-ffff1000 r-xp 00000000 00:00 0           [vectors]

Systemd succesfully restarted it once and it looks like it uploaded a bunch of cached data, but then the journal is full of similar crash messages until it gave up. I restarted it manually when I noticed and it's running OK again.

This is on a RPi 2, running arch linux.
Thanks,

Did it crash on its own or when you accessed the Web UI?
 

caius

Member
I don't think so. I noticed because I tried to look at the web page, but the crash was an hour or so before.
 

Lee Armstrong

Administrator
Staff member
Ok thanks. I've not used ArchLinux before and that is a neat log, what log was it that reported all that crash info?
 

caius

Member
Yes, it's pretty easy to do. Here is the unit file:

Code:
[Unit]
Description=Planefinder data feed 

[Service]
Type=simple
ExecStart=/usr/bin/pfclient
PIDFile=/run/pfclient.pid
RestartSec=10
Restart=on-failure

[Install]
WantedBy=multi-user.target

You can make unit files quite a bit more complicated to account for different types of daemon, and set dependencies etc. I find it simpler than init scripts though.
 

mgunther

New Member
I had a crash today (version .450). I noticed that the map was not updating any more. Not sure what logs to check and how to restart the client, so I rebooted to Pi. The only thing I see is in syslog:
Code:
Apr 20 21:54:04 piaware pfclient: *** glibc detected *** /usr/bin/pfclient: double free or corruption (!prev): 0x01985fb0 ***
Let me know if there is anything else I can help you with.
 

Lee Armstrong

Administrator
Staff member
I had a crash today (version .450). I noticed that the map was not updating any more. Not sure what logs to check and how to restart the client, so I rebooted to Pi. The only thing I see is in syslog:
Code:
Apr 20 21:54:04 piaware pfclient: *** glibc detected *** /usr/bin/pfclient: double free or corruption (!prev): 0x01985fb0 ***
Let me know if there is anything else I can help you with.
Thank you,

I take it you had the map open then which then stopped refreshing?
 

mgunther

New Member
Actually I don't think it was actively open when it stopped refreshing. I was away from the laptop with the lid closed. But I think even then it does some periodical updates in the background. When I came back to it, I had quick glances at both Dump1090 and PF maps and noticed that they did not match.
 

caius

Member
@Lee Armstrong Are you interested in feature requests for the new client? If so, I was thinking it would be good to have a range histogram, and a polar range plot in the stats page. They would be very useful for comparing changes to receiver configurations. Modesdeco has this but dump1090 doesn't. It looks like this:

graphs.PNG
 
Status
Not open for further replies.
Top