[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Weird problem importing data to an OpenLDAP Server
Perangelo:
On Tuesday we decided to upgrade to SuSE 10.1, this version of SuSE
provides OpenLDAP 2.3.19. The problem still persists.
I'm writing right now an email giving further clarification, since the
problem is very wierd. I was able to update most of the objects in my
new setup, but only a few (about 50 or so) still resist to be updated ;)))).
Andres
Pierangelo Masarati wrote:
> On Mon, 2006-06-05 at 18:35 -0300, Andres Tarallo wrote:
>
>> I'm using OpenLDAP version 2.2.27, from SuSE RPMs, in SuSE 10.0. We have
>> an Old SuSE Email Server and we're dumping soem of the attributes of
>> it's users and importing them to the corresponding users in the New LDAP
>> Server.
>>
>> With the data of some users i get something like this as error: *
>> ldapadd: invalid format (line 12) entry:
>> "uid=XXXXX,ou=Users,dc=ort,dc=edu,dc=uy"*
>>
>> I runned ldapadd with an -S swtich, in the log file I've got:* Error:
>> Bad parameter to an ldap routine (-9)*.
>>
>> I'm lost so any help you can offer is welcome.
>>
>
> First of all, I suggest you drop 2.2.27 and install a decent 2.3 from
> scratch. Moving from what you call "Old" to what we call "Ancient"
> would put people in a better mood as to whether spend time providing
> further suggestions.
>
> Then you should provide a bit more information about what error you're
> encountering. For example, post the contents of the LDIF file that
> caused the issue. Since you appear to have a format problem, make sure
> you only sanitize the contents as little as possible for security
> reasons (if you change a username, make sure you don't hide that it
> contained fancy chars, and so). You should run ldapadd with debug
> switched on (-d something; libldap mostly uses "trace" so you should be
> fine with it). From your posting, it is not clear what the offending
> string is. Is the stars and the double quotes part of the DN? By
> inspecting the real LDIF it should be immediately clear what's wrong.
>
> p.
>
>
>
>