SageTV Server Linux with Comskip for Docker (and unRAID) Support Thread

[BobbyDing]

Hi. Having issue accessing Jetty. This is the java 8 docker. I get the login window to enter my username/password, but only get the following error (full error in attachment):

Problem accessing /apps/. Reason:

PWC6033: Unable to compile class for JSP

PWC6199: Generated servlet error:
The type java.util.Comparator cannot be resolved. It is indirectly referenced from required .class files

The Jetty plugin lists BMT, SageTV Web Interface, sagex api and upnp as dependent services if that makes any difference.

Any ideas?

Thanks,

Bobby
.

[alfi33]

The http://<IP>:<PORT>/apps/ page does not work with Java 8.

If you want the /apps/ page to work, you'll need to use Java 7.

[BobbyDing]

Ah, OK. Yes, the direct links are working. Thank You!

[m1k3g]

Originally Posted by jorryn

I was able to get it running on Synology. You will need the latest release version of Docker installed in order to do the Docker Host networking, Synology just updated it a few days ago. To use the Docker Host there is a check box at the bottom of the Port Settings tab. I'm having a bit of an issue where comskip isn't processing the recordings however everything else seems to be working. It finds my HDHomerun tuners as well.

Docker Version 1.11.1-0265
DSM 6.0.1-7393

Hey thanks for that info! I've played around with the net=host and of course it never worked. I'm on DSM 5.2 so I'll have to upgrade to 6 at some point to get this working, it looks like. Since I'm running Xpenology rather than Synology software, it'll probably be awhile before I can do that. May try just upgrading the Docker package only first.

Thanks again.

[BobbyDing]

Apologies if this is something simple. I'm not software oriented. How would I go about editing the sage.properties file in the docker image? I won't let me save any changes to \\TOWER\apps\sagetv\server.

[stuckless]

Originally Posted by BobbyDing

Apologies if this is something simple. I'm not software oriented. How would I go about editing the sage.properties file in the docker image? I won't let me save any changes to \\TOWER\apps\sagetv\server.

It might not be quite so simple Because I took some shortcuts getting this setup, the contain runs as "root" (or Administrator for you windows folks). Then means that files that sagetv creates/modifies will pick up the ownership and permissions of "root".

In my case, I have to ssh to the box the edit the files using vi. (that is not user friendly).

You could probably ftp to your server, using the "root" username/password, and then upload a new file to overwrite the existing one... that's probably the easist approach until I create a container that runs as user "nobody" (which is the default for unraid).

[SomeWhatLost]

I have just been ssh'ing into the box and chmod 777 {filename} things that I need to edit...
not sure what 777 means, but looking at some linuxy docs online it seemed like the thing to do?
seems to work well at least...

[EnterNoEscape]

Originally Posted by stuckless

You could probably ftp to your server, using the "root" username/password, and then upload a new file to overwrite the existing one... that's probably the easist approach until I create a container that runs as user "nobody" (which is the default for unraid).

If you're a Windows user, WinSCP will help you out here. You'll still need to log in as root. You can directly open the file via WinSCP, edit it, when you save it, WinSCP will upload the the changes for you.

[EnterNoEscape]

Originally Posted by SomeWhatLost

I have just been ssh'ing into the box and chmod 777 {filename} things that I need to edit...
not sure what 777 means, but looking at some linuxy docs online it seemed like the thing to do?
seems to work well at least...

chmod 777 basically means anyone can read/write/execute the file/files you have applied this permissions mask to. Sometimes this is desirable, usually it's not. I recommend either using the root account or sudo to edit files owned by root. Changing file permissions to edit a file it is usually reserved for files that contain passwords and then you need to change everything back when you're done. Most other cases, sudo vi will be sufficient. If you're a Windows user and don't want to learn how insert, write and quit in vi, WinSCP should be the next best thing.

[BobbyDing]

Thanks all! I'll try the different methods to see which works best for me.

Just wondering, could an addition be made to the docker template to load a particular sage.properties file when you save/start (whatever the terminology is) the image in Docker?

Bobby

[stuckless]

Originally Posted by BobbyDing

Thanks all! I'll try the different methods to see which works best for me.

