check_proc services - why attached to windows group?
Posted: Wed May 18, 2016 1:44 pm
Hello:
We've grouped our servers into various hostgroups and have started attaching relevant services to each.
For example, to our 'windows_baseline' hostgroup, we've attached several custom services:
WINDOWS-LOGON-ERRORS.cfg
WINDOWS-PAGE-FILE-SERVICE.cfg
WINDOWS-SERVER-WORK-QUEUES.cfg
WINDOWS-STANDARD-C-DRIVE.cfg
WINDOWS-STANDARD-CPU-SERVICE.cfg
WINDOWS-STANDARD-MEMORY-SERVICE.cfg
WINDOWS-UPTIME.cfg
Each of these services is based on a pre-defined setting. Well and good.
What's not good is that Nagios XI shows that each host in this windows-baseline has a phantom service which is checking unsuccessfuly, namely, a Linux service, "check_proc".
I've examined all the cfg files under /usr/local/nagios/etc and 'check_proc' appears as it should, in:
commands.cfg
nrpe.cfg
services/REDHAT-STANDARD-PROCESSES.cfg
services/UBUNTU-PROCESS-CHECK.cfg
I don't understand why Nagios is trying to apply check_proc to our Windows servers.
Attached is a system profile for examination.
One note: Every 5 minutes a cronjob runs and produces the same email message to root. Example:
To: [email protected]
Subject: Cron <root@nagios03> LANG=C LC_ALL=C /usr/bin/mrtg /etc/mrtg/mrtg.cfg --lock-file /var/lock/mrtg/mrtg_l --confcache-file /var/lib/mrtg/mrtg.ok
Date: Wed, 18 May 2016 14:35:01 -0400 (EDT)
ERROR: unable to open include file: conf.d/*.cfg
Could this ERROR be related?
Thanks in advance for helping us get rid of the spurious process checks on the Windows servers.
--Bill
We've grouped our servers into various hostgroups and have started attaching relevant services to each.
For example, to our 'windows_baseline' hostgroup, we've attached several custom services:
WINDOWS-LOGON-ERRORS.cfg
WINDOWS-PAGE-FILE-SERVICE.cfg
WINDOWS-SERVER-WORK-QUEUES.cfg
WINDOWS-STANDARD-C-DRIVE.cfg
WINDOWS-STANDARD-CPU-SERVICE.cfg
WINDOWS-STANDARD-MEMORY-SERVICE.cfg
WINDOWS-UPTIME.cfg
Each of these services is based on a pre-defined setting. Well and good.
What's not good is that Nagios XI shows that each host in this windows-baseline has a phantom service which is checking unsuccessfuly, namely, a Linux service, "check_proc".
I've examined all the cfg files under /usr/local/nagios/etc and 'check_proc' appears as it should, in:
commands.cfg
nrpe.cfg
services/REDHAT-STANDARD-PROCESSES.cfg
services/UBUNTU-PROCESS-CHECK.cfg
I don't understand why Nagios is trying to apply check_proc to our Windows servers.
Attached is a system profile for examination.
One note: Every 5 minutes a cronjob runs and produces the same email message to root. Example:
To: [email protected]
Subject: Cron <root@nagios03> LANG=C LC_ALL=C /usr/bin/mrtg /etc/mrtg/mrtg.cfg --lock-file /var/lock/mrtg/mrtg_l --confcache-file /var/lib/mrtg/mrtg.ok
Date: Wed, 18 May 2016 14:35:01 -0400 (EDT)
ERROR: unable to open include file: conf.d/*.cfg
Could this ERROR be related?
Thanks in advance for helping us get rid of the spurious process checks on the Windows servers.
--Bill