Sage TV Docker Not Running Sage?

[Striker:WG]

So, I've been messing around with getting Sage working in an Unraid Docker. Just got my Firewire card working, and things were moving along.

It's happened twice now where I had to restart my docker container and then Sage just wouldn't start. The container comes up and I can work with the file system through the console, but Sage itself doesn't startup.

The first time this happened, I deleted the docker, removed the trace files from the appdata folder and started fresh. My fresh start didn't go well as it refused to let me install the Jetty web server claiming I was missing the Ant dependency jar, but I couldn't find a way to install it through the plugin manager. I tried manually copying it in, but then the container started refusing to work again.

Has anyone else run into issues like this? I'm still pretty new to Unraid, Dockers, and even Linux, so forgive my n00b questions, but how does one go about troubleshooting this?

Thanks for any advice offered!

[Striker:WG]

OK, so I'm not sure what changed, but after restarting the docker container AGAIN, Sage did come up.

Still not able to install the Jetty web server though.

How does one go about getting the Ant 1.8.2+ dependency jar installed and registered?

Thanks!

[Striker:WG]

Hooray! My ANT+ plugin issue was resolved.

Going back to the original issue in this thread, it appears to be a very long startup time for the docker container. Probably about 7 minutes.

My UNRAID server is an older 3rd generation i7 /w 36GB DDR3 RAM, so it's not the fastest thing around, but its no slouch either.

Is this just a normal startup time?

[stuckless]

If you look at the docker startup scripts for sagetv on unRAID it runs a few scripts. But, I suspect this is the one that is causing your delay

https://github.com/stuckless/sagetv-....d/30-setperms

This script will set the sagetv permissions on all files before allowing sagetv to start. So if you have lots of media files this could take some time.

It appears that if you set the OPT_SETPERMS to N it will skip it.

[Striker:WG]

Thanks! It does seem to be starting up a lot faster now. About 1 minute or less!

[EnterNoEscape]

I wanted to share when I had a similar issue, it was because my cache drive was starting to fail. Just something else to check on if anyone finds this thread in the future.