June 2008 - Xymon - Xymon mailman web

Snapshot has ping failure
by matt＠oddprocess.org 20 Jun '08

20 Jun '08

I installed today's snapshot and since then the conn test seems to fail: Service conn on vir is not OK : Host does not respond to ping System unreachable for 9 poll periods (5743 seconds) I am using fping and have configured to do so at configure time, and I double checked to make sure fping works manually: $ /usr/sbin/fping vir vir is alive So that works. Any suggestions? -- Matthew Daubenspeck http://oddprocess.org Gentoo Linux x86_64 Dual Core AMD Opteron(tm) Processor 165 13:33:27 up 221 days, 4:21, 4 users, load average: 0.06, 0.02, 0.00

1 0

Snapshot has ping failure
by matt＠oddprocess.org 20 Jun '08

20 Jun '08

I just installed the snapshot from today and it seems that all hosts conn now fails: Service conn on foo is not OK : Host does not respond to ping System unreachable for 6 poll periods (4840 seconds) I have manually run fping and it works. I have also selected to use it during configure time. Any suggestions? -- Matthew Daubenspeck http://oddprocess.org Gentoo Linux x86_64 Dual Core AMD Opteron(tm) Processor 165 13:15:46 up 221 days, 4:03, 4 users, load average: 0.00, 0.00, 0.00

1 0

Invalid timespec from DOWNTIME definition
by nelis＠nlr.nl 20 Jun '08

20 Jun '08

Hello, On 2008.02.05 linuxmasterjedi (at) free.fr wrote: > Hi, > [Skipping two questions] > > Finaly, the last question : > 2008-02-05 13:43:19 Invalid timespec - expected 4 digits, got: 'BackUP' > 2008-02-05 13:43:19 Bad timespec (missing colon or wrong weekdays): 1 > 2008-02-05 13:43:22 Invalid timespec - expected 4 digits, got: 'BackUP' > 2008-02-05 13:43:22 Bad timespec (missing colon or wrong weekdays): 1 > 2008-02-05 13:43:24 Invalid timespec - expected 4 digits, got: 'BackUP' > 2008-02-05 13:43:24 Bad timespec (missing colon or wrong weekdays): 1 > > Here is my bb-hosts configuration file : > 1.2.3.4 server1 # conn ssh DOWNTIME=60:2300:2359:BackUP,1:0000:0500:BackUP > 1.2.3.5 server2 # conn ssh DOWNTIME=60:2300:2359:BackUP,1:0000:0500:BackUP > 1.2.3.6 server3 # conn ssh DOWNTIME=60:2300:2359:BackUP,1:0000:0500:BackUP > 1.2.3.7 server4 # conn ssh DOWNTIME=60:2300:2359:BackUP,1:0000:0500:BackUP > > Did I configured something wrong ? The same goes for me. Hobbit is reporting this error quite some time now, but since the last restart it also reports the error in the hobbitd test, under the heading "Latest error messages", causing the hobbit server to become yellow. Changing the cause field in a DOWNTIME specification resulted in the same change in the error, which is reported both in hobbitd.log and in the hobbitd test. We are running Hobbit version 4.3.0-20070727. Is there another way of solving this problem other than moving to the latest snapshot? Kind regards, Wim Nelis. ********************************************************************************************** Our disclaimer (http://www.nlr.nl/emaildisclaimer) is valid for this e-mail message. **********************************************************************************************

2 1

Unrecognized escape error in shares.pl
by Doug.Linder＠sabic-ip.com 20 Jun '08

20 Jun '08

I've searched the archive and not found anything about this. Every five minutes, the root account on this system gets another copy of the mail below. I've triple-chekced and the bb4 user does NOT have any cron jobs. Despite the name we are running Hobbit and not BB. Does anyone have any idea what the problem might be? This tends to fill up the mail spool... ----- From: root at hostname.fqdn <mailto:root at hostname.fqdn> (Cron Daemon) To: <mailto:root at m> root@ <mailto:root at hostname.fqdn> hostname.fqdn Subject: Cron <mailto:bb4 at v> bb4@ <mailto:bb4 at hostname> hostname /bb4/bb/server/ext/shares.pl X-Cron-Env: <SHELL=/bin/bash> X-Cron-Env: <PATH=/sbin:/bin:/usr/sbin:/usr/bin> X-Cron-Env: <MAILTO=root> X-Cron-Env: <HOME=/> X-Cron-Env: <LOGNAME=bb4> Unrecognized escape \w passed through at /bb4/bb/server/ext/shares.pl line 84. ------- --- Doug Linder UNIX Systems Administrator CompuCom Systems, Inc. SABIC Innovative Plastics T: 413 448 7563 D: *838 7563 E: doug.linder at sabic-ip.com <mailto:doug.linderrdoug.linder at sabic-ip.com>

3 4

[hobbit] Hobbit client to monitor Solaris RAID devices
by Martin.Ward＠colt.net 20 Jun '08

20 Jun '08

The last one seems to have lost something in translation. Please accept my apologies and use this (working) version! #!/bin/sh # # meta: Sun Enterprise Server check - BB external script test # ##### Purpose is to report back to a central server, all Solaris ##### DiskSuite RAID software faults. ##### # # version 1.0 # version 2.0 - properly uses $THIS_HOST instead of $MACHINE due to fqdn using # comma in name # removed all direct program calls in favor of env vars in bbsys.* # changed /tmp to $BBTMP # meta to $TEST # $THIS_HOST to $MACHINE # removed code that checked for the existance of "meta" # after the server name in bb-hosts # moved comment explaining purpose of script to start of code # caused output of metadb, metastat, and metahs to be displayed # on the web page # version 2.1 - Warns if default values are not used # Applied changes by Todd Jimenez # - created get_header and get_footer functions # - set summary value # - added &red to red alerts # - added &yellow to yellow alerts # restored functionality to check for the existence of "meta" # after the server name in bb-hosts, but now optional # version 2.2 - Change status to &yellow when disk is resyncing. # version 2.3 - Added code to check for raidctl command and perfrom raid checks # using that if it's there. # Using this version REQUIRES sudo ! # raidctl(1m) on Solaris can only be run as root. Sudo is a # nice workaround. # # BIG BROTHER / XXXXXXXXXXXXXXXX status # # Written by Galen Johnson # on October 25, 2000 # # Inspired by a module of the perl clone of BB written # by Charles Hall in August 1998 # # Based on code found in the DiskSuite manual # # 2.0 Updates by Mike Arnold <mike at razorsedge dot org> # on September 27, 2001 # # 2.1 Updates by Mike Arnold <mike at razorsedge dot org> # on November 23, 2001 # # 2.2 Updates by Martin Ward <martin dot ward at colt dot net> # on Monday 19th May 2008 # # 2.3 Updates by Martin Ward <martin dot ward at colt dot net> # on Monday 19th June 2008 ######################################## # NOTE # This has been tested with BB 1.8c and Hobbit 4.2.0 # # Tested on : # Sun 220R, 420R, E250/450, E4500 ######################################## ######################################## # INSTALLATION # step 1 - update bb-bbexttab to include this meta # (older BB versions update EXT section of the bbdef.sh script) # # step 2 - copy lines mentioned to bbsys.local (without the #'s) # # step 3 - if you are using an older version of BB without bb-bbexttab # and you don't want this run on every client uncomment # CHECK_BB_HOSTS="Y" and add the name of this $TEST to # bb-hosts for this client. eg. # myserver1.domain.com # meta # # step 4 - If you have sudo installed need to use the raidctl control, # add the following line into your /etc/sudoers file: # hobbit ALL=(root) NOPASSWD:/usr/sbin/raidctl -l # step 5 - restart Big Brother # # NOTE - the TEST variable in the configuration section, this is the name used # as the column header. ######################################## ################################## # CONFIGURE IT HERE ################################## TEST="raid" SCRIPT_VER="bb-raid.sh v2.3" BBPROG="$0"; export BBPROG DEBUG=0 # # Start of lines to put in bbsys.local # NOTE: MDBIN can be either /usr/sbin or /usr/opt/SUNWmd/sbin # MDBIN=/usr/sbin METADB=${MDBIN}/metadb METAHS=${MDBIN}/metahs METASTAT=${MDBIN}/metastat SUDO=/opt/sfw/bin/sudo RAIDCTL=/usr/sbin/raidctl export MDBIN METADB METAHS METASTAT SUDO RAIDCTL # # End of lines to put in bbsys.local # # define colours for graphics # Comment these out if using older BB versions RED_PIC="&red" YELLOW_PIC="&yellow" GREEN_PIC="&green" # don't scan through bb-hosts every time # this is here for older BB versions without bb-bbexttab # uncomment to activate #CHECK_BB_HOSTS=Y ################################## # Start of script ################################## #BBHOME="/home/bb/bb"; export BBHOME if test ! "$BBHOME" then echo "template: BBHOME is not set" exit 1 fi if test ! -d "$BBHOME" then echo "template: BBHOME is invalid" exit 1 fi if test ! "$BBTMP" # GET DEFINITIONS IF NEEDED then # echo "*** LOADING BBDEF ***" . $BBHOME/etc/bbdef.sh # INCLUDE STANDARD DEFINITIONS fi get_header() { echo "" echo "$1 ($2) " # If you do not want the header in a bigger font use line below instead #echo "$1 ($2)" # If you want the "Paul Luzzi" look uncomment this section and comment # out the above sections: #echo "<DIV ALIGN=\"CENTER\"><HR>" #echo "============== $1 ==============" #echo "--- ($2) ---" #echo "<HR></DIV>" #echo "<BLOCKQUOTE>" } get_footer() { echo "" # If you want the "Paul Luzzi" look uncomment this section and comment # out the above sections: #echo "</BLOCKQUOTE>" } ##### ##### Get MD Status proc - used if the server uses a metadb ##### get_md_status() { ##### ##### Setup some variables for use later ##### COLOR="green" # Check defaults have been set if [ "$MDBIN" = "" ]; then MDBIN=/usr/sbin echo "" echo "$YELLOW_PIC MDBIN command is not defined in etc/bbsys.local - using default: $MDBIN" fi if [ "$METADB" = "" ]; then METADB=${MDBIN}/metadb echo "" echo "$YELLOW_PIC METADB command is not defined in etc/bbsys.local - using default: $METADB" fi if [ "$METAHS" = "" ]; then METAHS=${MDBIN}/metahs echo "" echo "$YELLOW_PIC METAHS command is not defined in etc/bbsys.local - using default: $METAHS" fi if [ "$METASTAT" = "" ]; then METASTAT=${MDBIN}/metastat echo "" echo "$YELLOW_PIC METASTAT command is not defined in etc/bbsys.local - using default: $METASTAT" fi ### ### Check replicas for problems, capital letters in the flags indicate an error. ### get_header "MetaDatabases" "$METADB -i" dbtrouble=`${METADB} 2>/dev/null | ${TAIL} +2 | ${AWK} '{ fl = substr($0,1,20); if (fl ~ /[A-Z]/) print $0 }'` if [ "${dbtrouble}" ]; then COLOR="red" echo "" echo "$RED_PIC Database replicas are not active: " echo "" ${METADB} -i 2>/dev/null else ${METADB} -i 2>/dev/null fi get_footer ### ### Check the metadevice state, if the state is not Okay, something is up. ### get_header "Metadevices" "$METASTAT" mdtrouble=`${METASTAT} | ${GREP} "Resyncing"` if [ "${mdtrouble}" ]; then COLOR="yellow" CLR_PIC="$YELLOW_PIC" fi mdtrouble=`${METASTAT} | ${GREP} -v "Resyncing" | ${AWK} '/State:/ { if ( $2 != "Okay" ) print $0 }'` if [ "${mdtrouble}" ]; then COLOR="red" CLR_PIC="$RED_PIC" fi if [ "$COLOR" != "green" ]; then echo "" echo "$CLR_PIC Metadevices are not Okay: " echo "" ${METASTAT} else ${METASTAT} fi get_footer ### ### Check the hotspares to see if any have been used. ### ### Hotspare test disabled because writing to BBOUT when no hotspare pools # get_header "Hot Spares" "$METAHS -i" # hstrouble=`${METAHS} -i | ${AWK} ' /blocks/ { if ( $2 != "Available" ) print $0 }'` # if [ "${hstrouble}" ]; then # if [ COLOR != "red" ]; then # COLOR="yellow" # fi # echo "" # echo "$YELLOW_PIC Hot spares in use: " # echo "" # ${METAHS} -i 2>&1 # else # ${METAHS} -i 2>&1 # fi # get_footer ##### ##### Make sure to export COLOR so that it gets back to "central" ##### export COLOR ##### ##### End of get_md_status proc ##### } ##### ##### Get LSI Status proc - used if the server has LSI1030 or ##### LSI1064 RAID-enabled controllers. ##### get_lsi_status() { ##### ##### Setup some variables for use later ##### COLOR="green" # Check defaults have been set if [ "$RAIDCTL" = "" ]; then RAIDCTL=/usr/sbin echo "" echo "$YELLOW_PIC RAIDCTL command is not defined in etc/bbsys.local - using default: $RAIDCTL" fi ### ### Check replicas for problems. Strip off the header then print any entries ### that do not have the work OK in them, or do have the words "DEGRADED" or ### "FAILED". ### dberrors=`${SUDO} ${RAIDCTL} -l | ${AWK} 'BEGIN { D=0; } /------/ { D=1; next; } /DEGRADED|FAILED/ { if (D==1) {print $0; next; } } / OK/ { if (D==1) { next; } } { if (D==1) {print "1 ",$0; } }' ` if [ "${dberrors}" ]; then COLOR="red" echo "" echo "$RED_PIC RAID errors exist: " echo "<pre>" ${SUDO} ${RAIDCTL} -l echo "</pre>" else echo "<pre>" ${SUDO} ${RAIDCTL} -l echo "</pre>" fi get_footer ##### ##### Make sure to export COLOR so that it gets back to "central" ##### export COLOR ##### ##### End of get_lsi_status proc ##### } ##### ##### Get Status proc - used to get all responses ##### get_status() { ##### ##### Decide which RAID we have, then call the right subroutine. ##### COLOR=WHITE export COLOR if [ "${RAIDCTL}" != "" ]; then TST=`${SUDO} ${RAIDCTL} -l | grep "No RAID volumes found" | wc -l` if [ $TST -lt 1 ] then get_lsi_status fi fi if [ "${METADB}" != "" ]; then TST=`${METADB} 2>&1 | grep "there are no existing databases" | wc -l` if [ $TST -lt 1 ] then get_md_status fi fi ##### ##### End of get_status proc ##### } ##### ##### Main body ##### if [ "$CHECK_BB_HOSTS" = "Y" ]; then # convert "," to "." in the hostname MACHINE_WITH_DOTS=`echo $MACHINE | $SED 's/,/\./g'` $GREP $MACHINE_WITH_DOTS $BBHOSTS | $GREP "$TEST" | while read line do if [ ! -z "$line" ]; then get_status > $BBTMP/$MACHINE.$TEST ### Tack the script version on to the end echo "<table><tr><td align=right>${SCRIPT_VER}</td></tr></table>" >> $BBTMP/$MACHINE.$TEST if [ ${DEBUG} = "1" ]; then echo "$BB $BBDISP \"status $BBTMP/$MACHINE.$TEST $COLOR" `$DATE` `$CAT $BBTMP/$MACHINE.$TEST` "\"" >> $BBTMP/raid.output else # NOW USE THE BB COMMAND TO SEND THE DATA ACROSS $BB $BBDISP "status $BBTMP/$MACHINE.$TEST $COLOR `$DATE` `$CAT $BBTMP/$MACHINE.$TEST` " fi fi done else get_status > $BBTMP/$MACHINE.$TEST ### Tack the script version on to the end echo "<table><tr><td align=right>${SCRIPT_VER}</td></tr></table>" >> $BBTMP/$MACHINE.$TEST if [ ${DEBUG} = "1" ]; then echo "$BB $BBDISP \"status $MACHINE.$TEST $COLOR" `$DATE` `$CAT $BBTMP/$MACHINE.$TEST` "\" " >> $BBTMP/raid.output else # NOW USE THE BB COMMAND TO SEND THE DATA ACROSS $BB $BBDISP "status $MACHINE.$TEST $COLOR `$DATE` `$CAT $BBTMP/$MACHINE.$TEST` " fi fi # Clean up our mess # Checking for existence of each file since the whole test may be optional # and may not actually run on every client # if [ -f $BBTMP/$MACHINE.$TEST ]; then $RM $BBTMP/$MACHINE.$TEST fi ############################################## # end of script ############################################## ************************************************************************************* The message is intended for the named addressee only and may not be disclosed to or used by anyone else, nor may it be copied in any way. The contents of this message and its attachments are confidential and may also be subject to legal privilege. If you are not the named addressee and/or have received this message in error, please advise us by e-mailing security at colt.net and delete the message and any attachments without retaining any copies. Internet communications are not secure and COLT does not accept responsibility for this message, its contents nor responsibility for any viruses. No contracts can be created or varied on behalf of COLT Telecommunications, its subsidiaries or affiliates ("COLT") and any other party by email Communications unless expressly agreed in writing with such other party. Please note that incoming emails will be automatically scanned to eliminate potential viruses and unsolicited promotional emails. For more information refer to www.colt.net or contact us on +44(0)20 7390 3900.

