Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-13265

Ldap connection failed - jenkins loosing FQDN of ldap server

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: ldap-plugin
    • Environment:
      Jenkins in all 1.4xx versions, Linux X86, SLES 10, Apache Tomcat 7.0.14
    • Similar Issues:

      Description

      Jenkins is configured to use LDAP login which works perfectly. After some time - some times directly after restarting tomcat - the login fails. When checking catalina.out the attached exception is thrown. The reason for the failed login is clear - Jenkins is configured to connect to ldap.my.domain - but when this happens Jenkins forgets "ldap" and tries to connect to my.domain only - for sure this does not work as this is no valid host name.

      To fix this, we need to restart Tomcat until it failes again.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              jomu78 Joern Muehlencord
            • Votes:
              4 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated: