SageTV 7.0 Linux Upgrade - Non Debian

[bcjenkins]

I am wondering if anyone has an upgrade script sorted out which supports the tarball install on Linux? I am having an issue with plugins setting up correctly and have to uninstall and reinstall.

B

[stuckless]

I looked at doing something like this awhile ago... now I just nuke everything and start over with each install

[bcjenkins]

I think I am going to use rsync and see if I can make that work. Right now I am just cp'ing files, but I am missing things.

B

[stuckless]

Be sure to share, if you create anything

[Motofreak75]

Maybe i'm doing it wrong, but for the but 9 months I have just backed up the entire sagetv server folder and then downloading the tar file in the server folder and unpacking it, and editing the sagecore file for java path and heap size and then just used ./startsage without removing or reinstalling any plug-ins.

I have yet to see anything go wrong but I still back up the entire directory first.

[bcjenkins]

Interesting. I will try that the next time around. Use the sagesettings to store files.

B

Edit: I meant sagesettings for config information. Thanks for clarifying Jeff

[Narflex]

I just use the sagesettings to store my config-specific settings and then unpack the tarball on top of my /opt/sagetv/server folder each time I upgrade. And I have no issues. The only thing it won't catch is if we remove things from the install...but the only time that was ever an issue was when we change the name of the default theme in V7.

I also use the 'presage' scripts to do other things like copy a customer firewire tuner .so (my server doesn't have the required dependencies for the one we bundle with our linux installer); and also create a 'restart' file so that the server process will automatically restart itself if for some reason it dies (not that I need that anymore; it was mainly for early beta testing stages before we go public when things aren't as stable).

[stuckless]

Originally Posted by Narflex

I just use the sagesettings to store my config-specific settings and then unpack the tarball on top of my /opt/sagetv/server folder each time I upgrade. And I have no issues. The only thing it won't catch is if we remove things from the install...but the only time that was ever an issue was when we change the name of the default theme in V7.

I also use the 'presage' scripts to do other things like copy a customer firewire tuner .so (my server doesn't have the required dependencies for the one we bundle with our linux installer); and also create a 'restart' file so that the server process will automatically restart itself if for some reason it dies (not that I need that anymore; it was mainly for early beta testing stages before we go public when things aren't as stable).

I wasn't aware of the 'presage' scripts, so that's good to know as well. I'll try the unzip and overwrite method and see what happens from now on. Btw, when I install from the .deb, does it remove the previous install, or does it simply extract over the current install?

[bcjenkins]

Clearly I have been doing this the harder way..

I guess my new upgrade script will be:

1. Download Upgrade from $2 url
2. execute $1/stopsage
3. tar the current directory
4. untar the upgrade into the directory
5. execute $1/startsage
6. Grab some and watch TV

B

[stuckless]

Originally Posted by bcjenkins

Clearly I have been doing this the harder way..

I guess my new upgrade script will be:

1. Download Upgrade from $2 url
2. execute $1/stopsage
3. tar the current directory
4. untar the upgrade into the directory
5. execute $1/startsage
6. Grab some and watch TV

B

It's sad that the first thing that entered my mind was, "why is he paying 2 dollars for the url?".... And it's not like I don't live in a command shell

EDIT: btw, if you have a simple script that does that... then post it.. it'll be handy to use. I tend to just do it manually.

[bastafidli]

What I am doing is

1. rm /opt/sagetv/server
2. cp /opt/sagetv/server_7.x.old /opt/sagetv/server_7.x.new
3. untar xx.tar to /opt/sagetv/server_7.x.new
4. ln /opt/sagetv/server_7.x.new /opt/sagetv/server

This way I am always using /opt/sagetv/server as my current sagetv install and have backups to switch to immediately if somethind doesn't work.

The only issue with this is that SageTV is detecting the current page as the absolute path /opt/sagetv/server_7.x.new rather than the logical path from where it is started /opt/sagetv/server. What this leads to is that from time to time I have to go and edit the properties and remove the version numbers from the paths stored there.

Long time ago I have reported it as a bug for Linux version but must have fallen through the cracks.

[bcjenkins]

Originally Posted by stuckless

"why is he paying 2 dollars for the url?"

I always buy my download links on Ebay.

I will post something later after I engineer something overly complex.

B

[drewg]

Originally Posted by bastafidli

The only issue with this is that SageTV is detecting the current page as the absolute path /opt/sagetv/server_7.x.new rather than the logical path from where it is started /opt/sagetv/server. What this leads to is that from time to time I have to go and edit the properties and remove the version numbers from the paths stored there.

Long time ago I have reported it as a bug for Linux version but must have fallen through the cracks.

This really isn't so much a bug in sagetv, its more just how *nix works. There are 2 ways to obtain the current working directory -- the $PWD environment variable maintained by the shell, and the getcwd system call. Typically, the shell will maintain $PWD via the path you took to some directory (so it will say /opt/sagetv/server), but the getcwd syscall will contain the real path (/opt/sagetv.7.x/server).

That said, this could be fixed in sagetv if there was a sage_config_path or something where you could specify the path to the sage configuration. Then you could plug in the symlink path..

