https://bugzilla.redhat.com/show_bug.cgi?id=770705
Upgrade 389-ds-base from 1.2.2-1.el5 to 1.2.9.9-1.el5. The server refuses to start, the error log complains: [28/Dec/2011:06:24:16 -0600] - nsslapd-subtree-rename-switch is on, while the in stance userRoot is in the DN format. Please run dn2rdn to convert the database format. [28/Dec/2011:06:24:16 -0600] - nsslapd-subtree-rename-switch is on, while the instance NetscapeRoot is in the DN format. Please run dn2rdn to convert the databa se format.[28/Dec/2011:06:24:16 -0600] - start: Failed to start databases, err=-1 Unknown error: -1[28/Dec/2011:06:24:16 -0600] - Failed to start database plugin ldbm database[28/Dec/2011:06:24:16 -0600] - WARNING: ldbm instance userRoot already exists [28/Dec/2011:06:24:16 -0600] - WARNING: ldbm instance NetscapeRoot already exists Discover that dn2rdn is called from setup-ds.pl, so we run "setup-ds.pl -u". No idea why the RPM postinstall script doesn't "do the right thing". We run "setup-ds.pl -u" and it emits thousands of warnings, one for each entry in the database: [28/Dec/2011:06:37:16 -0600] - userRoot: WARNING: skipping an entry with a corrupted dn (syntax value): zzz0107A (id 63863) [28/Dec/2011:06:37:16 -0600] - userRoot: WARNING: skipping an entry with a corrupted dn (syntax value): zzz MS E (id 63864) [28/Dec/2011:06:37:16 -0600] - userRoot: WARNING: skipping an entry with a corrupted dn (syntax value): zzz0111A (id 63865) [28/Dec/2011:06:37:16 -0600] - userRoot: WARNING: skipping an entry with a corrupted dn (syntax value): zzz DR I (id 63866) At the end up the upgrade process, the database is completely empty, all data has been destroyed. The message "skipping an entry with a corrupted dn (syntax value)" is too vague to be useful - it doesn't say what DN, it doesn't say what syntax value, so I'm in the dark as what action to take.
batch update to FUTURE milestone
Added initial screened field value.
Metadata Update from @rmeggins: - Issue set to the milestone: N/A
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/5
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Invalid)
Login to comment on this ticket.