I parsed the service check command to my cli (replacing check_mk_active-ldap! with the actual path)
/omd/sites/cmk/lib/nagios/plugins/check_ldap -H ‘< hostaddress>’ -b OU=< value>,OU=< value>,DC=< value>,DC=< value> -D CN=< value>,CN=,DC=< value>,DC=< value> -P ‘< password>’ -3
The output I get is “LDAP OK - 0.028 seconds response time|time=0.027852s;;;0.000000”
So this check seems to work both via CLI AND during service discovery. It only changes its state to UNKOWN later on.
I have the same check setup for another LDAP server, which works fine.
I already tried recreating the check, reinitialize/rediscover services, however, the problem seems to persist.
Does anyone face a similiar issue?
Wait a few minutes, Raw is sometimes a bit lazy. You can also force the re-run of the check by going to the monitoring view of the host, clicking on the Hamburger menu and select “re-schedule this check”.
the problem still persists.
I even tried adding it with “Integrate Nagios plug-ins” so it directly runs the command in the cli: /omd/sites/cmk/lib/nagios/plugins/check_ldap -H ‘<HostIP’ -b OU=,OU=< value>,DC=< value>,DC=< value> -D CN=< value>,CN=< value>,DC=< value>,DC=local -P ‘< value>’ -3
On the CLI and during service discovery I get
“LDAP OK - 0.028 seconds response time|time=0.027852s;;;0.000000”
But as soon as I look in the services the service state is UNKOWN (as seen above).
This only happens for this specific host. I do have a different host with the same service that works perfectly fine.
I tried deleting and adding the host again, unfortunately, this changed nothing.
unfortunately, after all these months and updating to 2.3.0p39 the problem still persists.
I will be upgrading to 2.4 soon and hope the problem will disappear
