[Date Prev][Date Next]
Re: Bind to meta-backend returns err=52
- To: OpenLDAP Software List <openldap-software@OpenLDAP.org>
- Subject: Re: Bind to meta-backend returns err=52
- From: Dave Horsfall <firstname.lastname@example.org>
- Date: Mon, 3 Apr 2006 09:42:41 +1000 (EST)
- Archive: No
- In-reply-to: <1143787170.3352.0.camel@ando>
- References: <20060330103450.L96835@mippet.ci.com.au> <Pine.SOL.email@example.com> <1143701324.3347.1.camel@ando> <20060331093627.U57938@mippet.ci.com.au> <1143787170.3352.0.camel@ando>
On Fri, 31 Mar 2006, Pierangelo Masarati wrote:
> > Seriously, my own workaround (do a search against the meta every five
> > minutes) seems to be working. I haven't specified any of those timeouts
> > at all, so they would be whatever the defaults are.
> By default, they're off; it might be the remote server's fault if it's
> doing some sort of idletimeout.
The remote server is the local server; it looks itself up via a named
I've managed to reproduce it 100%, and it's really strange...
The FreeBSD port of OpenLDAP comes with a script
/usr/local/etc/rc.d/slapd.sh which handles starting/stopping etc. Call
this from CRON, it will fail 100% of the time, on the first search. Call
it via a remote shell, ditto. Call it from the command line, works OK.
And only on this server, which has an identical configuration to another
As it would not appear to be an OpenLDAP problem after all (but perhaps a
bug is being tickled somehow) I won't pursue it any further on this list.
Dave Horsfall DTM VK2KFU firstname.lastname@example.org Ph: +61 2 9552-5509 (d) -5500 (sw)
Corinthian Engrng P/L, Ste 54 Jones Bay Whf, 26-32 Pirrama Rd, Pyrmont 2009, AU