[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Ghost report from 127.0.0.1



I had that exact problem way back when when I first started up devmon.


Paul Root
Lead Internet Systems Eng
Qwest Network Services




________________________________
From: Johan Sjöberg [mailto:johan.sjoberg (at) deltamanagement.se]
Sent: Friday, January 21, 2011 9:09 AM
To: xymon (at) xymon.com
Subject: [xymon] RE: Ghost report from 127.0.0.1

It was the devmon "dm" report. "hostname" on the new server just returned the short name, where it returned fqdn on the old one. This caused devmon to report with the wrong host name.

/Johan

From: Johan Sjöberg [mailto:johan.sjoberg (at) deltamanagement.se]
Sent: den 21 januari 2011 15:19
To: xymon (at) xymon.com
Subject: [xymon] RE: Ghost report from 127.0.0.1

Great idea, I'll try that.
Thanks.

/Johan

From: Root, Paul [mailto:Paul.Root (at) qwest.com]
Sent: den 21 januari 2011 13:20
To: 'xymon (at) xymon.com'
Subject: [xymon] RE: Ghost report from 127.0.0.1

Whenever I get something like this, I define this host in my bb-hosts file (hosts.cfg) and let it cycle. The test that is running it should show up, and that gives you the hint you need to find the offending script.


Paul Root
Lead Internet Systems Eng
Qwest Network Services


________________________________
From: Johan Sjöberg [mailto:johan.sjoberg (at) deltamanagement.se]
Sent: Friday, January 21, 2011 4:46 AM
To: xymon (at) xymon.com
Subject: [xymon] Ghost report from 127.0.0.1
Hi.

We have recently migrated to Xymon 4.3.0 beta3 from 4.2.3. I now see the Xymon server under "Ghost reports":

Ghost reports:
  127.0.0.1       reported host mon


I can't find what causes this. The status updates as it should for the Xymon server. We use fqdn in all config files and hosts.cfg, so it seems like this is somehow using the hostname in the OS (hostname should be "mon.domain.com", not "mon"). But I can't find any processes or similar that are related to this. I have not been able to find any scripts that are setup wrong either. Are ghost clients logged somewhere?
It is a source-install on Debian Lenny.

Does anyone know what might cause this? It's no major issue since all monitoring works correctly, but it's annoying to have it there.

/Johan

________________________________
This communication is the property of Qwest and may contain confidential or
privileged information. Unauthorized use of this communication is strictly
prohibited and may be unlawful. If you have received this communication
in error, please immediately notify the sender by reply e-mail and destroy
all copies of the communication and any attachments.

________________________________
This communication is the property of Qwest and may contain confidential or
privileged information. Unauthorized use of this communication is strictly
prohibited and may be unlawful. If you have received this communication
in error, please immediately notify the sender by reply e-mail and destroy
all copies of the communication and any attachments.