SLES 10 SP3 / OES2 SP3 PHYSICAL BOX time drifting forward

Hi all,
First time i’ve ever seen this happen with a physical box

Installed sles 10 sp3 / oes2 sp3 on a dl320 G3 box for a client

Configured NTP like the other servers:
remove the dummy local clock entry
put in the time source with prefer, burst and iburst parameters

no kernel parameters as it’s a physical box

in the last 2 days it’s gained 2 seconds from the other servers in the

this box is a cluster node which is only running the master resource
and a file share, so it’s not exactly being worked really hard

has anyone seen something like this before and can offer me some
pointers on where to from here?

we have the latest oes2 patches, but not the sles ones as we don’t seem
to have maintenance for some reason on sles, but only for oes2


gleach1’s Profile:
View this thread:


It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your problem been resolved? If not, you might try one of the following options:

  • Visit and search the knowledgebase and/or check all
    the other self support options and support programs available.
  • You could also try posting your message again. Make sure it is posted in the
    correct newsgroup. (

Be sure to read the forum FAQ about what to expect in the way of responses:

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your Novell Product Support Forums Team