1 0

Hobbit client to monitor Solaris RAID devices
by Martin.Ward＠colt.net 20 Jun '08

20 Jun '08

All, I have been using a script called bb-raid.sh for a few years to monitor Solaris meta devices. I then came across a Solaris server using raidctl for hardware raid, so I modified bb-raid.sh to monitor this one as well. Here is the code. Feel free to use it as you wish: |\/| ==== #!/bin/sh # # meta: Sun Enterprise Server check - BB external script test # ##### Purpose is to report back to a central server, all Solaris ##### DiskSuite RAID software faults. ##### # # version 1.0 # version 2.0 - properly uses $THIS_HOST instead of $MACHINE due to fqdn using # comma in name # removed all direct program calls in favor of env vars in bbsys.* # changed /tmp to $BBTMP # meta to $TEST # $THIS_HOST to $MACHINE # removed code that checked for the existance of "meta" # after the server name in bb-hosts # moved comment explaining purpose of script to start of code # caused output of metadb, metastat, and metahs to be displayed # on the web page # version 2.1 - Warns if default values are not used # Applied changes by Todd Jimenez # - created get_header and get_footer functions # - set summary value # - added &red to red alerts # - added &yellow to yellow alerts # restored functionality to check for the existence of "meta" # after the server name in bb-hosts, but now optional # version 2.2 - Change status to &yellow when disk is resyncing. # version 2.3 - Added code to check for raidctl command and perfrom raid checks # using that if it's there. # Using this version REQUIRES sudo ! # raidctl(1m) on Solaris can only be run as root. Sudo is a # nice workaround. # # BIG BROTHER / XXXXXXXXXXXXXXXX status # # Written by Galen Johnson # on October 25, 2000 # # Inspired by a module of the perl clone of BB written # by Charles Hall in August 1998 # # Based on code found in the DiskSuite manual # # 2.0 Updates by Mike Arnold <mike at razorsedge dot org> # on September 27, 2001 # # 2.1 Updates by Mike Arnold <mike at razorsedge dot org> # on November 23, 2001 # # 2.2 Updates by Martin Ward <martin dot ward at colt dot net> # on Monday 19th May 2008 # # 2.3 Updates by Martin Ward <martin dot ward at colt dot net> # on Monday 19th June 2008 ######################################## # NOTE # This has been tested with BB 1.8c and Hobbit 4.2.0 # # Tested on : # Sun 220R, 420R, E250/450, E4500 ######################################## ######################################## # INSTALLATION # step 1 - update bb-bbexttab to include this meta # (older BB versions update EXT section of the bbdef.sh script) # # step 2 - copy lines mentioned to bbsys.local (without the #'s) # # step 3 - if you are using an older version of BB without bb-bbexttab # and you don't want this run on every client uncomment # CHECK_BB_HOSTS="Y" and add the name of this $TEST to # bb-hosts for this client. eg. # myserver1.domain.com # meta # # step 4 - If you have sudo installed need to use the raidctl control, # add the following line into your /etc/sudoers file: # hobbit ALL=(root) NOPASSWD:/usr/sbin/raidctl -l # step 5 - restart Big Brother # # NOTE - the TEST variable in the configuration section, this is the name used # as the column header. ######################################## ################################## # CONFIGURE IT HERE ################################## TEST="raid" SCRIPT_VER="bb-raid.sh v2.3" BBPROG="$0"; export BBPROG DEBUG=0 # # Start of lines to put in bbsys.local # NOTE: MDBIN can be either /usr/sbin or /usr/opt/SUNWmd/sbin # MDBIN=/usr/sbin METADB=${MDBIN}/metadb METAHS=${MDBIN}/metahs METASTAT=${MDBIN}/metastat SUDO=/opt/sfw/bin/sudo RAIDCTL=/usr/sbin/raidctl export MDBIN METADB METAHS METASTAT SUDO RAIDCTL # # End of lines to put in bbsys.local # # define colours for graphics # Comment these out if using older BB versions RED_PIC="&red" YELLOW_PIC="&yellow" GREEN_PIC="&green" # don't scan through bb-hosts every time # this is here for older BB versions without bb-bbexttab # uncomment to activate #CHECK_BB_HOSTS=Y ################################## # Start of script ################################## #BBHOME="/home/bb/bb"; export BBHOME if test ! "$BBHOME" then echo "template: BBHOME is not set" exit 1 fi if test ! -d "$BBHOME" then echo "template: BBHOME is invalid" exit 1 fi if test ! "$BBTMP" # GET DEFINITIONS IF NEEDED then # echo "*** LOADING BBDEF ***" . $BBHOME/etc/bbdef.sh # INCLUDE STANDARD DEFINITIONS fi get_header() { echo "" echo "$1 ($2) " # If you do not want the header in a bigger font use line below instead #echo "$1 ($2)" # If you want the "Paul Luzzi" look uncomment this section and comment # out the above sections: #echo "<DIV ALIGN=\"CENTER\"><HR>" #echo "============== $1 ==============" #echo "--- ($2) ---" #echo "<HR></DIV>" #echo "<BLOCKQUOTE>" } get_footer() { echo "" # If you want the "Paul Luzzi" look uncomment this section and comment # out the above sections: #echo "</BLOCKQUOTE>" } ##### ##### Get MD Status proc - used if the server uses a metadb ##### get_md_status() { ##### ##### Setup some variables for use later ##### COLOR="green" # Check defaults have been set if [ "$MDBIN" = "" ]; then MDBIN=/usr/sbin echo "" echo "$YELLOW_PIC MDBIN command is not defined in etc/bbsys.local - using de fault: $MDBIN" fi if [ "$METADB" = "" ]; then METADB=${MDBIN}/metadb echo "" echo "$YELLOW_PIC METADB command is not defined in etc/bbsys.local - using d efault: $METADB" fi if [ "$METAHS" = "" ]; then METAHS=${MDBIN}/metahs echo "" echo "$YELLOW_PIC METAHS command is not defined in etc/bbsys.local - using d efault: $METAHS" fi if [ "$METASTAT" = "" ]; then METASTAT=${MDBIN}/metastat echo "" echo "$YELLOW_PIC METASTAT command is not defined in etc/bbsys.local - using default: $METASTAT" fi ### ### Check replicas for problems, capital letters in the flags indicate an erro r. ### get_header "MetaDatabases" "$METADB -i" dbtrouble=`${METADB} 2>/dev/null | ${TAIL} +2 | ${AWK} '{ fl = substr($0,1,20) ; if (fl ~ /[A-Z]/) print $0 }'` if [ "${dbtrouble}" ]; then COLOR="red" echo "" echo "$RED_PIC Database replicas are not active: " echo "" ${METADB} -i 2>/dev/null else ${METADB} -i 2>/dev/null fi get_footer ### ### Check the metadevice state, if the state is not Okay, something is up. ### get_header "Metadevices" "$METASTAT" mdtrouble=`${METASTAT} | ${GREP} "Resyncing"` if [ "${mdtrouble}" ]; then COLOR="yellow" CLR_PIC="$YELLOW_PIC" fi mdtrouble=`${METASTAT} | ${GREP} -v "Resyncing" | ${AWK} '/State:/ { if ( $2 ! = "Okay" ) print $0 }'` if [ "${mdtrouble}" ]; then COLOR="red" CLR_PIC="$RED_PIC" fi if [ "$COLOR" != "green" ]; then echo "" echo "$CLR_PIC Metadevices are not Okay: " echo "" ${METASTAT} else ${METASTAT} fi get_footer ### ### Check the hotspares to see if any have been used. ### ### Hotspare test disabled because writing to BBOUT when no hotspare pools # get_header "Hot Spares" "$METAHS -i" # hstrouble=`${METAHS} -i | ${AWK} ' /blocks/ { if ( $2 != "Available" ) print $0 }'` # if [ "${hstrouble}" ]; then # if [ COLOR != "red" ]; then # COLOR="yellow" # fi # echo "" # echo "$YELLOW_PIC Hot spares in use: " # echo "" # ${METAHS} -i 2>&1 # else # ${METAHS} -i 2>&1 # fi # get_footer ##### ##### Make sure to export COLOR so that it gets back to "central" ##### export COLOR ##### ##### End of get_md_status proc ##### } ##### ##### Get LSI Status proc - used if the server has LSI1030 or ##### LSI1064 RAID-enabled controllers. ##### get_lsi_status() { ##### ##### Setup some variables for use later ##### COLOR="green" # Check defaults have been set if [ "$RAIDCTL" = "" ]; then RAIDCTL=/usr/sbin echo "" echo "$YELLOW_PIC RAIDCTL command is not defined in etc/bbsys.local - using default: $RAIDCTL" fi ### ### Check replicas for problems. Strip off the header then print any entries ### that do not have the work OK in them, or do have the words "DEGRADED" or ### "FAILED". ### dberrors=`${SUDO} ${RAIDCTL} -l | ${AWK} 'BEGIN { D=0; } /------/ { D=1; next; } /DEGRADED|FAILED/ { if (D==1) {print $0; next; } } / OK/ { if (D==1) { next; } } { if (D==1) {print "1 ",$0; } }' ` if [ "${dberrors}" ]; then COLOR="red" echo "" echo "$RED_PIC RAID errors exist: " echo "<pre>" ${SUDO} ${RAIDCTL} -l echo "</pre>" else echo "<pre>" ${SUDO} ${RAIDCTL} -l echo "</pre>" fi get_footer ##### ##### Make sure to export COLOR so that it gets back to "central" ##### export COLOR ##### ##### End of get_lsi_status proc ##### } ##### ##### Get Status proc - used to get all responses ##### get_status() { ##### ##### Decide which RAID we have, then call the right subroutine. ##### COLOR=WHITE export COLOR if [ "${RAIDCTL}" != "" ]; then TST=`${SUDO} ${RAIDCTL} -l | grep "No RAID volumes found" | wc -l` if [ $TST -lt 1 ] then get_lsi_status fi fi if [ "${METADB}" != "" ]; then TST=`${METADB} 2>&1 | grep "there are no existing databases" | wc -l` if [ $TST -lt 1 ] then get_md_status fi fi ##### ##### End of get_status proc ##### } ##### ##### Main body ##### if [ "$CHECK_BB_HOSTS" = "Y" ]; then # convert "," to "." in the hostname MACHINE_WITH_DOTS=`echo $MACHINE | $SED 's/,/\./g'` $GREP $MACHINE_WITH_DOTS $BBHOSTS | $GREP "$TEST" | while read line do if [ ! -z "$line" ]; then get_status > $BBTMP/$MACHINE.$TEST ### Tack the script version on to the end echo "<table><tr><td align=right>${SCRIPT_VER}</td></tr></table>" >> $BBTMP/$MACHINE.$TEST if [ ${DEBUG} = "1" ]; then echo "$BB $BBDISP \"status $BBTMP/$MACHINE.$TEST $COLOR" `$DATE` `$CAT $BBTMP/$MACHINE.$TEST` "\"" >> $BBTMP/raid.output else # NOW USE THE BB COMMAND TO SEND THE DATA ACROSS $BB $BBDISP "status $BBTMP/$MACHINE.$TEST $COLOR `$DATE` `$CAT $BBTMP/$MACHINE.$TEST` " fi fi done else get_status > $BBTMP/$MACHINE.$TEST ### Tack the script version on to the end echo "<table><tr><td align=right>${SCRIPT_VER}</td></tr></table>" >> $BBTMP/$MACHINE.$TEST if [ ${DEBUG} = "1" ]; then echo "$BB $BBDISP \"status $MACHINE.$TEST $COLOR" `$DATE` `$CAT $BBTMP/$MACHINE.$TEST` "\" " >> $BBTMP/raid.output else # NOW USE THE BB COMMAND TO SEND THE DATA ACROSS $BB $BBDISP "status $MACHINE.$TEST $COLOR `$DATE` `$CAT $BBTMP/$MACHINE.$TEST` " fi fi # Clean up our mess # Checking for existence of each file since the whole test may be optional # and may not actually run on every client # if [ -f $BBTMP/$MACHINE.$TEST ]; then $RM $BBTMP/$MACHINE.$TEST fi ############################################## # end of script ############################################## ==== -- Martin Ward Network Systems Operations Specialist DDI: +44 (0) 20 7863 5218 Fax: +44 (0) 20 7863 5610 Mob: +44 (0) 7971 97 77 21 www.colt.net Data | Voice | Managed Services Help reduce your carbon footprint | Think before you print COLT Telecommunications, Beaufort House, 15 St Botolph Street, London, EC3A 7QN UK Registered in England and Wales, registered number 02452736, VAT number GB 645 4205 50 ************************************************************************************* The message is intended for the named addressee only and may not be disclosed to or used by anyone else, nor may it be copied in any way. The contents of this message and its attachments are confidential and may also be subject to legal privilege. If you are not the named addressee and/or have received this message in error, please advise us by e-mailing security at colt.net and delete the message and any attachments without retaining any copies. Internet communications are not secure and COLT does not accept responsibility for this message, its contents nor responsibility for any viruses. No contracts can be created or varied on behalf of COLT Telecommunications, its subsidiaries or affiliates ("COLT") and any other party by email Communications unless expressly agreed in writing with such other party. Please note that incoming emails will be automatically scanned to eliminate potential viruses and unsolicited promotional emails. For more information refer to www.colt.net or contact us on +44(0)20 7390 3900.

