Java memory in MB

[starfire]

Strange, have this Variable 2 set to 1512 in the docker template yet my extenders are only reporting 768MB ?

Docker image is the latest, no errors in the unRAID logs for the docker.

Any ideas how to troubleshoot ?

[stuckless]

Originally Posted by starfire

Strange, have this Variable 2 set to 1512 in the docker template yet my extenders are only reporting 768MB ?

Docker image is the latest, no errors in the unRAID logs for the docker.

Any ideas how to troubleshoot ?

I could be that this broke during the last round of updates... I'll have to verify this in my dev environment... I typically don't set the memory option for testing, but I'll set it to 1512 and see what happens. I would expect that when you go into System Information it should show the current and max memory.

[Taddeusz]

Mine is working fine. Make sure the variable you're setting is called "JAVA_MEM_MB".

[stuckless]

Originally Posted by Taddeusz

Mine is working fine. Make sure the variable you're setting is called "JAVA_MEM_MB".

And the value that you set (if I recall) should just be a number, like 1512 and not 1512m.

Thanks for checking this.

[EnterNoEscape]

Originally Posted by stuckless

And the value that you set (if I recall) should just be a number, like 1512 and not 1512m.

Thanks for checking this.

I can say this variable only worked for me when I first added the docker container. Changes thereafter have not actually changed the value reported by SageTV.

Take a look at line #106 in https://github.com/stuckless/sagetv-...upgrade-sagetv. If SageTV is at the latest version, the script exits immediately and never gets to line #124 to update sagesettings.

[stuckless]

Originally Posted by EnterNoEscape

I can say this variable only worked for me when I first added the docker container. Changes thereafter have not actually changed the value reported by SageTV.

Take a look at line #106 in https://github.com/stuckless/sagetv-...upgrade-sagetv. If SageTV is at the latest version, the script exits immediately and never gets to line #124 to update sagesettings.

Yeah, that's what I was wondering... That script used to be different... before I restructured all the init scripts... previously it would install gentuner, comskip, and do all those operations every time. I need to adjust this script so that the license data and mem options happen every time. Thanks for pointing that out.

[Taddeusz]

Until that change is made it's honestly not that difficult to remove the SageTV docker container and then re-add it using either the "my-stuckless-sagetv-server-java8" or "my-stuckless-sagetv-server-java7" template, depending on whether you're using Java 7 or 8.

No data is lost by removing and re-adding the container.

[starfire]

Originally Posted by EnterNoEscape

Take a look at line #106 in https://github.com/stuckless/sagetv-...upgrade-sagetv. If SageTV is at the latest version, the script exits immediately and never gets to line #124 to update sagesettings.

Aha, I have a version set for Sage so it doesn't get updated on a restart so that would explain why the Java value is not being set.

I'll wait for an update of the Docker template from stuckless.

Thanks.

[stuckless]

I've pushed out an update to the SageTV images... it includes the fix for the memory so that it's set every time (not just on an upgrade) and it includes a small fix to the user-script provided by EnterNoEscape (thanks)... So unless you are affected by either of these things, there is no rush to update your unRAID container.

[starfire]

Thanks, updated and now have the correct Java heap size