Sudden SageTV problem, service stops a few seconds after starting

[hagur]

Hi,

Suddenly my SageTV service will no longer run properly for more than a few seconds. All my SageTV clients lost their connection today, so I checked the status of the SageTV service - it was stopped. I started it up, but after a few seconds it just stopped again. I restarted the computer which runs the service, but it still will only run for a few seconds.

If I monitor the processes of the machine, I can see the SageTVService.exe, then the SageTVTranscoder.exe process starts and immediately consumes about 50% of the CPU and the memory usage jumps to about 400mb immediately, then it stays that way for 5-10 seconds and then the service stops. I've turned all my clients off, but still this transcoder process starts up, is that normal?

Here's my SageTV log, from startup until the service stops:

http://pastebin.com/c1rAu7aJ

Hope someone can help, I don't recall making any changes to my system, I was successfully watching Live TV via the SageTV placeshifter yesterday.

[BobPhoenix]

First thing I would try is a check disk on all your recording directories and your OS boot drive. It probably won't be that but it won't hurt. You might also try a MemTest and see if you have a memory problem. Didn't necessarily see anything in your log except for a possible network issue but don't think that would cause your problem. You could also start up just the SageTV GUI without service mode and see if you get the same problems. Out of ideas for you otherwise. Maybe someone that can read the log better will give you a better solution.

[hagur]

Thanks for the input. I saw an old thread mentioning high CPU usage by the SageTVTranscoder and lockups/crashes. That was related to corrupted media in the import directories, with which the transcoder got stuck when extracting thumbnails from the videos.

I completely uninstalled my SageTV server and reinstalled and I've got it configured like it was before, except the library import paths and everything is working smoothly again. I'm going to add my library import paths one at a time to see when it fails (if it does so again) - that way I can hopefully pinpoint the media that is messing with the transcoder.