Very well put :) I think the concept of running the BB
server and a client on the same machine confuses some people.
OK, here
goes. I'm going to try to over-explain this in hopes of answering
your question somewhere in here. :-) Somebody else feel free to chime in
here if something is confusing/misleading:
The BB
server should only run on one machine. (Technically, you can break out
the BBDISPLAY, BBNET, and BBPAGER, but I find it more convenient to run it all
on the same box.) This is the machine which will answer to the BB URL
(http://myhost/bb, or whatever.) It also
runs all of the tests which can be run without an account on the client machine(s). [Those are the BBNET tests. (Is it ping-able? Is
mail running? etc.)]
Every
machine that you want "local" information for needs to run the BB
client. This collects information which can only be determined by
running a command on the client. (How much disk space is used? How
much processor is used? etc.)
So to
extend your example a little, let's say that server1 runs - or can run - a Web
server, in addition to its other server duties. That would make it an
ideal machine to be the BB server. Install the BB server on it.
Because you also want to track load average, disk utilization, etc., install
the BB client as well, but in a different directory. (For instance, ${BBSERVER}="/usr/local/bbserver" and
${BBCLIENT}="/usr/local/bbclient".)
server2
may or may not run a Web server as well - it doesn't matter, because you don't
need another BB server; server1 is doing that. Just install the BB client on server2, and add it into server1's ${BBSERVER}/etc/bb-hosts
file. Repeat for all other machines you want to the "local" tests to be
run on.
Finally,
let's say that you have a machine, router1, that you don't care about the
"local" tests on; you just want to make sure that it can be pinged. Just
create an appropriate entry in server1's ${BBSERVER}/etc/bb-hosts file; there
is no need to install anything on router1 since the ping test is run by
the server.
Fire
everything up (BB server on server1, BB client on server1 and server2)
and wait 5 or 10 minutes. Look at the BB Web page, and you should
be all set. (If not, look at BBOUT in all ${BBSERVER} and ${BBCLIENT}
directories.)
The ext
directory on the BB server *is* used, but for different things than the client. Take LARRD for instance (since I was just thinking about it for
a different question.) To generate the graphs, there are two functions
that have to happen: grabbing the data (which is done by a script in the ${BBCLIENT}/ext directory structure, run on each client) and stuffing the data
into RRD log files on the server (which is done by a script in the
${BBSERVER}/ext directory structure, run on the server only.) It won't
work without both pieces doing their part.
Regards,
Charles
The idea was to keep only one copy of the config
files to be honest. The only directories that are together are the etc and
ext directories. Everything else is separate.
I think my question was more about the behaviour of
the server processes an if they run any of the local stuff themselves.
I have been looking at the structure a bit more closely this morning and I
think I have a better idea of what is going on. But one other
question.
Say you have server1 and server2. Server1 is your
server and Server2 is your client. You obviously want to monitor the server
as well as the client so do you specifically start both server and client
code or should the server also kick off the bblocal stuff. (I know that this
doesn't happen as the bblocal stuff is only in the client dist. So I guess
you kick off both server and client code on a server ? Does that mean
that you do not use the ext directory that is part of the server dist then
?
Cheers
Dave
I'm as
confused as Kimberly. Big Brother is divided into two separate pieces: the client and the server. Install them both (say in usr/local/bbserver and /usr/local/bbclient) and run them separately.
By attempting to combine them you are going to cause yourself problems,
and make your configuration unique such that others (us, for
example ;-) won't be much help.
If I
might ask, why would you want a distribution area for the server,
anyway? It's designed so you only have to distribute the
client.
Regards,
Charles
Also, I have just checked, all of the files in
the server distribution from the etc directory that are not specific to
the server (bbdef-server.sh for example) are identical to the client
versions. I was pretty sure that was the case as that was one of the
reasons why I did this in the first place.
When you run the server code on a box, what is
responsible for kicking off the local tests ? If I can find that out
then I will have something to go on. As I said there is a variable that
is set in the bbrun.sh script but that seems to start them up according
to the output but I can't find the bb-local.sh script running.
Cheers
Dave
I'm not entirely sure I followed that. You
combined the etc folders for your server and client? Because that would most definitely screw it up... the server and the client need to
be in separate directories and started out of those separate
directories. Please correct me if I interpreted that wrong.
Guys,
I
have an issue with the server component of big brother. All of the
local tests show up purple. Even if I set the bblocal to TRUE in the
runbb.sh script so that the local stuff runs explicitely it still doesn't work and the bblocal dies with no errors reported into BBOUT.
I am
worried that I have inadvertantly screwed with the config because I
have combined the etc directories from the client and the server into
one area so that I can have the same distribution area for both server
and client.
Anyone got any ideas ?
Cheers
|
Dave
Murphy
Unix Systems
Administrator
TSG Unix
Team |
'
È |
02075 428627 |
| |
| 07710
400301 |
-----------------------------------------------------------------
Visit
our Internet site at http://www.reuters.com
To find out more
about Reuters Products and Services visit
http://www.reuters.com/productinfo
Any views expressed in this
message are those of the individual
sender, except where the sender
specifically states them to be
the views of Reuters
Ltd.
-----------------------------------------------------------------
Visit
our Internet site at http://www.reuters.com
To find out more about Reuters Products and Services visit
http://www.reuters.com/productinfo
Any views expressed in this
message are those of the individual
sender, except where the sender
specifically states them to be
the views of Reuters
Ltd.
-----------------------------------------------------------------
Visit
our Internet site at http://www.reuters.com
To find out more about
Reuters Products and Services visit http://www.reuters.com/productinfo
Any views expressed in this message are those of the
individual
sender, except where the sender specifically states them to
be
the views of Reuters
Ltd.