SLES 10.3 NTP offset

Hi all,
could anyone help me understanding NTP offset problem.

We have several servers with SLES and NTP running. On many systems there are no problems with NTP. But at two or three systems the
NTP offset runs crazy.

If you can see here the ntpq -np command lists the offset in -4989.8.

#> ntpq -np
remote refid st t when poll reach delay offset jitter 2 u 304 512 377 0.393 -4989.8 2816.26

As I find somewhere in the documentation the offset is a measured time between the last 8 requests and the system time.
But if I use date the system time is running fine. There is no offset the time is the exact the time within the timeserver.

Why does the offset is so high on this machine ?

Thanks for advice.

WoW ! It looks like that only the SLES-10.3 systems have this problem.


Is this on virtual or physical servers?
Could you list the kernel and ntp packages that are installed on the system (to determinate patchlevels)?

Also you mention this in only on SLES 10.3… what other systems/versions are you running where you are not seeing this?


Maybe it’s loosing touch with the ntp server it’s syncing too?

Have you checked to logs for any further info, maybe the daemon is

What if you watch the process and maybe run tcpdump (filter for ntp),
for example

watch ntpq -np

tcpdump -i eth0 udp port 123

Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 3.0.34-0.7-default
up 17 days 10:26, 3 users, load average: 0.31, 0.31, 0.33
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU