<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 11 (filtered medium)"> <style>  </style> </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> <o:p> </o:p> <o:p> </o:p> > -----Original Message----- > From: nagios-users-admin@lists.sourceforge.net [mailto:nagios-users- > admin@lists.sourceforge.net] On Behalf Of John Jolet > Sent: Friday, May 05, 2006 11:52 AM > To: nagios-users@lists.sourceforge.net > Subject: Re: [Nagios-users] Check_NTP issues > > On Friday 05 May 2006 12:10, Tiago Cruz wrote: > > Thanks again by your attention! :) > > > > John Jolet wrote: > > > did you run check_ntp -H localhost on the box in question? did it > return > > > okay? > > > > I'll post all the output here, because I'm not understanding what's can > be > > happing here :-( > > > > Trinity, IP 10.0.0.173 (Nagios Server) > > > > trinity:~# ntpq -p localhost > > remote refid st t when poll reach delay offset > > jitter > > > ========================================================================== > = > >=== 10.0.0.91 .INIT. 16 u 704 1024 0 0.000 0.000 > > 4000.00 > > > > trinity:~# /.../check_ntp -H localhost > > Argument "(not parsed)" isn't numeric in abs at /.../check_ntp line 355. > > NTP WARNING: Desynchronized peer server found > okay, first thing is that neither of those servers are synced with anyone. > if > they were synced, they would have a * next to the "remote" address. i'd > get > ntp working and synchronizing first, before I messed with checking that > service. If 10.0.0.91 is supposed to be the reference for the rest of > your > network, get him syncing to at least 3 servers on at least two strata > first. > If you want to email me offlist with your ntpd.conf file, i'll try to help > out some more. However, until ntp is actually working on the server > that's > supposed to be supplying your time locally, i think you're going to be > kinda > off-topic for this list with this issue.<o:p></o:p> <o:p> </o:p> 1. First check if ntp can set the date from a remote server<o:p></o:p> <o:p> </o:p> $ ntpdate 0.north-america.pool.ntp.org<o:p></o:p> <o:p> </o:p> 8 May 08:16:57 ntpdate[77470]: adjust time server 24.130.207.189 offset -0.018950 sec<o:p></o:p> <o:p> </o:p> 2. If you can then setup a basic ntp.conf<o:p></o:p> <o:p> </o:p> server 0.north-america.pool.ntp.org<o:p></o:p> server 1.north-america.pool.ntp.org<o:p></o:p> server 2.north-america.pool.ntp.org<o:p></o:p> server 3.north-america.pool.ntp.org<o:p></o:p> driftfile /etc/ntp.drift<o:p></o:p> <o:p> </o:p> 3. Then start ntpd<o:p></o:p> <o:p> </o:p> # ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid<o:p></o:p> <o:p> </o:p> Check the process table to see if it running, and check your messages file for errors. On FreeBSD there will be a startup message in the log.<o:p></o:p> <o:p> </o:p> May 8 08:20:37 test3 ntpd[77481]: ntpd 4.2.0-a Thu Nov 3 07:34:18 UTC 2005 (1)<o:p></o:p> <o:p> </o:p> 4. If its running run ntpq to see its status<o:p></o:p> <o:p> </o:p> # ntpq -p<o:p></o:p> <o:p> </o:p> remote refid st t when poll reach delay offset jitter<o:p></o:p> ==============================================================================<o:p></o:p> 207.245.43.147 132.246.168.164 3 u 57 64 3 103.767 -114.87 7.123<o:p></o:p> dworley.hsd1.ma 131.107.1.10 2 u 53 64 3 81.996 14.393 1.338<o:p></o:p> S01060007952c37 216.234.161.11 3 u 58 64 3 89.563 34.492 3.726<o:p></o:p> h-69-3-12-50.hs 129.6.15.28 2 u 55 64 3 52.325 9.224 1.694<o:p></o:p> <o:p> </o:p> Ed<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> </div> </body> </html>