[Nagiosplug-checkins] CVS: nagiosplug/contrib check_log2.pl,NONE,1.1 check_vcs.pl,NONE,1.1
Subhendu Ghosh
sghosh at users.sourceforge.net
Thu May 23 09:41:01 CEST 2002
Update of /cvsroot/nagiosplug/nagiosplug/contrib
In directory usw-pr-cvs1:/tmp/cvs-serv18045
Added Files:
check_log2.pl check_vcs.pl
Log Message:
New plugins from Aaron Bostick - Veritas Cluster, logfile
--- NEW FILE ---
#!/usr/bin/perl
#
# Log file regular expression detector for Nagios.
# Written by Aaron Bostick (abostick at mydoconline.com)
# Last modified: 05-02-2002
#
# Thanks and acknowledgements to Ethan Galstad for Nagios and the check_log
# plugin this is modeled after.
#
# Usage: check_log2 -l <log_file> -s <seek_file> -p <pattern> [-n <negpattern>]
#
# Description:
#
# This plugin will scan arbitrary text files looking for regular expression
# matches. The text file to scan is specified with <log_file>.
# <log_seek_file> is a temporary file used to store the seek byte position
# of the last scan. This file will be created automatically on the first
# scan. <pattern> can be any RE pattern that perl's s/// syntax accepte. Be
# forewarned that a bad pattern will send this script into never never land!
#
# Output:
#
# This plugin returns OK when a file is successfully scanned and no pattern
# matches are found. WARNING is returned when 1 or more patterns are found
# along with the pattern count and the line of the last pattern matched.
# CRITICAL is returned when an error occurs, such as file not found, etc.
#
# Notes (paraphrased from check_log's notes):
#
# 1. The "max_attempts" value for the service should be 1, as this
# will prevent Nagios from retrying the service check (the
# next time the check is run it will not produce the same results).
#
# 2. The "notify_recovery" value for the service should be 0, so that
# Nagios does not notify you of "recoveries" for the check. Since
# pattern matches in the log file will only be reported once and not
# the next time, there will always be "recoveries" for the service, even
# though recoveries really don't apply to this type of check.
#
# 3. You *must* supply a different <log_Seek_file> for each service that
# you define to use this plugin script - even if the different services
# check the same <log_file> for pattern matches. This is necessary
# because of the way the script operates.
#
# Examples:
#
# Check for error notices in messages
# check_log2 -l /var/log/messages -s ./check_log2.messages.seek -p 'err'
#
BEGIN {
if ($0 =~ s/^(.*?)[\/\\]([^\/\\]+)$//) {
$prog_dir = $1;
$prog_name = $2;
}
}
require 5.004;
use lib $main::prog_dir;
use utils qw($TIMEOUT %ERRORS &print_revision &support &usage);
use Getopt::Long;
sub print_usage ();
sub print_version ();
sub print_help ();
# Initialize strings
$log_file = '';
$seek_file = '';
$re_pattern = '';
$neg_re_pattern = '';
$pattern_count = 0;
$pattern_line = '';
$plugin_revision = '$Revision: 1.1 $ ';
# Grab options from command line
GetOptions
("l|logfile=s" => \$log_file,
"s|seekfile=s" => \$seek_file,
"p|pattern=s" => \$re_pattern,
"n|negpattern:s" => \$neg_re_pattern,
"v|version" => \$version,
"h|help" => \$help);
!($version) || print_version ();
!($help) || print_help ();
# Make sure log file is specified
($log_file) || usage("Log file not specified.\n");
# Make sure seek file is specified
($seek_file) || usage("Seek file not specified.\n");
# Make sure re pattern is specified
($re_pattern) || usage("Regular expression not specified.\n");
# Open log file
open LOG_FILE, $log_file || die "Unable to open log file $log_file: $!";
# Try to open log seek file. If open fails, we seek from beginning of
# file by default.
if (open(SEEK_FILE, $seek_file)) {
chomp(@seek_pos = <SEEK_FILE>);
close(SEEK_FILE);
# If file is empty, no need to seek...
if ($seek_pos[0] != 0) {
# Compare seek position to actual file size. If file size is smaller
# then we just start from beginning i.e. file was rotated, etc.
($dev,$ino,$mode,$nlink,$uid,$gid,$rdev,$size,$atime,$mtime,$ctime,$blksize,$blocks) = stat(LOG_FILE);
if ($seek_pos[0] <= $size) {
seek(LOG_FILE, $seek_pos[0], 0);
}
}
}
# Loop through every line of log file and check for pattern matches.
# Count the number of pattern matches and remember the full line of
# the most recent match.
while (<LOG_FILE>) {
if ($neg_re_pattern) {
if ((/$re_pattern/) && !(/$neg_re_pattern/)) {
$pattern_count += 1;
$pattern_line = $_;
}
} elsif (/$re_pattern/) {
$pattern_count += 1;
$pattern_line = $_;
}
}
# Overwrite log seek file and print the byte position we have seeked to.
open(SEEK_FILE, "> $seek_file") || die "Unable to open seek count file $seek_file: $!";
print SEEK_FILE tell(LOG_FILE);
# Close seek file.
close(SEEK_FILE);
# Close the log file.
close(LOG_FILE);
# Print result and return exit code.
if ($pattern_count) {
print "($pattern_count): $pattern_line";
exit $ERRORS{'WARNING'};
} else {
print "OK - No matches found.\n";
exit $ERRORS{'OK'};
}
#
# Subroutines
#
sub print_usage () {
print "Usage: $prog_name -l <log_file> -s <log_seek_file> -p <pattern> [-n <negpattern>]\n";
print "Usage: $prog_name [ -v | --version ]\n";
print "Usage: $prog_name [ -h | --help ]\n";
}
sub print_version () {
print_revision($prog_name, $plugin_revision);
exit $ERRORS{'OK'};
}
sub print_help () {
print_revision($prog_name, $plugin_revision);
print "\n";
print "Scan arbitrary log files for regular expression matches.\n";
print "\n";
print_usage();
print "\n";
print "-l, --logfile=<logfile>\n";
print " The log file to be scanned\n";
print "-s, --seekfile=<seekfile>\n";
print " The temporary file to store the seek position of the last scan\n";
print "-p, --pattern=<pattern>\n";
print " The regular expression to scan for in the log file\n";
print "-n, --negpattern=<negpattern>\n";
print " The regular expression to skip in the log file\n";
print "\n";
support();
exit $ERRORS{'OK'};
}
--- NEW FILE ---
#!/usr/bin/perl
#
# Veritas Cluster System monitor for Nagios.
# Written by Aaron Bostick (abostick at mydoconline.com)
# Last modified: 05-22-2002
#
# Usage: check_vcs {-g <vcs_group> | -r <vcs_resource> } -s <vcs_system> [-n]
#
# Description:
#
# This plugin is just a perl wrapper to the vcs commands hagrp and hares.
# You specify what group/resource and system you want the status for, and
# the plugin returns a status code based on the output of either hagrp or
# hares.
#
# Normal hagrp/hares status codes are ONLINE and OFFLINE depending on where the
# cluster service currently lives. I have added an option, -n, which makes
# the expected state to be OFFLINE rather than ONLINE so you can run the
# plugin on both sides of the cluster and will receive critical alerts when
# the cluster fails over i.e. a proper failover will make the standby node
# go from OFFLINE to ONLINE for the group, so an ONLINE status should alert
# you! (You do want to know when the cluster fails over, right? :))
#
# Output:
#
# This plugin returns OK when hagrp/hares -state <grp> -sys <system> returns
# ONLINE (or OFFLINE if -n is specified). Any other hagrp/hares string returns
# CRITICAL... Would a WARNING ever be justified??? UNKNOWN is returned if
# hagrp/hares cannot run for some reason.
#
# Examples:
#
# Make sure group oracle is ONLINE on server dbserver1:
# check_vcs -g oracle -s dbserver1
#
# Make sure group oracle is OFFLINE on server dbserver2:
# check_vcs -g oracle -s dbserver2 -n
#
# Make sure resource oraip is ONLINE on server dbserver1:
# check_vcs -r oraip -s dbserver1
#
# Make sure resource oraip is OFFLINE on server dbserver2:
# check_vcs -r oraip -s dbserver2 -n
#
BEGIN {
if ($0 =~ s/^(.*?)[\/\\]([^\/\\]+)$//) {
$prog_dir = $1;
$prog_name = $2;
}
}
require 5.004;
use lib $main::prog_dir;
use utils qw($TIMEOUT %ERRORS &print_revision &support);
use Getopt::Long;
sub print_usage ();
sub print_version ();
sub print_help ();
# Initialize strings
$vcs_bin = '/opt/VRTSvcs/bin';
$vcs_command = '';
$vcs_arg = '';
$vcs_group = '';
$vcs_resource = '';
$vcs_system = '';
$vcs_negate = '';
$vcs_result = '';
$vcs_expected_result = 'ONLINE';
$plugin_revision = '$Revision: 1.1 $ ';
# Grab options from command line
GetOptions
("g|group:s" => \$vcs_group,
"r|resouce:s" => \$vcs_resource,
"s|system=s" => \$vcs_system,
"n|negate" => \$vcs_negate,
"v|version" => \$version,
"h|help" => \$help);
(!$version) || print_version ();
(!$help) || print_help ();
(!$vcs_negate) || ($vcs_expected_result = 'OFFLINE');
# Make sure group and resource is not specified
!($vcs_group && $vcs_resource) || usage("Please specify either a group or a resource, but not both.\n");
# Make sure group or resource is specified
($vcs_group || $vcs_resource) || usage("HA group or resource not specified.\n");
# Make sure system is specified
($vcs_system) || usage("HA system not specified.\n");
# Specify proper command
if ($vcs_group) {
$vcs_command = 'hagrp';
$vcs_arg = $vcs_group;
} else {
$vcs_command = 'hares';
$vcs_arg = $vcs_resource;
}
# Run command and save output
$vcs_result = `$vcs_bin/$vcs_command -state $vcs_arg -sys $vcs_system`;
chomp ($vcs_result);
# If empty result, return UNKNOWN
if (!$vcs_result) {
print "UNKNOWN: Problem running $vcs_command...\n";
exit $ERRORS{'UNKNOWN'};
}
# If result is expected, return OK
# If result is not expected, return CRITICAL
if ($vcs_result eq $vcs_expected_result) {
print "OK: $vcs_command $vcs_arg is $vcs_result\n";
exit $ERRORS{'OK'};
} else {
print "CRITICAL: $vcs_command $vcs_arg is $vcs_result\n";
exit $ERRORS{'CRITICAL'};
}
#
# Subroutines
#
sub usage () {
print @_;
print_usage();
exit $ERRORS{'OK'};
}
sub print_usage () {
print "\nUsage: $prog_name { -g <vcs_group> | -r <vcs_resource> } -s <vcs_system> [-n]\n";
print "Usage: $prog_name [ -v | --version ]\n";
print "Usage: $prog_name [ -h | --help ]\n";
}
sub print_version () {
print_revision($prog_name, $plugin_revision);
exit $ERRORS{'OK'};
}
sub print_help () {
print_revision($prog_name, $plugin_revision);
print "\n";
print "Validate output from hagrp/hares command.\n";
print "\n";
print_usage();
print "\n";
print "-g, --group=<vcs_group>\n";
print " The HA group to be validated\n";
print "-r, --resource=<vcs_resource>\n";
print " The HA resource to be validated\n";
print "-s, --system=<vcs_system>\n";
print " The HA system where the group/resource lives\n";
print "-n, --negate=<negate>\n";
print " Set expected result to OFFLINE instead of ONLINE\n";
print "\n";
support();
exit $ERRORS{'OK'};
}
More information about the Commits
mailing list