BB Unix Network Monitor - Message

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: {bb} dig on clients?



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?

IdeaS?




-----Original Message-----
From: owner-bb@bb4.com [mailto:owner-bb@bb4.com] On Behalf Of Cristian
Danci
Sent: Tuesday, May 23, 2006 2:29 PM
To: bb@bb4.com
Subject: RE: {bb} dig on clients?

Thanks Phil,

This email in particular is for 5.1

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.

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?

Also I can't find "set -x":

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


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.

-----Original Message-----
From: owner-bb@bb4.com [mailto:owner-bb@bb4.com] On Behalf Of Philip
Clark
Sent: Tuesday, May 23, 2006 12:25 PM
To: bb@bb4.com
Subject: RE: {bb} dig on clients?

On Tue, 2006-05-23 at 01:24, Cristian Danci wrote:
> Its returns 19

That looks OK.

> Background
> 
> Several AIX boxes
> 
> Versions 5.1, 5.2 and 5.3
> 
> Version 5.1 = runbb.sh doesn't run out of the box and needed syntax
> changes
> Version 5.2 = Worked fine :)
> Version 5.3 = runbb.sh starts but nothing happens BBOUT file is empty
> (aside from starting BB entry)

So the one that we are concerned with here is 5.3

It would appear, from the previous output in BBOUT, that bb-combo.sh
may be the cause of part of the problem. If you remove the "set -x"
from bb-local.sh and add it to bb-combo.sh instead, you should get
a different trace output in BBOUT. Hopefully, that will provide
some more clues.

Also, with reference to your earlier post, if this machine has not
been configured with a hostname, you will have to provide a match
for the name used in the bb-hosts file in $BBHOME/etc/bbaliasname.
Otherwise, BB will not be able to determine how to correctly form
the messages it is trying to send.

Note that the "uname -n" command is not (directly) related to the
"named" daemon. I don't remember exactly how AIX used to do this
(and I don't think that I've ever seen 5.3), but "uname" is normally
just an interface to various local information. The "uname -n" often
uses a file, such as /etc/hostname, as a source. The DNS name (as
reported by "named" or another BIND) can be something else entirely.

Cheers, Phil.



-- 
By the time they had diminished from 50 to 8, the other dwarves
began to suspect 'Hungry.' (Gary Larson, "The Far Side")

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

According to our recent survey, more than half of Australian women (56%)
think they're better off financially if they are not married


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

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


Home | Main Index | Thread Index