{bb} Custom Extensions

["Collins, Kevin" <kCollins@nesbittengineering.com>]

I've installed BB on a machine in my network and it's providing the basic "Yeah the machine is alive" kind of information.  In addition I have gotten paging and e-mail notifications working as I want them.  So the server is working just fine.

Now, I want to add RAID monitoring on several of my Dell servers.  So I went off to http://www.deadcat.net to find a script.  I did - bb-afaraid2.sh.  I followed what I thought was the proper method for setting up the client on a lab machine and waited for the "Afaraid" column to show up on the BB Server.  That was yesterday around 2:00 pm.  Nothing has shown up yet.

So obviously I've done something wrong.  Below is the step-by-step process that I used to install the client and the bb-afaraid2.sh extension.  Can somebody please tell me what I did wrong?

1). Created a BB user "bbuser" with a home directory of "/home/bbuser".  
2). Copied over the client tarball, BBCLT-bbc1.9h-btf.rar, to bbuser's home directory.
3). As "bbuser", I untarred the tarball with "tar zvf BBCLT-bbc1.9h-btf.rar", this created a bbc1.9h-btf sub-directory.
4). Moved into that new subdirectory with "cd bbc1.9h-btf".
5). Switched into the ./install directory "cd install".
6). Typed "./bbconfig redhatES", which failed.  Fell back to "./bbconfig".  This detected that I was running redhatES anyway, so all's good.  I'm running RedHat ES 3 Update 5, BTW.
7). Answered all the questions as needed.
8). Built the client.  "cd ../src; make; make install" - I did that as three separate commands.
9). On the Server, I added the client to the $BBHOME/etc/bb-hosts file and copied to the client's $BBHOME/etc directory.
10). Edited the "bbdef.sh" and "bbdef-client.sh" files in $BBHOME/etc on the client as needed.
11). Ran "bbchkcfg.sh" and "bbchkhosts.sh" - everything was fine.
12). Created a link for ease of use: "ln -s bbc1.9h-btf bb"
13). Set the proper permissions: "chown -R bbuser:bbuser ."  <-- This I did as root
13). Started BB "/home/bbuser/bb/runbb.sh start"

To this point, everything appeared fine, The only thing I asked the server to monitor was connectivity and that was working.  So I then proceeded to install the extension.

1). Downloaded and moved the "bb-afaraid2.sh" file into $BBHOME/ext.
2). Followed the directions inside the script to create the "seed" configuration, added "bbuser" to the sudoers file so the script could actually work.
3). Edited the $BBHOME/etc/bb-bbexttab.DIST file, make the following changes and saving as $BBHOME/etc/bb-bbexttab.
=============================================================
     Contents of bb-bbexttab:
     romulas.nesbitt.local : : bb-afaraid2.sh
=============================================================
4). Restarted the client.  Go the following message:
=============================================================
    Starting Big Brother
             Starting external scripts
                     Starting external script bb-afaraid2.sh
             Starting Local tests (bb-local)...
     Big Brother 1.9h started     
=============================================================
5). Waited for the afaraid column to appear in on the server.

I'm still waiting.

Now, I am getting this in $BBHOME/BBOUT:

=============================================================
Thu Sep 15 16:22:47 2005 bb-afaraid2.sh Thu Sep 15 16:22:47 2005 bb CAN'T CONNECT TO bbd SERVER @ 127.0.0.1
Thu Sep 15 16:22:47 2005 bb-local.sh Thu Sep 15 16:22:47 2005 bb CAN'T CONNECT TO bbd SERVER @ 127.0.0.1
=============================================================

Does this mean I have to install the server on the client machine as well???  The way I read the README.INSTALL, I wasn't lead to believe so.


Any guidance would be great.
--
Kevin L. Collins, MCSE
Systems Manager
Nesbitt Engineering, Inc.


--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
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.