1 0

Hobbit script attributes
by Martin.Ward＠colt.net 20 Jun '08

20 Jun '08

All, I have been modifying an old script I found lying around (for Solaris RAIDs, but I'll get on to that in another email) and have found that I want to display which version of the script is running on which client, on the website. To this end I have started adding a variable "SCRIPT_VER" near the head of my client script, and adding some code to write it out to the bottom of the client output in a small table, which brings up the following questions: 1. Are there any standard attributes that should be set in a Hobbit script? TEST is a common one but is it required or not? Are there others? 2. Should there be a standard for displaying the script name and version in the output that is sent to the Hobbit server, to be displayed in the webpage? What do you think? |\/|artin -- Martin Ward Network Systems Operations Specialist DDI: +44 (0) 20 7863 5218 Fax: +44 (0) 20 7863 5610 Mob: +44 (0) 7971 97 77 21 www.colt.net Data | Voice | Managed Services Help reduce your carbon footprint | Think before you print COLT Telecommunications, Beaufort House, 15 St Botolph Street, London, EC3A 7QN UK Registered in England and Wales, registered number 02452736, VAT number GB 645 4205 50 ************************************************************************************* The message is intended for the named addressee only and may not be disclosed to or used by anyone else, nor may it be copied in any way. The contents of this message and its attachments are confidential and may also be subject to legal privilege. If you are not the named addressee and/or have received this message in error, please advise us by e-mailing security at colt.net and delete the message and any attachments without retaining any copies. Internet communications are not secure and COLT does not accept responsibility for this message, its contents nor responsibility for any viruses. No contracts can be created or varied on behalf of COLT Telecommunications, its subsidiaries or affiliates ("COLT") and any other party by email Communications unless expressly agreed in writing with such other party. Please note that incoming emails will be automatically scanned to eliminate potential viruses and unsolicited promotional emails. For more information refer to www.colt.net or contact us on +44(0)20 7390 3900.

1 0

Log File messages : Don't work
by mailinglist.benoit＠gmail.com 20 Jun '08

20 Jun '08

Hello guys I begin to be crazy to monitor log file on client ! *On server I have put in "client-local.cfg" that : * [server1] log:/var/log/messages:10240 *On client I have put in localclient.cfg that : * DEFAULT # Uptime mini UP 1h ----------------truncated---------------------------------- # LOG LOG %/var/log/messages %(I/O|read).error COLOR=red LOG /var/log/messages COLOR=red LOG /var/log/messages FAILBACK COLOR=yellow LOG /var/log/messages "VCS ERROR" COLOR=red # Ports PORT LOCAL=%(:8888|:8889) color="red" # Ports PORT LOCAL=%(:8888|:8889) color="red" The privilege work well for user hobbit : ll /var/log/messages -rw-r----- 1 root adm 210719 Jun 18 15:21 /var/log/messages # getent group adm adm:x:4:root,hobbit,adm,daemon I was try a lot of possibility on several host, and all my columns "msg" is always grey and says : -- System logs at Wed Jun 18 15:28:38 CEST 2008 : No log data available -- The client did not report any logfile data However my host "server1" generated very well new entrie in /var/log/messages I don't understand why the message don't work ! But when I check client log it write that : cat ../logs/hobbitclient.log 2008-06-18 15:02:30 Failed to get a message, terminating 2008-06-18 15:04:31 Failed to get a message, terminating 2008-06-18 15:06:32 Failed to get a message, terminating 2008-06-18 15:08:32 Failed to get a message, terminating 2008-06-18 15:10:33 Failed to get a message, terminating 2008-06-18 15:12:34 Failed to get a message, terminating 2008-06-18 15:14:34 Failed to get a message, terminating Where comes to this error ? Could you help me Thank you very much by advance Regards -- <mailinglist.benoit - at - gmail!com>

3 2

apache|apache1|apache2|apache3
by annaj＠hi.is 19 Jun '08

19 Jun '08

On monday I posted a message with a wrong link. Here I repost it with the correct link. : Can anybody tell me how to get all the apache graphs under the http test, not just the TRENDS. http://www.hswn.dk/hobbit/help/hobbit-tips.html#apachetest I need to know this because I am developing a flexlm module for hobbit that uses a similar technique. It shows up on the TRENDS column but not under my test. -- Kindest Regards, Anna Jonna Ármannsdóttir, %& A: Because people read from top to bottom. Unix System Aministration, Computing Services, %& Q: Why is top posting bad? University of Iceland.

3 6

Monitor IGNORE configs
by rpeters＠columbia.com 19 Jun '08

19 Jun '08

Is there a way to ignore a specific monitor (not the whole system) for a specific time? I know how to turn off warnings for the whole box but didn't see a way to limit a specific one.

3 3