RE: {bb} big brother monitoring a df that it shouldn't be

It's been a year or more since I worked with Big Brother but I remember
getting this type of error on HPUX servers I was supporting.  The error
was basically meaningless since there was no file system filling up or
one that matched the name in the error ("/opt/bb/tmp" I think).  I
eventually modified one of the scripts.  I just did a search of the text
files in the bin directory for the tmp message.  I don't recall exactly
what I did to the script.  I either changed the event from a panic (red)
to a warn (yellow) level message or changed another setting(s) to get
Big Bro to ignore the event when it came up.

Sorry I can't be of more help.  Too much rust on the brain.

Mike J.

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Philip
Clark
Sent: Monday, March 10, 2008 6:49 PM
To: [email protected]
Subject: Re: {bb} big brother monitoring a df that it shouldn't be


On Mon, 2008-03-10 at 13:27 -0400, Scott Mohnkern wrote:
> I'm having a problem with bb a 1.6e1 client reporting on a partition 
> that it shouldn't be.
> 
> It's acting like the tmp directory for the client (in this case 
> /usr/local/bb16e1/tmp) is a partition, and reporting it full (and its 
> not a partition at all, just a directory).
> 
> adding the following to bb-dftab doesn't seem to help:
> 
> localhost:/usr/local/bb16e1/tmp:101:101
> 
> For the life of me, I can't figure out where it's deciding that 
> /usr/local/bb16e1/tmp is a partition, and that it needs to be
monitored.
> 
> Any suggestions?

Erm, 1.6e1? This would be archaeology then. I'll just fetch my trowel :)

These "tmp filesystem full" messages are not generally the result of
examining the disks. A more complete translation would be, "I tried to
save some data to my tmp directory and all I got was an empty file."

Two well know candidates are the Solaris "tail" bug and the altered
"sort" options:

  http://support.bb4.com/archive/200405/msg00222.html

  http://support.bb4.com/archive/200603/msg00170.html

If neither of those looks likely, check through the client scripts
until you find the part that is generating the error message. If it
appears more than once, append an identifier to the message to isolate
it. Then you can try running the commands that precede it manually
to get a better idea of why they are failing.

If you still can't locate the problem, let the list know. Unfortunately,
you would need to actually send me the client tarball (off list) as I
don't have anything nearly as old as that.

Cheers, Phil.



--
Real Programmers don't play tennis, or any other sport that
requires you to change clothes. Mountain climbing is OK, and real
programmers wear their climbing boots to work in case a mountain
should suddenly spring up in the middle of the machine room.


--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:[email protected] with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:[email protected] with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.