R: R: R: R: check_memory does not work properly

[Marco Borsani]

Here it is.

 

./check_memory

 

NAME

  check_memory - custom script to check free memory (RAM) on SmartOS and
Linux machines

SYNOPSIS

  check_memory -w <warning> -c <critical> [<options>]

 

   -c, --critical <threshold% or threshold (MB)>

          Output this help text

   -w, --warning  <threshold% or threshold (MB)>

          Output this help text

   -d, --debug

          Output useful development debug info

   -h, --help

          Output this help text

 

 

 

Da: Deborah Martin [mailto:Deborah.Martin at kognitio.com] 
Inviato: giovedì 2 agosto 2012 17:02
A: Nagios Users List
Oggetto: Re: [Nagios-users] R: R: R: check_memory does not work properly

 

Can you run check_memory  plugin on the command line to get the full menu of
options available to the plugin and post it here. 

 

Regards,

Deborah 

 

 

From: Marco Borsani [mailto:m.borsani at it.net] 
Sent: 02 August 2012 15:28
To: 'Nagios Users List'
Subject: [Nagios-users] R: R: R: check_memory does not work properly

 

1)      Nagios user

2)      Yes

3)      Which details ? the point is that the plugin work correctly on
command line, but not on web gui


Command line out à OK + <memory info> + exit status 0

Web gui output à WARNING + (null message) + exit status 1

Log file à SERVICE ALERT: <host address>; <service
description>;WARNING;HARD;3;(null)

 

Regards

 

Da: James Osbourn [mailto:james.osbourn at citrix.com] 
Inviato: giovedì 2 agosto 2012 15:58
A: Nagios Users List
Oggetto: Re: [Nagios-users] R: R: check_memory does not work properly

 

What user is your Nagios server running as?  Is it the same as the user that
you are using on the command line?  Could you post more details about the
exact check_memory command that you are using, there are several of them out
there.  The output you are getting from Nagios, is this on the web gui, or
in one of the log files.

 

It could be many things related to the check scripts itself, who you are
running as where you are running the command.  The command line is not
always the same as when the server executes.

 

James

 

From: Marco Borsani [mailto:m.borsani at it.net] 
Sent: 02 August 2012 14:48
To: 'Nagios Users List'
Subject: [Nagios-users] R: R: check_memory does not work properly

 

No idea?

 

Regards

 

Da: Marco Borsani [mailto:m.borsani at it.net] 
Inviato: mercoledì 1 agosto 2012 09:19
A: 'Nagios Users List'
Oggetto: [Nagios-users] R: check_memory does not work properly

 

Commands.cfg

 

# 'check_local_memory' command definition

define command{

        command_name    check_local_memory

        command_line    $USER1$/check_memory -w $ARG1$ -c $ARG2$

        }

 

Services.cfg

 

define service{

        use                                               active-service


        host_name                               <ip- addresses>

        service_description               check_local_memory

        check_command                   check_local_memory!10%!5%

        max_check_attempts           3

        normal_check_interval         5

        retry_check_interval             1

        check_period                           24x7

        notification_interval              120

        notification_period                24x7

        notification_options              w,u,c,r

        notifications_enabled          1

        contact_groups                       CG_admin

        }

 

 

>From line command:

$> ./check_memory -w 10% -c 5%

OK - free memory is 27% which is within expected threshold|
mem=27;10;5;0;100

 

Regards

 

 

Da: Morris, Patrick [mailto:patrick.morris at hp.com] 
Inviato: martedì 31 luglio 2012 23:24
A: nagios-users at lists.sourceforge.net
Oggetto: Re: [Nagios-users] check_memory does not work properly

 

Posting your check configuration is really helpful in cases like this.  It’s
almost impossible to give a good answer without knowing how you’ve set the
check up.

 

From: Marco Borsani [mailto:m.borsani at it.net] 
Sent: Tuesday, July 31, 2012 6:52 AM
To: NAGIOS
Subject: [Nagios-users] check_memory does not work properly

 

Hi all

 

 

I am using a simple plug-in to check the nagios server memory.

 

When I run it like user Nagios, it works perfectly. I see this output:

OK - free memory is 40% which is within expected threshold|
mem=40;10;5;0;100

 

When I run it with Nagios program I receive this notification:

 


..

Command:         check_local_memory

State:                   WARNING

Message:            (null)


.

 

 

Any idea ?




This e-mail and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you are not the intended recipient, please delete this e-mail
immediately. Any unauthorised distribution or copying is strictly
prohibited.

Whilst Kognitio endeavours to prevent the transmission of viruses via
e-mail, we cannot guarantee that any e-mail or attachment is free from
computer viruses and you are strongly advised to undertake your own
anti-virus precautions. Kognitio grants no warranties regarding performance,
use or quality of any e-mail or attachment and undertakes no liability for
loss or damage, howsoever caused.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20120803/bd286d8b/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
-------------- next part --------------
_______________________________________________
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