Java Heap question

[Evil_Attorney]

Originally Posted by sacrament055

I was seeing a similar issue yesterday after having upgraded my client to the latest version and it turned out the Sage Client app didn't have proper permission to the REG keys so it was ignoring my change to max out the memory at 400h and my disabling of the sagetv demux.

I tried opening it as administrator and noticed it worked correctly then I changed reg permissions to give "everyone" full control and it works fine now without needing to open as administrator.

OK, I finally got mine working. Previously, I had set the "Frey Technologies" registry key to allow "everyone" full control. That didn't work, so today I tried setting the sub registry entry "SageTV" to allow "Users" full control. That seemed to do the trick, as JVM is at 1038. I think the installer needs to be tweaked to address this registry permission issue.

[thomaszoo]

I don't know if this helps, but I just looked at mine. My server is Win10 32 bit. Placeshifter (on a 64 bit PC) shows JVM at 1038. Running the client on the same 64 bit PC shows JVM at 779.

[SDeGonge]

Originally Posted by Evil_Attorney

OK, I finally got mine working. Previously, I had set the "Frey Technologies" registry key to allow "everyone" full control. That didn't work, so today I tried setting the sub registry entry "SageTV" to allow "Users" full control. That seemed to do the trick, as JVM is at 1038. I think the installer needs to be tweaked to address this registry permission issue.

This worked for me also.

Great job figuring this out

[jusjoken]

Originally Posted by thomaszoo

I don't know if this helps, but I just looked at mine. My server is Win10 32 bit. Placeshifter (on a 64 bit PC) shows JVM at 1038. Running the client on the same 64 bit PC shows JVM at 779.

Placeshifter reports the heap of the server where a local client reports it's own heap.

k

[Evil_Attorney]

I should add that my Sage service is logged in as my Windows user name, not a local account. My user account is an admin, so I would think that the "user" setting in the registry wouldn't matter, but I guess it does.

[sacrament055]

Originally Posted by jusjoken

What were you upgrading from/to?

k

I started on sage 7 with upgraded jar files and used the largest windows installer to upgrade.

[sacrament055]

Originally Posted by Evil_Attorney

I should add that my Sage service is logged in as my Windows user name, not a local account. My user account is an admin, so I would think that the "user" setting in the registry wouldn't matter, but I guess it does.

I had that issue as well. When I upgraded my server the service reset to local system and I had to move it back to my user account to get things working again.

[jusjoken]

Originally Posted by sacrament055

I had that issue as well. When I upgraded my server the service reset to local system and I had to move it back to my user account to get things working again.

That issue is corrected in 9.0.13...R1.010 so if you used that version let me know as it should no longer change the service settings on an upgrade.

k

[jusjoken]

Originally Posted by Evil_Attorney

OK, I finally got mine working. Previously, I had set the "Frey Technologies" registry key to allow "everyone" full control. That didn't work, so today I tried setting the sub registry entry "SageTV" to allow "Users" full control. That seemed to do the trick, as JVM is at 1038. I think the installer needs to be tweaked to address this registry permission issue.

This is now - hopefully - fixed in the latest installer that is uploading tonight. Same version of SageTV 9.0.13.536 but the installer is now at R1.011 which should fix this registry issue.

k

[jgsouthard]

Originally Posted by jusjoken

This is now - hopefully - fixed in the latest installer that is uploading tonight. Same version of SageTV 9.0.13.536 but the installer is now at R1.011 which should fix this registry issue.

k

Thanks! It looks like I upgraded from v7 to v9 two days too early. The fix was easy for me - just a registry edit with no permission changes involved - but from the comments it looks like this will help significantly with the upgrade process.

[Evil_Attorney]

Originally Posted by jusjoken

This is now - hopefully - fixed in the latest installer that is uploading tonight. Same version of SageTV 9.0.13.536 but the installer is now at R1.011 which should fix this registry issue.

k

Your work on this (along with everyone else's) is much appreciated!

[SDeGonge]

FYI - Just ran into another issue with the heap. For days now I've been running with the heap set to 400h on Windows 10. Today when I attempted to start the SageTV client I got the following message...

"Java Missing. Could not create JVM. Please reinstall Java Runtime Environment 1.4"

Odd that it all of a sudden started failing.

I reduced the heap to 399h and was able to start up without any problems.

[JREkiwi]

One issue is that the Java heap requires the specified size in contiguous memory. Depending on what else is running, you could have a large amount of available memory, but not have a block of 1024MB available.

John

[btrcp2000]

Raising this thread from the dead to ask if any of you are using this info to run Gemstone and multiple Android clients from a windows server?

[wayner]

How many mini-clients are you trying to run simultaneously? You can and should set JVM heap size to 1GB or 400h. But unRAID is the way to go so that you can use way larger heap sizes. I have mine set to 3GB and just for fun I connected over a dozen mini-clients.

You appear to be running Sage in a Win VM on unRAID. Why not also install it in a docker? Even if you don’t install tuners I that version you could use it as a server for additional clients to play non-live TV content?

[btrcp2000]

Updated my sig. It's always outdated as I have been trying so many different configs just to get back to a stable combination on unraid. You've seen and tried to help with most of my issues. I've been on docker for a few months.

My most stable sage setup included my dish r5000 boxes, which never required any attention. Channel changes were perfect, always had 5.1 sound, no nightly reboots, etc. It just worked and I had any channel I wanted to pay for in Sage. Unfortunately there appears to be no way to get them to work in UNRAID using a windows VM as the ancient software can't translate a linux filepath. I want to use Gemstone, but that requires UNRAID for java heap purposes, so it would seem to be impossible to have both. I was hoping that this thread indicated the possibility of increasing the windows java heap to make gemstone work better.

I only own 2 mi boxes, but assumed I would need more as the sage boxes die over time.

[Monedeath]

I don't know if this is even advisable in a single-box configuration, but IIRC SageTV's server can be "slaved" as an external tuner to yet another SageTV server. Perhaps configure unraid as the primary(for extender/client java heap), and then configure a "bare-bones" slaved version of SageTV running on Windows to support the R5000's?

Sounds like a nightmare to configure, even on separate boxes where port/ip conflicts shouldn't be plentiful. But might be something for someone who wants to hit their head against a wall for a bit to investigate.

Particularly given I seem to recall that the SageTV functionality in question might not be working as advertised in 9.x

[btrcp2000]

That's how my Colossus tuners are currently running (albeit not stable). They are installed on the windows VM along with a sage instance which is set up as a network encoder. It works, but for some reason sage won;t leave the usbuirt ir files as is. It switches back and forth between them meaning channel changes don't work and the dish boxes are usually asleep. I have it set up to emit "SELECT" before any channel changes, but it doesn't matter if it's using the wrong ir file.

This is why I miss r5000, which was vip211->usb cable->server. Colossus requires hdmi/component, splitter for hdcp, optical, usbuirt with the correct zones. So many moving parts need to function in unison, and THEN you have to worry about it all surviving nightly reboots.

The r5000 is already a network tuner. Even though it's physically installed on the winvm sagetv server, it still has to find the vm's sagetv instance with a loopback ip. I have tried giving it the docker IP. Docker is able to find it and tune it, but the r5000 software complains that it can't find docker's recordings directory because it's looking for UNC \\ paths not linux / paths.