Re: [Nagios-users] monitoring oracle grid

2012-04-13 Thread Claudio Kuenzler
Don't know about Oracle Grid, but I have another suggestion.
If I understood correctly, your issue is to monitor the tablespaces which
where added by the DBA's?

If so, you should try the plugin check_oracle_health which has an option to
monitor ALL tablespaces (not just the utilization of one given tablespace):
--mode tablespace-usage

If wanted you can also monitor a single tablespace by using:
--mode tablespace-usage --tablespace MYTABLE

http://labs.consol.de/lang/en/nagios/check_oracle_health/

On Fri, Apr 13, 2012 at 4:11 AM, Tim Dunphy bluethu...@jokefire.com wrote:

 hello list,

  We've been monitoring our Oracle Database using a plugin called
 'check_oracle'. It's proven quite handy in getting the sizes of tablespaces
 and alerting based on percentages of space used.

  However the DBAs point out that the database is very dynamic and that
 tablespaces are always being added and removed. It seems like they don't
 want to notify us each time this happens. Keeping on top of them to do this
 is a pain.

  They've just installed Oracle Grid and suggested we use nagios to monitor
 that instead. I've never seen or used Oracle Grid so I was hoping someone
 out there with a little more knowledge than me on the topic might have some
 suggestions on how to accomplish this.

  Are there any plugins already out there that are written to take
 information from the oracle grid and parse that for use in nagios?

 Thanks
 Tim


 --
 For Developers, A Lot Can Happen In A Second.
 Boundary is the first to Know...and Tell You.
 Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
 http://p.sf.net/sfu/Boundary-d2dvs2
 ___
 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

--
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2___
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] Nagios Uptime Error

2012-04-13 Thread Ollie Campbell
Have you tried manually running the NSClient with the /test switch (from a
command line) on that server to see if there are issues?



On 11 April 2012 18:27, Chris Snyder chris.sny...@gocruisers.org wrote:

 Good morning,

 I am using Nagios Core for monitoring our servers.  I am monitoring 35
 Windows servers (mostly 2003, we have about five 2008 servers) using the
 nsclient++ plugin.  I have one server showing a timeout error when checking
 the uptime (External command error: Timeout: No response from
 xxx.xxx.xxx.xxx).  It is the only server showing this error and the only
 error on the server.  I copied the nsc.ini file between the servers so they
 are all the same.  Do you know what could be causing this error on this one
 server?

 --
 Chris Snyder
 Technology Coordinator
 Groveport Madison Schools



 --
 For Developers, A Lot Can Happen In A Second.
 Boundary is the first to Know...and Tell You.
 Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
 http://p.sf.net/sfu/Boundary-d2dvs2
 ___
 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




-- 
Ollie Campbell
Service Delivery Manager

* 60 Kingly Street, London, W1B 5DS*
D: +44 20 7453 4930
M: +44 7584 518539

www.bartleboglehegarty.com

-- 

This transmission is from BBH Partners LLP, it is confidential and intended 
solely for the person or organisation to whom it is addressed. This 
transmission may contain confidential information within its content or any 
attachment.  You should not copy, use or distribute in any way any of the 
information contained within this transmission other than in accordance 
with the prior written permission of an authorised BBH representative.

Partnership Information: 
Registered name: BBH Partners LLP 
Registered office: 60 Kingly Street London W1B 5DS
Place of registration: England and Wales 
Registered number: OC355051

Although all messages/file attachments passing through this gateway are 
scanned for viruses we cannot guarantee that any file is 100% virus-free.

--
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2___
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] Nagios Uptime Error

2012-04-13 Thread FTL Nagios
I had this on a particular 2008 server. The other 86 servers were fine just
not this one.

 

I had to rebuild the performance counter indexes.

 

Try running:  lodctr /R from a cmd prompt and then reboot the server and see
if that sorts.

 

From: Ollie Campbell [mailto:ollie.campb...@bbh.co.uk] 
Sent: 13 April 2012 09:07
To: Nagios Users List
Subject: Re: [Nagios-users] Nagios Uptime Error

 

Have you tried manually running the NSClient with the /test switch (from a
command line) on that server to see if there are issues?

 

 

On 11 April 2012 18:27, Chris Snyder chris.sny...@gocruisers.org wrote:

Good morning,

 

