Red Hat NETSCAPE MANAGEMENT SYSTEM 6.0 - COMMAND-LINE Bedienungsanleitung PDF herunterladen (Seite 34)

remote refid st t when poll reach delay offset jitter

==============================================================================

LOCAL(0) LOCAL(0) 10 l 1 64 3 0.000 0.000 0.015

*navobs1.oar.net .USNO. 1 u 5 64 1 222.555 68.548 0.015

+darkcity.cerias .GPS. 1 u 60 64 1 44.732 -19.367 0.015

+ntp-2.gw.uiuc.e truechimer.cso. 2 u 61 64 1 22.875 -27.707 0.015

A telltale sign that you don’t have proper synchronization is when all the remote servers have

jitters of 4000 with delay and reach values of zero.

remote refid st t when poll reach delay offset jitter

==============================================================================

LOCAL(0) LOCAL(0) 10 u - 64 0 0.000 0.000 4000.00

navobs1.oar.net 0.0.0.0 16 u - 64 0 0.000 0.000 4000.00

darkcity.cerias 0.0.0.0 16 u - 64 0 0.000 0.000 4000.00

ntp-2.gw.uiuc.e 0.0.0.0 16 u - 64 0 0.000 0.000 4000.00

This could be caused by:

• The restrict default ignore statement in the /etc/ntp.conf file not being

commented out;

• A firewall blocking access to your Internet NTP servers over port UDP 123.

Useful troubleshooting command (must have the ntpd daemon service stopped to use this):

• ntptrace –d –v <time_server>

Test NTP

Want to test the whole thing? Set your system and hardware clock to a wacked date, like

follows:

date 0603008501999 (this sets the current time on the software clock to June 3, 1999,

8:50am

hwclock --systohc (this sets the hardware clock to match the software clock)

Now, reboot the server and see if both of the clocks re-synched properly by issuing the following

two commands to check the software and hardware clocks, respectively:

date

hwclock

If you see some errors such as set_rtc_mmss: can’t update from x to x (where x = a

number), then you need to manually set the hardware clock. This error stems from a known

kernel issue (as of October 27, 2003) when the hardware clock is off from the software clock by

more than some amount (there seems to be some debate as to what that amount is). To fix this,

set the clock manually and reboot to see if the error(s) go away:

hwclock –systohc

reboot

1 2 ... 29 30 31 32 33 34 35 36 37 38 39 ... 59 60

Keine Kommentare

Red Hat NETSCAPE MANAGEMENT SYSTEM 6.0 - COMMAND-LINE Bedienungsanleitung Seite 34