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

[Taddeusz]

Ok, different problem. I start to do the configuration wizard. It gets to the time zone screen and the selection area is empty.

[stuckless]

Originally Posted by Taddeusz

Ok, different problem. I start to do the configuration wizard. It gets to the time zone screen and the selection area is empty.

I've heard of people having this issue, not even with the unRAID version, but with sagetv in general. Try shutting down sagetv docker, then delete the clients directory (or back it up if you need it). And then start the container again, and see what happens.

[Taddeusz]

Originally Posted by stuckless

I've heard of people having this issue, not even with the unRAID version, but with sagetv in general. Try shutting down sagetv docker, then delete the clients directory (or back it up if you need it). And then start the container again, and see what happens.

That did not work. What I ended up doing was manually entering my timezone into the Sage.properties file. However, it appears the time is wrong when I connect now.

[Taddeusz]

Even though the Sage.properties file has time_zone=America/Chicago the detailed settings shows GMT as the selected time zone. Attempting to change it just brings up an empty dialog.

[stuckless]

Originally Posted by Taddeusz

Even though the Sage.properties file has time_zone=America/Chicago the detailed settings shows GMT as the selected time zone. Attempting to change it just brings up an empty dialog.

Out of curiousity is your timezone set on your unRAID machine correctly? Setting Date/Time. I see some dockers making reference to /dev/rtc (rtc being real time clock)... I wonder if I need to also utilize that as well. I'll have to do some research.

I do know that I haven't had any issues selecting the timezone on my server or in my local development area, which also uses the same docker images... but all my devices are set with the same timezone... EDT.

[Taddeusz]

Ok, originally I was attempting to use the Java 7 version since I use sagex to interface with Plex. I finally tried the Java 8 version and it works correctly. I'm not sure why there's a difference between the two packages. Something is preventing the Java 7 version from obtaining a list of available time zones.

[Taddeusz]

Originally Posted by stuckless

Out of curiousity is your timezone set on your unRAID machine correctly? Setting Date/Time. I see some dockers making reference to /dev/rtc (rtc being real time clock)... I wonder if I need to also utilize that as well. I'll have to do some research.

I do know that I haven't had any issues selecting the timezone on my server or in my local development area, which also uses the same docker images... but all my devices are set with the same timezone... EDT.

Yes, it is set correctly. Sorry, I didn't see this comment before I made my last post. Seems to be some sort of issue with the Java 7 version. I have the Java 8 version working now but of course sagex won't work.

[stuckless]

Originally Posted by Taddeusz

Yes, it is set correctly. Sorry, I didn't see this comment before I made my last post. Seems to be some sort of issue with the Java 7 version. I have the Java 8 version working now but of course sagex won't work.

sagex works in java 8... but the javascript services do not... so when you say sagex, do you mean the plex integration? (plex uses sagex javascript)

EDIT: Both of these use openjdk... I might change them to use the Oracle JDK, but, openjdk has been working fine for me since I created these... but I only use the java8 version.

[SomeWhatLost]

Originally Posted by Taddeusz

Yes, it is set correctly. Sorry, I didn't see this comment before I made my last post. Seems to be some sort of issue with the Java 7 version. I have the Java 8 version working now but of course sagex won't work.

fwiw, I had the same Timezone issue with Java7 sage, and it just works with Java8...

wonder whats causing it?

[Taddeusz]

I'm not that familiar with Docker and how it works but since I can build my own Sage.jar is there a way I can update it myself without having to wait for your official update? Also, how quickly do you update the SageTV docker after the codebase gets an update?

[Taddeusz]

Maybe it's just my test configuration but I'm having trouble with live comskip stopping mid recording. I have live_tv_retries=16 and standoff=8000000 and still have problems. Doing a single recording seems to work fine but any more than that seems to progressively make each one stop until there is only a single comskip process still running.

BTW, my current Windows server has 3 recording drives and is configured to optimize for bandwidth. It runs live comskip on all 4 HDHR tuners without breaking a sweat.

[alfi33]

Originally Posted by Taddeusz

Maybe it's just my test configuration but I'm having trouble with live comskip stopping mid recording. I have live_tv_retries=16 and standoff=8000000 and still have problems. Doing a single recording seems to work fine but any more than that seems to progressively make each one stop until there is only a single comskip process still running.

BTW, my current Windows server has 3 recording drives and is configured to optimize for bandwidth. It runs live comskip on all 4 HDHR tuners without breaking a sweat.

I haven't had much luck with live Comskip in the Docker on unRAID either. From watching the unRAID logs, it looks like the Comskip process is crashing shortly after it starts running.

For me, it'll die with just a single recording going. It works fine if I have Comskip wait until the recording completes.

I had this issue on Windows too with some of the later Comskip builds.

[EnterNoEscape]

From what I've seen, if the file is zero length when it starts, it immediately fails. I had this problem when I used SageDCT with raw content since it returns immediately to SageTV before anything is actually being written, but it has created the file. It would be nice to have a configurable delay for live in the Comskip plugin. I wrote a Groovy script for SJQ that would wait until at least 5 minutes had passed or the recording was done/stopped; whichever comes first. Part of my logic there was if I'm channel surfing, I really didn't want it to kick off right away.

[stuckless]

Originally Posted by Taddeusz

I'm not that familiar with Docker and how it works but since I can build my own Sage.jar is there a way I can update it myself without having to wait for your official update? Also, how quickly do you update the SageTV docker after the codebase gets an update?

The Docker contain maps /opt/sagetv to some location where you've specified... likely, /mnt/user/appdata/sagetv/. So the everything related to sagetv is stored outside the container itself, and stored in a location that you can access.

Under the sagetv/ folder is the "server" directory that contains the entire sagetv install, including the Sage.jar, wiz.bin, etc. So, you can simply replace that Sage.jar with your own, and restart the docker container for sagetv. As of the latest image update, all those files should be owned by the default user/group 99/100 which means that if you exposed the appdata share, then you can simply browse to it using windows explorer, and then edit/copy the files that way.

The installation/upgrading of sagetv is done automatically on a container restart. So, if there is a new SageTV build, and you restart the container, you'll get it immediately.

Originally Posted by Taddeusz

Maybe it's just my test configuration but I'm having trouble with live comskip stopping mid recording. I have live_tv_retries=16 and standoff=8000000 and still have problems. Doing a single recording seems to work fine but any more than that seems to progressively make each one stop until there is only a single comskip process still running.

BTW, my current Windows server has 3 recording drives and is configured to optimize for bandwidth. It runs live comskip on all 4 HDHR tuners without breaking a sweat.

The configuration for comskip is in /mnt/user/appdata/sagetv/comskip. The comskip.ini that is in that folder didn't use to have the comskip livetv flag set... Maybe check the comskip.ini file in that directory and see if the settings are correct for you. I don't notice anything odd, myself, but I only have 2 tuners, and I never use livetv.

[alfi33]

I probably need to play with the settings in the ini file some more, but I'm sure I had live_tv set to 1...and I'm pretty sure I configured it to wait a few minutes before processing. But no luck yet unless I wait for the recording to finish.

Originally Posted by stuckless

I don't notice anything odd, myself, but I only have 2 tuners, and I never use livetv.

I'd be curious to know if anyone is successfully processing livetv with this version of comskip in the Docker.

[stanger89]

Along these lines, is it possible to configure it to run on liveTV, but then re-run after the recording is finished?

[Taddeusz]

I've raised live_tv_retries to 300 and standoff to 32000000 and I still can't get live tv detection to work. Not sure what would cause this. The logs don't have any apparent errors. It just seems to stop running.

[alfi33]

I see these Comskip related errors in the unRAID log:

Jul 15 13:07:27 Tower kernel: comskip[21926]: segfault at 0 ip 00002acd8900c638 sp 00007fff1953f7e0 error 4 in libc-2.23.so[2acd88f9e000+1c0000]

[BobPhoenix]

Originally Posted by alfi33

I see these Comskip related errors in the unRAID log:

Jul 15 13:07:27 Tower kernel: comskip[21926]: segfault at 0 ip 00002acd8900c638 sp 00007fff1953f7e0 error 4 in libc-2.23.so[2acd88f9e000+1c0000]

Been getting those myself. So far I've just ignored them. May have had a few videos without comskip info but haven't paid too much attention.

[alfi33]

Originally Posted by BobPhoenix

Been getting those myself. So far I've just ignored them. May have had a few videos without comskip info but haven't paid too much attention.

Are you processing live_tv or are you waiting for the recording to finish before starting Comskip processing?