Monitor the LDAP services in checkmk tool

[Rao]

Hi Team,

Looking for your support.

How can we monitor the LDAP services in check mk raw edition.
check-mk 1.6.0 p12 raw edition.

[Heavy]

There is a ruleset for checking an LDAP service.

Checkmk 2.0: Setup → Services → HTTP, TCP, Email… → Check LDAP service access
Checkmk 1.6: Host and Service Parameters → Active Checks → Check access to LDAP service

[Rao]

Thanks sharing the details, Could you please share me the parameter values.

[andreas-doehler (Andreas)]

The parameters are completely defined by your infrastructure.
If you need authentication to browse the LDAP (what i hope is the case) you need to define authentication credentials.
Important is the “Base DN” to connect to. These two are the minimal settings i think.
All other are optional.

[Rao]

Thanks sharing the details, i am getting this error

when i have ran below command server manually getting LDAP is OK

/omd/versions/default/lib/nagios/plugins/check_ldaps/check_ldaps -H -b ‘dc=xx,dc=xx,dc=xx,dc=xx’ -D ‘cn=admin,dc=xx,dc=xx,dc=xxx,dc=xx’ -P ‘password’ -p 389
LDAP OK - 0.014 seconds response time|time=0.014317s;;;0.000000

I tried to add the rules Checkmk 1.6: Host and Service Parameters → Active Checks → Check access to LDAP service but getting the below error

check_mk_active-ldap! -H ‘’ -b ‘dc=xx,dc=xx,dc=xx,dc=xx’ -D ‘cn=admin,dc=xx,dc=xx,dc=xx,dc=xx’ -P ‘passwrd’ -p 389

Could not bind to the LDAP server

[Rao]

Thanks sharing the details, i am getting this error

when i have ran below command server manually getting LDAP is OK

/omd/versions/default/lib/nagios/plugins/check_ldaps/check_ldaps -H -b ‘dc=xx,dc=xx,dc=xx,dc=xx’ -D ‘cn=admin,dc=xx,dc=xx,dc=xxx,dc=xx’ -P ‘password’ -p 389
LDAP OK - 0.014 seconds response time|time=0.014317s;;;0.000000

I tried to add the rules Checkmk 1.6: Host and Service Parameters → Active Checks → Check access to LDAP service but getting the below error

check_mk_active-ldap! -H ‘’ -b ‘dc=xx,dc=xx,dc=xx,dc=xx’ -D ‘cn=admin,dc=xx,dc=xx,dc=xx,dc=xx’ -P ‘passwrd’ -p 389

Could not bind to the LDAP server

[martin.schwarz]

check_ldap != check_ldaps

If this plugin is called via ‘check_ldaps’, method ‘STARTTLS’ will be
implied (using default port 389) unless --port=636 is specified. In that case
‘SSL on connect’ will be used no matter how the plugin was called.
This detection is deprecated, please use ‘check_ldap’ with the ‘–starttls’ or ‘–ssl’ flags
to define the behaviour explicitly instead.

I’m not sure if the required options are available in the WATO web interface. But if all else fails, you can still integrate the working command with a rule in “Classical active and passive Monitoring checks”