NSClient++ Help (#1) - Connection refused (#47) - Message List

Connection refused

I'm having a problem with a XP Pro machine; when trying to perform a check from a Fedora 7 box I get the following message:

[root@kronos libexec]# ./check_nt -H192.168.16.115 -vUPTIME -spassword Connection refused could not fetch information from server

I've tried and tried to figure out where I have gone wrong, but so far, no luck.

XP Pro config file listed below.

[modules]

# NSCLIENT++ MODULES # A list with DLLs to load at startup.

FileLogger.dll CheckSystem.dll CheckDisk.dll NSClientListener.dll NRPEListener.dll SysTray.dll CheckEventLog.dll CheckHelpers.dll

# CheckWMI IS AN EXTREM EARLY IDEA SO DONT USE FOR PRODUCTION ENVIROMNEMTS! ;CheckWMI.dll

# RemoteConfiguration IS AN EXTREM EARLY IDEA SO DONT USE FOR PRODUCTION ENVIROMNEMTS! ;RemoteConfiguration.dll

[Settings] # OBFUSCATED PASSWORD # This is the same as the password option but here you can store the password in an obfuscated manner. # *NOTICE* obfuscation is *NOT* the same as encryption, someone with access to this file can still figure out the # password. Its just a bit harder to do it at first glance. ;obfuscated_password=Jw0KAUUdXlAAUwASDAAB

# PASSWORD # This is the password (-s) that is required to access NSClient remotely. If you leave this blank everyone will be able to access the daemon remotly. password=password

# ALLOWED HOST ADDRESSES # This is a comma-delimited list of IP address of hosts that are allowed to talk to the all daemons. # If leave this blank anyone can access the deamon remotly (NSClient still requires a valid password). # The syntax is host or ip/mask so 192.168.0.0/24 will allow anyone on that subnet access ;allowed_hosts=127.0.0.1/32

allowed_hosts=192.168.16.23

# USE THIS FILE # Use the INI file as opposed to the registry if this is 0 and the use_reg in the registry is set to 1 # the registry will be used instead. use_file=1

[log] # LOG DEBUG # Set to 1 if you want debug message printed in the log file (debug messages are always printed to stdout when run with -test) ;debug=1

# LOG FILE # The file to print log statements to file=NSC.log

# LOG DATE MASK # The format to for the date/time part of the log entry written to file. date_mask=%Y-%m-%d %H:%M:%S

[NSClient] # ALLOWED HOST ADDRESSES # This is a comma-delimited list of IP address of hosts that are allowed to talk to NSClient deamon. # If you leave this blank the global version will be used instead. allowed_hosts=192.168.16.23

# NSCLIENT PORT NUMBER # This is the port the NSClientListener.dll will listen to. port=12489

# BIND TO ADDRESS # Allows you to bind server to a specific local address. This has to be a dotted ip adress not a hostname. # Leaving this blank will bind to all avalible IP adresses. ;bind_to_address=

[Check System] # CPU BUFFER SIZE # Can be anything ranging from 1s (for 1 second) to 10w for 10 weeks. Notice that a larger buffer will waste memory # so don't use a larger buffer then you need (ie. the longest check you do +1). CPUBufferSize=1h

# CHECK RESOLUTION # The resolution to check values (currently only CPU). # The value is entered in 1/10:th of a second and the default is 10 (which means ones every second) CheckResolution?=10

[NRPE] # NRPE PORT NUMBER # This is the port the NRPEListener.dll will listen to. port=5666

# COMMAND TIMEOUT # This specifies the maximum number of seconds that the NRPE daemon will allow plug-ins to finish executing before killing them off. command_timeout=60

# COMMAND ARGUMENT PROCESSING # This option determines whether or not the NRPE daemon will allow clients to specify arguments to commands that are executed. allow_arguments=1

# COMMAND ALLOW NASTY META CHARS # This option determines whether or not the NRPE daemon will allow clients to specify nasty (as in |`&><'"\[]{}) characters in arguments. ;allow_nasty_meta_chars=0

# USE SSL SOCKET # This option controls if SSL should be used on the socket. ;use_ssl=1

# BIND TO ADDRESS # Allows you to bind server to a specific local address. This has to be a dotted ip adress not a hostname. # Leaving this blank will bind to all avalible IP adresses. ; bind_to_address=

# ALLOWED HOST ADDRESSES # This is a comma-delimited list of IP address of hosts that are allowed to talk to NRPE deamon. # If you leave this blank the global version will be used instead. ;allowed_hosts=

# SCRIPT DIRECTORY # All files in this directory will become check commands. # *WARNING* This is undoubtedly dangerous so use with care! ;script_dir=scripts\

[NRPE Handlers] # COMMAND DEFINITIONS # Command definitions that this daemon will run. # Can be either NRPE syntax: ;command[check_users]=/usr/local/nagios/libexec/check_users -w 5 -c 10

# Or simplified syntax: ;test=c:\test.bat foo $ARG1$ bar ;check_disk1=/usr/local/nagios/libexec/check_disk -w 5 -c 10

# Or even loopback (inject) syntax (to run internal commands) # This is a way to run "NSClient" commands and other internal module commands such as check eventlog etc. ;check_cpu=inject checkCPU warn=80 crit=90 5 10 15 ;check_eventlog=inject CheckEventLog Application warn.require.eventType=error warn.require.eventType=warning critical.require.eventType=error critical.exclude.eventType=info truncate=1024 descriptions ;check_disk_c=inject CheckFileSize ShowAll MaxWarn=1024M MaxCrit=4096M File:WIN=c:\ATI\*.*

# But be careful: # dont_check=inject dont_check This will "loop forever" so be careful with the inject command... # Check some escapings... ; check_escape=inject CheckFileSize ShowAll MaxWarn=1024M MaxCrit=4096M "File: foo \" WIN=c:
WINDOWS
*.*"

# Some real world samples ;nrpe_cpu=inject checkCPU warn=80 crit=90 5 10 15 ;nrpe_ok=scripts\ok.bat

;[includes] # The order when used is "reversed" thus the last included file will be "first" # Included files can include other files (be carefull only do basic recursive checking)

; myotherfile.ini ; real.ini

The service is installed and running ok, no Windows firewall present... but strangely I see no open port (via netstat -a).

Fedora box is running nagios plugins 1.4.7

Any ideas?

  • Message #55

    Humm, have you checked the ports? (nsclient++ does not use the "regular" nsclient port so you need to change that)

    (This was as the "Normal" nsclient port caused problems with exchange)

    • Message #56

      Same problem here: I can start NSClient++-Win32-2007-09-11 without any trouble using a config file which works with Versions from June 2007. Can't produce a debug file, nsclient++ is running, but doesn't open any port or writes anything to the debug file.

      Starting with nsclient++ /test failed: NRPEListener is missing SSLEAY32.DLL?

      Huh?

      wob

      • Message #57

        ahhh... could be when I changed for 64bit build stuff I managed to remove some static links then... that might explain it...

        MickeM

      • Message #60

        Try the new "NSClient++-Win32-20070925-0646.zip" and see if that works better...

    • Message #58

      Same problem here: I can start NSClient++-Win32-2007-09-11 without any trouble using a config file which works with Versions from June 2007. Can't produce a debug file, nsclient++ is running, but doesn't open any port or writes anything to the debug file.

      Starting with nsclient++ /test failed: NRPEListener is missing SSLEAY32.DLL?

      Huh?

      wob

      • Message #59

        Oops, sorry for double posting (was reloading browser from wrong window)

        wob

Subscriptions