Hi Jess,
Did you used the patch i did and i posted here and on bugzilla for bug #18756 ?
No, I didn't. I must admit that it is difficult to spot the info (tree) for the forest at times -- at least for me, though I notice I did comment on this and am already cc'ed on this bug. I guess I had been hoping that any necessary patches of this magnitude would be wrapped into a release by this point.
I have not yet gotten any core dumps, though a co-worker did *once* -- and has not been able to reproduce it. Also all works fine as long as I don't exceed the alloted shared memory (annoying, but livable) or the cache entry limit (this is the real kicker as I can't predict this for all our customers and many of them can't predict it either).
Finally HP claims that they're using stock 2.0.46 in this regard and their mod_ldap works fine (with mod_worker).
For your first issue, the problem should be that all memory allocation are not controlled in the code, i mean if it return NULL or an address to the memory, it's the same.
Yep.
So maybe when you are at user 376, you allocated all the memory of the ldap_cache, and it's unable to give more, but it continue as it was ok.
I believe that's what it's doing. I just wasn't able to get the debugger stopped right in the act -- only after this *appeared* to have occured. Looking at all the information, however, everything strongly points in this direction.
I am actually working on this problem, this issue is maybe the source of the next problem too.
For issue 2, it seems to be a bad unlock when you reach the maximum user limit, i will look this too
Thanks!
-- Jess Holle
