[JIRA] (JENKINS-13265) Ldap connection failed - jenkins loosing FQDN of ldap server
Jesse Glick updated JENKINS-13265 Ldap connection failed - jenkins loosing FQDN of ldap server Change By: Jesse Glick (18/Oct/12 8:53 PM) Component/s: ldap Component/s: security This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13265) Ldap connection failed - jenkins loosing FQDN of ldap server
Joern Muehlencord commented on JENKINS-13265 Ldap connection failed - jenkins loosing FQDN of ldap server The workaround seems to work here also (even I think this kind of a bad hack). On our end ldap.mycompany.com is a load balancer with 5 or 6 servers behind. So the servers we are talking have different ip addresses - but ldap has one ip address only and the real servers behind should be transparent to Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13265) Ldap connection failed - jenkins loosing FQDN of ldap server
1 2 commented on JENKINS-13265 Ldap connection failed - jenkins loosing FQDN of ldap server I was having the same issue and found a workaround. In my case the problem was due to a rather weird network configuration. LDAP server was dc.mycompany.com which resolves to (say) 10.0.10.1. In turn my company.com has two IPs assigned: 10.0.10.1 (same as dc.mycompany.com) and 10.0.10.2. I believe that Jenkins resolves dc.mycompany.com and then goes back to DNS name with a reverse DNS lookup yielding my company.com instead of dc.mycompany.com. When it was time to talk with LDAP server Jenkins resolved mycompany.com and getting either 10.0.10.1 or 10.0.10.2 randomly. If it did resolve to the "right" address things worked just fine otherwise LDAP login failed. The workaround was to ensure that mycompany.com always resolved to the "right" address with the help of /etc/hosts. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13265) Ldap connection failed - jenkins loosing FQDN of ldap server
[ https://issues.jenkins-ci.org/browse/JENKINS-13265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kohsuke Kawaguchi updated JENKINS-13265: Component/s: security (was: active-directory) Wrong component as this is not about the AD plugin. > Ldap connection failed - jenkins loosing FQDN of ldap server > > > Key: JENKINS-13265 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13265 > Project: Jenkins > Issue Type: Bug > Components: security >Affects Versions: current > Environment: Jenkins in all 1.4xx versions, Linux X86, SLES 10, > Apache Tomcat 7.0.14 >Reporter: Joern Muehlencord > Labels: ConnectExcetion, ldap, plugin > Attachments: exception.txt > > > 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13265) Ldap connection failed - jenkins loosing FQDN of ldap server
[ https://issues.jenkins-ci.org/browse/JENKINS-13265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] > Ldap connection failed - jenkins loosing FQDN of ldap server > > > Key: JENKINS-13265 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13265 > Project: Jenkins > Issue Type: Bug > Components: active-directory >Affects Versions: current > Environment: Jenkins in all 1.4xx versions, Linux X86, SLES 10, > Apache Tomcat 7.0.14 >Reporter: Joern Muehlencord > Labels: ConnectExcetion, ldap, plugin > Attachments: exception.txt > > > 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13265) Ldap connection failed - jenkins loosing FQDN of ldap server
[ https://issues.jenkins-ci.org/browse/JENKINS-13265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-13265 stopped by Joern Muehlencord. > Ldap connection failed - jenkins loosing FQDN of ldap server > > > Key: JENKINS-13265 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13265 > Project: Jenkins > Issue Type: Bug > Components: active-directory >Affects Versions: current > Environment: Jenkins in all 1.4xx versions, Linux X86, SLES 10, > Apache Tomcat 7.0.14 >Reporter: Joern Muehlencord > Labels: ConnectExcetion, ldap, plugin > Attachments: exception.txt > > > 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13265) Ldap connection failed - jenkins loosing FQDN of ldap server
Joern Muehlencord created JENKINS-13265: --- Summary: Ldap connection failed - jenkins loosing FQDN of ldap server Key: JENKINS-13265 URL: https://issues.jenkins-ci.org/browse/JENKINS-13265 Project: Jenkins Issue Type: Bug Components: active-directory Affects Versions: current Environment: Jenkins in all 1.4xx versions, Linux X86, SLES 10, Apache Tomcat 7.0.14 Reporter: Joern Muehlencord Attachments: exception.txt 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
