Xymon Mailing List Archive search

Solaris 10 client not sending msg

2 messages in this thread

list Eric Poinsignon · Tue, 27 Feb 2007 08:44:32 +0100 ·
Hello,

I didn't find a solution in the known issues nor archives, that's why I
pollute this list.

 
I installed Hobbit 420 on my network with many unix flavours and
windows, all of the clients work fine 

except those running Solaris 10. The <hobbitdir>/tmp/msg.mymachine.txt
file is correctly created 

on the client side, but no information (except conn, info, ntp and
trends) appears on the server side.

The Hobbit server is running RedHat.

 
Is there a trick about this particular Solaris10 platform ?

 
Best regards.

Eric Poinsignon
Unix system engineer
Odyssey Financial Technologies
Chemin du Viaduc 1
CH-1008 Prilly
Switzerland

T. +41 (0) 21 310 09 25
F. +41 (0) 21 310 00 99
www.odyssey-group.com

 
� This email and any files transmitted with it are CONFIDENTIAL and intended
  solely for the use of the individual or entity to which they are addressed.
� Any unauthorized copying, disclosure, or distribution of the material within
  this email is strictly forbidden.
� Any views or opinions presented within this e-mail are solely those of the
  author and do not necessarily represent those of Odyssey Financial
Technologies SA unless otherwise specifically stated.
� An electronic message is not binding on its sender. Any message referring to
  a binding engagement must be confirmed in writing and duly signed.
� If you have received this email in error, please notify the sender immediately
  and delete the original.
list Henrik Størner · Tue, 27 Feb 2007 13:13:08 +0100 ·
quoted from Eric Poinsignon
On Tue, Feb 27, 2007 at 08:44:32AM +0100, Eric Poinsignon wrote:
except those running Solaris 10. The <hobbitdir>/tmp/msg.mymachine.txt
file is correctly created 
on the client side, but no information (except conn, info, ntp and
trends) appears on the server side.
Could you check if the host is listed in the "Ghost clients" report on
the Hobbit server ? This is often caused by the host having one name 
in the bb-hosts file, and the client reporting with a different name
(e.g. one with the fully-qualified domain name, the other without).

If that is the cause, then adding a "CLIENT:client.host.name" to the
host entry in bb-hosts will take care of it.


Regards,
Henrik