Modify

Ticket #3123 (closed defect: fixed)

Opened 22 months ago

Last modified 22 months ago

Error Experienced in Importing Users to New Master LDAP server

Reported by: aldrin@… Owned by: cperez@…
Milestone: Component: users
Severity: blocker Keywords: migrate, migration, migrate users, ldap
Cc:

Description

Problem: error: Couldn't bind to LDAP server, result code: 49

  1. Setting up the Zentyal master LDAP server
  2. Installed Ubuntu 10.04 using minimal CD
  3. Installed Zentyal using apt-get
  1. Creating the config file to be imported to new Zentyal Master LDAP server
  2. Exported configuration of original Zentyal server
  3. Exported configuration of new Zentyal server from step A.
  4. Transferred users.bak of file from step 3 to file of step 4
  5. Deleted the entry of root from master-data.ldif of file from step 3. The deleted data is below:

uid=root,ou=Users,dc=SG-FS,dc=allproperty,dc=org uid: root sambaSID: S-1-5-21-3818554400-921237426-3143208535-1002 displayName: root objectClass: sambaSamAccount objectClass: account structuralObjectClass: account entryUUID: fb829dd0-dce3-102f-999e-abc4fa884e0b creatorsName: cn=ebox,dc=SG-FS,dc=allproperty,dc=org createTimestamp: 20110307085231Z sambaNTPassword: 6CF5B8FE5261B23C09AF7B6DED69FE7A sambaPasswordHistory: 00000000000000000000000000000000000000000000000000000000

00000000

sambaAcctFlags: [U ] sambaHomePath:
SG-FS\homes\root sambaPwdLastSet: 1313036220 entryCSN: 20110811041700.076990Z#000000#000#000000 modifiersName: cn=ebox,dc=SG-FS,dc=allproperty,dc=org modifyTimestamp: 20110811041700Z

dn:

If step 6 is not done, the import of the config file to new server will fail because user root already exists.

  1. Importing the config file to the new Zentyal Master LDAP server
  2. Disabled MD5sum check from new Master LDAP server. (Based from here:  http://trac.zentyal.org/ticket/2709).
  3. Imported the config file.
  4. Saved settings
  5. Enabled Users & Groups Module

-> Err: Couldn't bind to LDAP server, result code: 49

Attachments

exported config of new zentyal master ldap server.tar Download (152.5 KB) - added by anonymous 22 months ago.
exported & edited config of new zentyal master ldap server.tar Download (152.5 KB) - added by anonymous 22 months ago.
original exported config of new zentyal master ldap server.tar Download (92.5 KB) - added by aldrin@… 22 months ago.
the un-edited exported config file of new master zentyal server
exported config of original zentyal master ldap server.zip.001 Download (107.0 KB) - added by aldrin@… 22 months ago.
1st part of the exported configuration of our production server
exported config of original zentyal master ldap server.zip.002 Download (107.0 KB) - added by aldrin@… 22 months ago.
2nd part of the exported configuration of our production server
exported config of original zentyal master ldap server.zip.003 Download (52.6 KB) - added by aldrin@… 22 months ago.
3rd part of the exported configuration of our production server

Change History

Changed 22 months ago by anonymous

Changed 22 months ago by aldrin@…

the un-edited exported config file of new master zentyal server

comment:1 Changed 22 months ago by aldrin@…

  • Keywords migrate, migration, migrate users, ldap added
  • Severity changed from normal to blocker

Basically, what I'm doing is migrating users & groups from one Zentyal server (w/ multiple enabled modules) to a Zentyal server w/ LDAP only.

I need a way on how to easily do this without using scripting. The steps as described here,  http://trac.zentyal.org/wiki/Documentation/Community/HowTo/MigrateUsers, are unclear & incomplete (e.g. see step 3).

Using 2 test zentyal master ldap servers, I was able to migrate users w/ no problems by simply copying & pasting users.bak folder from one exported configuration file to another. However, I'm unable to do this w/ our current zentyal ldap production server.

Changed 22 months ago by aldrin@…

1st part of the exported configuration of our production server

Changed 22 months ago by aldrin@…

2nd part of the exported configuration of our production server

Changed 22 months ago by aldrin@…

3rd part of the exported configuration of our production server

comment:2 Changed 22 months ago by aldrin@…

The 3-part zip file of the exported configuration file is the file from our Zentyal production server. It can be extracted using 7-zip.

comment:3 Changed 22 months ago by aldrin@…

  • Status changed from new to closed
  • Resolution set to fixed

I've resolved my problem.

Steps:

  1. Updated our production server's core Zentyal files from 2.0.21 to 2.0.22.
  2. Exported config of production server.
  3. Changed users.bak of exported config file of test LDAP master server to users.bak of exported config of production server.
  4. Imported the edited config file to test LDAP master server.
View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.