1753604 Members
6100 Online
108797 Solutions
New Discussion юеВ

Re: Linux Date

 
SOLVED
Go to solution
gigiz
Valued Contributor

Linux Date

Hi guys,
i have a problem with my Redhat ES4 with kernel
2.6.9-5elsmp v. 8664 installed on my DL380 servers.I have a problem with a date.
I set a date at the installation.
In few day a date advance to many hours.
If i re-set the date in few day the same problem.
I try to check a system time with date and the hardware time with clock i try to align their, but i have the same problem ....
Help me ...
Thanks a lot
Many point at any response .....
19 REPLIES 19
Rob Leadbeater
Honored Contributor

Re: Linux Date

Hi,

I take it you haven't configured NTP...

That will allow you to keep the server in sync. with an external time source.

It doesn't answer the question of why the system clock is getting so far ahead of itself, but it should keep the time right.

Hope this helps,

Regards,

Rob
Wouter Jagers
Honored Contributor

Re: Linux Date

Check out this link:
http://linux.derkeiler.com/Mailing-Lists/Fedora/2005-11/2688.html

I assume it's possible you'll need to have the mainboard replaced..

Anyway, worth to check before spending lots of time on it ;-)

Cheers,
Wout
an engineer's aim in a discussion is not to persuade, but to clarify.
Ivan Ferreira
Honored Contributor

Re: Linux Date

Your best option is to use NTP. The NTP configuration is very easy. See:

http://www.brandonhutchinson.com/Using_ntp_with_Red_Hat_Linux.html
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Wouter Jagers
Honored Contributor

Re: Linux Date

Problem is NTP will complain (and stop doing its job) when the clock is on too wild a rampage :-/

NTP is good, though.. you should really consider using it even when this problem is gone.

Cheers
an engineer's aim in a discussion is not to persuade, but to clarify.
gigiz
Valued Contributor

Re: Linux Date

ntp server is a warkaround is not a solution,
my customer want a solution ....
:-(
Rob Leadbeater
Honored Contributor

Re: Linux Date

Is this happening on *all* of the servers or just one ?

Just wondering if it's a hardware problem with the DL380 or something broken in RedHat...

What generation DL380 are you using ?

Cheers,

Rob
John Poff
Honored Contributor

Re: Linux Date

Hi,

You mention the kernel version as being "v.8664". What exactly does it show when you do a 'uname -r' on the box? Are you running a 64 bit kernel (x86_64)? If so, do you have 64 bit CPUs in the system? What does /proc/cpuinfo report about the CPUs?

I'm wondering if you have the right kernel.

JP
Stuart Browne
Honored Contributor

Re: Linux Date

I'm with John here.

In any case, the current release of kernel for RHEL4 is 2.6.9-42.0.10.EL. A 2.6.9-5 is not even U1! You've done your updates, yes?
One long-haired git at your service...
Matti_Kurkela
Honored Contributor

Re: Linux Date

I agree with John and Stuart above.

If you have a dual-core CPU, you *must* have at least U1, or you *will* have problems. If you read RedHat's list of supported hardware, it will note that U1 is a requirement on dual-core CPUs.

You can use the base ES4 CDs (with no update level, or "U0") to install a system with dual-core CPU(s), but you will get random crashes with high load and various timing problems. These will go away when you go to U1.

The easiest way is to register the system to RedHat Network and let up2date do its job.

By the way, if you have a x86_64 CPU, the system's model number should be DL385, not DL380.

MK
MK