Andrew. I don't know what kind of time difference you can tolerate, but all of my RH servers lose about 12 seconds per day. Our business can tolerate that. I cron an update once per day a la: /usr/sbin/ntpdate our_AD_ntp_Server_IP >> /usr/local/scripts/logs/ntp_log.txt It's simple and it works. HTH Regards, Marshall >-----Original Message----- >From: redhat-list-bounces@xxxxxxxxxx >[mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of >Andrew.Bridgeman@xxxxxxxxxxxxxx >Sent: Thursday, August 09, 2007 4:06 AM >To: redhat-list@xxxxxxxxxx >Subject: NTP issue Continued > > > > > >Information about the NTP issue continued. > >I have run a few commands to try and find out why ntp is not working >correctly and the output of these commands are below. Could >someone tell me >anything that jumps out at them as the potential issue i >currently have. > >P.s I have set it up so we have two servers to look at incase >one is not >available. It seems to be polling OK but just does not change >the time on >the ntp client for some reason. > >Command = ntptrace -r 5 -d -v IP > >DoTransmit(IP) >DoTransmit to IP >ReceiveBuf(IP, IP) >server IP, port 123 >stratum 2, precision -6, leap 00 >refid server1_name delay 0.00029, dispersion 0.00000 offset -0.010315 >rootdelay 0.03125, rootdispersion 10.99594, synch dist 11.01157 >reference time: ca655261.636499dd Thu, Aug 9 2007 9:44:17.388 >originate timestamp: ca65541f.5343d541 Thu, Aug 9 2007 9:51:43.325 >transmit timestamp: ca65541f.55de0503 Thu, Aug 9 2007 9:51:43.335 > >DoTransmit(IP) >DoTransmit to IP >ReceiveBuf(IP, IP) >server IP, port 123 >stratum 1, precision -6, leap 00 >refid 'LOCL' delay 0.00011, dispersion 0.00000 offset -0.007780 >rootdelay 0.00000, rootdispersion 10.93810, synch dist 10.93810 >reference time: ca641cc8.fbef9db2 Wed, Aug 8 2007 11:43:20.984 >originate timestamp: ca65541f.54000000 Thu, Aug 9 2007 9:51:43.328 >transmit timestamp: ca65541f.55f9f01b Thu, Aug 9 2007 9:51:43.335 > >Command ntpq -p > > remote refid st t when poll reach delay >offset jitter >=============================================================== >=============== > > Server1_name .LOCL. 1 u 3 64 377 0.199 >-12.229 0.008 > Server2_name Server1_name 2 u 1 64 377 0.246 >-15.424 0.421 > >Regards > >Andrew Bridgeman > >----- Forwarded by Andrew Bridgeman/UK/Corus on 09/08/2007 09:49 ----- >|+-----------+----------------------------------------------| >|| Andrew | | >|| Bridgema| To: redhat-list@xxxxxxxxxx | >|| n | cc: | >|| | Subject: NTP issue Continued| >|| 08/08/20| | >|| 07 09:46| | >|| | | >|+-----------+----------------------------------------------| > > > > >I am still having problems getting 40 redhat machines to use ntp and >synchronise with our Windows 2003 Cluster. I have tried a >couple of things >suggested by people but have had no luck in fixing the issue. >It seems that >when I put either the IP of the cluster, the name of the cluster or the >fully qualified name of the cluster in the config files the ntp service >communicates with the Windows cluster straight away and all >the machines >are synchronised OK. The problem comes when i leave them >afterwards for an >hour or a day or even a week and look back at the time on the >machines and >they are all different. > >I read on the net that the communication used with ntp is UDP >over port 123 >and was wondering if i have some kind of polling issue after >the initial >start-up of ntp. Does anyone know more detail on how the ntp >part works. >i.e How often does is poll the cluster server for the time or >is there a >way of checking the communication on that port is working. > >Any help on this would be much appreciated. > >Regards > >Andrew Bridgeman > > >********************************************************************** >This transmission is confidential and must not be used or disclosed by >anyone other than the intended recipient. Neither Corus Group >Limited nor >any of its subsidiaries can accept any responsibility for any use or >misuse of the transmission by anyone. > >For address and company registration details of certain entities >within the Corus group of companies, please visit >http://www.corusgroup.com/entities > >********************************************************************** > > >-- >redhat-list mailing list >unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe >https://www.redhat.com/mailman/listinfo/redhat-list > -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
