Client software closes overnight... weird...

[ShadoWolf]

I've been using the Sage Client (v4) for a couple of weeks now and I've run into a weird issue where the Sage client software closes overnight. I have my client box setup to auto-logon and A/C power recovery is on... so if it was a power issue it would log straight back in and startup Sage (I've tested this by tripping the circuit breaker...)

This has been happening nearly every night since installing the client, and tonight it happen for the first time WHILE I was watching "Live" TV. The client just closed out like someone closed the program. Screen went to the main desktop, nothing left running in Task Manager... jsut **POOF** and it was gone... I'm suspecting this is what is happening every night.

I've verified that ALL my power-save functions are turned off, there are no scheduled tasks running on this box... it's a fresh load of Windows XP SP2 that only has Sage Client, StreamZap remote, and the Sonic Cineplayer Decoders... all current hardware drivers... it's a Dell GX270 Small Form Factor w/ 2.4 GHz P4, 256 MB RAM, GeForce4 MX 440...

I'm totally stumped...

This did major damage to the WAF until I mapped one of the StreamZap buttons to launch the client... but I'd still like to fix it if I can... TIA!

[Opus4]

Check to see if there is any sort of error log in the SageTV directory.

Also, you can place debug_logging=TRUE in the sageclient.properties file (exactly as shown, including CAPS) to turn on SageTV's logging. Maybe there will be something at the end of the file when the client exits.

- Andy

[deliverer]

I have the exact same issue, except it will sometimes close in the middle of watching something. When this happens, the sage icon go around and around and then it just exits. This is happening on my two clients. My server is solid and never has issues.

I will put the debug command in as suggested and then report back with the results.

Regards,

Deliverer

[deliverer]

It happened again. Does this log shed any light on the issue? I attached the entire log as well.

Sun 12/25 13:56:50.060 Received command of:SCHEDULE_CHANGED 0 from Socket[addr=/192.168.1.240,port=42024,localport=1025]
Sun 12/25 13:56:50.064 VF processing job null nPlayin=true
Sun 12/25 13:56:50.065 isRec=true rd=3409879 base=3398039
Sun 12/25 13:56:50.065 VF thread is now waiting for 1:03:21.525
Sun 12/25 13:56:50.894 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1025]
Sun 12/25 13:56:50.897 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1031]
Sun 12/25 13:56:55.894 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1025]
Sun 12/25 13:56:55.898 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1031]
Sun 12/25 13:57:00.896 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1025]
Sun 12/25 13:57:00.899 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1031]
Sun 12/25 13:57:05.899 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1025]
Sun 12/25 13:57:05.900 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1031]
Sun 12/25 13:57:10.900 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1025]
Sun 12/25 13:57:10.901 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1031]
Sun 12/25 13:57:15.901 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1025]
Sun 12/25 13:57:15.902 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1031]
Sun 12/25 13:57:16.360 PM currState=3 wakeupTime=Wed 12/31/1969 18:00:00.000
Sun 12/25 13:57:20.905 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1025]
Sun 12/25 13:57:20.906 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1031]
Sun 12/25 13:57:25.906 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1025]
Sun 12/25 13:57:25.907 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1031]
Sun 12/25 13:57:30.908 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1031]
Sun 12/25 13:57:30.909 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1025]
Sun 12/25 13:57:35.908 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1031]
Sun 12/25 13:57:35.909 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1025]
Sun 12/25 13:57:40.910 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1031]
Sun 12/25 13:57:40.911 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1025]
Sun 12/25 13:57:45.910 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1031]
Sun 12/25 13:57:45.911 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1025]
Sun 12/25 13:57:46.360 PM currState=3 wakeupTime=Wed 12/31/1969 18:00:00.000
Sun 12/25 13:57:50.911 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1031]
Sun 12/25 13:57:50.912 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1025]
Sun 12/25 13:57:55.912 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1031]
Sun 12/25 13:57:55.913 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1025]
Sun 12/25 13:58:00.913 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1031]
Sun 12/25 13:58:00.914 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1025]
Sun 12/25 13:58:05.914 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1031]
Sun 12/25 13:58:05.915 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1025]
Sun 12/25 13:58:10.914 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1031]
Sun 12/25 13:58:10.916 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1025]
Sun 12/25 13:58:15.915 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1031]
Sun 12/25 13:58:15.918 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1025]
Sun 12/25 13:58:16.361 PM currState=3 wakeupTime=Wed 12/31/1969 18:00:00.000
Sun 12/25 13:58:20.916 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1031]
Sun 12/25 13:58:20.919 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1025]
Sun 12/25 13:58:25.917 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1031]
Sun 12/25 13:58:25.920 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1025]
Sun 12/25 13:58:30.919 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1031]
Sun 12/25 13:58:30.921 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1025]
Sun 12/25 13:58:35.920 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1031]
Sun 12/25 13:58:35.922 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1025]
Sun 12/25 13:58:40.922 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1031]
Sun 12/25 13:58:40.923 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1025]
Sun 12/25 13:58:45.927 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1025]
Sun 12/25 13:58:45.928 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1031]
Sun 12/25 13:58:46.361 PM currState=3 wakeupTime=Wed 12/31/1969 18:00:00.000
Sun 12/25 13:58:50.928 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1025]
Sun 12/25 13:58:50.928 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1031]
Sun 12/25 13:58:55.929 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1031]
Sun 12/25 13:58:55.930 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1025]
Sun 12/25 13:59:00.931 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1031]
Sun 12/25 13:59:00.932 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1025]
Sun 12/25 13:59:05.932 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1031]
Sun 12/25 13:59:05.953 Received command of:NOOP from Socket[addr=/192.168.1.240,port=42024,localport=1025]