Just wondering, could an addition be made to the docker template to load a particular sage.properties file when you save/start (whatever the terminology is) the image in Docker?

Bobby

Not 100% what you are asking, to be honest. Why would you want/need to use a separate Sage.properties, other than the one that is in the Sage install area?

[BobPhoenix]

I've been used the editor in MidnightCommander (MC) on unRAID to edit the SageTV properties of the docker.

[BobbyDing]

Originally Posted by BobPhoenix

I've been used the editor in MidnightCommander (MC) on unRAID to edit the SageTV properties of the docker.

Thanks, I'll try that.
.

[BobbyDing]

Originally Posted by stuckless

Not 100% what you are asking, to be honest. Why would you want/need to use a separate Sage.properties, other than the one that is in the Sage install area?

.
I was just thinking folks could make the changes that they need to the sage.properties, save that file externally from the image, then when you select "edit" from the drop down menu, you'd have the option of pulling in the newly modified properties file to replace the old one when saving/restarting the image. It was just a thought to get around the root file restrictions you mentioned and mostly my lack of linux knowledge. But please disregard. I'll try the methods listed above.
.
Thanks for all you do here!

[BobbyDing]

Originally Posted by BobPhoenix

I've been used the editor in MidnightCommander (MC) on unRAID to edit the SageTV properties of the docker.

MC works great via putty. I have found sage files in several locations under /mnt. /disk1, /user & /user0. But gain my lack of linux knowledge is biting my butt. Do I edit the properties file in any of these? Or in one location in particular? Or somewhere else?

Thanks

[starfire]

On unRAID typically you should edit file under /mnt/user and not any specific disk share unless that's what you want.

See http://lime-technology.com/forum/ind...?topic=27285.0

[stanger89]

Originally Posted by BobbyDing

.
I was just thinking folks could make the changes that they need to the sage.properties, save that file externally from the image, then when you select "edit" from the drop down menu, you'd have the option of pulling in the newly modified properties file to replace the old one when saving/restarting the image. It was just a thought to get around the root file restrictions you mentioned and mostly my lack of linux knowledge. But please disregard. I'll try the methods listed above.
.
Thanks for all you do here!

The whole Sage install (sage.properties and all AFAIK) is external to the docker image. You can blow away your docker image, re-add the Sage, and you won't have to reconfigure anything.

The problem with file restrictions isn't due to the file being in the docker image, it's due to the user that was chosen for Sage to run as.

[BobbyDing]

I'm making progress. Thanks everybody!!!!

[stuckless]

I've updated the SageTV Docker container to run as a normal user... that means when sagetv records files, or modifies files, etc, it should be set to user nobody with group users. This should fix the permissions issues.

I'm still testing this out on my server, since I need to still access the video devices and the tuning device... so far it seems to be working, though.

If you don't get the option to update, you can do into the Dockers section and force an update.

[stanger89]

Do we have to blow away the docker and re-add it? I'm still on unraid 6.1.7 and I don't see an update. Or does just restarting the docker (which seems to have updated Sage) do it?



I'm also having trouble getting my import dirs to "work". I can successfully browse to them as samba shares, and that all works well, but when Sage goes to scan them, it finds nothing, this is all I see in the log:

Sun 7/3 10:35:23.042 [LibraryImporter@6f683bdf] Checking video directories for new files
Sun 7/3 10:35:23.542 [LibraryImporter@6f683bdf] Seeker is starting the library import scan...
Sun 7/3 10:35:23.543 [LibraryImporter@6f683bdf] Starting to scan lib import root: /tmp/sagetv_shares/unraid/blu-ray
Sun 7/3 10:35:23.573 [LibraryImporter@6f683bdf] Starting to scan lib import root: /tmp/sagetv_shares/unraid/tv
Sun 7/3 10:35:23.603 [LibraryImporter@6f683bdf] Starting to scan lib import root: /tmp/sagetv_shares/unraid/media/Processed Pics
Sun 7/3 10:35:23.603 [LibraryImporter@6f683bdf] Skipping import directory because it's offline: /tmp/sagetv_shares/unraid/media/Processed Pics
Sun 7/3 10:35:23.603 [LibraryImporter@6f683bdf] Seeker has finished the library import scan.
S