dimago
April 1, 2008, 11:03pm
1
hey all
regards;
Loose
April 2, 2008, 9:44am
2
Hi!
I can see a number of reasons for this problem.
make sure that you have the line:
It will create a log named “nrpe_nt.log” in the nrpe directory.
Hope this helps;
dimago
April 2, 2008, 11:24am
3
hey loose
debug is 1
and this log of the last line… all lines is same… then…
2008-04-02 08:19:34; 3884; 4;Host 10.0.0.9 is not allowed to talk to us!
in my nrpe if I put the server_address i cant start the service in windows… then, i leave this line…
this is my nrpe in windows…
PORT NUMBER
Port number we should wait for connections on.
server_port=5666
SERVER ADDRESS
Address that nrpe should bind to in case there are more than one interface
and you do not want nrpe to bind on all interfaces.
#server_address=10.0.0.9
ALLOWED HOST ADDRESSES
This is a comma-delimited list of IP address of hosts that are allowed
to talk to the NRPE daemon.
NOTE: The daemon only does rudimentary checking of the client’s IP
address.
allowed_hosts=127.0.0.0
COMMAND ARGUMENT PROCESSING
This option determines whether or not the NRPE_NT service will allow clients
to specify arguments to commands that are executed
*** ENABLING THIS OPTION IS A SECURITY RISK! ***
Values: 0=do not allow arguments, 1=allow command arguments
dont_blame_nrpe=0
DEBUGGING OPTION
This option determines whether or not debugging messages are logged to the
eventlog.
Values: 0=debugging off, 1=debugging on
debug=1
COMMAND TIMEOUT
This specifies the maximum number of seconds that the NRPE_NT service will
allow plugins to finish executing before killing them off.
command_timeout=60
INCLUDE CONFIG FILE
This directive allows you to include definitions from an external config file.
#include=<somefile.cfg>
INCLUDE CONFIG DIRECTORY
This directive allows you to include definitions from config files (with a
.cfg extension) in one or more directories (with recursion).
#NOTE: This option is currently ignored with NRPE_NT!
COMMAND DEFINITIONS
Command definitions that this daemon will run. Definitions
are in the following format:
command<command_name>]=<command_line>
When the daemon receives a request to return the results of <command_name>
it will execute the command specified by the <command_line> argument.
Unlike Nagios, the command line cannot contain macros - it must be
typed exactly as it should be executed.
Note: Any plugins that are used in the command lines must reside
on the machine that this daemon is running on! The examples below
assume that you have plugins installed in a D:\NRPE_NT
directory. Also note that you will have to modify the definitions below
to match the argument format the plugins expect. Remember, these are
examples only!
The following examples use no command arguments…
command[check_disk_c_win]=C:\Arquivos de programas\Nagios NRPE Agent\bin\check_pdm.exe --disk --drive C: -w 90 -c 95
The following examples allow user-supplied arguments and can
only be used if NRPE_NT was compiled with support for
command arguments AND the dont_blame_nrpe directive in this
config file is set to ‘1’…
#command [check_arg]=D:\NRPE_NT\testarg.cmd $ARG1$#command [check_arg]=D:\NRPE_NT\testarg.exe -H $ARG1$ -p $ARG2$
ty again
dimago
April 2, 2008, 11:33am
4
yeappp
its works now…
i put in allowed hostst nagios server IP and its works…
i need to fix now the parameter for disks…
in my web interface, in collumm Status information its bring the NRPE_NT version LOLZ
ty loose
we will talk a lot still
(or us if you post them here).