Check_oracle_health plugin error

[Gerhard Lausser]

Hi Chetan,
 
looks like your tar command isn't able to handle filenames longer than 100
characters. (I think SuSE has this problem)
So when you unpacked the tar archive, not all of the files inside were
extracted. Please download the .shar.gz file and extract it with
sh check_oracle_health-1.6.2.shar.gz
 
Gerhard


  _____  

Von: chethan.mnc at wipro.com [mailto:chethan.mnc at wipro.com] 
Gesendet: Montag, 7. September 2009 12:38
An: Nagios-users at lists.sourceforge.net
Betreff: [Nagios-users] Check_oracle_health plugin error


Dear All,
 
I m trying to monitor oracle database hosted on solaris machine. when i try
to configure/compile  check_oracle_health plugin I m getting an error as
below...
 
Please let me know any work around for this error.
 
Regards,
Chethan M N
 
============================================================
bash-3.00# ./configure
checking for a BSD-compatible install... ./install-sh -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... nawk
checking whether make sets $(MAKE)... yes
checking how to create a pax tar archive... pax
checking build system type... sparc-sun-solaris2.10
checking host system type... sparc-sun-solaris2.10
checking for a BSD-compatible install... ./install-sh -c
checking whether make sets $(MAKE)... (cached) yes
variable with_statefiles_dir is /var/tmp/check_oracle_health
checking for sh... /usr/bin/sh
checking for perl... /usr/bin/perl
checking for gzip... /usr/bin/gzip
checking for gawk... no
checking for nawk... /usr/bin/nawk
checking for grep... /usr/bin/grep
checking for echo... /usr/bin/echo
checking for sed... /usr/bin/sed
checking for cat... /usr/bin/cat
configure: creating ./config.status
config.status: creating Makefile
config.status: creating plugins-scripts/Makefile
config.status: creating plugins-scripts/subst
config.status: creating t/Makefile
                       --with-perl: /usr/bin/perl
             --with-statefiles-dir: /var/tmp/check_oracle_health
                --with-nagios-user: nagios
               --with-nagios-group: nagios
bash-3.00# make
Making all in plugins-scripts
make: Fatal error: Don't know how to make target
`Nagios/DBD/Oracle/Server/Instance/SGA/SharedPool/DictionaryCache.pm'
Current working directory
/tmp/test/check_oracle_health-1.4.0.1/plugins-scripts
*** Error code 1
The following command caused the error:
failcom='exit 1'; \
for f in x $MAKEFLAGS; do \
  case $f in \
    *=* | --[!k]*);; \
    *k*) failcom='fail=yes';; \
  esac; \
done; \
dot_seen=no; \
target=`echo all-recursive | sed s/-recursive//`; \
list='plugins-scripts t'; for subdir in $list; do \
  echo "Making $target in $subdir"; \
  if test "$subdir" = "."; then \
    dot_seen=yes; \
    local_target="$target-am"; \
  else \
    local_target="$target"; \
  fi; \
  (cd $subdir && make  $local_target) \
  || eval $failcom; \
done; \
if test "$dot_seen" = "no"; then \
  make  "$target-am" || exit 1; \
fi; test -z "$fail"
make: Fatal error: Command failed for target `all-recursive'
============================================================================
=====

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20090909/f8511a7f/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
-------------- 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