Jeremy,
Yes, all files in the tmp directory match the hostname of the machine. It
seems as the mismatch is coming from the hobbitd on the server.
The false alarm is coming up just one time then wanishes.
Cordialement, Regards,Mit freundlichen Grüßen,
Gautier BEGIN
Admin and Tools Team
CSC Computer Sciences Luxembourg S.A.
12D Impasse Drosbach
L-1882 Luxembourg
Global Outsourcing Service | p:+352 24 834 276 | m:+352 621 229 172 |
user-083785ae1711@xymon.invalid | www.csc.com
CSC • This is a PRIVATE message. If you are not the intended recipient,
please delete without copying and kindly advise us by e-mail of the mistake
in delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail
for such purpose
• CSC Computer Sciences SAS • Registered Office: Immeuble Le Balzac, 10
Place des Vosges, 92072 Paris La Défense Cedex, France • Registered in
France: RCS Nanterre B 315 268 664
From: Jeremy Laidman <user-71895fb2e44c@xymon.invalid>
To: Gautier Begin/LUX/CSC at CSC
Cc: xymon at xymon.com
Date: 03/28/2012 04:49 AM
Subject: Re: [Xymon] False Alarm
On Wed, Mar 28, 2012 at 12:25 AM, Gautier Begin <user-083785ae1711@xymon.invalid> wrote:
Since last Thuesday, we encourter false alarms on procs and disk tests.
It
seems as real alarms are attributed to a wrong hostname because in the
attached data, we see that the xymon agent process is configured for an
other hostname.
On the client, do you have a file in /tmp (or $XYMONTMP) called
"msg.<name-of-host>.txt"? Does the filename match the hostname? Does
the contents show the correct hostname?