I think I have found the problem, Please see the following theread
http://article.gmane.org/gmane.network.nagios.plugins.devel/6738
On Wed, Aug 19, 2009 at 9:54 AM, shadih rahman wrote:
> I am using nagios-3.0.6 and nagios plugins-1.4.13
>
> As suggested I have read the check_ping man page.
On Tue, 18 Aug 2009, shadih rahman wrote:
> All,
>My check ping result is not making sense. I have the following in
> commands.cfg
>
> define command{
> command_namecheck-host-alive
> command_line$USER1$/check_ping -H $HOSTADDRESS$ -t 45 -4 -w
> 3000.0,100% -c 3000.
please read
http://nagiosplugins.org/man/check_ping
syntax is
-w rta,pl -c rta,pl
rta==round trip average,
pl = packet lost
of course warning should be less than critical. You have all same..
try : -w 200.0 30 -c 300.0, 40
Nice regards,
2009/8/18 shadih rahman :
> All,
> My check pin
shadih rahman wrote:
> David,
>Thanks for your reply. I am ensuring one icmp packet by using -p option
> in my command definition. Please advise on this. Thanks
>
> On Tue, Jul 14, 2009 at 2:40 PM, David Rosenstrauch wrote:
>> The plugin issues 5 pings by default:
$USER1$/check_ping -H $H
shadih rahman wrote:
> Nagios uses check_ping for the host check of most hosts.
>
> The check is configured to send only one ping.
>
> So if Nagios receives a response, it is 0% packet loss.
>
> If no response, it is 100% packet loss.
> How is it possible
A work around would be to run the check every 4 minutes -- the arp entry
won't time out then
(It takes our boxes less than a milisecond to respond to an arp, 397ms
would imply to me that something else is going on -- isdn link
reaquiring etc)
--
Paul Weaver
Systems Development Engineer
News P
On Tue, Jul 15, 2008 at 10:51:37AM +0200, Andreas Ericsson wrote:
[ me: ]
> >I've left Jeff's quote in so you can see, Andreas, that you misread
> >him. He didn't say "SUID root". He said sudo -- he plans to set the
> >nagios Linux user up so it can sudo to run ping as root.
>
> Ah, right. Havin
Jay R. Ashworth wrote:
> On Mon, Jul 14, 2008 at 01:54:03PM +0200, Andreas Ericsson wrote:
>> Jeff Koch wrote:
>>> Thanks for your help. When we ran ping as nagios it bombed. Permissions on
>>> ping needed to be set SUID root so that an ICMP socket could be opened. We
>>> had changed that for sec
On Mon, Jul 14, 2008 at 01:54:03PM +0200, Andreas Ericsson wrote:
> Jeff Koch wrote:
> > Thanks for your help. When we ran ping as nagios it bombed. Permissions on
> > ping needed to be set SUID root so that an ICMP socket could be opened. We
> > had changed that for security reasons. We'll make
Hi,
> Changing /bin/ping to not be suid root for security reasons and then changing
> Nagios to be suid root to fix a problem this causes seems more than just a
> little backwards to me.
>
> Do "chmod 4711 /bin/ping" instead. ping is a simple program of ~4000 LoC. It
> has been thouroughly audit
Jeff Koch wrote:
> Hi Philipp:
>
> Thanks for your help. When we ran ping as nagios it bombed. Permissions on
> ping needed to be set SUID root so that an ICMP socket could be opened. We
> had changed that for security reasons. We'll make nagios sudo root for
> ping. That should solve the probl
Hi Philipp:
Thanks for your help. When we ran ping as nagios it bombed. Permissions on
ping needed to be set SUID root so that an ICMP socket could be opened. We
had changed that for security reasons. We'll make nagios sudo root for
ping. That should solve the problem.
At 12:56 PM 7/13/2008,
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:nagios-users-
> [EMAIL PROTECTED] On Behalf Of Ilia Anokhin
> Sent: Thursday, August 17, 2006 8:00 AM
> To: nagios-users@lists.sourceforge.net
> Subject: [Nagios-users] Check ping error code 139
>
> Hi everyone.
>
> I've faced a str
13 matches
Mail list logo
