SageTV Client corrupt wiz.bin

[sdsean]

My servers and extenders seem to be running fine. . .however my SageTV client on my windows machine simply failed to start like 3 times in a row and had to kill it. . . .

You'll see in further posts below, when the server is running, I start up the client, and then in says "Initializing Service" and according to the logs it's attempting to connect to the server. It starts using localhost (127.0.0.1) with a given port, fails to get a connection, and increments the port number, and then tries again. When this happens it then generates a corrupt wiz.bin file as a result.


Attached is my log file. . . any help, please? Is there some setting I can use to tell it what port number to start searching at?

[sdsean]

shameless bump. . . can anyone help? i guess just a re-install? (ugh)

[JustFred]

Looking at your logs, it seems the client can't communicate with the server (which appear to both be on the same computer). This indicates a networking issue.

Assuming your sig is current and still running Win7, the PCs firewall might be causing this.

Has ANYTHING changed on this computer between the time Sage was working and not-working? Look there, first.

Re-installing Sage **might** resolve the issue. No harm, as long as there's a backup of a good sage.properties and wiz.bin which can always be dropped in place after the re-install.

[sdsean]

Yean the client is on the same machine as the server. . . and no nothing has changed at all. . . i mean unless the machine was hacked which i'm doubting. Server runs day/night, almost never reboot unless sage itself craps out and since I'm still using Windows 7 i've long since given up on updates. . . .


Very odd. . . a re-install did fix it last night, but then this morning after shutting down the client manually and trying to bring it back up manually, same thing (and again a reinstall seemed to fix it at least for now).

[JustFred]

Perhaps something to do with anti-virus software? Is the AV s/w updating or getting new virus definitions? I recall reading that some AV software (don't remember which vendor) needs to be explicitly told to exclude Sage.

I'm using MS Security Essentials on all my Sage servers, and haven't had a problem with it in many years of use.

On the other hand, Norton AntiVirus (which runs on all my desktop PCs) periodically gets pretty uppity and decides to block all incoming network traffic. It does this without any warning. Such behavior is what motivated me to use MS-SE on my Sage boxes.

[sdsean]

I too only use MS Security Essentials, and double checked the firewall stuff. . . .


But I did notice after a re-install, it seems to work fine but it's b/c the Sage service itself is not running, and it's just running in standalone mode. . . so you're definitely on to something. . .


Can't figure out for the life of me why it would have a problem talking to localhost/127.0.0.1 though . . .

[sdsean]

OK so I tracked this down a bit more. . .in the log file i see:

SError w/SageTV client connection:java.net.SocketException: Connection reset by peer: socket write error
Fri 8/3 12:28:57.016 [SageTVServer@1e989e3] java.net.SocketException: Connection reset by peer: socket write error
Fri 8/3 12:28:57.016 [SageTVServer@1e989e3] at java.net.SocketOutputStream.socketWrite0(Native Method)
Fri 8/3 12:28:57.016 [SageTVServer@1e989e3] at java.net.SocketOutputStream.socketWrite(Unknown Source)
Fri 8/3 12:28:57.016 [SageTVServer@1e989e3] at java.net.SocketOutputStream.write(Unknown Source)
Fri 8/3 12:28:57.016 [SageTVServer@1e989e3] at java.io.BufferedOutputStream.write(Unknown Source)
Fri 8/3 12:28:57.016 [SageTVServer@1e989e3] at sage.SageTVConnection$MyDataOutput.write(SageTVConnection.java:3552)
Fri 8/3 12:28:57.016 [SageTVServer@1e989e3] at sage.Wizard.sendDBThroughStream(Wizard.java:8743)
Fri 8/3 12:28:57.016 [SageTVServer@1e989e3] at sage.SageTVConnection.initializeListenerData(SageTVConnection.java:567)
Fri 8/3 12:28:57.016 [SageTVServer@1e989e3] at sage.NetworkClient.acceptFromClient(NetworkClient.java:217)
Fri 8/3 12:28:57.016 [SageTVServer@1e989e3] at sage.SageTV$4.run(SageTV.java:713)
Fri 8/3 12:28:57.016 [SageTVServer@1e989e3] Cleaning up c/s connection

It then seems to repeat over and over again, attempting to increment the port number to find an open port.

But doing a netstat I see the SageTVService normally using the following ports:

[SageTVService.exe]
TCP [::]:8080 Vader:0 LISTENING
[SageTVService.exe]
TCP [::]:31099 Vader:0 LISTENING
[SageTVService.exe]
TCP [::]:42024 Vader:0 LISTENING
[SageTVService.exe]
TCP [::]:49152 Vader:0 LISTENING


So I feel like when the client starts up it's using a start port range to connect thats wrong and so it never finds the service. Is there a setting in sagetv.properties that i can adjust this with?

[sdsean]

Also each time i start up the client seems to pick the last port number (which of course is wrong) and so it never finds it. . . there must be a way to tell the client the port range start should be. . . (especially since it seems to pick up where it left off)

[sdsean]

@here Anyone have any thoughts? Will the socket connection just keep cycling until maybe it finds the right one? Is there a way via properties that I can set it ( i tried various greps to no avail)

[pjwerdna]

Originally Posted by sdsean

But doing a netstat I see the SageTVService normally using the following ports:

[SageTVService.exe]
TCP [::]:8080 Vader:0 LISTENING
[SageTVService.exe]
TCP [::]:31099 Vader:0 LISTENING
[SageTVService.exe]
TCP [::]:42024 Vader:0 LISTENING
[SageTVService.exe]
TCP [::]:49152 Vader:0 LISTENING

Probably not relevent, but arent those all IPV6 rather than IPv4? Hopefully netstat also shows entries like
TCP 0.0.0.0:8080
and
TCP 127.0.0.1:8080

[sdsean]

I think it's showing both actually but the main thing is it seems to be looking for a specific port (based from the last shutdown i guess), and counting up when it doesn't find anything. . . I guess I could try to just leave it running and see if it ever finds something, but I feel like there must be a way to set / tell the client what port to use to talk to the server