User Interface not starting on v9 server

[jmv]

Folks,

Hopefully someone can help. My set up runs v9 server as a service and also launches the user interface. This has been my setup since original v7. V9 always took a long time to go from splash screen to actual user interface (over 5 min from boot splash would sit there but eventually user interface would show up. Recently it would be hit or miss with about 33% of the time the UI never showed up after the splash sat there from 5-10min I just never got a UI. Task manager shows the service and 3 instances to the client but no UI. I also can’t manually launch the client as I think it sees it as already running. my only other clients are HD300’s that run fine regardless of server UI launched or not. When this 100% fail started it was right after I installed the latest OS patches that I haven’t done for 2-3 months.

Configuration:
SageTV V9 9.0.14.568 32 Bit
Server Windows server 2012 R2 latest patches
JAVA 1.8.0_151

Will try to upload log files when I’m back home. Let me know if there is anything else is needed

[JustFred]

That's a **very** long time for the client to come up.

As a reference point, try this: Power cycle the HD300, but use the remote to stop it from automatically connecting to the server. Next, time how long it takes to connect to the server and display the normal SageTv GUI. The Sage Client should typically connect & display about as quickly as the HD300 does.

Providing log files for both the server AND client (during the relevant time period) will likely provide clues. How much physical memory is present? How much free memory does Windows report once the Sage server & client is running? What size is set for Sage's Java Heap space?

[Tiki]

I don’t know if it’s still the case, but Sage used to do all of its scheduling at startup. This could take a while if you had a lot of favorites, especially if you changed the scheduling look ahead to be longer than the default (which I think was five days), since it had to work through what tuners to use for each recording and resolve any conflicts (and also schedule the intelligent favorites).

There was a setting in the properties file called “limited carney init” that would let Sage startup quicker by doing some of that stuff in the background after Sage had started.

It might be worth investigating.

[jmv]

The delay is only on the client running on the same box as the SageTVserver service. In reviewing the log, it looks like there is about 4 min of connection failures trying to connect to the local host IP. I run this on a fixed IP address, so is there a way to force it to connect via the network IP? Not sure if that would help. Also the splash disappeared right about 9AM in the log it seems to just keep humming along, You can see it is still running as despite the UI never showing up, the log is still getting populated with new entries.

Memory (30% utilzied) is not an issue or CPU (1-3%).

Attached is the zipped client log from the server.

[JustFred]

It's unfortunate that the server log hasn't been posted yet. Comparing the events in the server and client logs is often helpful. The client log indicates a couple of unrelated issues.

Originally Posted by jmv

The delay is only on the client running on the same box as the SageTVserver service. In reviewing the log, it looks like there is about 4 min of connection failures trying to connect to the local host IP. I run this on a fixed IP address, so is there a way to force it to connect via the network IP? Not sure if that would help.

It took 13 minutes to establish a network connection. I suspect firewall issues. Try temporarily disabling the firewall on the server. This might be the Windows firewall or a firewall that's part of some anti-virus software.

Also the splash disappeared right about 9AM in the log it seems to just keep humming along, You can see it is still running as despite the UI never showing up, the log is still getting populated with new entries.

Memory (30% utilzied) is not an issue or CPU (1-3%).

Attached is the zipped client log from the server.

At 8:54 is "java.lang.ArrayIndexOutOfBoundsException". Not good.

You're still running V9.0.14.568. Since then, there have been several fixes for crashes. Upgrading to v9.2.1 includes these fixes. Consider installing the 64-bit version, since it also allows for much greater Java Heap space.

[jmv]

Attached are both the client and server logs. This happened to be a successful startup (got the UI, still 5-10 min launch screen).

On the firewall piece, I also assumed that would be the issue. I am running stock Windows Server2012R2 any pointers to a tutorial on how to allow SageTV through the firewall? I did some quick googling and it wasn't obvious what program I should allow and where I should make the entry to allow it through the firewall.

I am considering the upgrades...is there a tutorial on migrating from what I am running to the latest 32 or 64 bit. I have 10+ years of sagetv running and about 3000 programs stored, I wouldn't want to lose that data.

thanks for chiming in.

mv

[JREkiwi]

With the SageTV server shutdown, make this change to the Sage.properties

limited_carny_init=true

That should get your server starting faster than the 13 minutes it's taking currently, which is why your client cannot connect.

John

[jmv]

So far, so good JRE. Thanks for the input.