Running as service mode, no go. (anymore)

[pciccone]

I have the weirdest problem that took me now 5 hours to diagnose. Turns out my sagetv service will no longer run but will run fine under application mode. This was never a problem until now, I cannot figure out why. (I must use my login name under the service so I can access network UNC paths from within sagetv) I use the same username to login to the console, user has "login as" rights, password is good, using "SYSTEM" user produces same results etc. Machine runs in workgroup mode not domain mode, windows xp home edition.

The odd part is SageTV does load, then dies out for 1 of 2 reasons. Either the log shows that the service quit by itself (trying to recreate now but cannot), or two the log shows client connections (including the localhost) resetting themselves and never connecting to the service running.

Can anyone knowledgable in this area take a look at my startup log to see if they see a problem related to logging on as a service?

Example of a client connection problem, this occurs with all clients on the network when logged on under this user:

ue 12/28 19:04:17.821 Connection lost from: Socket[addr=/127.0.0.1,port=1321,localport=42024] by:java.io.EOFException
Tue 12/28 19:04:17.821 Cleaning up c/s connection
Tue 12/28 19:04:17.822 NetworkManager CommunicationFailure : /127.0.0.1:1320 type=3
Tue 12/28 19:04:17.822 NetworkClient fullCleanup /127.0.0.1:1320
Tue 12/28 19:04:17.822 Cleaning up c/s connection
Tue 12/28 19:04:17.823 Cleaning up c/s connection
Tue 12/28 19:04:17.823 Cleaning up c/s connection
Tue 12/28 19:04:17.823 Cleaning up c/s connection
Tue 12/28 19:04:17.824 Connection lost from: null by:java.net.SocketException: socket closed
Tue 12/28 19:04:17.825 Cleaning up c/s connection
Tue 12/28 19:04:17.825 NetworkManager CommunicationFailure : /127.0.0.1:1320 type=1

Tue 12/28 19:28:08.834 Sending DB to client of size:9295935
Tue 12/28 19:28:08.884 Error w/SageTV client connection:java.net.SocketException: Software caused connection abort: socket write error
Tue 12/28 19:28:08.885 Cleaning up c/s connection
Tue 12/28 19:28:08.886 SageTV received connection from:Socket[addr=/10.1.1.3,port=1298,localport=42024]
Tue 12/28 19:28:08.888 Connection lost from: Socket[addr=/10.1.1.3,port=1298,localport=42024] by:java.io.EOFException
Tue 12/28 19:28:08.889 Cleaning up c/s connection
Tue 12/28 19:28:08.889 Error w/SageTV client connection:java.io.EOFException
Tue 12/28 19:28:08.890 SageTV received connection from:Socket[addr=/10.1.1.23,port=1039,localport=42024]
Tue 12/28 19:28:08.894 Received command of:LISTENER from Socket[addr=/10.1.1.23,port=1039,localport=42024]
Tue 12/28 19:28:08.975 Error communicating with client:java.net.SocketException: Software caused connection abort: socket write error

This WAS working OK for a long time now, I am trying to figure out what changed without making any changes to the system.


This problem exists on 2.1 and 2.2beta. I am using 2.2beta now so I can see the logs. I also tried a fresh uninstall and re-install as well as restoring known good stable backups leading me to believe the problem is outside of SageTVs data directories (SageTV and Common). I also tried to uninstall, reboot and reinstall the Java runtime software. Keep in mind this is not a network issue as even the local client connection (127.0.0.1) is producing the same results. Also remember that all is perfect when running in application mode, ONLY service mode causes these problems.

Thanks for your time!

Phil