> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:nagios-users-
> [EMAIL PROTECTED] 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 :-(
>
> Tri
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 localho
On Friday 05 May 2006 10:03, Tiago Cruz wrote:
> John Jolet wrote:
> > not necessarily. You can use nrpe to run the check_ntp locally on those
> > hosts that do not need to listen to ntp requests from the net.
>
> Thanks!!!
> To begin a test, I did this:
>
> - Insert in nrpe.cfg one new command:
>
John Jolet wrote:
not necessarily. You can use nrpe to run the check_ntp locally on those hosts
that do not need to listen to ntp requests from the net.
Thanks!!!
To begin a test, I did this:
- Insert in nrpe.cfg one new command:
command[check_ntp]=/.../bin-1.4.2/libexec/check_ntp -H localho
On Friday 05 May 2006 07:36, Tiago Cruz wrote:
> Now, I'm just try find a way to monitory all the servers and discover how
> have a unsynchronized clock, but I'm not sure that what I have to do :)
>
> Please, say if I'm correct: All the servers MUST be listen in all
> interfaces, and not only in lo
Hugo van der Kooij wrote:
Yes, the ntpd daemon is only listen no 127.0.0.1. I did a test, please look:
Pardon me for noting. But shouldn't you setup ntp correctly before you
start to setup monitoring it? Untill ntp is working and keeping everything
in sync I would not spend another second
On Thu, 4 May 2006, Tiago Cruz wrote:
> Darren Dunham wrote:
>
> > This machine is not responding. It may not be running ntpd, or the
> > communication may be blocked in some manner (restrictions on the server,
> > firewall on the network, etc.)
>
> Yes, the ntpd daemon is only listen no 127.0.0.
Darren Dunham wrote:
This machine is not responding. It may not be running ntpd, or the
communication may be blocked in some manner (restrictions on the server,
firewall on the network, etc.)
Yes, the ntpd daemon is only listen no 127.0.0.1. I did a test, please look:
1- On host 10.0.0.91, i
> sidious:~# ntpq -p 10.0.0.19
> 10.0.0.19: timed out, nothing received
> ***Request timed out
This machine is not responding. It may not be running ntpd, or the
communication may be blocked in some manner (restrictions on the server,
firewall on the network, etc.)
> sidious:~# ntpq -p localhost
On Thursday 04 May 2006 14:21, Tiago Cruz wrote:
> John Jolet wrote:
> > On Thursday 04 May 2006 14:03, Tiago Cruz wrote:
> >> sidious:~# ./check_ntp -H 10.0.0.19
> >> Use of uninitialized value in division (/) at
> >> /interdotnet/tools/nagios/plugins/bin-1.4.2/libexec/check_ntp line 424.
> >> NTP
John Jolet wrote:
On Thursday 04 May 2006 14:03, Tiago Cruz wrote:
sidious:~# ./check_ntp -H 10.0.0.19
Use of uninitialized value in division (/) at
/interdotnet/tools/nagios/plugins/bin-1.4.2/libexec/check_ntp line 424.
NTP WARNING: Desynchronized peer server found|offset=-5.885026,
jitter=0,pe
On Thursday 04 May 2006 14:03, Tiago Cruz wrote:
> Hello all,
>
> I would like to know how the gentleman's are using the perl script
> called check_ntp, because I tried to use and have a lot of errors, like
> this:
>
> sidious:~# ./check_ntp -H 10.0.0.19
> Use of uninitialized value in division (/)
13 matches
Mail list logo