I am using Nagios Core for monitoring our servers.  I am monitoring 35
Windows servers (mostly 2003, we have about five 2008 servers) using the
nsclient++ plugin.  I have one server showing a timeout error when checking
the uptime (External command error: Timeout: No response from
xxx.xxx.xxx.xxx).  It is the only server showing this error and the only
error on the server.  I copied the nsc.ini file between the servers so they
are all the same.  Do you know what could be causing this error on this one
server?


 

-- 
Chris Snyder

Technology Coordinator

Groveport Madison Schools

 



--
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
___
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





 

-- 
Ollie Campbell
Service Delivery Manager

60 Kingly Street, London, W1B 5DS
D: +44 20 7453 4930
M: +44 7584 518539

 http://www.bartleboglehegarty.com www.bartleboglehegarty.com



Description: Image removed by sender.

 

 

This transmission is from BBH Partners LLP, it is confidential and intended
solely for the person or organisation to whom it is addressed. This
transmission may contain confidential information within its content or any
attachment.  You should not copy, use or distribute in any way any of the
information contained within this transmission other than in accordance with
the prior written permission of an authorised BBH representative.

 

Partnership Information: 

Registered name: BBH Partners LLP 

Registered office: 60 Kingly Street London W1B 5DS

Place of registration: England and Wales 

Registered number: OC355051

 

Although all messages/file attachments passing through this gateway are
scanned for viruses we cannot guarantee that any file is 100% virus-free.

 

~WRD000.jpg--
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2___
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] Warning alert isn't working

2012-04-13 Thread Leonardo Bacha Abrantes
Hi everybody!

I'm using check_openmanage plugin in nagios to monitoring the temperature
of my dell servers.
It's working, however, the warning and critical alerts that I configure are
not working.

[root@monitor:/etc/openmanage]# /usr/lib/nagios/plugins/check_openmanage -w
25 -c 30 -H 10.11.12.1 -C Test--only temp
TEMPERATURES OK - 1 temperature probes checked:BRTemperature Probe 0
[System Board Ambient Temp] reads 30 C (min=8/3, max=42/47)

The temperature is 30 and the check should appear WARNING because I used -w
25.


Can you help me, please ?


many thanks!
--
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2___
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] Warning alert isn't working

2012-04-13 Thread Trond Hasle Amundsen
Leonardo Bacha Abrantes leona...@lbasolutions.com writes:

 Hi everybody!

 I'm using check_openmanage plugin in nagios to monitoring the temperature of 
 my
 dell servers.
 It's working, however, the warning and critical alerts that I configure are 
 not
 working.

 [root@monitor:/etc/openmanage]# /usr/lib/nagios/plugins/check_openmanage -w 25
 -c 30 -H 10.11.12.1 -C Test--only temp
 TEMPERATURES OK - 1 temperature probes checked:BRTemperature Probe 0 [System
 Board Ambient Temp] reads 30 C (min=8/3, max=42/47)

 The temperature is 30 and the check should appear WARNING because I used -w 
 25.

Hello Leonardo,

The syntax you're using with the '-w' and '-c' options is wrong. From
the manual page:

   -w, --warning STRING or FILE
   Override the machine-default temperature warning
   thresholds. Syntax is id1=max[/min],id2=max[/min], The
   following example sets warning limits to max 50C for probe 0,
   and max 45C and min 10C for probe 1:

   check_openmanage -w 0=50,1=45/10

   The minimum limit can be omitted, if desired. Most often, you
   are only interested in setting the maximum thresholds.

   This parameter can be either a string with the limits, or a
   file containing the limits string. The option can be
   specified multiple times.

   NOTE: This option should only be used to narrow the field of
   OK temperatures wrt. the OMSA defaults. To expand the field
   of OK temperatures, increase the OMSA thresholds. See the
   plugin web page for more information.

   -c, --critical STRING or FILE
   Override the machine-default temperature critical
   thresholds. Syntax and behaviour is the same as for warning
   thresholds described above.

The reason that you need to specify the ID of the temperature probes is
that there may be more than one, each with its own thresholds. In your
case there is only one probe and its ID is 0, so replace your command
above with:

  check_openmanage -w 0=25 -c 0=30 -H 10.11.12.1 -C Test --only temp

That should do the trick.

Regards,
-- 
Trond H. Amundsen t.h.amund...@usit.uio.no
Center for Information Technology Services, University of Oslo

--
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
___
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