---
12/26/2005

I added another debug command after the client had closed.

[T3rry]

same issue here... any resolution to this?

[da_gringo]

I also see this. Where do i find these error logs?

[Keith]

I'm seeing an issue that may be related - my issue is my main Sage UI closes randomly.

I'm running the 4.1.4 beta.

Do all of you have Java update #6 (I know you do, ShadoWolf)? That's about when I started noticing the issue on my system. I'm hoping that's the cause. Meantime I removed the JRE from my system and installed the old version (update #4) and disabled the auto-update feature.

By the way, I had this error in my log file (look in \program files\sagetv\sagetv\sagetv_*.txt)

Wed 1/4 5:10:54.109 Error communicating with server:java.lang.NullPointerException
Wed 1/4 5:10:54.110 Cleaning up c/s connection
Wed 1/4 5:10:54.110 NetworkManager CommunicationFailure : /127.0.0.1:1713 type=1
Wed 1/4 5:10:54.111 MsgSend thread terminating for /127.0.0.1:1713

That's why I think it's Java related. Granted, I'm probably grasping at straws...

[Red Barchetta]

Hi,

I just signed up here because I started having the same issues lately. But, sometimes, while I am watching either live, or recoreded, the UI will switch back to the program Guide by its self, or sometimes just shut itself down. I have tried my different versions of Sage, but I get the same problem with my 2.x, 4.x and the 4.1 demo version. I have gotten the latest versions of Java, and as a last resort, totally re-formatted and re-installed everything (several times now) running tests with even the most basic, un-upgraded installes to a fully upgraded test. Its been weeks now since my system just suddenly started doing this, and I had assumed it was one of the Windows updates, but my tests have shown me that this may not be the case. I will set the debug_logging=TRUE option and see what I can capture for you.

[chrisc16]

I have the same problem as the rest of you... Sage randomly just exits and leaves me with the Windows desktop.

I submitted a support request one week ago; if I hear back I'll post an update.

-Chris

[zoundz]

Me three on the random shutdown problem. Just closes. Starts right back up and all is well. Only does it once, apparently.

[Opus4]

Is this happening after the registration license key has been entered?

- Andy

[Keith]

Andy,

Who was that adressed to? All of us? ;->

In my case, yes, I entered the license key for both server and client.

Any thoughts on the Java error I posted above?

[Opus4]

Originally Posted by Keith

Who was that adressed to? All of us? ;->

In my case, yes, I entered the license key for both server and client.

It was meant for anyone... I just wanted to double check something.

Any thoughts on the Java error I posted above?

Not really... but let us know if reverting helps. Tech support would be able to follow such logs better than I can, though. (Note: I don't know if CES will slow down any response from tech support.) Oh yeah -- if you are running the beta version, you can file a bug report on it too.

- Andy

[Keith]

If it can be definitively narrowed down to the beta, then I'll file a bug.

I haven't tried downgrading Sage to 4.0. That will be the next thing I do if the JRE downgrade doesn't help.

Is anyone having this problem running Sage 4.0?

[chrisc16]

Originally Posted by Keith

If it can be definitively narrowed down to the beta, then I'll file a bug.

I haven't tried downgrading Sage to 4.0. That will be the next thing I do if the JRE downgrade doesn't help.

Is anyone having this problem running Sage 4.0?

This problem started when I upgraded to v4.1.

-Chris

[Keith]

Originally Posted by chrisc16

This problem started when I upgraded to v4.1.

-Chris

What's your latest JRE update, Chris?

Granted, update #6 and Sage 4.1 seem to have hit at about the same time...

[SHS]

It may have some thing to with JRE 1.5.6 form time to time I have this problem with SageTV Client and some other Java builder had the some problem but never had and problem with the server becuase it using an older beta ver of JRE which is 1.5.4 so may want try drop back to stock SageTV Java builder or drop back to 1.5.4 if you have it.

[Keith]

You can get the 1.5.4 version here : http://javashoplm.sun.com/ECom/docs/...actionId=noreg

Make sure you go into the Windows Control Panel, open the Java settings, and disable the auto-update feature if you downgrade. I think the default is to not download updates without asking first, but better safe than sorry when troubleshooting, I think.

[SHS]

Be sure disable sagetv from startup first then close it then uninstall java then reinstall java after you have reboot which would be the rigth way to do it Keith.

[Keith]

Originally Posted by SHS

Be sure disable sagetv from startup first then close it then uninstall java then reinstall java after you have reboot which would be the rigth way to do it Keith.

Agreed. I assumed that was understood.