Faup1090 process stops

I have several Rpis using a custom image, dump1090-mutability, ModeSmixer, mlat-client and piaware (package-installation).

Uptimes are normally great, but one of these has a problem that the faup1090 process stops by itself every 60 to 90 days.

The rest of the software runs without problems at these occasions.

piaware.out has very old (from January ? ) and strange contents.

Any tips on where to look to find out what is causing this?


~# piaware-status
dump1090 is not running.
faup1090 is not running.
piaware is not running.
dump1090-mutabi is listening for connections on port 30005.
faup1090 is NOT connected to port 30005.
piaware is NOT connected to FlightAware.
dump1090-mutabi is producing data on port 30005.

~# more /tmp/piaware.out
01/09/2016 00:01:17 ****************************************************
01/09/2016 00:01:17 piaware version 2.1-4 is running, process ID 392
01/09/2016 00:01:17 your system info is: Linux P-ESGL2 4.1.10-v7+ #820 SMP PREEMPT Sun
Oct 4 16:26:51 BST 2015 armv7l GNU/Linux
01/09/2016 00:01:17 Connecting to FlightAware adept server at piaware.flightaware.com/
can’t read “catchResult”: no such variable
while executing
“log_locally “Connection to adept server at $host/$port failed: $catchResult””
(object “::adept” method “::fa_adept::AdeptClient::connect” body line 12)
invoked from within
“adept connect”
(procedure “main” line 82)
invoked from within
“main $argv”
invoked from within
“if {!$tcl_interactive} {
main $argv
(file “/usr/lib/piaware/main.tcl” line 125)
invoked from within
“source /usr/lib/piaware/main.tcl”
(“uplevel” body line 1)
invoked from within
“uplevel #0 source $path”
from tcllauncher running “piaware -p /var/run/piaware.pid”

No ideas ?

Start by upgrading to at least 2.1-5 (which fixes that traceback, IIRC), or ideally 3.0.3, and see if that fixes it.

Upgraded to 2.1-5, we see again in 60 days if its still with us. Thanks Obj.