SageTV Service Failures/Lock-ups

[CharleyZ]

Ever since I upgraded to SageTV v6.1.8, I have had to stop and restart the SageTV service practically every other day in order to get my MVPs to see the streaming server. Simply rebooting the MVPs did not help. Prior to upgrading, I never had to to this.

I upgraded by doing a "clean" install of 6.1.8 by copying "wiz.bin" and "wiz.bak", uninstalling SageTV, removing the remaining directories, and rebooting my server. I haven't installed any additional STVs or other addons yet, except for the STV posted for Google/YouTube video - v6.1.8.1; April 12, 2007.

I am running Java 1.6.0_01-b6.

Any suggestions?

[bcjenkins]

Please file a bug report submitting your debug logs. There is a whole (abandoned thread) with this as symptoms. I was seeing it until I scripted a stop and start nightly. However, Sage support thinks it is related to my OS choice (2K3) and they don't officially support it and don't have repro cases on XP.

B

[Narflex]

Originally Posted by CharleyZ

Ever since I upgraded to SageTV v6.1.8, I have had to stop and restart the SageTV service practically every other day in order to get my MVPs to see the streaming server. Simply rebooting the MVPs did not help. Prior to upgrading, I never had to to this.

I upgraded by doing a "clean" install of 6.1.8 by copying "wiz.bin" and "wiz.bak", uninstalling SageTV, removing the remaining directories, and rebooting my server. I haven't installed any additional STVs or other addons yet, except for the STV posted for Google/YouTube video - v6.1.8.1; April 12, 2007.

I am running Java 1.6.0_01-b6.

Any suggestions?

DO NOT UPGRADE LIKE THAT I've seen a few posts like that lately and I don't know why people are doing that (only copying their Wiz.bin/bak files). Simply just install the new version over the old version. Your upgrade is actually very 'dirty' the way you have done it.

[CharleyZ]

Well... I am running Windows 2003 as well. However, this did not occur until this upgrade. While the support folks my use this as an "excuse", I had no issues going from 5.0.4 to 6.0.18 to 6.0.19.

Also, I have always upgraded like this, only copying my "wiz" files. Why would this be a "dirty" install? If I remember correctly, this is the "best" method of upgrading as per the FAQ. Should I uninstall 6.1.8 like I mentioned, and reinstall 6.0.19 and then reinstall 6.1.8 on top of that to clean things up, or is it too late?

[bcjenkins]

major bummer. oh well

to fix it, not cure.. run a nightly job to stop the sagetv service and one minute later run one to start it.

I haven't had an issue since I did this.

B

[sakker]

Originally Posted by Narflex

DO NOT UPGRADE LIKE THAT I've seen a few posts like that lately and I don't know why people are doing that (only copying their Wiz.bin/bak files). Simply just install the new version over the old version. Your upgrade is actually very 'dirty' the way you have done it.

That is an interesting statement. I would figure that would be the absolute cleanest way to do it and the way I've done it to clear up quite a few problems with Sage on many occasions. Do tell.

[CharleyZ]

Ok - I've been doing a little digging and testing and this is what I've noticed so far...

It appears that the service only "freezes" after I've been using the YouTube interface for a while. I can go back to watching/recording tv and everything appears to be functioning correctly. However, when I go to "power down" my MVP, the service freezes. If I "power up" after that, the interface just hangs until I stop and restart the service.

I have gone now for 4 days without using the YouTube interface and everything is great - no random freezes or crashes. I will let it go a little more and then try using YouTube again to see what happens.

[valnar]

Originally Posted by bcjenkins

major bummer. oh well

to fix it, not cure.. run a nightly job to stop the sagetv service and one minute later run one to start it.

I haven't had an issue since I did this.

B

Have you received any feedback from the Sage devs on a more proper fix for this problem?

Robert