[389-users] initialization issue
Noriko Hosoi
nhosoi at redhat.com
Thu Apr 17 16:50:30 UTC 2014
We fixed a bug 4 months ago. Unfortunately, the fix is in
389-ds-base-1.3.1 and newer.
Ticket #47606 <https://fedorahosted.org/389/ticket/47606> - replica
init/bulk import errors should be more verbose
One of the common issues is nsslapd-maxbersize. The default value is
2MB. If your supplier database contains a larger entry, the consumer
initialization fails. You could increase the size in the consumers'
config file.
Thanks,
--noriko
Elizabeth Jones wrote:
> We upgraded our servers to 389-ds-base-1.2.11.25-1.el6.x86_64 a couple of
> months ago, and earlier this evening I tried to initialize a corrupted
> replica but it did not initialize successfully. I was using the
> 389-console gui, not sure if that makes any difference. My logs showed
> that the initialization had been successful, but my replica had no data in
> it. Everything had been erased, as expected, but nothing was imported.
> I've done this type of initialize many times in the past and this has
> never happened. Does anyone have any thoughts on why my replica did not
> initialize?
>
> thanks,
>
> EJ
>
>
> --
> 389 users mailing list
> 389-users at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/389-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/389-users/attachments/20140417/15e25322/attachment.html>
More information about the 389-users
mailing list