Ad Widget

Collapse

Assertion failure with RHEL5 OpenLDAP

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • xaeth
    Member
    • Nov 2004
    • 67

    #1

    Assertion failure with RHEL5 OpenLDAP

    Server: RHEL 5.3 x86 completely current
    OpenLDAP: 2.3.43

    We just upgraded to 1.6.5 yesterday, but we've been running zabbix for a bit now. We just started monitoring some ldap ports today and our proxy server does NOT like that. We see the following line in our zabbix_proxy.log:

    Code:
    ./../../libraries/libldap/getvalues.c:43: ldap_get_values: Assertion `target != ((void *)0)' failed.
    At which point it throws a kill signal and exits. We had to manually disable the hosts in the proxy's mysql database as well as teh web interface to actually get the server back up. I've googles around and the only other note I see about this error is someone complaining on the courier-users mailing list. The response to them was "it looks like its a deep dark openldap issue, talk to them"

    I have a RedHat support contract, and they said they will gladly debug the issue if we can give them some isolated code that throws the same error.

    He did mention that there is a known nss_ldap issue related to timeouts throwing a NULL if set to low, but checked our ldap.conf and its set to their recommended work-around time (120s)

    Anyone have any thoughts/fixes/scripts that might be of help?

    Thanks
  • xaeth
    Member
    • Nov 2004
    • 67

    #2
    so either no one...

    uses ldap monitoring from RHEL/CENTOS 5 on Zabbix 1.6

    or

    has this issue on RHEL/CENTOS 5 on Zabbix 1.6



    anyone care to comment on which?

    Comment

    • NOB
      Senior Member
      Zabbix Certified Specialist
      • Mar 2007
      • 469

      #3
      Originally posted by xaeth
      uses ldap monitoring from RHEL/CENTOS 5 on Zabbix 1.6

      or

      has this issue on RHEL/CENTOS 5 on Zabbix 1.6



      anyone care to comment on which?
      Both

      We use the Nagios plugin for that. Works fine ...

      Regards

      Norbert.

      Comment

      • xaeth
        Member
        • Nov 2004
        • 67

        #4
        so you don't have the problem, but you use nagios plugin to monitor LDAP anyways? (the subject was a prefix to both points)

        I'll look into using nagios for that, but we didn't install nagios in the first place for numerous reasons.

        Comment

        • NOB
          Senior Member
          Zabbix Certified Specialist
          • Mar 2007
          • 469

          #5
          Hi xaeth

          Originally posted by xaeth
          so you don't have the problem, but you use nagios plugin to monitor LDAP anyways? (the subject was a prefix to both points)

          I'll look into using nagios for that, but we didn't install nagios in the first place for numerous reasons.
          We don't use Nagios, either, for several reasons, too.

          But ZABBIX can use the Nagios plugins as external check.

          So just compile the Nagios checks on your system (you need the
          LDAP client library und headers installed aka. the -dev package)
          and copy the check_ldap binary into the directory where
          the ExternalScripts= entry in your zabbix_server.conf points to.

          Set the access rights correctly, write a small Nagios plugin wrapper script,
          create a valuemap for the Nagios exit codes and you're set.

          HTH,

          Norbert.

          Comment

          Working...