Re: oes2sp1 - Ndsd using up all threads

[a...@novell.com]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

How many replicas are we talking about? Just the one IDM driver? Do you
also use this one for direct authentication? You could try to increase
your thread count for eDirectory in case you're just reaching your limit
(run `sudo /opt/novell/eDirectory/bin/ndsconfig get` and look for anything
about max threads to see the limit per eDirectory settings) in eDirectory
but if your box itself is over-utilized in this state then that will not
really help. Any load you can divert from this box to another willing
machine will probably be worthwhile so this machine can focus on the tasks
that are assigned exclusively to it.

Good luck.

a2iacovi wrote:
> We have a root server that holds a replica of every partition in our
> tree, which is needed to run dirxml syncs to a flat tree we have that is
> an authoritative source for identity management in our environment.
>
> The root server cannot keep up with thread need / usage, when it cannot
> keep up anymore it locks up and effects services from enterprise logins
> to repkication across the entire tree. Users cannot login around the
> enterprise when it happens, replica partition syncs stop, very, very,
> very ugly.
>
> The thread count eventually gets to over 320 and the server ndsd needs
> to be restarted.
>
> To get around this we are restarting ndsd with a script, using a
> trigger of if used threads get close to 320.
>
> It is a OES2SP1SLES10SP2 64 bit, updated patches being managed by zlm.
>
> Latest version of edir also: 8.8.5
> Anyone else seeing this? Any ideas?
>
> Thanks
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJK9ZSYAAoJEF+XTK08PnB5NwAP/AoqahPOCq7Q6XaMBmcc4IoS
aG44hfIpY0BBR7XoHXLW/YIxRE43T0iMFkv6+5gVljOwF2ed1wgqM1Cqu0ODXLPe
HuD5ay0rojMEk3IB0/UFX+R/kraA6QYXocq7aAlniZbpyg9Fpzn+l5jdB5dI+Zl5
GmEATHYd44mvBxVJFcuTm9tjIpZ5BiLPhLVlA8uejPA7oUadOMALp+ZDAplLjVa+
l3scHUEP2EyAGe1h2gh92wX1YJCU2n2MPEAEd5O6iE7vdcZRS/SsNUrgrQaFlUFy
E3FhEctulKRz5i1uWfEFaHFzwMl1Y0rsvKZgcz4ZcjPs2QapX7y152DLxzWycQrl
DrK4h6ul15KXa1e7QaKpFRbsOvvU5jm24fuo6NUqQZWWYxr186i3kZ7PFWrg+zBV
Q+MT/Y3uF5v64DGd5ITdoURG1tnxnEteQ06ywdwugg2M7i+mieN9OS5ETfHPf1zi
iVi7Ha3rYLB5mys7wVw1PmMs3A15sng08grNGv9AaMnPPVY+2DD9uODgrsGRaX6l
nYBBBfC+FQ7T5QAJa6H8psYURhs6Jzs5ObbUsirBHDQ+PDg9jqIa3euzPPKClVPq
hsU7Io01WY126YunIX458cAZzg5ANJ6tiHGoq2pIzhPSTrGj3z27JU6jS16EOPl/
f0lWjbHKglgMfmGvj8VB
=p5Pp
-----END PGP SIGNATURE-----

[David Gersic]

On Fri, 20 Nov 2009 00:06:03 +0000, a2iacovi wrote:

>> Is there a way to tell it not to participate in referrels for certain
>> containers, so we could attempt balance that out.
>
> Does anyone know if I can do the above question?

Yes. You can't.

--
---------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Novell Knowledge Partner http://forums.novell.com

Please post questions in the newsgroups. No support provided via email.