Enabled debug mode, now clients can't connect

[gregmac]

I just turned on debug mode, while trying to nail down yet more problems with my tuner card, and now remote clients can no longer connect.

I used the sagetv windows client to set debug on, and then from an SSH console restarted the server.

Since that point, I've been unable to connect with a remote client. The only thing relevant I can see in the sagetv_0.txt log is this:

Sun 11/28 15:55:36.557 [LibraryImporter@1af4abb] Error communicating with client:java.net.SocketTimeoutException: Read timed out
Sun 11/28 15:55:53.213 [SageTVServer@13c3750] Error w/SageTV client connection:java.io.EOFException

I can use the placeshifter client locally, and I do see that 'remote' clients are enabled. I turned off debug, but it doesn't help.

The local placeshifter client is also unable to list recordings now, it just sits forever with the spinning loading circle. I'm not sure when it last worked as I haven't used it for a few days (gave up due to horrible performance of placeshifter).

I can connect to serverip:31099 from remote systems.

I'm not sure what else to check now. Any other info I can provide? Ideas?

[drewg]

Could be that Sage didn't fully die when it was restarted & is holding onto a socket. I'd stop sage from a command line. Then make sure that its all dead by doing 'pgrep java'. If you get any output from this, do 'sudo pkill -9 java'. Now start sage & see if it works.

If not, try stopping all the clients & then re-starting SageTV on the server.

Drew

[gregmac]

I had to kill -9 the sage process. I'm not sure if it was the same one or not, but after I did that and then started again, it was working once more.

Thanks.