Docker Containers updated to 1.0.4

[stuckless]

Originally Posted by Taddeusz

After having to do a hard reboot last night and going through a parity check I'm back on Java 8. Just tried Placeshifter from work and the login screen looks normal again.

That is a bizarre side effect of moving to Java 10... just wonder if perhaps if you tried Java 10 again, if it would work... ie, maybe the hard lockup and the corrupt placeshifter screen were symtomatic of some other memory corruption, and not really specific to Java 10.

[Taddeusz]

Originally Posted by stuckless

That is a bizarre side effect of moving to Java 10... just wonder if perhaps if you tried Java 10 again, if it would work... ie, maybe the hard lockup and the corrupt placeshifter screen were symtomatic of some other memory corruption, and not really specific to Java 10.

I'm running some movies through MKVToolNix and I'll try some different things after that's complete.

[Taddeusz]

Originally Posted by stuckless

That is a bizarre side effect of moving to Java 10... just wonder if perhaps if you tried Java 10 again, if it would work... ie, maybe the hard lockup and the corrupt placeshifter screen were symtomatic of some other memory corruption, and not really specific to Java 10.

It is weird.

I have both Java 8 and 10 versions installed so I can alternate between them on the same configuration. I was using Gemstone, which loaded fine using 10. I went back to the default STV and it also seems to work fine. It's just the login screen that gets garbled. I can actually enter my username and password even though it looks wrong on the screen. Can't imagine what is causing it to do that on just that screen.

[Tiki]

Originally Posted by Taddeusz

It is weird.

I have both Java 8 and 10 versions installed so I can alternate between them on the same configuration. I was using Gemstone, which loaded fine using 10. I went back to the default STV and it also seems to work fine. It's just the login screen that gets garbled. I can actually enter my username and password even though it looks wrong on the screen. Can't imagine what is causing it to do that on just that screen.

Could it be some cached file that was corrupted?

[AzJazz]

Originally Posted by stuckless

how did you install the docker sagetv to begin with? I suspect the upgrade process would be similar. As for the finding it... not sure why the search didn't work, but it is there

https://hub.docker.com/r/stuckless/sagetv-server-java8/
https://hub.docker.com/r/stuckless/sagetv-server-java9/
https://hub.docker.com/r/stuckless/s...server-java10/

I figured out why I'm not seeing them on my QNAP - Their Docker container search database must be updating at a slow rate. I don't know when they will show up on the QNAP search. So far, I haven't found an easy way to do an upgrade on an existing container on the QNAP, or to install a container without using the QNAP search function.

Oh, well - What I have now works pretty nicely, so maybe it's a signal that I shouldn't be doing an update?

[GBGB]

You may need to update the cacerts file in JVM in the Dockers? I found that i was unable to connect to Scheduled Direct with out updating the certificates. I was getting an "Unable to connect to Schedules Direct" Error message.

log file:
Sun 7/18 14:11:26.967 [EPG@293057b4] SDEPG Exception thrown: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Sun 7/18 14:11:26.968 [EPG@293057b4] javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Sun 7/18 14:11:26.969 [EPG@293057b4] at java.base/sun.security.ssl.Alerts.getSSLException(Alerts.java:198)

[glenner]

Hey all, I took the plunge and updated all my dockers today including my stuckless-sagetv-server-java8 docker container. Since the sage docker has restarted, I can no longer connect to it using any of my HD300s, or placeshifter. They just don’t connect. I get a black screen on my HD300. On the placeshifter, I get: "The SageTV Placeshifter is unable to connect to the specified SageTV Media Center Server..."

As best as I can tell, the server is up. I can connect to Jetty webserver, and BMT... With Jetty, I can see my recordings, EPG, schedule, etc.

Does anyone have any ideas on what I can try to debug? I've updated the sagetv container before without issue.

[KeithAbbott]

Originally Posted by glenner

Hey all, I took the plunge and updated all my dockers today including my stuckless-sagetv-server-java8 docker container. Since the sage docker has restarted, I can no longer connect to it using any of my HD300s, or placeshifter. They just does not connect. I get a black screen on my HD300. On the placeshifter, I get: "The SageTV Placeshifter is unable to connect to the specified SageTV Media Center Server..."

As best as I can tell, the server is up. I can connect to Jetty webserver , and BMT... With Jetty, I can see my recordings, EPG, schedule, etc.

Does anyone have any ideas on what I can try to debug? I've updated the sagetv container before without issue.

You might want to take a look at this thread: https://forums.sagetv.com/forums/showthread.php?t=66735

[glenner]

Yes… Thanks! I had found that thread after I posted and have since upgraded to stuckless-sagetv-server-java16. This seems to have fixed all my issues… I’ll test for a while and see if anything is amiss… Thanks!

[KeithAbbott]

Originally Posted by glenner

Yes… Thanks! I had found that thread after I posted and have since upgraded to stuckless-sagetv-server-java16. This seems to have fixed all my issues… I’ll test for a while and see if anything is amiss… Thanks!

I tried the upgrade this morning from stuckless-sagetv-server-java8 to stuckless-sagetv-server-java16. Most of the pages in the SageTV Web Interface worked fine, except for one very important one: the Home page. So I downgraded to stuckless-sagetv-server-java11, and the Home page seems to be working just fine. For now, I'm sticking with the stuckless-sagetv-server-java11 docker.

[glenner]

Originally Posted by KeithAbbott

I tried the upgrade this morning from stuckless-sagetv-server-java8 to stuckless-sagetv-server-java16. Most of the pages in the SageTV Web Interface worked fine, except for one very important one: the Home page. So I downgraded to stuckless-sagetv-server-java11, and the Home page seems to be working just fine. For now, I'm sticking with the stuckless-sagetv-server-java11 docker.

Thanks. I've also switched to java11 and the home page on the SageTV webUI seems to be working again. Odd... I'll also stick with 11 for now and see how it goes.