2 Instances of sagetvservice

[nyplayer]

Is it the norm now to have 2 instances of sagetvservice?

Is it the norm now to have 2 instances of sagetvservice?

* duplicate posts merged into 1 *

[GKusnick]

Yes. Likewise SageTV.exe and SageTVClient.exe. The second one is there to orchestrate the automatic restart of the primary instance when plugins are installed or uninstalled.

[bigo93bronco]

Ever since I upgraded to the new version of sage 7, ever time I restart the server, it starts 2 instances of sage. One is using about 1500 1.5MB of memory, and the other one is obviously in use, and uses around 650MB. Is this normal, or a glitch with the upgrade?

* merged *

[Opus4]

This is normal for v7.

- Andy

[Moskus]

This is normal... but can it be avoided?

Or let me ask in a different way: Why does SageTV 7 need two services?

[GKusnick]

One of them manages the automatic restart on plugin installation/upgrade.

[heffneil]

I noticed in task manager i have two instances of sagetvservice.exe. Any one know if that is correct? I don't think it is and I am not 100% sure where it is coming from to start the second instance. I am running windows 2003 server and sage tv is working properly?

Neil

* merged *

[heffneil]

Also just noticed when I run sagetv client on the machine to make changes it shows up two times! Any one seen this and think it is correct? Each instance has its own process id and when I closed the client both went away!

Thanks,

Neil

[heffneil]

i'm stupid

[btrcp2000]

Upgraded to 7.12 beta and began to get skips in playback on hd100. this usually means that comskip needs to be shut off as the server is doing too much, but when i went to task mgr to see what was up, i noticed two separate instances of the sage service, one using about 270mb memory, the other 26mb. Both are under user Admin. That can't be right??

Other thing I noticed is that WHS will not allow me to uninstall the 6.6 version from the console. My guess is because whatever it is looking for has been overwritten by 7. How to get rid of the 6.6 add-in entry?

* merged *

[sbeaulieu]

If the 2nd process is just for facilitating automatic restart for plugins, then why would it need to be running all the time? It could be launched just before a restart is needed and then killed once the restart occurred. Possibly it also has another purpose....

[TwistedMelon]

It could also have a different name, which would probably stop all these theads about people asking why there "seem" to be duplicate processes.

[phelme]

So I need to ask. How successful is this two process "wrapper" method working for everyone? Any time I upgrade a plugin that needs to restart the server (in my case a service), it *never* works. The service comes back, but never in a state where a client can connect to it. I need to to shutdown the service and then use a task manager to kill off the outer managing SageTVService process and restart the whole thing from scratch. I can't believe I'm the only one having this problem.

it's probably due to some plugin that uses Jetty, Phoenix etc. but I've never been able to figure out which.

[barney B.A.]

Originally Posted by phelme

So I need to ask. How successful is this two process "wrapper" method working for everyone? Any time I upgrade a plugin that needs to restart the server (in my case a service), it *never* works. The service comes back, but never in a state where a client can connect to it. I need to to shutdown the service and then use a task manager to kill off the outer managing SageTVService process and restart the whole thing from scratch. I can't believe I'm the only one having this problem.

it's probably due to some plugin that uses Jetty, Phoenix etc. but I've never been able to figure out which.

It has worked every time for me so far. I also use those plugins
Perhaps a re-install of Java.

[Fuzzy]

The service restart has worked every time for me.. however, I have noticed multiple times where the client instance (sagetv.exe) doesn't restart after the service is restarted. Starting it myself works fine.

[phelme]

When this happens the server is in an odd state. Most operations appear to be working (witnessed in the logs), it will even record programs. But, you simply can't connect to it, either with a client or the web interface. It requires the shutting down of both Sage services and starting it all up again.

This issue has actually been around since before v7 for me, but the plugin model, with the two services and more frequent restarts after updates has made it more apparent.

If I had to guess at the root cause it's probably one of the three clients I have running, somehow hosing the client thread upon first connect. One is actually a full SageTV server running as a client and network encoder, one without the encoding (use to be an encoder too) and one is client only software. Maybe it's the network encoding. One of these days I'll have to move the 2nd DirecTV box into the server's space and get rid of that.