Share

OpenLDAP ILM Management Agent

Code

Programming Languages: C#

License: BSD License

Repositories

browse code, statistics svn co https://openldap-xma.svn.sourceforge.net/svnroot/openldap-xma openldap-xma

Show:

What's happening?

  • Comment: ArgumentOutOfRangeException

    I found the reason for the ArgumentOutOfRangeException error. Is due to a lack of permissions of the connection user, it must have full read permissions to the entire LDAP tree, for the agent locate the domain defined in the namingContexts parameter.

    2009-12-14 17:45:51 UTC by jestrela

  • Comment: ArgumentOutOfRangeException

    I've the same problem. I'm using AD (Windows 2003) and OpenLDAP 2.3.30. I've found that despite namingContexts parameter has a correct value (dc=sc,dc=ipp,dc=pt), after making a full import with OpenLDAP XMA the log search in the OpenLDAP server has an empty base DN "".

    2009-12-14 12:53:32 UTC by jestrela

  • Followup: RE: LArge eDirectory Querys

    Ah, i remember now. Trawling did work, and nonpaged worked, but both hit out of memory errors due to the amount of the information. Hince the reason for the async search which creates the xml file as it does the search in chunks. everything worked great until i went to perform the action in a very very huge OU. seems anything over 250,000 objects in the OU caused the MA to chunk with the out of...

    2009-10-05 13:19:26 UTC by donaldgullett

  • Followup: RE: LArge eDirectory Querys

    The trawling mode should try cn=a\*, cn=b\*,cn=c\*. If it's still too big, it should try cn=aa\*, cn=ab\*, cn=ac\*. If still too big, cn=aaa \*, cn=aab\*. It think you get the idea. If it does not work then it's a bug.

    2009-10-05 12:19:39 UTC by fvandelanoitte

  • Followup: RE: LArge eDirectory Querys

    I Tried Trawling But there is still to many objects per query. I Added a Section calld "ASYNC" which does a ASYNC Search which works for me (only takes 10-15 minutes to pull every object). Our naming scheme does have it seperated into "A", "B", "C" users, but that is still extremly large.

    2009-10-05 11:51:50 UTC by donaldgullett

  • Followup: RE: LArge eDirectory Querys

    Try setting pagedSearch to "TRAWLING". It should segment the search into subsearches (cn=a\*, cn=b\*, cn=c\*,...)

    2009-10-05 08:33:53 UTC by fvandelanoitte

  • Modify Time Stamp Change

    Using Modify Time Stamp Attribute with eDirectory, you have to change the ".0Z" to "Z" in the code to support a delta search. Suggest Configuration Item to change this part.

    2009-10-04 16:46:21 UTC by donaldgullett

  • ASYNC Search Addition

    I would like to suggest a implementation of "ASYNC" added to the paged search which i have the code for. This runs the ldap query as a Asyncronous query which worked really well on large directories. With a OU of 500,000+ users the query completed in less then 15 minutes and started the import of the XML file. Edirectory does not support paged searches through the suggested OID.

    2009-10-04 16:43:40 UTC by donaldgullett

  • Comment: Out of Memory Errors with eDirectory

    I would like to suggest a implementation of "ASYNC" added to the paged search which i have the code for. This runs the ldap query as a Asyncronous query which worked really well on large directories. With a OU of 500,000+ users the query completed in less then 15 minutes and started the import of the XML file.

    2009-10-04 16:41:00 UTC by donaldgullett

  • modify timstamp query error in eDirectory

    The query during the delta import adds a ".0z" to modifytimestamp for delta import, I had to edit the code to remove the ".0".

    2009-10-03 16:45:12 UTC by donaldgullett