Re: initialization issue

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thank you.  I looked at the ticket and this was definitely me last night -

"Yes, that's true... My concern is when I was debugging this bug and bulk
import failed, the consumer's DB is completely wiped out and any attempt
to recover the db was quite tricky and painful"  :)

I ran into another issue last night as well.  When I tried to use my
backup to restore using the 389-console GUI 'restore directory server', it
restored the files to the wrong place - rather than put the db files under
db/NetscapeRoot and db/userRoot, they all landed in db.  Any ideas on how
that happened?  I was able to move them all into their proper places and
then everything started up, but I've never had that happen before.

Elizabeth


> 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@xxxxxxxxxxxxxxxxxxxxxxx
>> https://admin.fedoraproject.org/mailman/listinfo/389-users
>
> --
> 389 users mailing list
> 389-users@xxxxxxxxxxxxxxxxxxxxxxx
> https://admin.fedoraproject.org/mailman/listinfo/389-users


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





[Index of Archives]     [Fedora User Discussion]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Yosemite Photos]     [Linux Apps]     [Maemo Users]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux