4.1.1 client hostname
list Dirk Kastens
Hi, I just installed the new hobbit client on one of our linux machines. It didn't send data to the hobbit server until I changed its hostname to a fully qualified name. The bb client has the option FQDN that must be set to "true" if the server needs a fully qualified name. What about the hobbit client? The bb client also supports a file named bbaliasname where you can define an alias for the client hostname. Do I now have to edit the runbbclient.sh file directly and change the MACHINEDOTS variable if I want to change the hostname? Dirk
list Henrik Størner
▸
On Tue, Jul 26, 2005 at 12:40:26PM +0200, Dirk Kastens wrote:
I just installed the new hobbit client on one of our linux machines. It didn't send data to the hobbit server until I changed its hostname to a fully qualified name. The bb client has the option FQDN that must be set to "true" if the server needs a fully qualified name. What about the hobbit client?
By default, the Hobbit client sends in reports using
the name provided by "uname -n". If this is not the
name that is used in the Hobbit servers' bb-hosts file,
then the Hobbit server will silently discard these data
as being from an "unknown" host.
So you have three possibilities:
1) Make the client report their status with the same
hostname that you use in the Hobbit servers' bb-hosts
file. Do this by adding a
MACHINEDOTS="my.host.name"
entry in the clients' client/etc/hobbitclient.cfg file.
2) Same as 1), but done on the server side by modifying
the servers' bb-hosts file
3) Tell the server about the other hostname used by the
client, by adding a "CLIENT:clienthostname" tag to the
the hosts' entry in the servers' bb-hosts file.
I recommend 1) since that is the cleanest way of doing it.
Regards,
Henrik
list Brian Lynch
I experienced the same problem on my network and added the following lines to the hobbitclient.cfg. This change can be propogated to all servers without customizing the config file. MACHINE="$MACHINE.domain.com" MACHINEDOTS="$MACHINE"
▸
On 7/31/05, Henrik Stoerner <user-ce4a2c883f75@xymon.invalid> wrote:On Tue, Jul 26, 2005 at 12:40:26PM +0200, Dirk Kastens wrote:I just installed the new hobbit client on one of our linux machines. It didn't send data to the hobbit server until I changed its hostname to a fully qualified name. The bb client has the option FQDN that must be set to "true" if the server needs a fully qualified name. What about the hobbit client?By default, the Hobbit client sends in reports using the name provided by "uname -n". If this is not the name that is used in the Hobbit servers' bb-hosts file, then the Hobbit server will silently discard these data as being from an "unknown" host. So you have three possibilities: 1) Make the client report their status with the same hostname that you use in the Hobbit servers' bb-hosts file. Do this by adding a
MACHINEDOTS="my.host.name <http://my.host.name>";
▸
entry in the clients' client/etc/hobbitclient.cfg file.
2) Same as 1), but done on the server side by modifying
the servers' bb-hosts file
3) Tell the server about the other hostname used by the
client, by adding a "CLIENT:clienthostname" tag to the
the hosts' entry in the servers' bb-hosts file.
I recommend 1) since that is the cleanest way of doing it.
Regards,
Henrik
list Rolf Schrittenlocher
Hi,
▸
3) Tell the server about the other hostname used by the client, by adding a "CLIENT:clienthostname" tag to the the hosts' entry in the servers' bb-hosts file.
it seems like that could be a solution for our problem with aliasnames (as far as multiple entries like this are allowed). We'd only have to change the servers' bb-hosts file each time an alias is moving to another machine. kind regards Rolf Mit freundlichen Gruessen Rolf Schrittenlocher HRZ/BDV, Senckenberganlage 31, 60054 Frankfurt Tel. Sammelnr. LBS: (49) 69 - 798 28830 Fax: (XX) XX XXX XXXXX LBS: user-1e39a1813094@xymon.invalid Persoenlich: user-6ea8e907e200@xymon.invalid Tel: (XX) XX - XXX XXXXX