SageTV Docker not working

[ptaylor]

So, I just moved my docker install to my cache drive, and now my SageTV docker won't start, though the openDCT docker seems okay.

I even deleted the docker container and re-downloaded the image and I'm still getting the same failure.

Here is the log, any ideas?

*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
*** Running /etc/my_init.d/10-adduser...
*** Running /etc/my_init.d/20-upgrade-sagetv...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
SageTV Home: /opt/sagetv/server
SageTV Already At Version: 9.1.2.662, exiting...

*** Running /etc/my_init.d/25-add-license...
*** Running /etc/my_init.d/25-update-memory...
Updating Java Mem
*** Running /etc/my_init.d/25-upgrade-commandir...
*** Running /etc/my_init.d/25-upgrade-comskip...
Comskip already installed
*** Running /etc/my_init.d/25-upgrade-gentuner...
Generic Tuner Plugin already installed
*** Running /etc/my_init.d/30-setperms...
changed ownership of '/var/run' from root:root to root:sagetv
mode of '/var/run/' changed from 0755 (rwxr-xr-x) to 0775 (rwxrwxr-x)
mode of '/bin/mountpoint' changed from 0755 (rwxr-xr-x) to 4755 (rwsr-xr-x)
*** Running /etc/my_init.d/40-lirc...
changed ownership of '/usr/bin/irsend' from root:root to root:sagetv
mode of '/usr/bin/irsend' changed from 0755 (rwxr-xr-x) to 4755 (rwsr-xr-x)
*** Running /etc/my_init.d/85-user-script...
*** Running /etc/my_init.d/90-sagetv...
Changing to SageTV directory /opt/sagetv/server
cat: activkey: No such file or directory
Executing pre-scripts
*** Running /etc/my_init.d/95-jstatd...
JSTATD Remote Java Debugging is disabled.
*** Running /etc/my_init.d/99-zmessage...

************************************************
SageTV unRAID/Docker (Container Version: 1.0.2) is running

If this is your first time, install the Windows/Mac/Linux Placeshifter or the Android MiniClient and complete the configuration
Setting up tuners, scheduling recordings, installing plugins, etc, requires using the Placeshifter or MiniClient
To gain browser access, install the Jetty WebServer Plugin
- The SageTV Team -
*** Running /etc/rc.local...
*** Booting runit daemon...
*** Runit started as PID 87
./startsagecore: line 36: syntax error in conditional expression: unexpected token `;'

./startsagecore: line 36: syntax error near `;'

./startsagecore: line 36: `if [[ "$JAVA_VERSION" == "8" || "$JAVA_VERSION" == "9"]] ; then'
May 31 00:59:15 Tower syslog-ng[98]: syslog-ng starting up; version='3.5.6'

[EnterNoEscape]

This was noticed very early and a fix was pushed, but a new release with the fix should be forthcoming sometime tomorrow. To fix this right now, edit startsagecore using a program like Notepad++ if you're using Windows.

Change line 36 from:

if [[ "$JAVA_VERSION" == "8" || "$JAVA_VERSION" == "9"]] ; then

to

if [[ "$JAVA_VERSION" == "8" || "$JAVA_VERSION" == "9" ]] ; then

Note the space that was added at the end between the " and the ]] ;.

Edit: For anyone interested, there is a pull request for the fix. As you might guess this does not affect Windows at all, so do not expect another Windows release.

[dstanley]

Thank you - this one bit me too!

Dwight

[MacDaddy]

Yeppers. Went down at 5am for the appdata backup and never came back. Thanks for the quick patch. Will await the container update.

[Fuzzy]

Originally Posted by MacDaddy

Yeppers. Went down at 5am for the appdata backup and never came back. Thanks for the quick patch. Will await the container update.

Pretty sure the fix is out there already, so you should be able to just restart your container and it'll be up and running just fine now.

[MacDaddy]

The fix is in. Thanks.

[ptaylor]

Just started it up and it came up with no issues. Thanks!

[HuMan321]

Does everyone need to take action? Basketball set to record and not home
Thoughts?

[ptaylor]

You are probably fine unless you have your docker stop and restart at some regular interval, like 3 AM every night for a backup of your appdata folder.

[HuMan321]

I do not at this time
Thank you

[wayner]

Everything should be fine now if you restart your Docker. I just did this and I am on version 9.1.3.668 with no issues - at least not as far as I see.