Hi, I'm aware of the tree-lock, but still don't know how this can be handled, and when/how the project can transition to 2.4.x.
FWIW, I plead guilty of not testing a preliminary 2.4 port, but will do ASAP if I get my hands on one. The problem described below is still biting me hard. =8-( On Mon, 16.02.2009 at 11:16:13 +0100, Toni Mueller <openbsd-po...@oeko.net> wrote: > On Sun, 15.02.2009 at 15:28:00 +0100, Toni Mueller <openbsd-po...@oeko.net> > wrote: > > On Fri, 06.02.2009 at 12:21:06 +0100, Toni Mueller <openbsd-po...@oeko.net> > > wrote: > > > I have openldap-server-2.3.43, as shipped with OpenBSD 4.4/i386, under > > I have this package also running on 4.4/amd64, and it hung on an > > attempt to add an entry. I needed to use kill -9 in order to restart > > it. > > I adjusted the configuration of openldap on an i386 machine to the one > on an amd64 machine that I used to compare with, and found the > following, using ktrace/kdump (exerpt): > > > daemon: select: listen=8 active_threads=0 tvp=zero > PSIG SIGTERM caught handler=0x2eb7fc4 mask=0x0 > RET poll -1 errno 4 Interrupted system call > > CALL read(0x3,0x8a03d4d0,0x80) > RET read -1 errno 35 Resource temporarily unavailable > > --> The last thing I saw about 'fd 3' was some library opened. > > > daemon: shutdown requested and initiated. > daemon: closing 8 > > CALL fstat(0x8,0x8a03d5e0) > RET fstat -1 errno 22 Invalid argument > > --> I was unable to find anything like an open(2) call resulting in fd 8 > > slapd shutdown: waiting for 1 threads to terminate > > > --> The latest other message mentioning threads was the one at the > beginning, stating something about 'active_threads=0'. > > > When I remove the syncrepl slave clause, the problem goes away. Nuking > the db and starting over didn't help in any way. > > > I'm stumped... > > > -- > Kind regards, > --Toni++ > -- Kind regards, --Toni++
