Thanks Noriko.

I need to get an confirmation, but I am pretty sure that there are no quotes or backslashes in the DN. Having said that, the directory should be fine, right?

How is this bug you mentioned triggered? I am curious, because I have never seen this before.

One more question: Since the upgradednformat failed, the database was not indexed during the upgrade. Is this is a problem?

-Reinhard

From: 389-users-bounces@lists.fedoraproject.org [mailto:389-users-bounces@lists.fedoraproject.org] On Behalf Of Noriko Hosoi
Sent: Tuesday, September 27, 2011 2:13 PM
To: General discussion list for the 389 Directory server project.
Subject: Re: [389-users] Quick Upgrade question

You might have hit an upgradednformat bug; "upgradednformat failed to add RDN value", which was fixed in 1.2.9.

Unless your old DB contains old format DNs, there is no impact there. Do you see double quotes and/or backslashes in your DN strings?

--noriko

Reinhard Nappert wrote:

Hi,

I was wondering if the following was observed somewhere else.

I am upgrading 1.1.2 to 1.2.8.3 and I see the following message, when the upgrade of the dn is done:

[27/Sep/2011:07:57:22 +0000] - upgradedn NetscapeRoot: Index buffering is disabled./lib/dirsrv/slapd-ds/upgradednformat: line 59: 9661 Terminated ./ns-slapd upgradednformat -D /etc/dirsrv/slapd-ds -a $dir -n $be -N

This happened for all of my databases.

The server is up and running, but I was wondering what kind of impact this could have. More importantly, any idea why this happened.

Thanks,

-Reinhard
--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users