Drew

[bcjenkins]

Originally Posted by stuckless

btw, if you have a simple script that does that... then post it.. it'll be handy to use. I tend to just do it manually.

I just created this, this morning and tested the steps but won't use it until next release as my update has been running a few days already.

B

#!/bin/bash
# ©2010 Brandon Jenkins
# SageTV Upgrade Script - Version .1 BETA
# USE AT YOUR OWN RISK! Backup all your data!
# To use this script place it in a file called sagetv_upgrade.sh
# Execute "chmod +x sagetv_upgrade.sh"
# ./sagetv_upgrade.sh URL_TO_DOWNLOAD PATH_TO_SAGETV 
# The PATH_TO_SAGETV is not needed if SageTV is installed to the default path
# This script will default to /opt/sagetv/server

# Setting up application variables
SAGETV_HOME=/opt/sagetv/server
if [[ $2 ]]; then SAGETV_HOME=$2; fi
SAGETV_URL=$1
SAGETV_FILE=$(echo $SAGETV_URL | cut -d "/" -f $(expr $(echo $SAGETV_URL | grep -o "/" | wc -l) + 1))
SAGETV_BACKUP_PATH=$(echo $SAGETV_HOME |cut -d "/" -f -$(echo $SAGETV_HOME | grep -o "/" |wc -l))
#SAGETV_BACKUP_PATH=/opt/sagetv #Optional set hard path

# Download the file
if [[ ! $SAGETV_URL == "" ]]; then
  wget -O $SAGETV_BACKUP_PATH/$SAGETV_FILE $SAGETV_URL
  tar -tf $SAGETV_BACKUP_PATH/$SAGETV_FILE 2>/dev/null 1>/dev/null
  if [[ ! $? -eq 0 ]]; then
    echo "The download did not complete successfully. Aborting!"
    exit 1
  fi
else
  echo "Usage: Please provide a valid URL for the download. Eg. sagetv_upgrade.sh http://download.sage.tv/linuxbeta/server_7.0.16.tar.gz"
  exit 1
fi

#Stop SageTV and make sure it is dead :)
PIDFILE=/var/run/sagetv.pid
if [ -e $SAGETV_HOME/sagesettings ]; then . $SAGETV_HOME/sagesettings; fi
if [ -e $PIDFILE ]; then
  while [[ $(ps -f --pid $(cat $PIDFILE) | grep Sage.jar | grep -v grep) != "" ]]; do
    echo "Attempting to stop SageTV for upgrade"
    $SAGETV_HOME/stopsage
    #kill -9 $PIDFILE
  done
fi

# Backup the directory
tar -czf $SAGETV_BACKUP_PATH/server_$(date +%Y%m%d).tar.gz $SAGETV_HOME
if [[ ! $? -eq 0 ]]; then
  echo "The backup did not complete successfully. Aborting!"
  exit 1
fi

# Untar upgrade
cd $SAGETV_HOME
tar xzvf $SAGETV_BACKUP_PATH/$SAGETV_FILE
if [[ ! $? -eq 0 ]]; then
  echo "The installation did not complete successfully. Aborting!"
  exit 1
fi

# Start SageTV
$SAGETV_HOME/startsage

exit 0

[MrD]

Originally Posted by bcjenkins

Clearly I have been doing this the harder way..

I guess my new upgrade script will be:

1. Download Upgrade from $2 url
2. execute $1/stopsage
3. tar the current directory
4. untar the upgrade into the directory
5. execute $1/startsage
6. Grab some and watch TV

B

I think you can eliminate step 3 for efficiency Live on the edge!

[MrD]

Originally Posted by drewg

This really isn't so much a bug in sagetv, its more just how *nix works. There are 2 ways to obtain the current working directory -- the $PWD environment variable maintained by the shell, and the getcwd system call. Typically, the shell will maintain $PWD via the path you took to some directory (so it will say /opt/sagetv/server), but the getcwd syscall will contain the real path (/opt/sagetv.7.x/server).

That said, this could be fixed in sagetv if there was a sage_config_path or something where you could specify the path to the sage configuration. Then you could plug in the symlink path..

Drew

?

ROOT=`pwd`
echo $ROOT

[jpwegas]

Originally Posted by MrD

?

ROOT=`pwd`
echo $ROOT

Right, that returns the path that you cd'd to within the shell. But Drew's point is that if Sage is using the getcwd syscall then it gets the real path, which might be different and leads to the issue bastafidli described.

Example:

cd /tmp
mkdir foo
ln -s foo notfoo
cd foo
pwd
/tmp/foo
perl -e 'use Cwd; print getcwd . "\n";'
/tmp/foo
cd ../notfoo
pwd
/tmp/notfoo
perl -e 'use Cwd; print getcwd . "\n";'
/tmp/foo


--John

[bastafidli]

Correct, I think the solution is for the .startsage to pass the current working directory (the symlink one) to the Java code.

[bcjenkins]

The current version upgrade went off without a hitch with my super duper script. I have a nice tarball (not the BP kind) of the .16 version and an upgraded copy of SageTV.

Thanks for the pointer Jeff!

B