nsclient++ configuration, i am lost

[ThomasC.]

First of all, thanks for your help.

> First, unless you have a specific need for it, I would disallow "nasty 
> metacharacters."  They can, indeed, be nasty. :)

Done

> Second, for the space in "Program Files", put quotes around the entire 
> path and filename.  I believe you should use doublequotes, but I'm not 
> sure.  I will check this on Monday.
> Try:
> ../libexec/check_nrpe -H catorsv03 -c check_exchangeDB -a MaxWarn=15G 
> MaxCrit=16G File="d:\Program Files\Exchsrvr\MDBDATA\priv1.stm" 
> File="d:\Program Files\Exchsrvr\MDBDATA\priv1.edb"
>

Done too


Anyway i don't think it will work. I still get that error :

2006-04-24 10:49:17: debug:.\NSClient++.cpp:305: Loading plugin: 
NSClient server...
2006-04-24 10:49:17: error:../../include\Socket.h:443: bind failed: 10048

Besides,
The command use check_nrpe

--> in NSC.ini i got
[NRPE Handlers]
check_exchangeDB=inject CheckFileSize MaxWarn=15G MaxCrit=16G 
File="d:\Program Files\Exchsrvr\MDBDATA\priv1.stm" File="d:\Program 
Files\Exchsrvr\MDBDATA\priv1.edb"

but the command is launched this way :

  ../libexec/check_nrpe -H catorsv03 -c check_exchangeDB -a MaxWarn=15G 
MaxCrit=16G File='d:\Program Files\Exchsrvr\MDBDATA\priv1.stm' 
File='d:\Program Files\Exchsrvr\MDBDATA\priv1.edb'

So i have to define it (the command check_exchangeDB)  in the nrpe.cfg 
file in order to work? Or do nsclient++ uses nrpe automatically...


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Nagios-users mailing list
Nagios-users at 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