[Date Prev][Date Next]
Re: LDAPADD command hangs
--On Monday, February 28, 2005 10:48 AM +0800 "Sivasakthi d/o Sivagnanam"
Hope someone out there could help me here.
Openldap was installed on LINUX with 256MRAM.
A separate entity does an insertion using ldapadd to the openldap every
When the system went life, open to public....the ldapadd command just
hangs there. The traffic was really huge hence disrupting new CRL updates
and other insertion via ldapadd.
What we've done is open the slave machine for public access so that the
master openldap machine is dedicated for the insertion, hence not
disrupting new data from being updated.
Originally what we did was use host.deny and host.allow to control traffic
but we realised external all our uses couldn't get in hence that was not
the right solution. The above action seems to work. However, do you have
any other ideas ?
Also, the connection and query is taking a long time. How would one
control the traffic to openldap ? Do we introduce load balancer ?
Openldap only has 1 listener running I think, can one increase this so
that it can manage multiple query ? How does it actually manage all these
queries. Is it in a queue ? Max how many concurrent users could it manage
? Anyone could guide me how to improve the performance ? When I click on
each DN, it takes a long time to actually populate the result but when it
does it flows very quickly. The next time i do a refresh (am using
Softerra LDAP Browser to view it), again it takes a long time before
actually populating it.
I answered your last email, but it bounced at your host, so unless you've
fixed that, I suggest getting a working email address first.
Principal Software Developer
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html
"These censorship operations against schools and libraries are stronger
than ever in the present religio-political climate. They often focus on
fantasy and sf books, which foster that deadly enemy to bigotry and blind
faith, the imagination." -- Ursula K. Le Guin