problem with piaware 3.1.0

Nov 1 12:14:54 kane-radar piaware[1391]: piaware version 3.1.0 is running, process ID 1391
Nov 1 12:14:54 kane-radar piaware[1391]: your system info is: Linux kane-radar 4.4.26-v7+ #915 SMP Thu Oct 20 17:08:44 BST 2016 armv7l GNU/Linux
Nov 1 12:14:54 kane-radar piaware[1391]: *** buffer overflow detected ***: /usr/bin/piaware terminated
Nov 1 12:15:25 kane-radar piaware[1438]: creating pidfile /run/piaware/piaware.pid
Nov 1 12:15:25 kane-radar piaware[1438]: ****************************************************
Nov 1 12:15:25 kane-radar piaware[1438]: piaware version 3.1.0 is running, process ID 1438
Nov 1 12:15:25 kane-radar piaware[1438]: your system info is: Linux kane-radar 4.4.26-v7+ #915 SMP Thu Oct 20 17:08:44 BST 2016 armv7l GNU/Linux
Nov 1 12:15:25 kane-radar piaware[1438]: *** buffer overflow detected ***: /usr/bin/piaware terminated

Nov 1 12:14:54 kane-radar piaware[1391]: piaware version 3.1.0 is running, process ID 1391
Nov 1 12:14:54 kane-radar piaware[1391]: your system info is: Linux kane-radar 4.4.26-v7+ #915 SMP Thu Oct 20 17:08:44 BST 2016 armv7l GNU/Linux
Nov 1 12:14:54 kane-radar piaware[1391]: *** buffer overflow detected ***: /usr/bin/piaware terminated
Nov 1 12:15:25 kane-radar piaware[1438]: creating pidfile /run/piaware/piaware.pid
Nov 1 12:15:25 kane-radar piaware[1438]: ****************************************************
Nov 1 12:15:25 kane-radar piaware[1438]: piaware version 3.1.0 is running, process ID 1438
Nov 1 12:15:25 kane-radar piaware[1438]: your system info is: Linux kane-radar 4.4.26-v7+ #915 SMP Thu Oct 20 17:08:44 BST 2016 armv7l GNU/Linux
Nov 1 12:15:25 kane-radar piaware[1438]: *** buffer overflow detected ***: /usr/bin/piaware terminated

I Had same problem after upgrade from 2.1 and reverted back to it.
System is latest Raspbian on Raspberry Pi 1B with 256 MB RAM.

Can some developer please look at it or at least add more verbose debug output.
Thanks

Not one I’ve seen before. What is the system and how did you build piaware?

Mine piaware 3.1.0 was package from repository.


 deb http://flightaware.com/adsb/piaware/files/packages jessie piaware

What raspbian image did you use?

Image was Raspbian Jessie. Last update of packages was done before update to Piaware 3.1.0.

I could not reproduce this on a Pi 1B (512MB, I don’t have a 256MB model) using the current image from raspberrypi.org (2016-09-23-raspbian-jessie.zip) and the piaware install instructions at flightaware.com/adsb/piaware/install



Nov 15 01:31:37 raspberrypi piaware[4539]: creating pidfile /run/piaware/piaware.pid
Nov 15 01:31:38 raspberrypi piaware[4539]: ****************************************************
Nov 15 01:31:38 raspberrypi piaware[4539]: piaware version 3.1.0 is running, process ID 4539
Nov 15 01:31:38 raspberrypi piaware[4539]: your system info is: Linux raspberrypi 4.4.21+ #911 Thu Sep 15 14:17:52 BST 2016 armv6l GNU/Linux
Nov 15 01:31:39 raspberrypi piaware[4539]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Nov 15 01:31:39 raspberrypi piaware[4539]: Connection with adept server at piaware.flightaware.com/1200 established
Nov 15 01:31:40 raspberrypi piaware[4539]: TLS handshake with adept server at piaware.flightaware.com/1200 completed
Nov 15 01:31:41 raspberrypi piaware[4539]: FlightAware server certificate validated
Nov 15 01:31:41 raspberrypi piaware[4539]: encrypted session established with FlightAware
Nov 15 01:31:44 raspberrypi piaware[4539]: no ADS-B data program seen listening on port 30005 for 7 seconds, next check in 60s
Nov 15 01:31:44 raspberrypi piaware[4539]: logged in to FlightAware as user obj


The Pi 1Bs are notorious for having sdcard problems, maybe it is just sdcard corruption that you are seeing?

(The original poster is not on a 1B though)

Problem found by running under strace. Buffer overflow was after using ipv6 socket, but system has no ipv6 enabled. So Piaware didn’t check if IPv6 is enabled and tried to use it. :question: :question: :question: After loading ipv6 kernel module Piaware start working. :bulb: :angry: :exclamation: :exclamation: :exclamation:

Interesting. That sounds like a tcl bug then.

edit: if I blacklist the IPv6 module I can reproduce it now. Thanks for looking into it!

As a workaround, remove the IPv6 entry for localhost in /etc/hosts.

2 Likes

I experienced a similar issue. I removed all IPV6 nonsense from my Raspberry Pi computers because they started looked around for IPV6 on WLAN0 and essentially dropped off the network, never to return. That to me was clearly unacceptable.

I would like to pass on my to the original poster traincz and additional thanks for obj for his enlightening comments. Both of my Raspberry Pi FlightAware stations are now working reliably.