Re: [Nagios-users] Plugin check_oracle_health
Nagios network monitoring software is enterprise server monitoring
Brought to you by:
egalstad,
sawolf-nagios
Menu
▾
▴
Re: [Nagios-users] Plugin check_oracle_health
|
From: Cosmin N. <cos...@om...> - 2012-10-29 08:50:32
|
Hi Nagios Users,
Can someone help me or give a hint on why check_oracle_health does not
work (as describe below) ?
On 10/23/2012 04:59 PM, Cosmin Neagu wrote:
> Hi all,
>
> I manage to install the oracle client on nagios machine after all
> (google is the best) and making all the necesary setting so that
> check_oracle_health is working from command line as nagios user:
>
> nagios@monitor:/usr/local/nagios/libexec$ ./check_oracle_health
> --connect IGAS --username abc --password abc --mode=tnsping
> Use of qw(...) as parentheses is deprecated at ./check_oracle_health
> line 4163.
> Use of qw(...) as parentheses is deprecated at ./check_oracle_health
> line 6167.
> OK - connection established to IGAS.
> nagios@monitor:/usr/local/nagios/libexec$ ./check_oracle_health
> --connect IGAS --username abc --password abc --mode=connection-time
> Use of qw(...) as parentheses is deprecated at ./check_oracle_health
> line 4163.
> Use of qw(...) as parentheses is deprecated at ./check_oracle_health
> line 6167.
> OK - 0.10 seconds to connect as iapc_etl | connection_time=0.0968;1;5
> nagios@monitor:/usr/local/nagios/libexec$ ./check_oracle_health
> --connect IGAS --username abc --password abc --mode=connected-users
> Use of qw(...) as parentheses is deprecated at ./check_oracle_health
> line 4163.
> Use of qw(...) as parentheses is deprecated at ./check_oracle_health
> line 6167.
> OK - 31 connected users | connected_users=31;50;100
>
>
> The command is defined like this:
> define command{
> command_name check_oracle_health
> command_line $USER1$/check_oracle_health $ARG1$
> }
>
> And the services:
> define service {
> use generic-service
> host_name DBIGASDS
> service_description Reachability via tnsping
> check_command check_oracle_health! --connect IGAS
> --username abc --password abc --mode=tnsping
> contacts cosmin
> }
>
> define service {
> use generic-service
> host_name DBIGASDS
> service_description Connection time to DB
> check_command check_oracle_health!--connect IGAS
> --username abc --password abc mode=connection-time
> contacts cosmin
> }
> define service {
> use generic-service
> host_name DBIGASDS
> service_description Connected users to DB
> check_command check_oracle_health!--connect IGAS
> --username abc --password abc mode=connected-users
> contacts cosmin
>
>
> I also set in .bashrc the enviroment variables:
> export ORACLE_HOME=/usr/lib/oracle/11.2/client
> export PATH=$PATH:$ORACLE_HOME/bin
> export LD_LIBRARY_PATH=$ORACLE_HOME/lib
>
>
> But, in Nagios 3.4.1, i do not receive the corect status for those
> services:
> For all 3 services i receive:
> CRITICAL - cannot connect to IGAS. install_driver(Oracle) failed:
> Can't locate DBD/Oracle.pm in @INC (@INC contains:
> /usr/local/nagios/libexec /etc/perl /usr/local/lib/perl/5.14.2
> /usr/local/share/perl/5.14.2 /usr/lib/perl5 /usr/share/perl5
> /usr/lib/perl/5.14 /usr/share/perl/5.14 /usr/local/lib/site_perl .) at
> (eval 13) line 3.
>
>
> I realy don't know what to check anymore and why does it say that, so
> any help would be apreciated.
>
> More info:
> nagios@monitor:/usr/local/nagios/libexec$ ./check_oracle_health -V
> check_oracle_health (1.7.3)
> nagios@monitor:/usr/local/nagios/etc$ uname -a
> Linux monitor 3.2.0-29-generic-pae #46-Ubuntu SMP Fri Jul 27 17:25:43
> UTC 2012 i686 i686 i386 GNU/Linux
> nagios@monitor:/usr/local/nagios/etc$ lsb_release -a
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description: Ubuntu 12.04.1 LTS
> Release: 12.04
> Codename: precise
>
> Cosmin Neagu
> NOC Team Leader
> Str. I. G. Duca nr. 36
> Otopeni, Judetul Ilfov, 075100 Romania
> Tel: 021 303 3159 / 0732 669 193
> www.omnilogic.ro
> On 10/03/2012 09:34 AM, Claudio Kuenzler wrote:
>> It's not that hard and a lot of things are written in the
>> documentation of check_oracle_health.
>> I even wrote an article about this in September 2011 explaining the
>> steps:
>> http://www.claudiokuenzler.com/blog/192/install-perl-dbd-oracle-DBD::Oracle-on-SuSE-SLES10-without-cpan
>>
>>
>> You should do it the way you prefer of course. But in my setup I
>> wanted to run check_oracle_health on a standalone Nagios server. That
>> way I also see if there's a latency in the remote sql query. Real
>> life applications rarely use localhost connections.
>>
>> On Wed, Oct 3, 2012 at 8:14 AM, Cosmin Neagu
>> <cos...@om... <mailto:cos...@om...>> wrote:
>>
>> Well, thats the hard part for me, installing those ORA files -
>> didnt find yet how to do that. I think installing the plugin on
>> DBServer and using NRPE is easier.
>>
>> Cosmin Neagu
>> NOC Team Leader
>> Str. I. G. Duca nr. 36
>> Otopeni, Judetul Ilfov, 075100 Romania
>> Tel: 021 303 3159 / 0732 669 193
>> www.omnilogic.ro <http://www.omnilogic.ro>
>>
>> On 10/02/2012 06:05 PM, Claudio Kuenzler wrote:
>>>
>>> The plugin needs to be installed on the Oracle Database server.
>>>
>>>
>>> That's not entirely correct. It can also run on a standalone
>>> Nagios server.
>>> But you need to install the ora files to be able to launch the
>>> plugin against an Oracle DB server.
>>> I did that successfully on Nagios 3.3.1 against ORA11.
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Don't let slow site performance ruin your business. Deploy New Relic APM
>>> Deploy New Relic app performance management and know exactly
>>> what is happening inside your Ruby, Python, PHP, Java, and .NET app
>>> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
>>> http://p.sf.net/sfu/newrelic-dev2dev
>>>
>>>
>>> _______________________________________________
>>> Nagios-users mailing list
>>> Nag...@li... <mailto:Nag...@li...>
>>> 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
>>
>>
>> ------------------------------------------------------------------------------
>> Don't let slow site performance ruin your business. Deploy New
>> Relic APM
>> Deploy New Relic app performance management and know exactly
>> what is happening inside your Ruby, Python, PHP, Java, and .NET app
>> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
>> http://p.sf.net/sfu/newrelic-dev2dev
>> _______________________________________________
>> Nagios-users mailing list
>> Nag...@li...
>> <mailto:Nag...@li...>
>> 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
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Don't let slow site performance ruin your business. Deploy New Relic APM
>> Deploy New Relic app performance management and know exactly
>> what is happening inside your Ruby, Python, PHP, Java, and .NET app
>> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
>> http://p.sf.net/sfu/newrelic-dev2dev
>>
>>
>> _______________________________________________
>> Nagios-users mailing list
>> Nag...@li...
>> 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
>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_sfd2d_oct
>
>
> _______________________________________________
> Nagios-users mailing list
> Nag...@li...
> 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
|