piaware 2.1.4 not starting

Hi

After updating from 2.1.3 to 2.1.4 i’ve experienced that after a reboot, the piaware is not starting. Dump1090 is running, but piaware not. After starting it manually

  • sudo /etc/init.d/piaware start
    it runs without problems until next reboot.

with piaware 2.1.3 no problems at all.

Any suggestions?

Thankx

login as: pi
pi@192.168.10.127’s password:
Linux piaware 4.1.15-v7+ #830 SMP Tue Dec 15 17:02:45 GMT 2015 armv7l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Thu Dec 17 01:03:00 2015 from imac.fritz.box
pi@piaware ~ $ sudo piaware-status
dump1090 is running.
faup1090 is not running.
piaware is not running.
dump1090 is listening for connections on port 30005.
faup1090 is NOT connected to port 30005.
piaware is NOT connected to FlightAware.
dump1090 is producing data on port 30005.
pi@piaware ~ $ sudo /etc/init.d/piaware start
ok ] Starting piaware server: piaware.
pi@piaware ~ $ sudo piaware-status
dump1090 is running.
faup1090 is running.
piaware is running.
dump1090 is listening for connections on port 30005.
faup1090 is connected to port 30005.
piaware is connected to FlightAware.
dump1090 is producing data on port 30005.
pi@piaware ~ $

From the logfile:

12/17/2015 00:03:35 ****************************************************
12/17/2015 00:03:35 piaware version 2.1-4 is running, process ID 2343
12/17/2015 00:03:36 your system info is: Linux piaware 4.1.15-v7+ #830 SMP Tue Dec 15 17:02:45 GMT 2015 armv7l GNU/Linux
12/17/2015 00:03:36 Connecting to FlightAware adept server at piaware.flightaware.com/1200
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”
12/17/2015 00:05:22 ****************************************************
12/17/2015 00:05:22 piaware version 2.1-4 is running, process ID 2847
12/17/2015 00:05:22 your system info is: Linux piaware 4.1.15-v7+ #830 SMP Tue Dec 15 17:02:45 GMT 2015 armv7l GNU/Linux
12/17/2015 00:05:22 Connecting to FlightAware adept server at piaware.flightaware.com/1200
12/17/2015 00:05:22 ADS-B data program ‘dump1090’ is listening on port 30005, so far so good
12/17/2015 00:05:22 Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 48.966 --lon 12.163
12/17/2015 00:05:22 Started faup1090 (pid 2870) to connect to dump1090
12/17/2015 00:05:23 Connection with adept server at piaware.flightaware.com/1200 established
12/17/2015 00:05:23 FlightAware server SSL certificate validated
12/17/2015 00:05:23 encrypted session established with FlightAware
12/17/2015 00:05:23 autoUpdate in adept config is enabled, allowing update
12/17/2015 00:05:23 manualUpdate in adept config is enabled, allowing update
12/17/2015 00:05:23 multilateration support enabled (use piaware-config to disable)
12/17/2015 00:05:23 piaware received a message from dump1090!
12/17/2015 00:05:24 logged in to FlightAware as user Chemicalx
12/17/2015 00:05:24 multilateration support enabled (use piaware-config to disable)
12/17/2015 00:05:24 multilateration data requested, enabling mlat client
12/17/2015 00:05:24 Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --results beast,connect,localhost:30104 --udp-transport 70.42.6.197:5469:3562462955
12/17/2015 00:05:25 mlat(2875): fa-mlat-client 0.2.4 starting up
12/17/2015 00:05:25 mlat(2875): Using UDP transport to 70.42.6.197:5469
12/17/2015 00:05:25 mlat(2875): Input connected to localhost:30005
12/17/2015 00:05:25 mlat(2875): Beast-format results connection with localhost:30104: connection established
12/17/2015 00:05:33 piaware has successfully sent several msgs to FlightAware!
12/17/2015 00:05:52 15 msgs recv’d from dump1090; 14 msgs sent to FlightAware
12/17/2015 00:06:23 server is sending alive messages; we will expect them
12/17/2015 00:10:52 114 msgs recv’d from dump1090 (99 in last 5m); 113 msgs sent to FlightAware

Yeah, there will probably be a 2.1-5 soon. Thanks for the report.

Same problem here with 2.14.
Gone back to 2.13 works fine.

Where possible I’ve auto-upgraded the handful of feeders that were on 2.1-4 to 2.1-5 which should fix this bug.
If you are running 2.1-4 and didn’t get auto-upgraded you may want to do a manual update.
We’ll start doing autoupgrades more widely once 2.1-5 is settled in a bit.

Tried to launch auto upgrade debian, piaware and got:
Sorry, we were unable to fetch the log for this site. Please try again later.
Noted log usually about half hour behind.
Checked /tmp/piaware/out, found:
12/17/2015 17:54:21 manual update (user-initiated via their flightaware control page) requested by adept server
12/17/2015 17:54:21 manualUpdate in adept config is enabled, allowing update
12/17/2015 17:54:21 performing manual update, action: packages
12/17/2015 17:54:21 *** attempting to upgrade raspbian packages to the latest
12/17/2015 17:54:21 *** running command ‘apt-get --yes update’ and logging output
12/17/2015 17:54:21 *** error closing pipeline to command: E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily unavailable)
E: Unable to lock directory /var/lib/apt/lists/, continuing…
12/17/2015 17:54:21 *** running command ‘apt-get --yes upgrade’ and logging output
12/17/2015 17:55:34 > Reading package lists…
12/17/2015 17:55:34 > Fetched 7155 kB in 1min 13s (97.4 kB/s)
12/17/2015 17:55:34 242554 msgs recv’d from dump1090-mutab (88 in last 6m); 242546 msgs sent to FlightAware
12/17/2015 17:55:34 *** error closing pipeline to command: E: Problem renaming the file /var/cache/apt/pkgcache.bin.GoMeAa to /var/cache/apt/pkgcache.bin - rename (2: No such file or directory)
W: You may want to run apt-get update to correct these problems, continuing…
12/17/2015 17:55:34 update request complete
12/17/2015 17:55:34 *** running command ‘apt-get --yes upgrade’ and logging output
12/17/2015 17:55:34 *** error closing pipeline to command: E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?, continuing…
12/17/2015 17:55:34 update request complete

Upgrade did not appear to proceed.
SSH’ed to pi, ran apt-get update/ apt-get upgrade which worked.
Piaware remainded at 2.1…3

Launched piaware upgrade from FA page, received :
Sorry, we were unable to fetch the log for this site. Please try again later.
However, /tmp/piaware.out shows piaware upgrade request executed successfully and now at 2.1.5

No idea why apt-get upgrade did not complete from FA launch.
Curiouser and curiouser.

Autoupdate to 2.1.5 on both devices and it seems to work now and starts itself after a reboot.