Re: [Nagios-users] monitor directory size?

2006-02-15 Thread HP Geeza

nope no firewall getting in the way :-(

is there anything else i can try to fix this problem



From: Toto Capuccino <[EMAIL PROTECTED]>
To: HP Geeza <[EMAIL PROTECTED]>
CC: nagios-users@lists.sourceforge.net, [EMAIL PROTECTED]
Subject: Re: [Nagios-users] monitor directory size?
Date: Wed, 15 Feb 2006 18:28:25 +0100

Not sure, did you check firewall from both side.
Is nsclient installed as a service, take a look also at windows logs to see
errors.
2006/2/15, HP Geeza <[EMAIL PROTECTED]>:
>
> HI Toto,
>
> I've even tried what you suggested.but when i run: ./check_nrpe -H
>  -c check_cmd
>
> i get a connection refused :-(
>
> i'm even running the nsclient++ on the remote windows server as a local
> admin!
>
> here's a sample of the important bits out of my NSC.ini file:
>
> FileLogger.dll
> ;CheckSystem.dll
> CheckDisk.dll
> NSClientListener.dll
> NRPEListener.dll
> ;SysTray.dll
> ;CheckEventLog.dll
> ;CheckHelpers.dll
>
> ;# ALLOWED HOST ADDRESSES
> allowed_hosts=
>
> [NSClient]
> ;# NSCLIENT PORT NUMBER
> ;  This is the port the NSClientListener.dll will listen to.
> port=12489
>
> [NRPE]
> ;# NRPE PORT NUMBER
> ;  This is the port the NRPEListener.dll will listen to.
> port=5666
>
> [NRPE Handlers]
> command[check_cmd]=D:\hello.cmd
>
>
> any suggestions on what im doing wrong???
>
>
> >From: Toto Capuccino <[EMAIL PROTECTED]>
> >To: HP Geeza <[EMAIL PROTECTED]>
> >CC: nagios-users@lists.sourceforge.net, [EMAIL PROTECTED]
> >Subject: Re: [Nagios-users] monitor directory size?
> >Date: Wed, 15 Feb 2006 13:54:21 +0100
> >
> >Hi
> >
> >Everything is so well documented in nsclient++ doc that i wonder why 
you

> >prefer asking here. Anyway you should have first the check_nrpe plugin.
> >Then
> >you just have to define command in checkcommands using ./check_nrpe -H
> >hostname -c check_cmd
> >
> >define command {
> >
> > command_name Hello
> >
> > command_line check_nrpe -H $HOSTADDRESS$ -c check_cmd
> >
> >}
> >Please run check_nrpe -h to get the help of the plugin.
> >
> >cheers
> >2006/2/15, HP Geeza <[EMAIL PROTECTED]>:
> > >
> > > Hi All,
> > >
> > > I am having some difficulty with using nclient++ and was wondering 
if

> > > somebody could help??
> > >
> > > I have download nslicnet++ (from
> > > http://nscplus.medin.name/index.php/Main_Page) and installed it on a
> > > remote
> > > windows server.  I then modified the NSC.ini file and added a line:
> > >
> > > command[check_cmd]=D:\hello.cmd
> > >
> > > I then created a simple .cmd file called hello.cmd which contained 
the

> > > following:
> > >
> > > @echo off
> > > echo hello world
> > > exit 1
> > >
> > > MY QUESTION IS:
> > > what do i need to do/run on the nagios server inorder to run a check
> > > against
> > > hello.cmd for example?
> > >
> > >
> > > >From: Bill Jacqmein <[EMAIL PROTECTED]>
> > > >To: HP Geeza <[EMAIL PROTECTED]>
> > > >Subject: Re: [Nagios-users] monitor directory size?
> > > >Date: Tue, 14 Feb 2006 11:30:52 -0500
> > > >
> > > >in NSC.ini
> > > >
> > > >in the NRPE handlers section
> > > >
> > > >mycheck=c:\somecheck.bat
> > > >
> > > >
> > > >For coding the batch file
> > > >useful - 
http://nagiosplug.sourceforge.net/developer-guidelines.html

> > > >The main part is the return codes
> > > >
> > > >Numeric Value
> > > >
> > > >Service Status
> > > >
> > > >Status Description
> > > >
> > > >0
> > > >
> > > >OK
> > > >
> > > >The plugin was able to check the service and it appeared to be
> > > functioning
> > > >properly
> > > >
> > > >1
> > > >
> > > >Warning
> > > >
> > > >The plugin was able to check the service, but it appeared to be 
above

> > > some
> > > >"warning" threshold or did not appear to be working properly
> > > >
> > > >2
> > > >
> > > >Critical
> > > >
> > > >The plugin detected that either the service was not running or it 
was

> > > above
> > > >some "critical" thr

Re: [Nagios-users] monitor directory size?

2006-02-15 Thread HP Geeza

HI Toto,

I've even tried what you suggested.but when i run: ./check_nrpe -H 
 -c check_cmd


i get a connection refused :-(

i'm even running the nsclient++ on the remote windows server as a local 
admin!


here's a sample of the important bits out of my NSC.ini file:

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

;# ALLOWED HOST ADDRESSES
allowed_hosts=

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

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

[NRPE Handlers]
command[check_cmd]=D:\hello.cmd


any suggestions on what im doing wrong???



From: Toto Capuccino <[EMAIL PROTECTED]>
To: HP Geeza <[EMAIL PROTECTED]>
CC: nagios-users@lists.sourceforge.net, [EMAIL PROTECTED]
Subject: Re: [Nagios-users] monitor directory size?
Date: Wed, 15 Feb 2006 13:54:21 +0100

Hi

Everything is so well documented in nsclient++ doc that i wonder why you
prefer asking here. Anyway you should have first the check_nrpe plugin. 
Then

you just have to define command in checkcommands using ./check_nrpe -H
hostname -c check_cmd

define command {

command_name Hello

command_line check_nrpe -H $HOSTADDRESS$ -c check_cmd

}
Please run check_nrpe -h to get the help of the plugin.

cheers
2006/2/15, HP Geeza <[EMAIL PROTECTED]>:
>
> Hi All,
>
> I am having some difficulty with using nclient++ and was wondering if
> somebody could help??
>
> I have download nslicnet++ (from
> http://nscplus.medin.name/index.php/Main_Page) and installed it on a
> remote
> windows server.  I then modified the NSC.ini file and added a line:
>
> command[check_cmd]=D:\hello.cmd
>
> I then created a simple .cmd file called hello.cmd which contained the
> following:
>
> @echo off
> echo hello world
> exit 1
>
> MY QUESTION IS:
> what do i need to do/run on the nagios server inorder to run a check
> against
> hello.cmd for example?
>
>
> >From: Bill Jacqmein <[EMAIL PROTECTED]>
> >To: HP Geeza <[EMAIL PROTECTED]>
> >Subject: Re: [Nagios-users] monitor directory size?
> >Date: Tue, 14 Feb 2006 11:30:52 -0500
> >
> >in NSC.ini
> >
> >in the NRPE handlers section
> >
> >mycheck=c:\somecheck.bat
> >
> >
> >For coding the batch file
> >useful - http://nagiosplug.sourceforge.net/developer-guidelines.html
> >The main part is the return codes
> >
> >Numeric Value
> >
> >Service Status
> >
> >Status Description
> >
> >0
> >
> >OK
> >
> >The plugin was able to check the service and it appeared to be
> functioning
> >properly
> >
> >1
> >
> >Warning
> >
> >The plugin was able to check the service, but it appeared to be above
> some
> >"warning" threshold or did not appear to be working properly
> >
> >2
> >
> >Critical
> >
> >The plugin detected that either the service was not running or it was
> above
> >some "critical" threshold
> >
> >3
> >
> >Unknown
> >
> >Invalid command line arguments were supplied to the plugin or low-level
> >failures internal to the plugin (such as unable to fork, or open a tcp
> >socket) that prevent it from performing the specified operation.
> >Higher-level errors (such as name resolution errors, socket timeouts,
> etc)
> >are outside of the control of plugins and should generally NOT be
> reported
> >as UNKNOWN states.
> >
> >Hopeful this was enough get you closer to a solution. If not I have to
> >write
> >one in the near future so I will send how I went about creating the
> check.
> >
> >Thanks,
> >
> >   Bill
> >
> >On 2/14/06, HP Geeza <[EMAIL PROTECTED]> wrote:
> > >
> > > Hi Bill,
> > >
> > > Im affraid im having some trouble with nsclient++ and running a 
batch

> > > files
> > > via check_nrep.  Could you please help me with the syntax that i 
need

> to
> > > use
> > > to setup the check on both the nagios server and remote windows
> server.
> > >
> > > any help would be great!
> > >
> > >
> > > >From: Bill Jacqmein <[EMAIL PROTECTED]>
> > > >To: HP Geeza <[EMAIL PROTECTED]>
> > > >Subject: Re: [Nagios-users] monitor directory size?
> > > >Date: Mon, 13 Feb 2006 14:44:40 -0500
> > > >
> > > >nsclient++ has the ability to run batch files via check_nrep. Might
> be
> >an
> > &

Re: [Nagios-users] monitor directory size?

2006-02-15 Thread HP Geeza

Hi,

thanks for your relpy! - i have read the documentation but im affraid im 
still having trouble with a particular check.


I have compiled and installed the check_nrpe plugin on my nagios box...i 
then edited the following config files:  ive got a host setup


checkcommands.cfg
define command{
   command_namecheck_directory_size
   command_linecheck_nrpe -H $HOSTADDRESS$ -c CheckFileSize
   }

services.cfg
define service{
   use  generic-service ; Name 
of service template to use

   host_name   testServer
   service_description Directory Size
   check_commandcheck_directory_size
   }

NOW i have read the CheckDisk documentation for the nsclient++.  However i 
dont quiet understand how i setup the check in the NSC.ini file.  There is 
an example in the CheckDisk documentation section which has the following 
(this is what i almost need).


EXAMPLE 1:-

Check the size of the windows directory and make sure it stays below 1 
gigabyte:

CheckFileSize ShowAll MaxWarn=1024M MaxCrit=4096M File:WIN=c:\WINDOWS\*.*
WARNING: WIN: 2G (2325339822B)|WIN=2325339822;1073741824;4294967296

define command {
   command_name CheckFileSize
   command_line check_nrpe -H $HOSTADDRESS$ -p 5666 -c CheckFileSize -a 
ShowAll MaxWarn=$ARG1$ MaxCrit=$ARG2$ File:$ARG4$=$ARG5$

}

   check_command CheckFileSize!1024M!4096M!WIN!c:\WINDOWS\*.*


I am abit puzzled on what i need to enter in the NSC.ini file.
I have a directory on the 'd' drive called ghosti would like to monitor 
the size of this directory and raise an alert when it reaches say 200GB.


Could you please help me edit the NSC.ini file and perform this check???

your help will be much appreciated




From: Toto Capuccino <[EMAIL PROTECTED]>
To: HP Geeza <[EMAIL PROTECTED]>
CC: nagios-users@lists.sourceforge.net, [EMAIL PROTECTED]
Subject: Re: [Nagios-users] monitor directory size?
Date: Wed, 15 Feb 2006 13:54:21 +0100

Hi

Everything is so well documented in nsclient++ doc that i wonder why you
prefer asking here. Anyway you should have first the check_nrpe plugin. 
Then

you just have to define command in checkcommands using ./check_nrpe -H
hostname -c check_cmd

define command {

command_name Hello

command_line check_nrpe -H $HOSTADDRESS$ -c check_cmd

}
Please run check_nrpe -h to get the help of the plugin.

cheers
2006/2/15, HP Geeza <[EMAIL PROTECTED]>:
>
> Hi All,
>
> I am having some difficulty with using nclient++ and was wondering if
> somebody could help??
>
> I have download nslicnet++ (from
> http://nscplus.medin.name/index.php/Main_Page) and installed it on a
> remote
> windows server.  I then modified the NSC.ini file and added a line:
>
> command[check_cmd]=D:\hello.cmd
>
> I then created a simple .cmd file called hello.cmd which contained the
> following:
>
> @echo off
> echo hello world
> exit 1
>
> MY QUESTION IS:
> what do i need to do/run on the nagios server inorder to run a check
> against
> hello.cmd for example?
>
>
> >From: Bill Jacqmein <[EMAIL PROTECTED]>
> >To: HP Geeza <[EMAIL PROTECTED]>
> >Subject: Re: [Nagios-users] monitor directory size?
> >Date: Tue, 14 Feb 2006 11:30:52 -0500
> >
> >in NSC.ini
> >
> >in the NRPE handlers section
> >
> >mycheck=c:\somecheck.bat
> >
> >
> >For coding the batch file
> >useful - http://nagiosplug.sourceforge.net/developer-guidelines.html
> >The main part is the return codes
> >
> >Numeric Value
> >
> >Service Status
> >
> >Status Description
> >
> >0
> >
> >OK
> >
> >The plugin was able to check the service and it appeared to be
> functioning
> >properly
> >
> >1
> >
> >Warning
> >
> >The plugin was able to check the service, but it appeared to be above
> some
> >"warning" threshold or did not appear to be working properly
> >
> >2
> >
> >Critical
> >
> >The plugin detected that either the service was not running or it was
> above
> >some "critical" threshold
> >
> >3
> >
> >Unknown
> >
> >Invalid command line arguments were supplied to the plugin or low-level
> >failures internal to the plugin (such as unable to fork, or open a tcp
> >socket) that prevent it from performing the specified operation.
> >Higher-level errors (such as name resolution errors, socket timeouts,
> etc)
> >are outside of the control of plugins and should generally NOT be
> reported
> >as UNKNOWN states.
> >
> >Hopeful this was enough get you closer to a solution. If not I have to
> >write
> 

Re: [Nagios-users] monitor directory size?

2006-02-15 Thread HP Geeza

Appologies for the numerous emails!!

I noticed that nsclient++ has a checkDisk.dll which you can use to check the 
size of one of more files or directories.  So this sounds like what i need 
to use.but i still dont know how to check this from the nagios server - 
is there another plugin that i need to run on the nagios serverwhat to 
have in the config files???




From: Bill Jacqmein <[EMAIL PROTECTED]>
To: HP Geeza <[EMAIL PROTECTED]>
Subject: Re: [Nagios-users] monitor directory size?
Date: Tue, 14 Feb 2006 11:30:52 -0500

in NSC.ini

in the NRPE handlers section

mycheck=c:\somecheck.bat


For coding the batch file
useful - http://nagiosplug.sourceforge.net/developer-guidelines.html
The main part is the return codes

Numeric Value

Service Status

Status Description

0

OK

The plugin was able to check the service and it appeared to be functioning
properly

1

Warning

The plugin was able to check the service, but it appeared to be above some
"warning" threshold or did not appear to be working properly

2

Critical

The plugin detected that either the service was not running or it was above
some "critical" threshold

3

Unknown

Invalid command line arguments were supplied to the plugin or low-level
failures internal to the plugin (such as unable to fork, or open a tcp
socket) that prevent it from performing the specified operation.
Higher-level errors (such as name resolution errors, socket timeouts, etc)
are outside of the control of plugins and should generally NOT be reported
as UNKNOWN states.

Hopeful this was enough get you closer to a solution. If not I have to 
write

one in the near future so I will send how I went about creating the check.

Thanks,

  Bill

On 2/14/06, HP Geeza <[EMAIL PROTECTED]> wrote:
>
> Hi Bill,
>
> Im affraid im having some trouble with nsclient++ and running a batch
> files
> via check_nrep.  Could you please help me with the syntax that i need to
> use
> to setup the check on both the nagios server and remote windows server.
>
> any help would be great!
>
>
> >From: Bill Jacqmein <[EMAIL PROTECTED]>
> >To: HP Geeza <[EMAIL PROTECTED]>
> >Subject: Re: [Nagios-users] monitor directory size?
> >Date: Mon, 13 Feb 2006 14:44:40 -0500
> >
> >nsclient++ has the ability to run batch files via check_nrep. Might be 
an

> >option to do a dir and parse the filesize out of that.
> >
> >On 2/13/06, HP Geeza <[EMAIL PROTECTED]> wrote:
> > >
> > > From what i can tell though check_snmp_storage.pl only allows you to
> >check
> > > for particular kinds of storage settingswhat i need to do is
> monitor
> > > the
> > > size of a directory on a remote windows server for example, d:\data
> > >
> > > i am using nsclient at the moment but can't monitor directory size
> (only
> > > disk space).  Is there a way to monitor a directories size via
> snmp
> > >
> > >
> > > >From: Hendrik Baecker <[EMAIL PROTECTED]>
> > > >To: nagios-users@lists.sourceforge.net
> > > >Subject: Re: [Nagios-users] monitor directory size?
> > > >Date: Mon, 13 Feb 2006 12:44:00 +0100
> > > >
> > > >Google for: "check_snmp_storage.pl"
> > > >
> > > >
> > > >HP Geeza schrieb:
> > > >
> > > >>Hi All,
> > > >>
> > > >>I was wondering whether it is possible to monitor the size of a
> > > directory
> > > >>(eg find out how big it is in in MB or GBs) and then send an alert
> >when
> > > >>the size goes over a certain threshold?
> > > >>
> > > >>Any help would be great!
> > > >>
> > > >>_
> > > >>The new MSN Search Toolbar now includes Desktop search!
> > > >>http://toolbar.msn.co.uk/
> > > >>
> > > >>
> > > >>
> > > >>---
> > > >>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&kid=103432&bid=230486&dat=121642
> > > >>___
> > > >>Nagios-users mailing list
> > > >>Nagios-users@lists.sourceforge.net
> > > >>htt

Re: [Nagios-users] monitor directory size?

2006-02-15 Thread HP Geeza

Hi All,

I am having some difficulty with using nclient++ and was wondering if 
somebody could help??


I have download nslicnet++ (from 
http://nscplus.medin.name/index.php/Main_Page) and installed it on a remote 
windows server.  I then modified the NSC.ini file and added a line:


command[check_cmd]=D:\hello.cmd

I then created a simple .cmd file called hello.cmd which contained the 
following:


@echo off
echo hello world
exit 1

MY QUESTION IS:
what do i need to do/run on the nagios server inorder to run a check against 
hello.cmd for example?




From: Bill Jacqmein <[EMAIL PROTECTED]>
To: HP Geeza <[EMAIL PROTECTED]>
Subject: Re: [Nagios-users] monitor directory size?
Date: Tue, 14 Feb 2006 11:30:52 -0500

in NSC.ini

in the NRPE handlers section

mycheck=c:\somecheck.bat


For coding the batch file
useful - http://nagiosplug.sourceforge.net/developer-guidelines.html
The main part is the return codes

Numeric Value

Service Status

Status Description

0

OK

The plugin was able to check the service and it appeared to be functioning
properly

1

Warning

The plugin was able to check the service, but it appeared to be above some
"warning" threshold or did not appear to be working properly

2

Critical

The plugin detected that either the service was not running or it was above
some "critical" threshold

3

Unknown

Invalid command line arguments were supplied to the plugin or low-level
failures internal to the plugin (such as unable to fork, or open a tcp
socket) that prevent it from performing the specified operation.
Higher-level errors (such as name resolution errors, socket timeouts, etc)
are outside of the control of plugins and should generally NOT be reported
as UNKNOWN states.

Hopeful this was enough get you closer to a solution. If not I have to 
write

one in the near future so I will send how I went about creating the check.

Thanks,

  Bill

On 2/14/06, HP Geeza <[EMAIL PROTECTED]> wrote:
>
> Hi Bill,
>
> Im affraid im having some trouble with nsclient++ and running a batch
> files
> via check_nrep.  Could you please help me with the syntax that i need to
> use
> to setup the check on both the nagios server and remote windows server.
>
> any help would be great!
>
>
> >From: Bill Jacqmein <[EMAIL PROTECTED]>
> >To: HP Geeza <[EMAIL PROTECTED]>
> >Subject: Re: [Nagios-users] monitor directory size?
> >Date: Mon, 13 Feb 2006 14:44:40 -0500
> >
> >nsclient++ has the ability to run batch files via check_nrep. Might be 
an

> >option to do a dir and parse the filesize out of that.
> >
> >On 2/13/06, HP Geeza <[EMAIL PROTECTED]> wrote:
> > >
> > > From what i can tell though check_snmp_storage.pl only allows you to
> >check
> > > for particular kinds of storage settingswhat i need to do is
> monitor
> > > the
> > > size of a directory on a remote windows server for example, d:\data
> > >
> > > i am using nsclient at the moment but can't monitor directory size
> (only
> > > disk space).  Is there a way to monitor a directories size via
> snmp
> > >
> > >
> > > >From: Hendrik Baecker <[EMAIL PROTECTED]>
> > > >To: nagios-users@lists.sourceforge.net
> > > >Subject: Re: [Nagios-users] monitor directory size?
> > > >Date: Mon, 13 Feb 2006 12:44:00 +0100
> > > >
> > > >Google for: "check_snmp_storage.pl"
> > > >
> > > >
> > > >HP Geeza schrieb:
> > > >
> > > >>Hi All,
> > > >>
> > > >>I was wondering whether it is possible to monitor the size of a
> > > directory
> > > >>(eg find out how big it is in in MB or GBs) and then send an alert
> >when
> > > >>the size goes over a certain threshold?
> > > >>
> > > >>Any help would be great!
> > > >>
> > > >>_
> > > >>The new MSN Search Toolbar now includes Desktop search!
> > > >>http://toolbar.msn.co.uk/
> > > >>
> > > >>
> > > >>
> > > >>---
> > > >>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&kid=103432&bid=230486&dat=121642
> >

Re: [Nagios-users] monitor directory size?

2006-02-13 Thread HP Geeza
From what i can tell though check_snmp_storage.pl only allows you to check 
for particular kinds of storage settingswhat i need to do is monitor the 
size of a directory on a remote windows server for example, d:\data


i am using nsclient at the moment but can't monitor directory size (only 
disk space).  Is there a way to monitor a directories size via snmp




From: Hendrik Baecker <[EMAIL PROTECTED]>
To: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] monitor directory size?
Date: Mon, 13 Feb 2006 12:44:00 +0100

Google for: "check_snmp_storage.pl"


HP Geeza schrieb:


Hi All,

I was wondering whether it is possible to monitor the size of a directory 
(eg find out how big it is in in MB or GBs) and then send an alert when 
the size goes over a certain threshold?


Any help would be great!

_
The new MSN Search Toolbar now includes Desktop search! 
http://toolbar.msn.co.uk/




---
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&kid=103432&bid=230486&dat=121642
___
Nagios-users mailing list
Nagios-users@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







---
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&kid=103432&bid=230486&dat=121642
___
Nagios-users mailing list
Nagios-users@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


_
Are you using the latest version of MSN Messenger? Download MSN Messenger 
7.5 today! http://messenger.msn.co.uk




---
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&kid=103432&bid=230486&dat=121642
___
Nagios-users mailing list
Nagios-users@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


[Nagios-users] monitor directory size?

2006-02-13 Thread HP Geeza

Hi All,

I was wondering whether it is possible to monitor the size of a directory 
(eg find out how big it is in in MB or GBs) and then send an alert when the 
size goes over a certain threshold?


Any help would be great!

_
The new MSN Search Toolbar now includes Desktop search! 
http://toolbar.msn.co.uk/




---
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&kid=103432&bid=230486&dat=121642
___
Nagios-users mailing list
Nagios-users@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


RE: [Nagios-users] snmp not working

2005-11-16 Thread HP Geeza

./check_snmp -V

returns:

check_snmp (nagios-plugins 1.4) 1.53



From: Subhendu Ghosh <[EMAIL PROTECTED]>
To: HP Geeza <[EMAIL PROTECTED]>
CC: nagios-users@lists.sourceforge.net
Subject: RE: [Nagios-users] snmp not working
Date: Wed, 16 Nov 2005 11:17:22 -0500 (EST)


All plugins -V provides version info.

On Wed, 16 Nov 2005, HP Geeza wrote:

how do i find out which version of the check_snmp plugin im using? - sorry 
for yet another silly question!!! - im having one of those daysss




From: Subhendu Ghosh <[EMAIL PROTECTED]>
To: HP Geeza <[EMAIL PROTECTED]>
CC: nagios-users@lists.sourceforge.net
Subject: RE: [Nagios-users] snmp not working
Date: Wed, 16 Nov 2005 11:10:19 -0500 (EST)


Ok - what version of check_snmp?

On Wed, 16 Nov 2005, HP Geeza wrote:


the result of running:

snmpget -v 1 -c public 10.30.129.30 .1.3.6.1.4.1.2012.1.1.1.4.2.0

is:

SNMPv2-SMI::enterprises.2012.1.1.1.4.2.0 = INTEGER: 68





From: Subhendu Ghosh <[EMAIL PROTECTED]>
To: HP Geeza <[EMAIL PROTECTED]>
CC: nagios-users@lists.sourceforge.net
Subject: RE: [Nagios-users] snmp not working
Date: Wed, 16 Nov 2005 11:03:01 -0500 (EST)

On Wed, 16 Nov 2005, HP Geeza wrote:


Hi Subhendu,

Appologies for the silly question but what do you mean add a -m?



Add a "-m:"
The colon after the -m option indicates an empty miblist.  You don't 
need a miblist if you are providing a numeric OID.
A normal miblist is a colon separated list of directories containing 
mib files.  It is used by the snmpget utility to translate to a numeric 
OID. e.g.  system.sysDescr.0 ==> .1.3.6.1.2.1.1.1.0


Also please post the result of the following:
snmpget -v 1 -c public 10.30.129.30 .1.3.6.1.4.1.2012.1.1.1.4.2.0

If you see data other than
SNMPv2-SMI::enterprises.2012.1.1.1.4.2.0 = INTEGER: 69

then you may have some local mib files that don't have the correct 
syntax.


The WARNING is then the result of output seen on STDERR where it was 
not expected.



when i run:
./check_snmp -H 10.30.129.30 -o .1.3.6.1.4.1.2012.1.1.1.4.2.0 -w 80 -c 
85 -C public -v -m

i get ./check_snmp: option requires an argument -- m

how do i find out what the miblist is

WHEN I RUN:
./check_snmp -H 10.30.129.30 -o .1.3.6.1.4.1.2012.1.1.1.4.2.0 -w 80 -c 
85 -C public -v


i get:
/usr/bin/snmpget -t 1 -r 5 -m ALL -v 1 -c public 10.30.129.30:161 
.1.3.6.1.4.1.2012.1.1.1.4.2.0

SNMPv2-SMI::enterprises.2012.1.1.1.4.2.0 = INTEGER: 69

SNMP WARNING - 69


NOTE if it is of any use, there is a line space between SNMP WARNING - 
69 and INTEGER 69





From: Subhendu Ghosh <[EMAIL PROTECTED]>
To: HP Geeza <[EMAIL PROTECTED]>
CC: nagios-users@lists.sourceforge.net
Subject: RE: [Nagios-users] snmp not working
Date: Wed, 16 Nov 2005 10:03:05 -0500 (EST)

On Wed, 16 Nov 2005, HP Geeza wrote:


Hi

Thanks for the info, but im affraid it still isn't working :-(

FYI
Usage: check_snmp -H  -o  [-w warn_range] [-c 
crit_range]

[-C community] [-s string] [-r regex] [-R regexi]
[-t timeout] [-e retries]
[-l label] [-u units] [-p port-number] [-d 
delimiter]
[-D output-delimiter] [-m miblist] [-P snmp 
version]
[-L seclevel] [-U secname] [-a authproto] [-A 
authpasswd]

[-X privpasswd]

i try running the command: ./check_snmp -H 10.30.129.30 -o 
.1.3.6.1.4.1.2012.1.1.1.4.2.0 -w 80 -c 85 -C public


and still get a value of "SNMP WARNING - 69" back

accoring to the command im running should the waring only come up 
when the -w parameter is met? - i.e 80 and critical when its 85??


Any help would be great



Add a "-m:"

Also please post the result of tagging on a "-v" option

-sg



From: "Marc Powell" <[EMAIL PROTECTED]>
To: 
Subject: RE: [Nagios-users] snmp not working
Date: Tue, 15 Nov 2005 12:55:15 -0600



> -Original Message-
> From: [EMAIL PROTECTED] 
[mailto:nagios-users-

> [EMAIL PROTECTED] On Behalf Of HP Geeza
> Sent: Tuesday, November 15, 2005 11:26 AM
> To: nagios-users@lists.sourceforge.net
> Subject: [Nagios-users] snmp not working
>
> Hi All,
>
> I was hoping that somebody might be able to help me with a snmp
monitoring
> issue on my nagios box.  I am running the following command on 
the

command
> line on the nagios box:
>
> /usr/local/nagios/libexec/./check_snmp in

our
> lab)
> -o .1.3.6.1.4.1.2012.1.1.1.4.2.0 -C public
>
> and get a value of SNMP "WARNING - 68" back
>
> however i dont think that this value is correct and as a reult 
the
> check_snmp plugin seems to be obtaining the wrong result as i 
dont

expect
> this to be a warning.  For example if i run:

Well, you haven't told check_snmp if that's OK or CRITICAL so it 
doesn't
know what to report it as, hence WARNING. Remember the OIDs can 
contain
just about any kind of data and check_snmp has no i

RE: [Nagios-users] snmp not working

2005-11-16 Thread HP Geeza
how do i find out which version of the check_snmp plugin im using? - sorry 
for yet another silly question!!! - im having one of those daysss




From: Subhendu Ghosh <[EMAIL PROTECTED]>
To: HP Geeza <[EMAIL PROTECTED]>
CC: nagios-users@lists.sourceforge.net
Subject: RE: [Nagios-users] snmp not working
Date: Wed, 16 Nov 2005 11:10:19 -0500 (EST)


Ok - what version of check_snmp?

On Wed, 16 Nov 2005, HP Geeza wrote:


the result of running:

snmpget -v 1 -c public 10.30.129.30 .1.3.6.1.4.1.2012.1.1.1.4.2.0

is:

SNMPv2-SMI::enterprises.2012.1.1.1.4.2.0 = INTEGER: 68





From: Subhendu Ghosh <[EMAIL PROTECTED]>
To: HP Geeza <[EMAIL PROTECTED]>
CC: nagios-users@lists.sourceforge.net
Subject: RE: [Nagios-users] snmp not working
Date: Wed, 16 Nov 2005 11:03:01 -0500 (EST)

On Wed, 16 Nov 2005, HP Geeza wrote:


Hi Subhendu,

Appologies for the silly question but what do you mean add a -m?



Add a "-m:"
The colon after the -m option indicates an empty miblist.  You don't need 
a miblist if you are providing a numeric OID.
A normal miblist is a colon separated list of directories containing mib 
files.  It is used by the snmpget utility to translate to a numeric OID. 
e.g.  system.sysDescr.0 ==> .1.3.6.1.2.1.1.1.0


Also please post the result of the following:
snmpget -v 1 -c public 10.30.129.30 .1.3.6.1.4.1.2012.1.1.1.4.2.0

If you see data other than
SNMPv2-SMI::enterprises.2012.1.1.1.4.2.0 = INTEGER: 69

then you may have some local mib files that don't have the correct 
syntax.


The WARNING is then the result of output seen on STDERR where it was not 
expected.



when i run:
./check_snmp -H 10.30.129.30 -o .1.3.6.1.4.1.2012.1.1.1.4.2.0 -w 80 -c 
85 -C public -v -m

i get ./check_snmp: option requires an argument -- m

how do i find out what the miblist is

WHEN I RUN:
./check_snmp -H 10.30.129.30 -o .1.3.6.1.4.1.2012.1.1.1.4.2.0 -w 80 -c 
85 -C public -v


i get:
/usr/bin/snmpget -t 1 -r 5 -m ALL -v 1 -c public 10.30.129.30:161 
.1.3.6.1.4.1.2012.1.1.1.4.2.0

SNMPv2-SMI::enterprises.2012.1.1.1.4.2.0 = INTEGER: 69

SNMP WARNING - 69


NOTE if it is of any use, there is a line space between SNMP WARNING - 
69 and INTEGER 69





From: Subhendu Ghosh <[EMAIL PROTECTED]>
To: HP Geeza <[EMAIL PROTECTED]>
CC: nagios-users@lists.sourceforge.net
Subject: RE: [Nagios-users] snmp not working
Date: Wed, 16 Nov 2005 10:03:05 -0500 (EST)

On Wed, 16 Nov 2005, HP Geeza wrote:


Hi

Thanks for the info, but im affraid it still isn't working :-(

FYI
Usage: check_snmp -H  -o  [-w warn_range] [-c 
crit_range]

[-C community] [-s string] [-r regex] [-R regexi]
[-t timeout] [-e retries]
[-l label] [-u units] [-p port-number] [-d delimiter]
[-D output-delimiter] [-m miblist] [-P snmp version]
[-L seclevel] [-U secname] [-a authproto] [-A 
authpasswd]

[-X privpasswd]

i try running the command: ./check_snmp -H 10.30.129.30 -o 
.1.3.6.1.4.1.2012.1.1.1.4.2.0 -w 80 -c 85 -C public


and still get a value of "SNMP WARNING - 69" back

accoring to the command im running should the waring only come up when 
the -w parameter is met? - i.e 80 and critical when its 85??


Any help would be great



Add a "-m:"

Also please post the result of tagging on a "-v" option

-sg



From: "Marc Powell" <[EMAIL PROTECTED]>
To: 
Subject: RE: [Nagios-users] snmp not working
Date: Tue, 15 Nov 2005 12:55:15 -0600



> -Original Message-
> From: [EMAIL PROTECTED] 
[mailto:nagios-users-

> [EMAIL PROTECTED] On Behalf Of HP Geeza
> Sent: Tuesday, November 15, 2005 11:26 AM
> To: nagios-users@lists.sourceforge.net
> Subject: [Nagios-users] snmp not working
>
> Hi All,
>
> I was hoping that somebody might be able to help me with a snmp
monitoring
> issue on my nagios box.  I am running the following command on the
command
> line on the nagios box:
>
> /usr/local/nagios/libexec/./check_snmp in

our
> lab)
> -o .1.3.6.1.4.1.2012.1.1.1.4.2.0 -C public
>
> and get a value of SNMP "WARNING - 68" back
>
> however i dont think that this value is correct and as a reult the
> check_snmp plugin seems to be obtaining the wrong result as i dont
expect
> this to be a warning.  For example if i run:

Well, you haven't told check_snmp if that's OK or CRITICAL so it 
doesn't
know what to report it as, hence WARNING. Remember the OIDs can 
contain
just about any kind of data and check_snmp has no idea what it is 
you're
querying, it just has an SNMP 'address'. You have to add in the 
status

intelligence.

> ./check_snmp 10.30.129.30 -o .1.3.6.1.4.1.2012.1.1.1.4.2.0 -C 
public

-wv
> 80
> -cv 85
>
> i still get a value of "WARNING - 68"

I'm not sure what version of check_snmp you're using but -wv and -cv
a

RE: [Nagios-users] snmp not working

2005-11-16 Thread HP Geeza

the result of running:

snmpget -v 1 -c public 10.30.129.30 .1.3.6.1.4.1.2012.1.1.1.4.2.0

is:

SNMPv2-SMI::enterprises.2012.1.1.1.4.2.0 = INTEGER: 68





From: Subhendu Ghosh <[EMAIL PROTECTED]>
To: HP Geeza <[EMAIL PROTECTED]>
CC: nagios-users@lists.sourceforge.net
Subject: RE: [Nagios-users] snmp not working
Date: Wed, 16 Nov 2005 11:03:01 -0500 (EST)

On Wed, 16 Nov 2005, HP Geeza wrote:


Hi Subhendu,

Appologies for the silly question but what do you mean add a -m?



Add a "-m:"
The colon after the -m option indicates an empty miblist.  You don't need a 
miblist if you are providing a numeric OID.
A normal miblist is a colon separated list of directories containing mib 
files.  It is used by the snmpget utility to translate to a numeric OID. 
e.g.  system.sysDescr.0 ==> .1.3.6.1.2.1.1.1.0


Also please post the result of the following:
snmpget -v 1 -c public 10.30.129.30 .1.3.6.1.4.1.2012.1.1.1.4.2.0

If you see data other than
SNMPv2-SMI::enterprises.2012.1.1.1.4.2.0 = INTEGER: 69

then you may have some local mib files that don't have the correct syntax.

The WARNING is then the result of output seen on STDERR where it was not 
expected.



when i run:
./check_snmp -H 10.30.129.30 -o .1.3.6.1.4.1.2012.1.1.1.4.2.0 -w 80 -c 85 
-C public -v -m

i get ./check_snmp: option requires an argument -- m

how do i find out what the miblist is

WHEN I RUN:
./check_snmp -H 10.30.129.30 -o .1.3.6.1.4.1.2012.1.1.1.4.2.0 -w 80 -c 85 
-C public -v


i get:
/usr/bin/snmpget -t 1 -r 5 -m ALL -v 1 -c public 10.30.129.30:161 
.1.3.6.1.4.1.2012.1.1.1.4.2.0

SNMPv2-SMI::enterprises.2012.1.1.1.4.2.0 = INTEGER: 69

SNMP WARNING - 69


NOTE if it is of any use, there is a line space between SNMP WARNING - 69 
and INTEGER 69





From: Subhendu Ghosh <[EMAIL PROTECTED]>
To: HP Geeza <[EMAIL PROTECTED]>
CC: nagios-users@lists.sourceforge.net
Subject: RE: [Nagios-users] snmp not working
Date: Wed, 16 Nov 2005 10:03:05 -0500 (EST)

On Wed, 16 Nov 2005, HP Geeza wrote:


Hi

Thanks for the info, but im affraid it still isn't working :-(

FYI
Usage: check_snmp -H  -o  [-w warn_range] [-c 
crit_range]

[-C community] [-s string] [-r regex] [-R regexi]
[-t timeout] [-e retries]
[-l label] [-u units] [-p port-number] [-d delimiter]
[-D output-delimiter] [-m miblist] [-P snmp version]
[-L seclevel] [-U secname] [-a authproto] [-A 
authpasswd]

[-X privpasswd]

i try running the command: ./check_snmp -H 10.30.129.30 -o 
.1.3.6.1.4.1.2012.1.1.1.4.2.0 -w 80 -c 85 -C public


and still get a value of "SNMP WARNING - 69" back

accoring to the command im running should the waring only come up when 
the -w parameter is met? - i.e 80 and critical when its 85??


Any help would be great



Add a "-m:"

Also please post the result of tagging on a "-v" option

-sg



From: "Marc Powell" <[EMAIL PROTECTED]>
To: 
Subject: RE: [Nagios-users] snmp not working
Date: Tue, 15 Nov 2005 12:55:15 -0600



> -Original Message-
> From: [EMAIL PROTECTED] [mailto:nagios-users-
> [EMAIL PROTECTED] On Behalf Of HP Geeza
> Sent: Tuesday, November 15, 2005 11:26 AM
> To: nagios-users@lists.sourceforge.net
> Subject: [Nagios-users] snmp not working
>
> Hi All,
>
> I was hoping that somebody might be able to help me with a snmp
monitoring
> issue on my nagios box.  I am running the following command on the
command
> line on the nagios box:
>
> /usr/local/nagios/libexec/./check_snmp  lab)
> -o .1.3.6.1.4.1.2012.1.1.1.4.2.0 -C public
>
> and get a value of SNMP "WARNING - 68" back
>
> however i dont think that this value is correct and as a reult the
> check_snmp plugin seems to be obtaining the wrong result as i dont
expect
> this to be a warning.  For example if i run:

Well, you haven't told check_snmp if that's OK or CRITICAL so it 
doesn't

know what to report it as, hence WARNING. Remember the OIDs can contain
just about any kind of data and check_snmp has no idea what it is 
you're

querying, it just has an SNMP 'address'. You have to add in the status
intelligence.

> ./check_snmp 10.30.129.30 -o .1.3.6.1.4.1.2012.1.1.1.4.2.0 -C public
-wv
> 80
> -cv 85
>
> i still get a value of "WARNING - 68"

I'm not sure what version of check_snmp you're using but -wv and -cv
aren't valid command line args, at least with 1.4 and prior.

> is there a different check_snmp plugin i could use? or am i just
running
> the
> command wrong?  I dont want the service to show up as a warning when
the
> temperature is 68F...hence the reason for doing -wv 80 -cv 85

You just need to tell check_snmp what to expect for each range.
Check_snmp (and a couple other plugins) behave differently than other
plugins WRT warn

RE: [Nagios-users] snmp not working

2005-11-16 Thread HP Geeza

Hi Subhendu,

Appologies for the silly question but what do you mean add a -m?

when i run:
./check_snmp -H 10.30.129.30 -o .1.3.6.1.4.1.2012.1.1.1.4.2.0 -w 80 -c 85 -C 
public -v -m

i get ./check_snmp: option requires an argument -- m

how do i find out what the miblist is

WHEN I RUN:
./check_snmp -H 10.30.129.30 -o .1.3.6.1.4.1.2012.1.1.1.4.2.0 -w 80 -c 85 -C 
public -v


i get:
/usr/bin/snmpget -t 1 -r 5 -m ALL -v 1 -c public 10.30.129.30:161  
.1.3.6.1.4.1.2012.1.1.1.4.2.0

SNMPv2-SMI::enterprises.2012.1.1.1.4.2.0 = INTEGER: 69

SNMP WARNING - 69


NOTE if it is of any use, there is a line space between SNMP WARNING - 69 
and INTEGER 69





From: Subhendu Ghosh <[EMAIL PROTECTED]>
To: HP Geeza <[EMAIL PROTECTED]>
CC: nagios-users@lists.sourceforge.net
Subject: RE: [Nagios-users] snmp not working
Date: Wed, 16 Nov 2005 10:03:05 -0500 (EST)

On Wed, 16 Nov 2005, HP Geeza wrote:


Hi

Thanks for the info, but im affraid it still isn't working :-(

FYI
Usage: check_snmp -H  -o  [-w warn_range] [-c crit_range]
[-C community] [-s string] [-r regex] [-R regexi]
[-t timeout] [-e retries]
[-l label] [-u units] [-p port-number] [-d delimiter]
[-D output-delimiter] [-m miblist] [-P snmp version]
[-L seclevel] [-U secname] [-a authproto] [-A authpasswd]
[-X privpasswd]

i try running the command: ./check_snmp -H 10.30.129.30 -o 
.1.3.6.1.4.1.2012.1.1.1.4.2.0 -w 80 -c 85 -C public


and still get a value of "SNMP WARNING - 69" back

accoring to the command im running should the waring only come up when the 
-w parameter is met? - i.e 80 and critical when its 85??


Any help would be great



Add a "-m:"

Also please post the result of tagging on a "-v" option

-sg



From: "Marc Powell" <[EMAIL PROTECTED]>
To: 
Subject: RE: [Nagios-users] snmp not working
Date: Tue, 15 Nov 2005 12:55:15 -0600



> -Original Message-
> From: [EMAIL PROTECTED] [mailto:nagios-users-
> [EMAIL PROTECTED] On Behalf Of HP Geeza
> Sent: Tuesday, November 15, 2005 11:26 AM
> To: nagios-users@lists.sourceforge.net
> Subject: [Nagios-users] snmp not working
>
> Hi All,
>
> I was hoping that somebody might be able to help me with a snmp
monitoring
> issue on my nagios box.  I am running the following command on the
command
> line on the nagios box:
>
> /usr/local/nagios/libexec/./check_snmp  lab)
> -o .1.3.6.1.4.1.2012.1.1.1.4.2.0 -C public
>
> and get a value of SNMP "WARNING - 68" back
>
> however i dont think that this value is correct and as a reult the
> check_snmp plugin seems to be obtaining the wrong result as i dont
expect
> this to be a warning.  For example if i run:

Well, you haven't told check_snmp if that's OK or CRITICAL so it doesn't
know what to report it as, hence WARNING. Remember the OIDs can contain
just about any kind of data and check_snmp has no idea what it is you're
querying, it just has an SNMP 'address'. You have to add in the status
intelligence.

> ./check_snmp 10.30.129.30 -o .1.3.6.1.4.1.2012.1.1.1.4.2.0 -C public
-wv
> 80
> -cv 85
>
> i still get a value of "WARNING - 68"

I'm not sure what version of check_snmp you're using but -wv and -cv
aren't valid command line args, at least with 1.4 and prior.

> is there a different check_snmp plugin i could use? or am i just
running
> the
> command wrong?  I dont want the service to show up as a warning when
the
> temperature is 68F...hence the reason for doing -wv 80 -cv 85

You just need to tell check_snmp what to expect for each range.
Check_snmp (and a couple other plugins) behave differently than other
plugins WRT warning and critical detection as the results of the SNMP
query are highly variable. Here are a couple of examples --

To test for a very specific value where anything but that value is bad
you might use something like -
define command{
command_namecheck_bgp_peer_state
command_line$USER1$/check_snmp -H $HOSTADDRESS$ -o
.1.3.6.1.2.1.15.3.1.2.$ARG1$ -s 6 -C $USER3$ -l 'BGP Peer $ARG1$ State'
}

The above will be OK if the value of that OID is 6 and CRITICAL if it's
anything else.

To check for a range of values you might use the following -

define command{
command_namecheck_temperature_server_sites
command_line$USER1$/check_snmp -H $HOSTADDRESS$ -u 'Degrees
Celsius' -o .1.3.6.1.4.1.9.9.13.1.3.1.3.2 -C $USER3$ -w 37:32 -c 99:38
-l '
Temperature is'
}

The above will result in WARNING if the value of the OID is between 32
and 37 (inclusive), CRITICAL if it's between 38 and 99 (inclusive) and
OK for all other values.

Hope that helps. Use 'check_snmp --help' for other command line args and
their description.

--
M

RE: [Nagios-users] snmp not working

2005-11-16 Thread HP Geeza

Hi

Thanks for the info, but im affraid it still isn't working :-(

FYI
Usage: check_snmp -H  -o  [-w warn_range] [-c crit_range]
 [-C community] [-s string] [-r regex] [-R regexi]
 [-t timeout] [-e retries]
 [-l label] [-u units] [-p port-number] [-d delimiter]
 [-D output-delimiter] [-m miblist] [-P snmp version]
 [-L seclevel] [-U secname] [-a authproto] [-A authpasswd]
 [-X privpasswd]

i try running the command: ./check_snmp -H 10.30.129.30 -o 
.1.3.6.1.4.1.2012.1.1.1.4.2.0 -w 80 -c 85 -C public


and still get a value of "SNMP WARNING - 69" back

accoring to the command im running should the waring only come up when the 
-w parameter is met? - i.e 80 and critical when its 85??


Any help would be great


From: "Marc Powell" <[EMAIL PROTECTED]>
To: 
Subject: RE: [Nagios-users] snmp not working
Date: Tue, 15 Nov 2005 12:55:15 -0600



> -Original Message-
> From: [EMAIL PROTECTED] [mailto:nagios-users-
> [EMAIL PROTECTED] On Behalf Of HP Geeza
> Sent: Tuesday, November 15, 2005 11:26 AM
> To: nagios-users@lists.sourceforge.net
> Subject: [Nagios-users] snmp not working
>
> Hi All,
>
> I was hoping that somebody might be able to help me with a snmp
monitoring
> issue on my nagios box.  I am running the following command on the
command
> line on the nagios box:
>
> /usr/local/nagios/libexec/./check_snmp  lab)
> -o .1.3.6.1.4.1.2012.1.1.1.4.2.0 -C public
>
> and get a value of SNMP "WARNING - 68" back
>
> however i dont think that this value is correct and as a reult the
> check_snmp plugin seems to be obtaining the wrong result as i dont
expect
> this to be a warning.  For example if i run:

Well, you haven't told check_snmp if that's OK or CRITICAL so it doesn't
know what to report it as, hence WARNING. Remember the OIDs can contain
just about any kind of data and check_snmp has no idea what it is you're
querying, it just has an SNMP 'address'. You have to add in the status
intelligence.

> ./check_snmp 10.30.129.30 -o .1.3.6.1.4.1.2012.1.1.1.4.2.0 -C public
-wv
> 80
> -cv 85
>
> i still get a value of "WARNING - 68"

I'm not sure what version of check_snmp you're using but -wv and -cv
aren't valid command line args, at least with 1.4 and prior.

> is there a different check_snmp plugin i could use? or am i just
running
> the
> command wrong?  I dont want the service to show up as a warning when
the
> temperature is 68F...hence the reason for doing -wv 80 -cv 85

You just need to tell check_snmp what to expect for each range.
Check_snmp (and a couple other plugins) behave differently than other
plugins WRT warning and critical detection as the results of the SNMP
query are highly variable. Here are a couple of examples --

To test for a very specific value where anything but that value is bad
you might use something like -
define command{
command_namecheck_bgp_peer_state
command_line$USER1$/check_snmp -H $HOSTADDRESS$ -o
.1.3.6.1.2.1.15.3.1.2.$ARG1$ -s 6 -C $USER3$ -l 'BGP Peer $ARG1$ State'
}

The above will be OK if the value of that OID is 6 and CRITICAL if it's
anything else.

To check for a range of values you might use the following -

define command{
command_namecheck_temperature_server_sites
command_line$USER1$/check_snmp -H $HOSTADDRESS$ -u 'Degrees
Celsius' -o .1.3.6.1.4.1.9.9.13.1.3.1.3.2 -C $USER3$ -w 37:32 -c 99:38
-l '
Temperature is'
}

The above will result in WARNING if the value of the OID is between 32
and 37 (inclusive), CRITICAL if it's between 38 and 99 (inclusive) and
OK for all other values.

Hope that helps. Use 'check_snmp --help' for other command line args and
their description.

--
Marc


---
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_idv28&alloc_id845&op=click
___
Nagios-users mailing list
Nagios-users@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


_
MSN Messenger 7.5 is now out. Download it for FREE here. 
http://messenger.msn.co.uk




---
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification 

Re: [Nagios-users] snmp not working

2005-11-15 Thread HP Geeza

yes there was a -H before the host ip address

sorry for the confusion!



From: Jason Byrns <[EMAIL PROTECTED]>
To: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] snmp not working
Date: Tue, 15 Nov 2005 13:12:39 -0600

HP Geeza wrote:
./check_snmp 10.30.129.30 -o .1.3.6.1.4.1.2012.1.1.1.4.2.0 -C public -wv 
80 -cv 85


Verify your check_snmp syntax.  That plugin requires a "-H" before your 
host IP address.


--
Jason Byrns
Production Manager
System Administrator
http://www.MicroLnk.com/
402-328-8600 ext. 653


---
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
___
Nagios-users mailing list
Nagios-users@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


_
MSN Messenger 7.5 is now out. Download it for FREE here. 
http://messenger.msn.co.uk




---
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
___
Nagios-users mailing list
Nagios-users@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


[Nagios-users] snmp not working

2005-11-15 Thread HP Geeza

Hi All,

I was hoping that somebody might be able to help me with a snmp monitoring 
issue on my nagios box.  I am running the following command on the command 
line on the nagios box:


/usr/local/nagios/libexec/./check_snmp however i dont think that this value is correct and as a reult the 
check_snmp plugin seems to be obtaining the wrong result as i dont expect 
this to be a warning.  For example if i run:


./check_snmp 10.30.129.30 -o .1.3.6.1.4.1.2012.1.1.1.4.2.0 -C public -wv 80 
-cv 85


i still get a value of "WARNING - 68"

is there a different check_snmp plugin i could use? or am i just running the 
command wrong?  I dont want the service to show up as a warning when the 
temperature is 68F...hence the reason for doing -wv 80 -cv 85


Any help would be much appreciated

_
Be the first to hear what's new at MSN - sign up to our free newsletters! 
http://www.msn.co.uk/newsletters




---
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
___
Nagios-users mailing list
Nagios-users@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