Re: {bb} LDAP Monitoring Problem

[Eric Frisch <ericf@conetra.com>]

The script logic keys the test completely off of the "ldap" tag in
bb-hosts.  It just loops through those hosts pulling the tests from the
bb-ldap.cfg file.  If you are sure the tag is gone from bb-hosts and BB
has been restarted then it won't be running there.  I would personally
suspect that someone cloned a BB instance and that bb-ldap.sh is getting
launched on a client machine.  e.g. watch for liberal use of localhost
in the exttab file etc.  Hence the test may be running/failing regularly
there and is sending status to the display server regularly so the test
never goes purple.  bb-ldap will just as happily run on a client as it
will on the display server.

I am only subscribed to the digest so answers may come very slowly.  If
you get stuck, fire me a personal email, I have some experience with
this thing . . .

Eric



Subject: Re: {bb} LDAP Monitoring Problem
> 
> Ben
> 
> I still have this problem and have just come back to it today, I would appreciate
> if you can have a look at this one...
> 
> Problem is I want to STOP testing LDAP on a particular client.
> 
> The LDAP test is running the /ext script bb-ldap.sh from the BBMON server.
> The entry for the client on the servers bb-hosts no longer has the ldap flag
> included. The server has been restarted as has the client (several times!).
> I have completed a "bbrm <client hostname> ldap " and then restarted the server
> again.
> After a few minutes BB mails with a RED status for ldap on that client. Removing
> the logs, hist, and histlogs for that client.ldap does not stop the problem even if
> I do it manually.
> The status never goes PURPLE but remains on RED.
> 
> How do I get rid of this test for that particular client?
> 
> Many thanks for any help
> 
> Alex.
> 
> 

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.