v7 Hangs on Startup

[Diego Garcia]

I'm noticing two problems that appeared a couple of days ago. Not sure if they're related...but I don't believe in coincidences .

The first involves playing back certain video files over my LAN to an HD200. The files, all from the same cable TV show, will not display. The HD200 appears to crash, after a brief pause, when I try to play them. I say "appears to crash" because the screen goes black and I have to power cycle the HD200 to get the user interface back.

The second involves the SageTV UI (i.e., not the service) hanging on my server when it starts up. It stays frozen on "waiting for UI to initialize" or some such for an extended period of time. The only solution -- which doesn't always work -- is to reboot the server. Obviously not a good solution .

One other thing: the first time the problem appeared the Sage UI crashed on the server with the message that the JVM had run out of memory. The process was using just shy of half a gigabyte of RAM at that point.

I looked in the log file and don't see anything odd. In fact, I don't see much of anything at all.

Any tips/pointers/suggestions on how to diagnose and resolve this?

This is all occurring under Win7 32 bit, 4GB RAM, plenty of hard disk space.

[mike1961]

Couple things you can try. First, the fact that your HD200 appears to crash but not crash might be because the sage service is not responding the way it should and therefore the client HD200 might be just fine.

Have you checked CPU resources in the task manager to make sure there are no issues?

Have you checked on the server at start, all programs, accessories, system tools, system restore to see if there were any new programs, windows updates, etc. installed recently? You could do a system restore and go back to a prior restore point a few days ago before this incident started to see if that resolves it.

The other thing you can try doing is stop the service and make a backup copy of your sage.properties file and try a prior one before this started. I had a hell of a time getting my new HD HomeRun Prime to work and spent a most of the day working on it and banging my head against the wall only to find out it was a bad sage.properties file on the server.

Mike

[Tiki]

You should also check the Windows Event Log for error messages. You may have a hardware problem on your server (maybe a failing hard drive or something?).

[mike1961]

Tiki - I was just thinking that when I reread the post - it could be that he has a hard drive going bad. He could schedule a scandisk.

Mike