On Jun 5, 2009, at 6:47 AM, Elvir Kuric wrote: > Hi all, > > I have an question related to monitoring windows machines using > nagios. I installed nagios on debian and it works > super. For monitoring windows client I installed on windows NSClient++ > - 0.3.5.2 2008-09-24, and set up NSC.ini ( among other configuration > elements ) > > command[check_load]=/usr/lib/nagios/plugins/check_load -w 15,10,5 -c > 30,25,20 > ( just want to make first step with this ) > > When I execute from my linux -nagios server command as bellow > > /usr/lib/nagios/plugins# ./check_nrpe -H WIN_IP_ADDRESS -c check_load > > I got error: > > ExternalCommands: failed to create process > (/usr/lib/nagios/plugins/check_load -w 15,10,5 -c 30,25,20): 3: The > system cannot find the path specified.
I don't use nsclient++ but to help you understand the concepts and get you pointed in the right direction, check_nrpe contacts a daemon running on a remote host (NRPE or NSClient(++)) and asks that daemon to execute a plugin *installed and runnable* on the remote host. In your case, /usr/lib/nagios/plugins/check_load is almost certainly not installed on your Windows machine, in that path, and it certainly isn't executable by Windows if it was (outside of using Cygwin). This documentation may be useful to you - http://nsclient.com/nscp/wiki/doc/usage/nagios The specific check you're looking for appears to be - http://nsclient.com/nscp/wiki/CheckCPU -- Marc ------------------------------------------------------------------------------ OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get _______________________________________________ Nagios-users mailing list [email protected] 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
