RE: {bb} dig on clients?

[Philip Clark <bblist@cannae.uklinux.net>]

On Tue, 2006-05-23 at 05:28, Cristian Danci wrote:
> Thanks Phil,
> 
> This email in particular is for 5.1

OK

> However after doing a clean install on 5.3 (and coping the bbdef.sh
> from the 5.1 box) I'm starting to believe it is a name issue.

That should not be necessary. The contents of bbdef.sh should be set
by the configuration process. I don't expect it will do any harm, but
it's probably a bad habit to form.
 
> On the 5.1 and 5.3 box; uname returns the name of the box which is
> directly resolvable. 
> 
> $ uname -n
> heat
> $ ping heat
> PING heat: (10.0.0.6): 56 data bytes
> 64 bytes from 10.0.0.6: icmp_seq=0 ttl=255 time=0 ms
> 64 bytes from 10.0.0.6: icmp_seq=1 ttl=255 time=0 ms
> ^C
> 
> However the bb server is sitting on fedora box (it has the host names
> as heat.domain.com.au)
> 
> Does the server and the client need to have the same DNS entries?

The only requirement is that the BB view is consistent between client
and server. If you put "heat.domain.com.au" into $BBHOME/etc/bbaliasname
that should be sufficient.

> Also I can't find "set -x":
> 
> # find . -exec grep "set -x" '{}' \; -print
> # pwd
> /home/crisd/bbnew/bbc1.9i-btf
> #

The "set" command is normally a "built in" of the shell rather than
a separate binary. If you consult the "man" page for the shell and/or
play with it, you should get the hang of it. E.g.:

  dixon:/ # FOO="bar"
  dixon:/ # echo $FOO
  bar
  dixon:/ # set -x
  dixon:/ # echo $FOO
  + echo bar
  bar
  dixon:/ # set +x
  + set +x
  dixon:/ # echo $FOO
  bar
  dixon:/ #

> BBOUT on 5.3:
> Tue May 23 14:13:49 2006 bb-local.sh
> /home/crisd/bbnew/bbc1.9i-btf/bin/bb-combo.
> sh[67]: status .disk red Tue May 23 14:13:49 EET 2006 - Disk on  at
> PANIC level^
> J&red /pro (100%) has reached the defined disk space PANIC level
> (95%)^J&red /te
> stdata (97%) has reached the defined disk space PANIC level
> (95%)^J^J/dev/hd3
>         786432     56068    730364    8% /tmp^J/dev/hd4          
589824
> 804
> 60    509364   14% /^J/dev/hd1            65536     11320     54216
> 18% /home^
> J/dev/lv02          196608     63432    133176   33% /pc^J/dev/hd9var
> 524
> 288    221280    303008   43% /var^J/dev/hd2          2097152  
1183316
> 91383
> 6   57% /usr^J/dev/hd10opt        65536     51720     13816   79%
> /opt^J/dev/lv0
> 1        49610752  39753476   9857276   81% /data^J/dev/fslv00
> 27066368  26
> 058608   1007760   97% /testdata^J/dev/lv00         3604480   3588508
> 15972
>  100% /pro:  not found.
> Tue May 23 14:13:50 2006 bb-local.sh
> /home/crisd/bbnew/bbc1.9i-btf/bin/bb-combo.
> sh[59]: combo^Jstatus .cpu green Tue May 23 14:13:49 EET 2006 up: 130
> days, 2 us
> ers, 79 procs, load=18^J^J^JLOAD AVG on is 18:  not found.
> Tue May 23 14:13:50 2006 bb-local.sh
> /home/crisd/bbnew/bbc1.9i-btf/bin/bb-combo.
> sh[67]: status .msgs red Tue May 23 14:13:49 EET 2006 Urgent message
> file proble
> ms reported^J^J^J&red /var/adm/syslog/syslog.log has vanished^J:  not
> found.
> Tue May 23 14:13:50 2006 bb-local.sh
> /home/crisd/bbnew/bbc1.9i-btf/bin/bb-combo.
> sh[153]: combo^Jstatus .procs green Tue May 23 14:13:50 EET 2006 All
> processes a
> re OK^J^J&green cron >=1 - 1 instance running ^J&green bbrun >=1 - 1
> instance ru
> nning :  not found.

OK. That's on 5.3, but on 5.1 there is nothing unusual appearing in
BBOUT. Is that correct? You start the client and it gives you something
like:

  Mon May 22 20:24:43 BST 2006: Starting Big Brother...
          Starting Local tests (bb-local)...
  Big Brother 1.9i started

and the client appears to be running, but no status appears on the
server. If that is the case, this could simply be the name issue.
You might actually have log files like "heat.cpu" in $BBVAR/logs
on the server, rather than "heat,domain,com,au.cpu" which is
what it is expecting.

> Ok after looking at more code I think the problem is the variable
> $MACHINE is empty?

It looks that way on the 5.3 output. Is do you have similar results on
the 5.1 machine? If not, it's probably better to ignore 5.3 and get
5.1 working first. The two problems may be completely unrelated.

> Would this cause the problem and also where is the variable created
> or found?

I think that etc/bbinc.sh does most of the work.

> OK I played around with this a bit more and I found that bbinc.sh is
> not being included when called by bbdef.sh (don't know why)?
> 
> Therefore the BBDISPLAY, MACHINE and other important things aren't
> coming through?

> Ok I was wrong, open to ideas :)

So, you now believe that bbinc.sh is being sourced OK. If so, I'd
recommend the following on the 5.1 machine:

  1. Create the "bbaliasname" on the client containing the Fully
     Qualified Domain Name.

  2. Run (or attempt to run) the client and leave it for five
     minutes. While you are waiting, you can take a look at the
     logs directory on the server to see if there are files which
     correspond to the unqualified name of the client.

  3. If the client bails out, or the status fails to appear on the
     server. Try adding the "set -x" command near the top of
     "bb-local.sh", restart the client and run it for one cycle
     before stopping (if required).

You can send me the contents of BBOUT directly, rather than to the list,
if you want me to take a look at it.

Cheers, Phil.



-- 
This Klein bottle for rent -- enquire within.

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