Must reboot computer every two days

[mfgolfnut]

I get my Media MVP to connect but after 2 days neither of my MVP's will get through the boot cycle without rebooting my computer and then they come up automatically. No need to reboot MVP unit.

Very frustrating, if you want to watch something and it is recording you loose whatever was recording during reboot.


mfgolfnut
View Public Profile
Send a private message to mfgolfnut
Find all posts by mfgolfnut
Add mfgolfnut to Your Buddy List

[carlgar]

You probably already know but that is not normal. I suspect it is a problem with your DHCP server. Does your DHCP server allow you to specify a static address? I think 2 days is about the time that the MVPs need to renew the IP number that they are allocated. Are you using a wired or wireless MVP?

[mfgolfnut]

Both of my MVP's are wired.

[jpaddock3000]

I kind of have that same problem, but not nearly as frequently. It appears to be a problem with the Sage Service. If you just restart the sage service, your MVP will come right up. I made a batch file on my desktop that just does a net stop sagetv and then net start sagetv. Then everything works in about 5 seconds.

[matt91]

What about Carlgar's question about static vs dynamic IPs on your network. Have you tried static?

[mfgolfnut]

I am going to have to do some research as I do not know how to do that. I do know my laptop shows it connects thru DHCP.

I am using a BEFW11S4 router

Thanks,

Mike

[davephan]

Mfgolfnut,

What are the hardware specs of your computer and what OS are you using?

Dave

[mfgolfnut]

Using XP Pro with Pentium 2.4 and 1.5 MB ram.

Thanks,

Mike

[sacrament055]

Anyone open a trouble ticket with Sage about this? I just had this happen today while watching programming. Sage started responding very slowly to commands then completely froze. I powered off and back on the extenders (1 HD and 1 SD) and they both saw the server but could not boot all the way up until I rebooted the sage server. I suppose restarting the service would have worked as well. FYI my DHCP server is not the same as my Sage server so I don't believe this has anything to do with DHCP.

[gplasky]

Make sure you're not running java version 1.0.5_xx. There was a memory leak problem with that. The best version to run is 1.0.6_4 (the latest) There is a performance increase over running 1.04 and some of the plugins need the latest. Worth looking at that.

Gerry

[carlgar]

Gerry, are you sure about your version numbers? I think you are reversing the 0 and 6. My java shows version 1.6.0_03-b05.

[gplasky]

Originally Posted by carlgar

Gerry, are you sure about your version numbers? I think you are reversing the 0 and 6. My java shows version 1.6.0_03-b05.

Sorry-you are correct. 1.6.0_03. (But you know what I mean. ) I'm also testing 1.6.0_10 which is a new a early access release. They call it Update N. Early Access Update N Some of the new features are:

Java SE 6 Update N (formerly know as the "Consumer JRE" project) is an update release that introduces new features and enhancements aimed at providing an optimized consumer end user experience. Java SE 6 Update N focuses on the following areas:

Enhanced JRE installation experience
The Deployment Toolkit takes the guess work out of determining what versions of the JRE end users have installed on their PC. It supplies Java based web applet/application deployers with a simple interface to accomplish Java detection and installation.
The Kernel online installer lets first time Java users run applets and Web Start applications without waiting for the whole JRE download. The default Kernel installation is expected to satisfy the requirements of most Java applets and applications, and any additional libraries that may be required at runtime are downloaded to complete the Kernel installation. This installation mechanism let the end user get up and running significantly faster, while the complete JRE installation takes place in the background. See Java Kernel FAQ for more information.
For current users of Java SE, the JRE update mechanism has also been improved, using a patch-in-place mechanism that translates in a faster and more reliable update process (the patch in place mechanism will take effect for end users who upgrade from this update release or later to a new update release). As an added benefit, follow-on update releases will no longer be listed as separate items in the Windows "Add or Remove Programs" dialog.


