At the moment in our environment, we have enabled the trending report funcion for only the connectivity test for every machine , we are using the BBFE 4.3 and i noticed that in our CGI-BIN directory we have installed the scripts bb-amcharts.sh and bb-doamcharts.sh from Quest software . My problem is that i can't find any configuration file for this feature ,and trying to troubleshooting the BBserver Script i haven't found nothing related to this feature .
Someone can help me please ?
I hope to be quite clear .
Good Morning Community,
i have read the post from Paul O'Brien about enabling the performance's data trendig . At the moment the solution seems to work only on my RHEL hosts, but for all our Solaris hosts i can't see any performance data sent to my BBSERVER, expecially , the dir $BBVAR/perf/$HOSTNAME is empty, and in the log of our BBSERVER and BBclient i can't see any warning regarding this issue , here is a bbdef-client.sh that doesn't work, could someone help me troubleshooting this problem ?
P.S. the version of the client /server is the bb4.3 PE .
bash-3.00$ cat bbc4.30-bbpe/etc/bbdef-client.sh
# BIG BROTHER DEFINITIONS AREA
# (c) Copyright Quest Software, Inc. 1997-2009 - All Rights Reserved.
# LOCAL CLIENT MONITORING CONFIGURATION FOR bb-local.sh
# WARNING AND PANIC LEVELS FOR LOCAL SYSTEM INFOMRAION
# YOU CAN SET VALUES ON A SPECIFIC FILESYSTEM BY USING
# THE etc/bb-dftab FILE
DFWARN=90 # (YELLOW) DISK % TO WARN
DFPANIC=95 # (RED) DISK % TO PANIC
export DFWARN DFPANIC
# CPU LEVELS ARE THE 5 MINUTE LOAD AVERAGE x 100
CPUWARN=150 # (YELLOW) WARN AT LOAD AVG OF 1.5
CPUPANIC=300 # (RED) PANIC AT LOAD AVG OF 3
DISPREALLOADAVG="FALSE" # DISPLAY THE LOAD AVERAGE AS FOUND IN UPTIME
# BB REMOVES THE '.' BY DEFAULT
export CPUPANIC CPUWARN DISPREALLOADAVG
# PROCESS MONITORING
# THESE VALUES ARE OVERRIDDEN BY THE etc/bb-proctab FILE
PROCS="bbrun" # (YELLOW) WARN IF NOT RUNNING
PAGEPROC="cron" # (RED) PAGE IF NOT RUNNING
export PROCS PAGEPROC
# MESSAGE FILE MONITORING (/var/adm/messages or similar)
# SMM: NEW IN BB 1.4
# CHKMSGLEN IS SET TO TRUE BY DEFAULT. IT WILL SCREAM IF IT FINDS
# AN EMPTY MESSAGES FILE. BETTER SAFE THAN SORRY.
# NOTE: AS OF VERSION 1.8 YOU CAN USE etc/bb-msgstab TO
# CONFIGURE THE VALUES OF PAGEMSG, MSGS AND IGNMSGS
# NOTE THAT KEYWORDS ARE SPACE SEPERATED HERE AS OPPOSED
# TO ';' SEPERTATED IN etc/bb-msgstab
CHKMSGLEN="TRUE" # MAKE SURE MSG FILE IS NON-ZERO LEN
PAGEMSG="NOTICE" # (RED) PAGE IF WE SEE THIS MESSAGE
MSGS="$PAGEMSG WARNING" # (YELLOW) MESSAGES TO WATCH FOR
# NOTE: WORDS IN PAGEMSG *MUST ALSO*
# BE DEFINED IN MSGS
IGNMSGS="" # List of messages to ignore if string(s) matches line
# delimit each message with ;
MSGEXPIRE="30:60" # EXPIRE WARNINGS IN 30 MIN, PANICS IN 60
YELLOWMSGSLINES=10 # Return the XX most recent WARNING messages
REDMSGSLINES=20 # Return the XX most recent PANIC messages
OLDSTYLEBBMSGS="FALSE" # Don't expire messages found
# just like the old days (they must be cleared by hand)
export MSGS PAGEMSG IGNMSGS CHKMSGLEN MSGEXPIRE YELLOWMSGSLINES REDMSGSLINES OLDSTYLEBBMSGS
# Control the color of the cpu dot when a host reboots
# Note that the maximum of minutes definable is 60, anything over will be reset to 60
export WARNMINSONREBOOT WARNCOLORONREBOOT
# THIS SETS A VALUE FOR IF YOU THINK MACHINES SHOULD BE REBOOTED EVERY X DAYS
# configuration variables associated with the perfomance data
# set as below for cpu and disk
# BBPERFTESTS="cpu disk"
# Variables to determine if local test is to be run
# and if so, does it send a msg anyway
NOCPUCOLOR="clear" # Set to "" if you don't want a message sent
NOMSGSCOLOR="clear" # anything else will send a message to BBDISPLAY
export DOMSGS DOPROCS DODISK DOCPU
export NOCPUCOLOR NOMSGSCOLOR NODISKCOLOR NOPROCSCOLOR
thank you for your answers,
Any error messages in BBOUT file on the BB client server?
if no error messages are present, try the following:
on the BB client in bin/bblocal.sh
change the first line from
#!/bin/sh -x (<number sign><bang><slash>bin<slash>sh<space><minus>x)
make this last at least a cycle on the BB client (no stop/start should be required) and look for "loadavg" in the BBOUT to verify that the BB client is at least trying to write perf data to the status log.
also check on the BBDISPLAY server, in the BBOUT file, if there are any messages like
"message truncated" or somthing like that.
don't forget to undo your change when done.
Good Morning Robert-Andre,
first of all, thank you for your answer.
As i said in my previous post, i can't see any error / warning in the BBOUT file in both client and server .
I made the changes you suggest to me , and the only output in my BBOUT client's file regarding the load average is the following :
Fri May 27 09:36:06 2011 bb-local.sh + set 9:36am up 41 day(s), 1 user, load average: 0.12, 0.15, 0.14
Fri May 27 09:36:06 2011 bb-local.sh LINE=LOAD AVG on xxxxx is 15
Fri May 27 09:36:06 2011 bb-local.sh + echo LOAD AVG on xxxxx is 15
Fri May 27 09:36:06 2011 bb-local.sh + /export/spare/bb-mon/bbc4.30-bbpe/bin/bb-combo.sh add status xxxxx.cpu green Fri May 27 09:36:06 CEST 2011 up: 41 day(s), 1 users, 184 procs, load=15
Fri May 27 09:36:06 2011 bb-local.sh LOAD AVG on xxxxx is 15
Fri May 27 09:41:05 2011 bb-local.sh + set 9:41am up 41 day(s), 5 min(s), 1 user, load average: 0.08, 0.11, 0.12
Fri May 27 09:41:05 2011 bb-local.sh LINE=LOAD AVG on xxxxx is 11
Fri May 27 09:41:05 2011 bb-local.sh + echo LOAD AVG on xxxxx is 11
Fri May 27 09:41:06 2011 bb-local.sh + /export/spare/bb-mon/bbc4.30-bbpe/bin/bb-combo.sh add status xxxxx.cpu green Fri May 27 09:41:06 CEST 2011 up: 41 day(s), 1 users, 183 procs, load=11
Fri May 27 09:41:06 2011 bb-local.sh LOAD AVG on xxxxx is 11
I think there is noting useful, not ?
Only one question , i noticed an error in the path of my BBHOME ( see in the lines before , the correct path is /export/share/bb-mon not /export/spare/bb-mon ) .
What other test can we do ?
Thank you for everything .
sorry, my fault, the correct path is /export/spare
any matches for "loadavg" ?
if not, is there any lines like this:
... for perftest in ...
if so, what is exact line?
no, i'm sorry, nothing about it .
it's possible to send you the whole trace ?