Marco Your syntax looks correct, here are a couple examples from my system.. ./check_nrpe -H hostName -c check_load NOW: Mean:0.437500% Variance: 0.114844% CUMULATIVE: Mean:0.437500% Variance: 0.114844% ./check_nt -H hostName -p 1248 -v UPTIME System Uptime - 14 day(s) 19 hour(s) 55 minute(s)
Hope that helps Dany Allard -----Original Message----- From: Marco Borsani [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 22, 2006 1:50 AM To: Dany Allard; 'NAGIOS' Subject: R: R: [Nagios-users] I: NSClient++ configuration problems Hi May someone give me any examples of commands to use to communicate with NSClient++? I tried: ./check_nt -H 151.x.x.x -v USEDDISKSPACE -l check_disk_c Where "check_disk_c" is a line uncommented in the nsc.ini file The answer is: "wrong -l argument" Or ./check_nrpe -H 151.x.x.x -c check_users Where "check_users" is a line uncommented in the nsc.ini file The answer is: "CHECK_NRPE: Error receiving data from host" May I use same "check_nrpe" that I am using for Unix systems? And same "check_nt" that I am using with old NSClient agent? Regards Marco -}-----Messaggio originale----- -}Da: [EMAIL PROTECTED] -}[mailto:[EMAIL PROTECTED] Per conto -}di Dany Allard -}Inviato: venerdì 17 febbraio 2006 19.20 -}A: NAGIOS -}Oggetto: RE: R: [Nagios-users] I: NSClient++ configuration problems -} -}Marco -} -} A quick test to make sure that the port is open is to telnet to it. -}> telnet YourHostname 1248 -} -}If you don't get a connection failed message the port should be open. -}If it fails with "..Could not open connection to the host..." -}then the port is being blocked somewhere. -} -} Dany Allard -} -}-----Original Message----- -}From: [EMAIL PROTECTED] -}[mailto:[EMAIL PROTECTED] On Behalf -}Of Marco Borsani -}Sent: Thursday, February 16, 2006 3:11 AM -}To: 'Michael Medin' -}Cc: 'NAGIOS' -}Subject: R: R: [Nagios-users] I: NSClient++ configuration problems -} -}I set 1248 (NSClient) and 5666 (NRPE) ports on NCS.INI file. -}I see both ports open (but associated to local IP 0.0.0.0), -}NSClient++ is running, but neither a check_nt, a check_nrpe -}or a check_tcp run correctly. -} -}Marco -}<snip> -}This message is intended only for the addressee and may -}contain personal, privileged or confidential information. -}If you have received this message in error, please notify the -}sender immediately and delete or destroy this message without -}making copies or opening any attachments. Any further -}distribution, duplication or disclosure is prohibited. -} -} -}------------------------------------------------------- -}This SF.net email is sponsored by: Splunk Inc. Do you grep -}through log files for problems? Stop! Download the new AJAX -}search engine that makes searching your log files as easy as -}surfing the web. DOWNLOAD SPLUNK! -}http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642 -}_______________________________________________ -}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 -} ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ 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