Improved performance and look & feel
The Quick Starter feature will prefetch portions of the JRE into memory, substantially decreasing the average JRE cold start-up time (the time that it takes to launch a Java application for the first time after a fresh reboot of a PC).
Hardware acceleration support: Java SE 6 Update N introduces a fully hardware accelerated graphics pipeline based on the Microsoft Direct3D 9 API, translating into improved rendering of Swing applications which rely on translucency, gradients, arbitrary transformations, and other more advanced 2D operations.
A new cross-platform Swing look & feel, code name Nimbus, provides a nice update over 'Metal' and 'Ocean'.


Next Generation Java Plug-In
A new implementation of the Java Plug-In that is designed to address long-standing issues with applets, and to feature increased reliability, ability to specify large heap sizes, ability to select a specific JRE version to execute a particular applet, and support for signed applets on Windows Vista.

What caught my eye was the fully hardware accelerated graphics pipeline based on DX 9 API.

So far no issues but I'm just running it on a client for now.


Gerry

[sacrament055]

Gerry are you running extenders as well? My client didn't have a problem even after my extenders stopped working. I also checked my java version and it is 1.6 update 3

[CollinR]

I put a DHCP server on my SageTV servers and have noticed a connection reliablity improvement.

My MVPs before were not saying they failed to obtain an IP address, leading to believe DHCP was not to blame, however the server DHCP improves connection speed and I have not had it not connect.

[gplasky]

Originally Posted by sacrament055

Gerry are you running extenders as well? My client didn't have a problem even after my extenders stopped working. I also checked my java version and it is 1.6 update 3

I run 2 of the original MVPs and one of the HD Extenders. You should be able to go into your router if you have that delivering DHCP and verify that any of the extenders get an IP address. If you give them static then you should also see this information in your router by connection. Make sure your subnet mask is correct. It should probably be 255.255.255.0. If you need to define a gateway it would be the IP of your router. Is your PC client getting an IP thru DHCP or is that static also?


Gerry

[mfgolfnut]

Originally Posted by CollinR

I put a DHCP server on my SageTV servers and have noticed a connection reliablity improvement.

My MVPs before were not saying they failed to obtain an IP address, leading to believe DHCP was not to blame, however the server DHCP improves connection speed and I have not had it not connect.

Can you explain the process to adding a DHCP server on Sage TV server?

Thanks,

Mike

[CollinR]

Set your SageTV server to have a static IP address in it's TCP/IP stack.

Get tftpd32 and use srvany to run as a service on your server. This would only work for the Windows version obviously.

You can give the MVPs static addresses in the tftpd32 configuration file.

You can link the MVP MAC address to IP address in thr server properties file.


You can have tftpd32 provide the mvp.bin to the MVPs if you so wish however I haven't attempted it.

[sacrament055]

My DHCP server has a lease time of 30 years so I don't think their lease expired and they were working up until they both stopped at the same time. I suspect it has something to do with the sage service based on previous posts that restarting the service restores service but it is interesting to see that others are not having the same problem. Perhaps I need to go back to using the default UI with no added STVi's and see if the problem remains.

[gplasky]

That's always a good rule of thumb for troubleshooting. Default STV, no plugins. You could lso try not running it as a service. You would just start the program up with the service stopped and disabled. See if it works any different for you. Don't be surprised if it wants you to go through your configuration again. (But it might not.)

Gerry

[mfgolfnut]

Originally Posted by CollinR

Set your SageTV server to have a static IP address in it's TCP/IP stack.

Get tftpd32 and use srvany to run as a service on your server. This would only work for the Windows version obviously.

You can give the MVPs static addresses in the tftpd32 configuration file.

You can link the MVP MAC address to IP address in thr server properties file.


You can have tftpd32 provide the mvp.bin to the MVPs if you so wish however I haven't attempted it.

I am afraid I am still confused regarding exactly where I look for these items and info I put in them. I have since noticed if I go back to the complete vanilla version of sage I don't seem to have the same issue. I however like sage MC UI.