I don't use "localhost" in any host or service configs. There is no use
for "localhost", since it is such an ambiguous hostname. In a
distributed setup where there are multiple sources feeding data into a
single server, *every* host name must be unique, otherwise they clobber
each other's data (as you have noticed). I use the actual FQDN hostnames
of the collectors (even the central one) in the configs. When there is
an issue with a service on one of the collectors, it shows up in the
interface under that particular collector's hostname, so I know exactly
which one is broken.
On 08/09/2010 03:23 PM, steve f wrote:
I finally got a distributed server up & running in Core 3.x and have a
stupid question on monitoring the dist server. I have the central
server currently configured to not do active checks. On the
distributed server, I had all of the localhost.cfg checks running and
in the nagios.log on the central server, I see the following :
EXTERNAL COMMAND: PROCESS_SERVICE_CHECK_RESULT;localhost;Root
Partition;0;DISK OK - free space: / 827 MB (86% inode=88%):
[1281213501] PASSIVE SERVICE CHECK: localhost;Root Partition;0;DISK OK
- free space: / 827 MB (86% inode=88%):
This is coming as a passive check from the distributed server with the
hostname of localhost and as such, it appears that on the central
server its using this check result & populating the checks for the
central server.
if I wanted to monitor the distributed server, would I not use the
localhost.cfg on the distributed server? SHould I rename everything
localhost in localhost.cfg to the name of the distributed server?
Whats the most rational way to monitor the distributed server ?
Thanks,
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Nagios-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Nagios-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
