Hi all, it looks like something in the job data directory causes Jenkins to fail connection to the LDAP server. How can I find out what job or build is responsible?
--- We tried to move to LDAP authentication, which works well on other (newly installed) Jenkins instances on the same and other systems. At first, when configuring it, it works once the manager credentials are entered (no form validation errors). Unfortunately, we're getting the following error message (form field validation without changing contents, includes stack trace) when revisiting the config page after saving it: Connection refused: connect Logins to Jenkins also fail. It doesn't seem to be an issue with the LDAP configuration, but a side effect of the job data: * Other Jenkins instances on the same and other systems use the same credentials and work fine. * Even when I just shut down this Jenkins, remove the jobs, fingerprints, and job config history directories, and start it again, it works! Our Jenkins instance, now 1.447.2, grew over time, from a few dozen jobs to over two hundred, with a 5 digit number of builds. A restart takes around 20 minutes every time, so I'm reluctant to try to locate the issue by adding a few jobs at a time and restarting Jenkins in between. Any ideas what I could do to find out what causes this issue? Thanks in advance, Daniel
