SageService CPU Maxed

[dertb]

I am running the latest sage server 4.1.8. For some reason it seems to pegging my CPU. I have a dual fx60 dual core chip and one core is maxed at 50%. When I try to restart the service it starts but at the max cpu again. When i try to restat the progrm it just hangs. Any Ideals?

[Opus4]

I don't remember if debug logging is on by default, but if not: set the debug_logging=TRUE property & then try starting SageTV again. There may be comments in there about what is happening. Inlcude the logs with any bug report you submit.

Check to see if it is hanging on any corrupted recordings or video imports -- any 0 length files in the recording directories?

- Andy

[dertb]

Here re the log files..report submitted

[ke6guj]

Its a media import issue with 4.1.8. Your system is hanging on the scanning of an import file

If you look at your log, you'll see this

Tue 2/28 12:12:44.401 testFile=4x06_-_Dudley_Moore.avi
Tue 2/28 12:12:44.403 MPEG1 file type detected
Tue 2/28 12:12:44.403 VF GetFileDuration:S:\imports\Muppets\4x06_-_Dudley_Moore.avi

It should immediately get the file duration and move on, but it hangs at that point and goes to max CPU. It does continue to do other Sage functions, but it should look something like this..

Tue 2/28 11:38:12.305 testFile=Black Hawk Down - Bodies-----.mpeg
Tue 2/28 11:38:12.307 Error instantiating metadata parser plugin of:java.lang.ClassNotFoundException: sage.WMATagParser
Tue 2/28 11:38:12.307 MPEG1 file type detected
Tue 2/28 11:38:12.307 VF GetFileDuration:E:\Shared\Black Hawk Down - Bodies-----.mpeg
Tue 2/28 11:38:12.311 File is not a valid MPEG-2 PS/TS file...using standard file duration detection
Tue 2/28 11:38:12.797 Duration is 188321 millis
Tue 2/28 11:38:12.807 Added:MediaFile[id=1499720 A[1499723,1499721,"Black Hawk Down - Bodies-----",0@0402.16:01,3] host=pvr encodedBy= E:\Shared\Black Hawk Down - Bodies-----.mpeg, Seg0[Sat 4/2 16:01:11.659-Sat 4/2 16:04:19.980]]
Tue 2/28 11:38:12.809 New Library Video File MediaFile[id=1499720 A[1499723,1499721,"Black Hawk Down - Bodies-----",0@0402.16:01,3] host=pvr encodedBy= E:\Shared\Black Hawk Down - Bodies-----.mpeg, Seg0[Sat 4/2 16:01:11.659-Sat 4/2 16:04:19.980]]

I have done some testing and it seems to a bug with only some MPEG files. IF you shut down sage and move all your imports, when you restart sage, it'll work fine. But when you re-import the files, it'll peg the CPU.

I have submitted a bug report on this and sent in a "bad" mpeg for sage to look at. I ended up rolling back to 4.1.7 because of this.


edit: I just got an email from Sage stating that this has been fixed for the next release

[mayamaniac]

Originally Posted by ke6guj

I just got an email from Sage stating that this has been fixed for the next release

Thats good news. I had the same problem posted here. I revert back to 4.17 also to get rid of it. I'm not gonna bother searching for the video file that is causing it since 4.17 works fine for me for the time being.

[Polypro]

I just had this happen last night. It was an mpeg video import (Didn't see if it was 1 or 2).

P