1

Topic: LDAP error while Migrating to new version

==== Required information ====
- iRedMail version (check /etc/iredmail-release): 0.8.1
- Linux/BSD distribution name and version: RHEL 5.6
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): LDAP
- Web server (Apache or Nginx):Apache
- Manage mail accounts with iRedAdmin-Pro? No
- Related log if you're reporting an issue:
====

I'm trying to migrate from the existing iRedmail version to new one. I'm following the exact steps mentioned in the migration document (http://iredmail.org/docs/backup.restore.html) for backup and restoration of LDAP accounts. However, while trying to restore in the new box I'm getting the below error..

str2entry: entry -1 has no dn
slapadd: could not parse entry (line=1)

Below are the first few lines of backup.ldif

dn: dc=xxxx,dc=xx
dc: xxxx
o: xxxx
objectClass: dcObject
objectClass: organization
objectClass: top
structuralObjectClass: organization
entryUUID: 9c8d6234-asdb-1032-86aa-0asd1dd508565
creatorsName: cn=Manager,dc=xxxx,dc=xx
createTimestamp: 20130210144051Z
entryCSN: 20130210144051Z#000000#00#000000
modifiersName: cn=Manager,dc=xxxx,dc=xx
modifyTimestamp: 20130210144051Z

The server info is as below.. The iRedmail version and OS are the only changes with better hardware support...

==== Required information ====
- iRedMail version (check /etc/iredmail-release): 0.9.4
- Linux/BSD distribution name and version: CentOS 6.5
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): LDAP
- Web server (Apache or Nginx):Apache
-----------------------------------------------------------------------------------------

Please help me to resolve the issue

--Divakar

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: LDAP error while Migrating to new version

What's the "suffix" setting in /etc/openldap/slapd.conf on both old and new servers?

3

Re: LDAP error while Migrating to new version

Hi,
Seems there was a mistake in editing the backup LDIF file. Took a fresh backup and used 'sed' for changes and restored successfully..
Thank You..