Date: Fri, 27 Dec 2019 12:35:16 -0500 From: Matt Garber <matt.garber@gmail.com> To: Lee Damon <nomad@castle.org> Cc: freebsd-stable@freebsd.org Subject: Re: ldapsearch stops working after ~4-12 hours (one host of 4) Message-ID: <CANwXMPM654ewduayedfTBUvbCgTx2yLXFpNeOVxKL3TuRbJX4w@mail.gmail.com> In-Reply-To: <23f18d16-7f86-8e94-8cd5-9bed61ea3405@castle.org> References: <23f18d16-7f86-8e94-8cd5-9bed61ea3405@castle.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Dec 27, 2019 at 12:10 PM Lee Damon <nomad@castle.org> wrote: > > Both times I observed this: > > : ldapsearch -v -LLL -x -h [redacted].ee.washington.edu -b > dc=3Dee,dc=3Dwashington,dc=3Dedu uid=3D[redacted] > ldap_initialize( ldap://[redacted].ee.washington.edu ) > ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1) Do you have connection/access logs on the LDAP server to verify whether a connection is even being established? Also, are you able to try running those same ldapsearch queries with the IP address(es) rather than DNS names for your server? The =E2=80=9Ccan=E2=80=99t contact=E2=80=9D initially seem= s more like potentially DNS resolution or firewall/connectivity than something LDAP related like failure to bind successfully=E2=80=A6 Thanks, -Matt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANwXMPM654ewduayedfTBUvbCgTx2yLXFpNeOVxKL3TuRbJX4w>