All times are UTC - 6 hours [ DST ]




Post new topic Reply to topic  [ 132 posts ]  Go to page Previous  1, 2, 3, 4, 5, 6
Author Message
 Post subject: Re: PiAware version 2 to version 3 upgrade
PostPosted: Wed Jul 05, 2017 8:12 am 
Online
FlightAware Staff
obj - FlightAware user avatar

Joined: Tue Sep 30, 2014 7:14 pm
Posts: 3672
The dependencies are related to the version of tcl that piaware (well, tcllauncher) was linked against during the build process. Rather than using the jessie packages, you could build from source on a wheezy system.

Reimaging is indeed a blunt instrument, but I can only realistically support a limited number of versions.
That usually means the latest sdcard version, and the latest package version on up to date Raspbian.

if you're on something else, you will need to diagnose any problems yourself.


Top
 Profile  
 
 Post subject: Re: PiAware version 2 to version 3 upgrade
PostPosted: Wed Jul 05, 2017 8:17 am 
Online
FlightAware Staff
obj - FlightAware user avatar

Joined: Tue Sep 30, 2014 7:14 pm
Posts: 3672
WhiteCitadel wrote:
Any idea why the website still says I am running 2.x package though? Where does it take this data from?

piaware reports its own version when it connects to the FA servers. It is reporting 2.1-5 so you still have that installed somewhere. That particular one has been connected continuously for almost a month.

The version of piaware has nothing to do with what you see on the local webmap; that map is driven entirely by dump1090.


Top
 Profile  
 
 Post subject: Re: PiAware version 2 to version 3 upgrade
PostPosted: Wed Jul 05, 2017 8:21 am 
Offline
FlightAware Member
abcd567 - FlightAware user avatar

Joined: Sat Feb 15, 2014 3:08 am
Posts: 2137
Location: Toronto CYYZ
WhiteCitadel wrote:
...Maybe I will be brave one day and "apt-get dist-upgrade" :wink:
GOOD LUCK! :wink:


Top
 Profile  
 
 Post subject: Re: PiAware version 2 to version 3 upgrade
PostPosted: Thu Jul 06, 2017 8:06 am 
Offline
WhiteCitadel - FlightAware user avatar

Joined: Tue Nov 17, 2015 10:36 am
Posts: 21
obj wrote:
The dependencies are related to the version of tcl that piaware (well, tcllauncher) was linked against during the build

process. Rather than using the jessie packages, you could build from source on a wheezy system.

I total missed that the source is of course on https://github.com/flightaware.

At this point having done more reading yesterday, I am waiting for the mac->ID transition version anyway, as at that point I can move to the new hardware I have planned. Will check 3.1 -> 3.5 release notes to see what I am missing.
obj wrote:
WhiteCitadel wrote:
Any idea why the website still says I am running 2.x package though? Where does it take this data from?


piaware reports its own version when it connects to the FA servers. It is reporting 2.1-5 so you still have that installed somewhere. That particular one has been connected continuously for almost a month.

Checking again:
Code:
$ dpkg -s piaware
Package: piaware
Status: install ok installed
...

$ piaware -v
3.1.0

All looks like 3.1 running locally.

Checking with PS I can see that piaware has been running since March 20th.

Trying to restart the service however is not working!

At some point it looks like the code change the PID location from /var/run/piaware/piaware.pid to /var/run/piaware.pid - but this has not handled the restart when piaware was updated so the 2.6 process was never killed (although service stop piaware reports success the process is still running)

Now I have manually killled the processes running, and started the service with "sudo service piaware start" I get a log file entry that 3.1 has started:
Code:
07/06/2017 12:27:52 creating pidfile /run/piaware/piaware.pid
07/06/2017 12:27:52 ****************************************************
07/06/2017 12:27:52 piaware version 3.1.0 is running, process ID 8463

Website now reports:
Code:
Feeder Check-In: a few seconds ago
Feeder Type: PiAware 3.1.0

So there you go - broken PID file change meant after upgrade however many months ago the old process was still running in memory as the PID was never killed!

At least that's that solved :D


Top
 Profile  
 
 Post subject: Re: PiAware version 2 to version 3 upgrade
PostPosted: Thu Jul 06, 2017 10:33 am 
Offline
FlightAware Member
abcd567 - FlightAware user avatar

Joined: Sat Feb 15, 2014 3:08 am
Posts: 2137
Location: Toronto CYYZ
WhiteCitadel wrote:
.....At least that's that solved :D

Wow! You are a Linux Guru.
If I face such a problem, I will not be able to resolve it, and will go for a fresh install. :)


Top
 Profile  
 
 Post subject: Re: PiAware version 2 to version 3 upgrade
PostPosted: Thu Jul 06, 2017 11:19 am 
Online
FlightAware Staff
obj - FlightAware user avatar

Joined: Tue Sep 30, 2014 7:14 pm
Posts: 3672
Yeah, the 2->3 transition requires manually killing the old process. This happens automatically if you do a remote-command-driven upgrade.


Top
 Profile  
 
 Post subject: Re: PiAware version 2 to version 3 upgrade
PostPosted: Fri Jul 07, 2017 8:27 am 
Offline
WhiteCitadel - FlightAware user avatar

Joined: Tue Nov 17, 2015 10:36 am
Posts: 21
obj wrote:
Yeah, the 2->3 transition requires manually killing the old process. This happens automatically if you do a remote-command-driven upgrade.


It would help if these things were documented :(

But all solved now :D


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 132 posts ]  Go to page Previous  1, 2, 3, 4, 5, 6

All times are UTC - 6 hours [ DST ]


Who is online

Users browsing this forum: jluebbe, orellana and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  
cron