ESXi Check

[James Pratt]

> -----Original Message-----
> From: Joseph L. Casale [mailto:JCasale at activenetwerx.com]
> Sent: Tuesday, February 17, 2009 3:29 PM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] ESXi Check
> 
> I am trying to implement the check_esx_wbem.py from nagiosexchange and
> from the cli I get a response so its setup correctly but my
implementation
> in Nagios seems to be not working as it returns null.
> 
> In resource.cfg I have:
> $USER13$=/usr/lib/nagios/plugins/contrib
> $USER14$=username
> $USER15$=password
> 
> In commands.cfg I have:
> define command{
>         command_name    check-esxi-host
>         command_line    $USER13$/check_esx_wbem.py
http://$HOSTADDRESS$:5989
> $USER14$ $USER15$
>         }
> 
> In my template I have:
> define service{
>         use                     generic-service
>         host_name               host.example.com
>         service_description     ESXi Health
>         check_command           check-esxi-host
>         }
> 
> Any ideas what could be wrong?
> Thanks!
> jl

Hi Joseph -

Check that nagios user can execute it at the command line like this:

su - nagios -c "/full/path/to/check_command -and -parms -go -here"

if it returns nothing, check the perms on the check_esx_wbem.py file ,
if they are 755 or better, I would look at why nagios can't run
python(?)... 


regards,
Jamie

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
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