Re: [Nagios-users] FPing command plugin says - Status UNKOWN

2007-03-15 Thread Marc Powell


> -Original Message-
> From: [EMAIL PROTECTED] [mailto:nagios-users-
> [EMAIL PROTECTED] On Behalf Of Nilesh Shastrakar
> Sent: Thursday, March 15, 2007 5:05 AM
> To: Lars Stavholm
> Cc: nagios-users@lists.sourceforge.net
> Subject: Re: [Nagios-users] FPing command plugin says - Status UNKOWN
> 
> Thanks its working now

Great example of why you should never test anything related to nagios as
root. You should perform plugin tests as the nagios user so you see
behavior as nagios would.

--
Marc

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null


Re: [Nagios-users] FPing command plugin says - Status UNKOWN

2007-03-15 Thread Nilesh Shastrakar
Thanks its working now
- Original Message - 
From: "Lars Stavholm" <[EMAIL PROTECTED]>
To: "Nilesh Shastrakar" <[EMAIL PROTECTED]>
Cc: 
Sent: Thursday, March 15, 2007 2:45 PM
Subject: Re: [Nagios-users] FPing command plugin says - Status UNKOWN


> Nilesh Shastrakar wrote:
>> Hello All,
>>
>> I have checked the check_fping plugin from shell it works fine
>> but when I add in command.cfg and localhost.cfg file the status shows me 
>> on webinterface is UNKNOWN
>>
>> [EMAIL PROTECTED] libexec]# ./check_fping -H 192.168.0.32 -v
>> /usr/sbin/fping -b 56 -c 1 192.168.0.32
>> 192.168.0.32 : [0], 84 bytes, 0.42 ms (0.42 avg, 0% loss)
>>
>> 192.168.0.32 : xmt/rcv/%loss = 1/1/0%, min/avg/max = 0.42/0.42/0.42
>> FPING OK - 192.168.0.32 (loss=0%, rta=0.42 ms)|loss=0%;;;0;100 
>> rta=0.000420s;;;0.00
>>
>> but in Nagios Weinterface it shows
>>
>>   Current Status:   UNKNOWN
>>(for 0d 0h 40m 42s)
>>   Status Information: /usr/sbin/fping -b 56 -c 1 192.168.0.32
>>   FPING UNKNOWN - 192.168.0.32
>
> It seems check_fping needs to be owned and executed by root,
> i.e. try:
>
> chown root check_fping
> chmod u+s check_fping
>
> /L
>
>> The Configurations in Command.cfg
>>
>> define command{
>> command_namecheck_fping
>> command_line$USER1$/check_fping -H 192.168.0.32 -v
>> }
>>
>> The Configuration localhost.cfg
>>
>> define service{
>> use local-service ; Name of 
>> service template to use
>> host_name   localhost
>> service_description PING to 192.168.0.32
>> check_command   check_fping
>> }
>>
>> Could someone help to solve the problem
>>
>> Thanks in advance
>> Nilesh.
>>
>>
>>
>> 
>>
>> -
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to share 
>> your
>> opinions on IT & business topics through brief surveys-and earn cash
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>>
>>
>> 
>>
>> ___
>> Nagios-users mailing list
>> Nagios-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/nagios-users
>> ::: Please include Nagios version, plugin version (-v) and OS when 
>> reporting any issue.
>> ::: Messages without supporting info will risk being sent to /dev/null
>
> 


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null


Re: [Nagios-users] FPing command plugin says - Status UNKOWN

2007-03-15 Thread Lars Stavholm
Nilesh Shastrakar wrote:
> Hello All,
> 
> I have checked the check_fping plugin from shell it works fine 
> but when I add in command.cfg and localhost.cfg file the status shows me on 
> webinterface is UNKNOWN
> 
> [EMAIL PROTECTED] libexec]# ./check_fping -H 192.168.0.32 -v
> /usr/sbin/fping -b 56 -c 1 192.168.0.32
> 192.168.0.32 : [0], 84 bytes, 0.42 ms (0.42 avg, 0% loss)
> 
> 192.168.0.32 : xmt/rcv/%loss = 1/1/0%, min/avg/max = 0.42/0.42/0.42
> FPING OK - 192.168.0.32 (loss=0%, rta=0.42 ms)|loss=0%;;;0;100 
> rta=0.000420s;;;0.00
> 
> but in Nagios Weinterface it shows 
> 
>   Current Status:   UNKNOWN  
>(for 0d 0h 40m 42s) 
>   Status Information: /usr/sbin/fping -b 56 -c 1 192.168.0.32
>   FPING UNKNOWN - 192.168.0.32

It seems check_fping needs to be owned and executed by root,
i.e. try:

chown root check_fping
chmod u+s check_fping

/L

> The Configurations in Command.cfg
> 
> define command{
> command_namecheck_fping
> command_line$USER1$/check_fping -H 192.168.0.32 -v
> }
> 
> The Configuration localhost.cfg
> 
> define service{
> use local-service ; Name of 
> service template to use
> host_name   localhost
> service_description PING to 192.168.0.32
> check_command   check_fping
> }
> 
> Could someone help to solve the problem
> 
> Thanks in advance
> Nilesh.
> 
> 
> 
> 
> 
> -
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> 
> 
> 
> 
> ___
> Nagios-users mailing list
> Nagios-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> ::: Please include Nagios version, plugin version (-v) and OS when reporting 
> any issue. 
> ::: Messages without supporting info will risk being sent to /dev/null


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null


[Nagios-users] FPing command plugin says - Status UNKOWN

2007-03-14 Thread Nilesh Shastrakar
Hello All,

I have checked the check_fping plugin from shell it works fine 
but when I add in command.cfg and localhost.cfg file the status shows me on 
webinterface is UNKNOWN

[EMAIL PROTECTED] libexec]# ./check_fping -H 192.168.0.32 -v
/usr/sbin/fping -b 56 -c 1 192.168.0.32
192.168.0.32 : [0], 84 bytes, 0.42 ms (0.42 avg, 0% loss)

192.168.0.32 : xmt/rcv/%loss = 1/1/0%, min/avg/max = 0.42/0.42/0.42
FPING OK - 192.168.0.32 (loss=0%, rta=0.42 ms)|loss=0%;;;0;100 
rta=0.000420s;;;0.00

but in Nagios Weinterface it shows 

  Current Status:   UNKNOWN  
   (for 0d 0h 40m 42s) 
  Status Information: /usr/sbin/fping -b 56 -c 1 192.168.0.32
  FPING UNKNOWN - 192.168.0.32
 

The Configurations in Command.cfg

define command{
command_namecheck_fping
command_line$USER1$/check_fping -H 192.168.0.32 -v
}

The Configuration localhost.cfg

define service{
use local-service ; Name of service 
template to use
host_name   localhost
service_description PING to 192.168.0.32
check_command   check_fping
}

Could someone help to solve the problem

Thanks in advance
Nilesh.
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null