FW: NSClient++ on windows machine

[Lars Stavholm]

Palle Jensen wrote:
> Hi to all,

Hej:)

> I have been trying to find out how you get the graphs for monitored
> service on Windows/Nsclient++.
> 
> It is working fine for the locahost (FC9) Memory, load, procs and users.
> I added a windows machine with NSClient++, I added the service Ping to
> both localhost and the windows machine, and the graphs are showing up
> fine. But when I add Memory, procs, load service to the windows machine
> no graphs shows. How come it works with ping for both localhost and
> Windows machine? Even though I made sure that the service_description is
> the same as for the localhost
> 
> I am about to go insain, please help? I know this belongs under
> NagiosGrapher mailinglist, and I posted there as well, but I got 0
> answers there, hoping that someone can help me here.

I'll just assume that you remembered to restart/reload
both NagiosGrapher and nagios when adding stuff in config.

There might be a difference in the performance data handed
back by NSClient as compared to the native check plugins.

The check_load, for instance, can be run manually. Now run the
check_load for the Windows boxes (whatever it's called) and
compare the output, especially the output to the righ of the '|'
character, i.e. the performance data delimiter. If they are not
the same, they wont fit the same graph definition.

Min you, I have no experience with NSClient at all, but still.

Cheers
/Lars

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
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