Date: Fri, 27 Dec 2019 10:53:12 -0800 From: Lee Damon <nomad@castle.org> To: Matt Garber <matt.garber@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: ldapsearch stops working after ~4-12 hours (one host of 4) Message-ID: <492d412f-042d-645d-4f29-1e12aacc2d3d@castle.org> In-Reply-To: <CANwXMPM654ewduayedfTBUvbCgTx2yLXFpNeOVxKL3TuRbJX4w@mail.gmail.com> References: <23f18d16-7f86-8e94-8cd5-9bed61ea3405@castle.org> <CANwXMPM654ewduayedfTBUvbCgTx2yLXFpNeOVxKL3TuRbJX4w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/27/19 09:35 , Matt Garber wrote: > On Fri, Dec 27, 2019 at 12:10 PM Lee Damon <nomad@castle.org > <mailto:nomad@castle.org>> wrote: > > > Both times I observed this: > > : ldapsearch -v -LLL -x -h [redacted].ee.washington.edu > <http://ee.washington.edu>; -b > dc=ee,dc=washington,dc=edu uid=[redacted] > ldap_initialize( ldap://[redacted].ee.washington.edu > <http://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? I've asked the people who run those servers for that information. > Also, are you able to try > running those same ldapsearch queries with the IP address(es) rather > than DNS names for your server? The “can’t contact” initially seems more > like potentially DNS resolution or firewall/connectivity than something > LDAP related like failure to bind successfully… The host command returned the correct IP address when I queried it. I don't remember substituting IP addresses when this happened yesterday and I know I didn't do it this morning. I'll try that the next time this happens. nomad
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?492d412f-042d-645d-4f29-1e12aacc2d3d>