openldap unstable on freebsd
alexs at ulgsm.ru
alexs at ulgsm.ru
Thu Oct 29 12:31:12 UTC 2009
* Dewayne Geraghty <dewayne.geraghty at heuristicsystems.com.au> [2009-10-29 10:39:22 +1100]:
> Alexs,
> Thank-you. You seem to be using a default setup from ports.
>
> If you are using the same configuration files for slapd.conf and
> /var/openldap-data/DB_CONFIG files on the three operating systems, and FreeBSD
> isn't working, I'm struggling to think of any load induced problems that it
> might be from the information provided.
>
> Rather than asking you a lot of questions, I think you need to rule out that
> disks can handle the load, that bdb is able to service the queries, and that
> the tools creating the ldap queries are using the same assumptions that the
> ldap server is using, etc. I think it unlikely, but I couldn't rule out a bad
> ldap query as a source of the problem.
I tryed put database on RAM drive (created by mdconfig -t malloc), fails
anyway.
All configs in defaults, inly indexes and some acls added.
> Review the "man slapd.conf" and determine the loglevel that you think
> appropriate, I'd suggest 2047 as a good start.
> /usr/local/libexec/slapd -d 2047 -4 -h ldapi://%2fvar%2frun%2fopenldap%2fldapi/
> ldap://alexs-ldap-server/
For geting crashes (for this mail only, real crashes needs to wait) I am use small
script via nss_ldap.
~]>cat test.sh
#!/bin/sh
while true
do id test > /dev/null
done
With 3 running scripts get fault in 30 seconds
http://pastebin.org/49205
http://pastebin.org/49211
http://pastebin.org/49213
So crashes in different places. I think need some another debuging.
I tried truss slapd process, but there different places too.
>
> Good luck, Dewayne.
--
Email: alexs at ulgsm.ru
Email/Jabber: alexs at ulgsm.ru
More information about the freebsd-stable
mailing list