I took your advice and looked up the versions of 389-ds-base.
On the servers we are having problems with, they are running version 1.3.6.1-19 and the servers replicating to them are running an older version of 389-ds-base: 1.3.5.10-21.
Would this cause the service to go awry if they are not all on the same version?
Paul M. Whitney
E-mail: paul.whitney@xxxxxxx
Sent from my browser.
E-mail: paul.whitney@xxxxxxx
Sent from my browser.
On Oct 19, 2017, at 12:45 PM, Marc Sauton <msauton@xxxxxxxxxx> wrote:
Those 2 methods should work fine, and are the right way to proceed, but you may need to review the exact errors on why the re-init and import failed.Also check for the 389-ds-base versions on each node.M.On Thu, Oct 19, 2017 at 10:03 AM, Paul Whitney <paul.whitney@xxxxxxx> wrote:Hi, not sure what happened to our DS server, but I need to clone the userRoot and groupRoot database from a working server to this one bad one. What is the preferred/recommended method for this:I tried simple reinit, that failed.I tried export/import from LDIF file and that failed.Will db2bak then bak2db work?Thanks,
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
