Re: Plugin XEN Nagios

Jose Oliveira <[email protected]>
Newsgroups gmane.network.nagios.user.brazil
Message-ID <[email protected]>
Ok Lucio
No seu server XEN temos então o seguinte serviço no NRPE:
command[check_xenvm]=/usr/lib/nagios/plugins/check_xenvm -w 2 -c 0 # XEN
Lucio


No seu servidor de Nagios, mandando a linha abaixo no prompt, o que vc
obtem?

check_nrpe -H host_do_xen -p 5666 -c check_xenvm


Observei que o seu NRPE só está aceitando conexões locais. Mude a linha
server_address=127.0.0.1
para o IP da rede local, através da qual o nagios chegará ao seu servidor.


Mude tambem
allowed_hosts=127.0.0.1
Para o IP do servidor do Nagios.


Acho que vai dar certo...



2009/7/24 Lucio Antonio de Carvalho Junior <[email protected]>

> BLZ
>
>
> #############################################################################
> # Sample NRPE Config File
> # Written by: Ethan Galstad ([email protected])
> #
> # Last Modified: 11-23-2007
> #
> # NOTES:
> # This is a sample configuration file for the NRPE daemon.  It needs to be
> # located on the remote host that is running the NRPE daemon, not the host
> # from which the check_nrpe client is being executed.
>
> #############################################################################
>
>
> # LOG FACILITY
> # The syslog facility that should be used for logging purposes.
>
> log_facility=daemon
>
>
>
> # PID FILE
> # The name of the file in which the NRPE daemon should write it's process
> ID
> # number.  The file is only written if the NRPE daemon is started by the
> root
> # user and is running in standalone mode.
>
> pid_file=/var/run/nrpe.pid
>
>
>
> # PORT NUMBER
> # Port number we should wait for connections on.
> # NOTE: This must be a non-priviledged port (i.e. > 1024).
> # NOTE: This option is ignored if NRPE is running under either inetd or
> xinetd
>
> 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.
> # NOTE: This option is ignored if NRPE is running under either inetd or
> xinetd
>
> #server_address=127.0.0.1
>
>
>
> # NRPE USER
> # This determines the effective user that the NRPE daemon should run as.
> # You can either supply a username or a UID.
> #
> # NOTE: This option is ignored if NRPE is running under either inetd or
> xinetd
>
> nrpe_user=nagios
>
>
>
> # NRPE GROUP
> # This determines the effective group that the NRPE daemon should run as.
> # You can either supply a group name or a GID.
> #
> # NOTE: This option is ignored if NRPE is running under either inetd or
> xinetd
>
> nrpe_group=nagios
>
>
>
> # ALLOWED HOST ADDRESSES
> # This is an optional comma-delimited list of IP address or hostnames
> # that are allowed to talk to the NRPE daemon.
> #
> # Note: The daemon only does rudimentary checking of the client's IP
> # address.  I would highly recommend adding entries in your
> /etc/hosts.allow
> # file to allow only the specified host to connect to the port
> # you are running this daemon on.
> #
> # NOTE: This option is ignored if NRPE is running under either inetd or
> xinetd
>
> allowed_hosts=127.0.0.1
>
>
>
> # COMMAND ARGUMENT PROCESSING
> # This option determines whether or not the NRPE daemon will allow clients
> # to specify arguments to commands that are executed.  This option only
> works
> # if the daemon was configured with the --enable-command-args configure
> script
> # option.
> #
> # *** ENABLING THIS OPTION IS A SECURITY RISK! ***
> # Read the SECURITY file for information on some of the security
> implications
> # of enabling this variable.
> #
> # Values: 0=do not allow arguments, 1=allow command arguments
>
> dont_blame_nrpe=0
>
>
>
> # COMMAND PREFIX
> # This option allows you to prefix all commands with a user-defined string.
> # A space is automatically added between the specified prefix string and
> the
> # command line from the command definition.
> #
> # *** THIS EXAMPLE MAY POSE A POTENTIAL SECURITY RISK, SO USE WITH CAUTION!
> ***
> # Usage scenario:
> # Execute restricted commmands using sudo.  For this to work, you need to
> add
> # the nagios user to your /etc/sudoers.  An example entry for alllowing
> # execution of the plugins from might be:
> #
> # nagios          ALL=(ALL) NOPASSWD: /usr/lib/nagios/plugins/
> #
> # This lets the nagios user run all commands in that directory (and only
> them)
> # without asking for a password.  If you do this, make sure you don't give
> # random users write access to that directory or its contents!
>
> # command_prefix=/usr/bin/sudo
>
>
>
> # DEBUGGING OPTION
> # This option determines whether or not debugging messages are logged to
> the
> # syslog facility.
> # Values: 0=debugging off, 1=debugging on
>
> debug=0
>
>
>
> # COMMAND TIMEOUT
> # This specifies the maximum number of seconds that the NRPE daemon will
> # allow plugins to finish executing before killing them off.
>
> command_timeout=60
>
>
>
> # CONNECTION TIMEOUT
> # This specifies the maximum number of seconds that the NRPE daemon will
> # wait for a connection to be established before exiting. This is sometimes
> # seen where a network problem stops the SSL being established even though
> # all network sessions are connected. This causes the nrpe daemons to
> # accumulate, eating system resources. Do not set this too low.
>
> connection_timeout=300
>
>
>
> # WEEK RANDOM SEED OPTION
> # This directive allows you to use SSL even if your system does not have
> # a /dev/random or /dev/urandom (on purpose or because the necessary
> patches
> # were not applied). The random number generator will be seeded from a file
> # which is either a file pointed to by the environment valiable $RANDFILE
> # or $HOME/.rnd. If neither exists, the pseudo random number generator will
> # be initialized and a warning will be issued.
> # Values: 0=only seed from /dev/[u]random, 1=also seed from weak randomness
>
> #allow_weak_random_seed=1
>
>
>
> # 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).
>
> #include_dir=<somedirectory>
> #include_dir=<someotherdirectory>
>
>
>
> # 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 /usr/local/nagios/libexec
> # 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 hardcoded command arguments...
>
> command[check_users]=/usr/lib/nagios/plugins/check_users -w 5 -c 10
> command[check_load]=/usr/lib/nagios/plugins/check_load -w 15,10,5 -c
> 30,25,20
> command[check_hda1]=/usr/lib/nagios/plugins/check_disk -w 20% -c 10% -p
> /dev/hda1
> command[check_zombie_procs]=/usr/lib/nagios/plugins/check_procs -w 5 -c 10
> -s Z
> command[check_total_procs]=/usr/lib/nagios/plugins/check_procs -w 150 -c
> 200
> command[check_xenvm]=/usr/lib/nagios/plugins/check_xenvm -w 2 -c 0 # XEN
> Lucio
>
> # The following examples allow user-supplied arguments and can
> # only be used if the NRPE daemon was compiled with support for
> # command arguments *AND* the dont_blame_nrpe directive in this
> # config file is set to '1'.  This poses a potential security risk, so
> # make sure you read the SECURITY file before doing this.
>
> #command[check_users]=/usr/lib/nagios/plugins/check_users -w $ARG1$ -c
> $ARG2$
> #command[check_load]=/usr/lib/nagios/plugins/check_load -w $ARG1$ -c $ARG2$
> #command[check_disk]=/usr/lib/nagios/plugins/check_disk -w $ARG1$ -c $ARG2$
> -p $ARG3$
> #command[check_procs]=/usr/lib/nagios/plugins/check_procs -w $ARG1$ -c
> $ARG2$ -s $ARG3$
>
> #
> # local configuration:
> #    if you'd prefer, you can instead place directives here
> include=/etc/nagios/nrpe_local.cfg
>
> #
> # you can place your config snipplets into nrpe.d/
> include_dir=/etc/nagios/nrpe.d/
>
>
>
>
> Em 23/07/2009 às 10:58 horas, "Jose Oliveira" <[email protected]>
> escreveu:
>
> Manda ai então o pedaço do nrpe.cfg que define o comando, que está no seu
> servidor Xen, pra gente dar um pitaco...
>
>
>
> 2009/7/23 Lucio Antonio de Carvalho Junior <[email protected]>
>
>> Então ja instalei (eu acho ) no servidor quanto no cliente
>>
>>
>> Em 22/07/2009 às 22:29 horas, "Jose Oliveira" <[email protected]>
>> escreveu:
>>
>> Olá colega
>>
>> Estou imaginando que o seu nagios dora na máquina A e o Xen serve na
>> máquina B.
>>
>> Se estou correto, voce precisa instalar na maquina B o nrpe e configurar
>> nele este plugin.
>>
>> No nagios, voce chama o check__nrpe passando o nome que colocastes no nrpe
>> do host do Xen.
>>
>>
>>
>> PS: Registre-se na lista-nagios acessando
>> <https://lists.sourceforge.net/lists/listinfo/nagios-users-br><https://lists.sourceforge.net/lists/listinfo/nagios-users-br>
>> https://lists.sourceforge.net/lists/listinfo/nagios-users-br
>>
>>
>> Abraços
>>
>>
>> 2009/7/22 Lucio A, de Carvalho Junior <[email protected]>
>>
>>> Estou tendo dificuldade para instalar o plungin do XEN do Nagios:
>>>
>>> esse é o plugin para os intereçados :
>>>
>>> #!/bin/sh
>>> #
>>> # COPYRIGHT    : (c) 2006 SUSE Linux GmbH. All rights reserved.
>>> #
>>> # AUTHOR       : Axel Schmidt
>>> #
>>> # BELONGS TO   : NLPOS/SLEPOS/Xen Nagios Integration
>>> #
>>> # DESCRIPTION  : Runs "xm list" and returns the available xen vms
>>> #
>>> # $Revision: 1.0 $
>>> #
>>> # Permission to use, copy, modify, distribute, and sell this software
>>> # and its documentation for any purpose is hereby granted without fee,
>>> # provided that the above copyright notice appear in all copies and that
>>> # both that copyright notice and this permission notice appear in
>>> # supporting documentation.
>>>
>>> # The above copyright notice and this permission notice shall be
>>> # included in all copies or substantial portions of the Software.
>>>
>>> # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
>>> # EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
>>> # MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
>>> # IN NO EVENT SHALL THE AUTHOR OR SUSE BE LIABLE FOR ANY CLAIM, DAMAGES
>>> # OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
>>> # OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR
>>> # THE USE OR OTHER DEALINGS IN THE SOFTWARE.
>>>
>>> PARM1=$1
>>> WARN=$2
>>> PARM2=$3
>>> CRIT=$4
>>>
>>> if [ "$PARM2" != "-c" -o "$CRIT" == "" ]; then
>>>        echo "Usage: $0 -w <warning> -c <critical>"
>>> # Nagios exit code 3 = status UNKNOWN = orange
>>>
>>> if [ "$PARM1" != "-h" ]; then
>>>        exit 3
>>>   else
>>>        echo ""
>>>        echo " -w = Minimum Number of Xen VMs to activate a warning
>>> message."
>>>        echo " -c = Number of Xen VMs to activate a critical message."
>>>        echo " -h = This help message."
>>>        exit 3
>>>   fi
>>> fi
>>>
>>> RUNNING=$(sudo /usr/sbin/xm list | awk '!/[DN]/  {print $1 }')
>>> NBVMS=$(echo $RUNNING | wc -w)
>>> HNAME=$(hostname)
>>>
>>> #echo "Xen Running =" $RUNNING
>>>
>>> if [ "$NBVMS" -le "$CRIT" ]; then
>>>        echo "Critical Xen VMs Usage - Total NB: $NBVMS - detected VMs:
>>> $RUNNING"
>>> # Nagios exit code 2 = status CRITICAL = red
>>>        exit 2
>>>        else if [ "$NBVMS" -le "$WARN" ]; then
>>>           echo "Warning Xen VMs Usage - Total NB: $NBVMS - detected
>>> VMs: $RUNNING"
>>> # Nagios exit code 1 = status WARNING = yellow
>>>           exit 1
>>>        else
>>>            echo "OK: Xen Hypervisor \"$HNAME\" is running Xen VMs:
>>> $RUNNING"
>>> # Nagios exit code 0 = status OK = green
>>>            exit 0
>>>        fi
>>> fi
>>> ##  FIM
>>>
>>>
>>> Retirado do proprio site da Novell :
>>>  <http://www.novell.com/coolsolutions/feature/19490.html><http://www.novell.com/coolsolutions/feature/19490.html>
>>> http://www.novell.com/coolsolutions/feature/19490.html
>>>
>>> Eu coloque a entrada do comando no /etc/nagios3/commands.cfg :
>>>
>>> ### added for Xen VM Monitoring
>>>
>>> define command{
>>>        command_name    check_xenvm
>>>        command_line    $USER1$/check_xenvm -w $ARG1$ -c $ARG2$
>>>        }
>>>
>>> Já reiniciei os seviços do nagios e o nrpe e continua com mesmo error:
>>>
>>> Warning: Return code of 127 for check of service 'Monitor XEN' on
>>> host 'fermat1' was out of bounds. Make sure the plugin you're trying to
>>> run
>>> actually exists.
>>>
>>> Então ele falar q o plugin não está funcionando, porem, fiz os teste
>>> local e funciou, será q tenho q colocar esse plugin em outro lugar ?
>>>
>>>
>>> Alguem ja usou esse plugin ?
>>>
>>> Obrigado
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> --
>>> [email protected] mailing list
>>>  <https://lists.sourceforge.net/lists/listinfo/nagios-users-br><https://lists.sourceforge.net/lists/listinfo/nagios-users-br>
>>> https://lists.sourceforge.net/lists/listinfo/nagios-users-br
>>> Wiki: <http://nagios-br.sf.net/wiki> <http://nagios-br.sf.net/wiki>
>>> http://nagios-br.sf.net/wiki
>>>
>>
>>
>>
>> --
>> Abraços
>> JGeraldo
>>
>>
>>
>>
>
>
> --
> Abraços
> JGeraldo
>
>
>
>


-- 
Abraços
JGeraldo
------------------------------------------------------------------------------
-- 
[email protected] mailing list
https://lists.sourceforge.net/lists/listinfo/nagios-users-br
Wiki: http://nagios-br.sf.net/wiki
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.