On Thu, Sep 14, 2006 at 01:04:15AM +0530, Unni, Krishnan (GE Indust, Plastics, consultant) wrote:

I would like to know if there is an option or facility to install BB Client on multiple servers at once remotely. I have to install BB Client in about 400 Servers and doing them one by one will consume lot of time to complete. Also if client configuration can be deployed the same way.

Not really Hobbit specific, but ok ...

The BBNT client has an option to perform a "silent install". It's a long time since I worked with it, but I think it is described in either the README or you can find it described on the BBNT mailing list archive.

As for the configuration, this is stored inside a subtree in the registry. So you can export this tree to a .reg file, and then just import this into each systems registry DB.

Regards, Henrik

-----Original Message----- From: hobbit-return-9498-david=stenhouseconsulting.com at hswn.dk [mailto:hobbit-return-9498-david=stenhouseconsulting.com at hswn. dk] On Behalf Of Henrik Stoerner Sent: Wednesday, September 13, 2006 4:01 PM To: hobbit at hswn.dk Subject: Re: [hobbit] Hobbit server resolving client name in correctly

On Wed, Sep 13, 2006 at 02:32:30PM -0400, David Gilmore wrote:

...

I have a new installation of Hobbit 4.2.0 monitoring a private network (192.158.151.0/24) It is currently monitoring a number of Windows servers with BB clients reporting data to hobbit. The Hobbit system is configured to use two Windows DC's for DNS resolution. Hobbit however is reporting in the CONN column that one of the DC's has a public IP address on the 64.20.33.0/29 network. How is this happening? The BBHOST file has the correct local IP address and FQDN host name.

Hobbit will always perform a DNS lookup to determine the IP-address. The IP you put into the bb-hosts file is only used if the host also has a "testip" tag.

So you should look at the resolver settings for your Hobbit server. What kind of system are you running Hobbit on ?

Running Hobbit on FC5, installed Hobbit from the RPM packages on SourceForge, which is a first as I typically have installed "manually".

Hobbit uses the ARES library for DNS lookups, and this does adhere to some settings controlling what the priority is between any /etc/hosts file and DNS. Is this host perhaps listed in /etc/hosts ?

It was not specifically added to /etc/hosts

You can also try this: Login as the Hobbit user, then run "bbcmd bbtest-net --debug MY.HOST.NAME" where MY.HOST.NAME is the hostname from the bb-hosts file. You should see something like this somewhere into the debug output:

2006-09-13 21:59:22 Opening file /usr/lib/hobbit/server/etc/bb-hosts 2006-09-13 21:59:22 Adding hostname 'client3.hswn.dk' to resolver queue 2006-09-13 21:59:22 Got DNS result for host client3.hswn.dk : 127.0.0.1 2006-09-13 21:59:22 Processing 1 DNS lookups with ARES

What does your output say?

I'll give this a shot and get back to you.

...

None of the client specific data is registering with Hobbit either.

Probably a different problem. Check if the host appears in the "Ghost clients" report on the Hobbit server; if it does, then the hostname reported by the client and the hostname you have in the bb-hosts file don't match (most often, one uses the fully-qualified hostname, and the other uses the plain hostname with no domain).

I also noticed some other odd behavior on this box after sending this message. The hobbit server itself was only reporting status on CONN BBD INFO and TRENDS. I made some modifications to the BBHOSTS file in preperation of adding in other systems (created four PAGE groups in BBHOSTS), but the changes never appeared. I attempted to restarting Hobbit from the script, but still no changes to main display, then restarted the Hobbit Service that was listed in the Services applet. Pages still did not display, but the remaining info for the HOBBIT server (CPU, DISK, MEMORT, etc) suddenly appeared.

Regards, Henrik

As always, thank you for your help, and for providing us with this great tool.

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk