Problem will windows service checks

[DBAFOX]

Hi,

I've got an issue with some windows process checks using the NCPA --
they show up critical: invalid credentials --
However, when i look at the core-config-manager --> services , I cannot find them listed for these servers.

the checks are simple ncpa checks
1) SQLSERVERAGENT (check_ncpa.py .... -q 'service=SQLSERVERAGENT,status=running')
2) MSSQL Service Status (check_ncpa.py .... -q 'service=MSSQLSERVER,status=running')

there are other servers with these checks -- just a couple of them are missing and keep coming up as alerts (see pics below)

Where would they be stored ? looked on /usr/local/nagios/etc and the subdirs
not there either (is this now an orphaned artifact in the database?)

Sincerely,
dBAFox

[kg2857]

Does the service have hostgroups?

[rose42snowden]

Based on your description, it sounds like the NCPA checks are configured on your Nagios server, but the service definitions for these specific checks on those particular servers are either not properly linked or are missing from the configuration files that Nagios reads. The "invalid credentials" error from NCPA is a bit misleading here, as it's likely a symptom of the check failing to execute properly, rather than an actual credential problem on the Windows host. The fact that the checks are not listed in the Core Config Manager for those servers suggests they might be defined in a separate or older configuration file that is still being loaded by Nagios, or they could be orphaned artifacts in the Nagios database that are causing alerts without a proper service definition to be displayed. You should check cfg files in /usr/local/nagios/etc and its subdirectories for any a d-hoc or misconfigured service definitions. It's also possible a stale file is being loaded from a different location or a backup directory, or that the database itself has an inconsistency.
mymilestonecard

[DBAFOX]

Yes -- they are part of a host group -- but i haven't done anything with the hosts groups (they are all basic )

sincerely,
dBAFox

[kg2857]

If the host in question is in the hostgroup attached to the service the mystery is solved.