On 05/05/2014 12:13 PM, Graham Leggett wrote:
On 05 May 2014, at 5:41 PM, Rich Megginson
<rmeggins(a)redhat.com> wrote:
>>> See
https://fedorahosted.org/389/ticket/47606
>> This bug looks quite consistent with the OP's symptoms and the presence of a
large group entry, but he should be seeing "Incoming BER Element was too long"
in the consumer log (don't think I saw that in any of the log snippets posted..).
> The consumer access log should have a closed - B2 message if this is the problem.
All three servers have what seems to be unlimited bersize values:
nsslapd-maxbersize: 0
0 tells the server to use the default value of 2mb, you need
to set it
higher(5mb?).
https://access.redhat.com/site/documentation/en-US/Red_Hat_Directory_Serv...
(search for maxber)
I am at a loss as to what exactly is triggering this, what I do know is:
- Any attempt by the supplier servera to initialize the serverc supplier results in
complete destruction of any existing data in serverc.
- The point at which the initilization dies is six seconds after an attempt is made to
synchronize a group containing 21000 uniqueMembers over a slower link than servera and
serverb.
- Attempts to synchronise serverc using a manual export of ldif from servera makes no
difference, the servers refuse to sync with one another. Has this been recently confirmed
to work?
Regards,
Graham
--
--
389 users mailing list
389-users(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users