Help! Directory listings take FOREVER now

[jhkoenig]

This is a new problem, following decades of solid performance. I'm running V9, with about a 6 month's old server image. On some, but not all, clients, pulling up a list of recorded shows or videos can take 10-20 minutes. On other clients it is instantaneous. My 2 Windows clients work great, but the Windows server UI takes forever. My Android mini-client (just installed) takes forever too.

Any ideas? Thanks, this is driving me crazy!

[Tiki]

My first guess would be a failing hard drive on the server. You may want to check the Windows error logs for clues.

You could also check the Sage logs for errors.

PS - when you say the Windows Clients are OK, I assume you really do mean Sage Client software (and not Sage Placeshifter).

[jhkoenig]

Thanks for the reply. Yes, when I say Windows Clients are OK, I mean Sage Clients on Windows computers. That's what makes this confusing; the behavior is different depending on which way the server is accessed. I would expect that a bad hard drive would present the same response time to all clients. I will check the SMART stats on the disk drives, but have not received an alert re failure counts.

[wnjj]

Sounds like a Java memory issue to me as the miniclients and server are having issues. Check on one of them for the memory in use via the info page. What size is the heap set to?

It's possible something recently increased the size of your wiz.bin. Check it for file size also.

[stuckless]

SageTV can be severely impacted by a faulty network port. I've had this happen twice where the UI was unusable and it turned out to be a faulty port on my router. (basically, this would show up as LOTS of dropped packets).

The other time I saw something take minutes to show up in the UI was when my drives on my server were set to spin down, and then after watching a show and try to access the UI it would take 1-2 minutes before the UI was responsive again. (I ended up setting my drives to never spin down).

[jhkoenig]

Thanks for all the good ideas! I have either the best or the worst outcome: the problem went away. Good news is the WAF was not destroyed. Bad news is that if the problem returns I still don't know what caused it.

Anyway, thanks for the advice! This great community still amazes me.

[wnjj]

You should still check on the Java memory usage and max in settings and make sure your wiz.bin hasn't exploded in size.

To reiterate, the common thing between the server and miniclients (but not full clients) is the use of memory on the server.

[jhkoenig]

Will do. i have checked the server to ensure that the java heap is maxed out (32 bit image because DCT) and have seen several out of memory errors about 2 months ago. The problem has popped up off and on the past few days, which seems to be primarily to test my patience ;-).

I need to research DCT operation under 64 bit Sage. When I put it in, only 32 bit was supported.

Thanks for your message!

[Galaxysurfer]

Which version of OpenDCT did you install or are you using? I use 64 bit version of both the OpenDCT as well as 64 bit SageTV just fine. The only hiccup I have experienced was with versions of java installed & utilized. I had adjusted heap size as well.

[jhkoenig]

Originally Posted by Galaxysurfer

Which version of OpenDCT did you install or are you using? I use 64 bit version of both the OpenDCT as well as 64 bit SageTV just fine. The only hiccup I have experienced was with versions of java installed & utilized. I had adjusted heap size as well.

I will wait for a window without recordings (tougher than it sounds) and check out the version of OpenDCT. I would love to migrate to 64 bit!

[jhkoenig]

Originally Posted by Galaxysurfer

Which version of OpenDCT did you install or are you using? I use 64 bit version of both the OpenDCT as well as 64 bit SageTV just fine. The only hiccup I have experienced was with versions of java installed & utilized. I had adjusted heap size as well.

Encouraged by your helpful comment, I upgraded Sage and OpenDCT today and it works! Thanks for the nudge. Only remaining/outstanding issue is that the SageTV Web Interface plugin still thinks that it is running on a 32bit server and does not work.

Thanks for the encouragement!