so there is a crash, but not a lot of information, a core file and a stack
trace would be needed to get more details, so I will direct to this doc:
http://www.port389.org/docs/389ds/FAQ/faq.html#debugging-crashes
also try to check for anything unexpected in the LDIF file.
also try to verify the cac
We have multiple failed attempts to reinit the directory (groupRoot). It seems
that the servers that were upgraded to 1.3.6.1-19 are failing on reinit from
servers running 1.3.5.10-21.
About half way through the groupRoot import using the ldif2db commmand (service
already stopped), we got th
What were the exact errors when the re-init and off-line import failed?
Thanks,
M.
On Fri, Oct 20, 2017 at 11:11 AM, Paul Whitney wrote:
> 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 s
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 al
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 wrote:
> Hi, not sure what happened to our
