On 03/18/2013 11:39 AM, Roberto Polli wrote:
Hi all,
while upgrading with yum from 1.2.2 to 1.2.10, 389 hang while in ns-slapd
upgradedb.
gdb says it's in ldbm_ancestorid_create_index(), but it's running from
3hrs on
an almost-empty database (there are just a few test entries).
Can somebody shed some light on that?
I don't know. We never tested upgrade from 1.2.2 directly to 1.2.10.
Looks like you might need to do a manual db upgrade procedure, even
though you should not be affected by the subtree rename conditions, as in
http://port389.org/wiki/Subtree_Rename#warning:_upgrade_from_389_v1.2.6_.28a.3F.2C_rc1_.7E_rc6.29_to_v1.2.6_rc6_or_newer
Thank you very much + Peace,
R.
--
Roberto Polli
Community Manager
Babel S.r.l. - http://www.babel.it
T: +39.06.9826.9651 M: +39.340.652.2736 F: +39.06.9826.9680
P.zza S.Benedetto da Norcia, 33 - 00040 Pomezia (Roma)
CONFIDENZIALE: Questo messaggio ed i suoi allegati sono di carattere
confidenziale per i destinatari in indirizzo.
E' vietato l'inoltro non autorizzato a destinatari diversi da quelli
indicati
nel messaggio originale.
Se ricevuto per errore, l'uso del contenuto e' proibito; si prega di
comunicarlo al mittente e cancellarlo immediatamente.
--
389 users mailing list
389-us...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
--
389 users mailing list
389-us...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
