Nagios Support Forum

I've recently configured LDAP via Apache in nagios.conf & nagiosxi.conf. I prefer to do this in Apache as we use both Nagios core & NagiosXI interfaces and would like a seamless transition between the two. Navigation and everything is working as expected. However, the only casualty is CCM (Core Config Manager).

I can authenticate against CCM using those specific credentials, make my changes, etc. However, once I click 'Apply configuration', it sits and spins on 'Waiting for configuration verification' indefinitely. If I tail cmdsubsys.log, all authentication looks great and all sections report 'OK'.

Once I remove the LDAP configuration from nagiosxi.conf, restart httpd, the 'Waiting for configuration verification' completes immediately. Any changes from that point forward apply within seconds until I put the LDAP configuration back in.

Has anyone seen this before and/or can shed any light on how to enable LDAP for NagiosXI using Apache w/o breaking CCM? Thanks!
Tim

Have you tried using the ldap XI component?

I did try that component, but I had issues getting into Nagios core. Especially, if the user would change their LDAP password or if the LDAP password contained spaces. I'd like to seamlessly go from Nagios Core to Nagios XI, which works with Apache doing the authentication. However, my CCM no longer works, which is one of the main benefits of NagiosXI.

However, my CCM no longer works, which is one of the main benefits of NagiosXI.

Can you give a little more detail as to how the CCM is broken?

When using Apache LDAP config, CCM will sit and spin when applying configuraiton (per my first post).

When using LDAP/AD components in NagiosXI, I have issues with seamlessly transitioning between Nagios Core & Nagios XI. We primarily use Nagios core, but the perfdata comes from Nagios XI, so I'd like to be able to click on extra actions and not have to authenticate again to Nagios XI. All of that works with Apache LDAP config, but CCM no longer functions.

It appears to be a win/lose situation. Maybe if it were possible to set the CCM directories up to not use LDAP authentication, but I'm not well versed with how to do that.

I found that creating a symbolic link to the perfdata in the nagios directory would make it so our users don't have to cross between Core & XI. It seems to be working great. Then, I could use the AD component for Nagios XI, if necessary.

I think I just discovered an issue with the latest version of XI, though. CCM appears to be changing '&' characters to & in the .cfg files, which is not understood.

I think I just discovered an issue with the latest version of XI, though. CCM appears to be changing '&' characters to & in the .cfg files, which is not understood.

This is a known bug for the 2012r1.4 release and is fixed the latest version (1.6).

I'm on 1.6 - immediately after the upgrade and applying the confguration is when this started.

Do you experience the issues when creating a brand new url service check, or are the issues just with preexisting checks?