Problem with ldapsync after server crash in OpenLDAP server

Best practice information from Scalix users relating to integration of Scalix with other products.

Moderator: ScalixSupport

skallen

Problem with ldapsync after server crash in OpenLDAP server

Postby skallen » Tue Oct 31, 2006 5:33 am

Hi all,

I have problems after having to move our openLDAP server to a new server, we did restore an ldif backup and after this we are not able to modify accounts.
The error messages is like:
Failed to locate or retrieve information in LDAP for id 7cd537d6-f228-102a-98f9-efbc7a07903a

I realize that the id must have been changed on the openLDAP server, but is there any way to fix this without having to backup the users mailboxes and delete the users?

vlaurenz
Posts: 123
Joined: Wed May 31, 2006 3:41 pm

Re: Problem with ldapsync after server crash in OpenLDAP ser

Postby vlaurenz » Tue Oct 31, 2006 9:51 am

skallen wrote:Hi all,

I have problems after having to move our openLDAP server to a new server, we did restore an ldif backup and after this we are not able to modify accounts.
The error messages is like:
Failed to locate or retrieve information in LDAP for id 7cd537d6-f228-102a-98f9-efbc7a07903a

I realize that the id must have been changed on the openLDAP server, but is there any way to fix this without having to backup the users mailboxes and delete the users?


Looks like the unique id for your users has changed in the new LDAP server. My first instinct tells me that you will have to run omldapsync with the -L flag to reload the Scalix directory. You'd then have to accept (either -A or -P) any errors.

Your other choice is to obtain all the new unique ids and come up with a script which will run an ommodent for each affected Scalix directory entry and change the unique id to match that of the LDAP server.

Hope this helps.

skallen

Re: Problem with ldapsync after server crash in OpenLDAP ser

Postby skallen » Wed Nov 01, 2006 6:30 am

vlaurenz wrote:Looks like the unique id for your users has changed in the new LDAP server. My first instinct tells me that you will have to run omldapsync with the -L flag to reload the Scalix directory. You'd then have to accept (either -A or -P) any errors.

Your other choice is to obtain all the new unique ids and come up with a script which will run an ommodent for each affected Scalix directory entry and change the unique id to match that of the LDAP server.

Hope this helps.


Thank you for the reply.

But it did not help, the omGlobalUniqueId did no change in scalix.

And when i run ommodent it looks like i can't change the omGlobalUniqueId...

[root@scalix ~]# ommodent -e "S=Olsson/G=Mikael/OU1=se-ka-sr020/OU2=se-ka/CN=Mikael Olsson" -n omGlobalUniqueId=79f964e2-f228-102a-9742-efbc7a07903a
omGlobalUniqueId=79f964e2-f228-102a-9742-efbc7a07903a
[OM 16073] Unknown attribute specified.

Attribute : omGlobalUniqueId

The solution that works so far is:
backup a mailbox
delete the user
remove the scalixUserClass for the user in OpenLDAP
run omldapsync
delete the user in scalix
add the scalixUserClass in OpenLDAP
run omldapsync
restore the mailbox

But this is a very slow process and might not even work for some users with big mailboxes (> 2GB), so i really need some way to modify the omGlobalUniqueId in scalix.

skallen

Re: Problem with ldapsync after server crash in OpenLDAP ser

Postby skallen » Wed Nov 01, 2006 8:16 am

I found out that i did it wrong, it should have been:

ommodent -e "S=Olsson/G=Mikael/OU1=se-ka-sr020/OU2=se-ka/CN=Mikael Olsson" -n GLOBAL-UNIQUE-ID=79f964e2-f228-102a-9742-efbc7a07903a
Now i can fix the problem.

Thanks for the help anyway
:)

vlaurenz
Posts: 123
Joined: Wed May 31, 2006 3:41 pm

Postby vlaurenz » Thu Nov 02, 2006 9:30 am

You're welcome.


Return to “Third Party Integration”



Who is online

Users browsing this forum: No registered users and 2 guests