Re: {bb} Nothing displayed for a client

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

On Wed, 2005-05-25 at 22:25, nickykav nickykav wrote:
> Hi Phillip,
>  
> Thankyou for your response, that was very informative. 
> below is the content of my bb-hosts file (it is the same on the server and
> all of the clients:

That's "a good thing <TM>". It makes things simpler if you keep them
synchronized.

> 12.40.98.2      support.xyz.com # BBPAGER BBNET BBDISPLAY ftp testip cpu disk procs http://www.xyz.com
> 169.143.196.44  devf50b # cpu disk procs testip
> 169.143.196.42  venus # cpu disk procs testip
> 12.20.194.5     devj30a # cpu disk procs testip
> 12.20.194.12    saturn # cpu disk procs testip

OK.

1. You can lose the directives for client tests. They're not doing
   anything and they are invalid.

2. You've got a fully qualified domain name (FQDN) for your server
   and short names for everything else. Don't do that, it'll only
   cause you grief. Unless you really, really have to, use FQDN
   for everything.

3. You've got "testip" directives there which modify the default
   behaviour (test by name) to perform network tests using the
   IP number instead. They are not doing anything for the clients
   (which don't have any network tests defined) and should be
   avoided for the server. If "support.xyz.com" does not resolve
   to your BB server, you would be much better off using a name
   that actually does resolve.

In summary, I think that your bb-hosts file should look more like:

 12.40.98.2      support.xyz.com # BBPAGER BBNET BBDISPLAY ftp 
http://www.xyz.com
 169.143.196.44  devf50b.xyz.com #
 169.143.196.42  venus.xyz.com #
 12.20.194.5     devj30a.xyz.com #
 12.20.194.12    saturn.xyz.com #

> the bbvar/logs do not show any files form an unknown source. i have
> confirmed that.

If you have files like "devj30a,xyz,com.cpu", then the client is
reporting with FQDN, but that will not match with the short name
that you were using in the bb-hosts file. If there are no files
starting with devj30a (other than "devj30a.conn") then the client
isn't getting it's report through.

> I do see some errors in the BBOUT of the client saturn (thats the client
> whos status i cant see)
> Wed May 25 14:22:40 2005 bb-local.sh Wed May 25 14:22:40 2005 bb CAN'T CONNECT TO bbd SERVER @ 12.40.98.2
> Wed May 25 14:22:40 2005 bb-local.sh Wed May 25 14:22:40 2005 bb Unknown host: support.xyz.com
> Wed May 25 14:22:46 2005 bb-local.sh Wed May 25 14:22:46 2005 bb CONNECTION TO 12.40.98.2 TIMED OUT...

An occasional failure might be OK but, if it's happening often the
status will end up going purple (stale). If possible, you should use
a name that resolves for your BB server (and avoid using "testip")

> But on the other hand, i checked the BBOUT of Venus (thats the client whos
> status i can see) i see simillar errors:
> ue May 24 14:36:18 2005 bb-local.sh Tue May 24 14:36:18 2005 bb CAN'T CONNECT TO bbd SERVER @ 12.40.98.2
> Tue May 24 14:36:18 2005 bb-local.sh Tue May 24 14:36:18 2005 bb Unknown host: support.xyz.com
> Tue May 24 14:36:19 2005 bb-local.sh Tue May 24 14:36:19 2005 bb CAN'T CONNECT TO bbd SERVER @ 12.40.98.2
>  
> Only difference in the 2 is that the connection is not timing out for venus.
> Can yout tell me what i can do now. to further investigate / solve this
> problem.

The best test for client connection problems is to see if you can
telnet to port 1984 on the server from the client. If not, you'll
need to try and figure out why. Common reasons are routing problems
or a firewall being configured by default on the server.

Since "saturn" on the 12 network is OK and "venus" on the 169.143
isn't, I'm guessing that "venus" doesn't have a valid route to the
12 network.

Cheers, Phil



-- 
Watson's Law: The reliability of machinery is inversely proportional to
the
number and significance of any persons watching it.

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