Hello Chris,
thank you for your answer :)
I replace  all 300 members at once because I'm importing data in my LDAP server 
from Active Directory Server.
I'm using SSL/TLS for all operations.

I thought to use modify/add and modify/delete, but in this case I should 
implement a custom compare method to understand which values are to add and 
which are to delete. In this way maybe the computational time is higher than 
using the replace method.

On my development machine I updated the perl-LDAP library to the 0.40-1 
version. I downloaded it directly from Red Hat repository, and I built it for 
RHEL 5.4. After this upgrade I can replace all 300 members at once.

Thanks,

Cheers 
        Francesco




-----Messaggio originale-----
Da: Chris Ridd [mailto:chrisr...@mac.com] 
Inviato: mercoledì 22 dicembre 2010 08:57
A: LIBRIZZI FRANCESCO
Cc: perl-ldap@perl.org; PENZO PAOLO (MPS-06286)
Oggetto: Re: Problem with modify/replace function


On 21 Dec 2010, at 09:13, LIBRIZZI FRANCESCO wrote:

> Hello,
> I wrote a script for updating the LDAP content. I want to modify the members 
> that belong to a group.
> Therefore I used the modify function with the replace option. In this latter 
> I used as parameter the new member list.
> When the group members number is lower than 300 the update works fine. 
> Whereas, if that number is greater than 300 the update does not work. In this 
> case, the server does not update anything and it replies with the following 
> message: LDAP_OPERATIONS_ERROR - Server encountered an internal error
> I tried the same operation by command line, using the ldapmodify command and 
> the same group member list. This latter works fine without any error message.
> 
> Do you have any suggestion?

Do you have to replace all 300 members at once? That's kind of expensive, and 
it can be *much* more efficient to use modify/add and modify/delete to just add 
and delete particular values.

Is this using SSL/TLS? There were problems in old releases with "large" 
operations over SSL, if memory serves. (I can't remember the details though.)

Can you call $ldap->debug(5) before the modify operation and verify that the 
encoded operation looks OK?

Cheers,

Chris

Reply via email to