On 12/15/11 11:14 PM, Howard Chu wrote:
A fix for this is in git master, please test.
Built and deployed, I've allowed to run for 72h and problem has yet to
show. I believe this particular bug has been squashed.
hume...@bofh.ca wrote:
I have reproduced the problem on 2.4.27. The mentioned ldapsearch query
seems to have a high probability of success if run immediately after
server start, which also seems true on 2.4.28.
I threw in an extra Debug() line and op-op_protocol == 2 at the check.
I'm
I have reproduced the problem on 2.4.27. The mentioned ldapsearch query
seems to have a high probability of success if run immediately after
server start, which also seems true on 2.4.28.
I threw in an extra Debug() line and op-op_protocol == 2 at the check.
I'm rebuilding with as many
Full_Name: Brandon Hume
Version: 2.4.28
OS: RHEL EL6.1, kernel 2.6.32-131.12.1.el6.x86_64
URL: http://den.bofh.ca/~hume/ol_v3_fail_syslog.txt
Submission from: (NULL) (2001:410:a010:2:223:aeff:fe74:400e)
OpenLDAP 2.4.28 compiled with BerkeleyDB 5.2.36, attempting to configure for
multi-master
hume...@bofh.ca wrote:
Full_Name: Brandon Hume
Version: 2.4.28
OS: RHEL EL6.1, kernel 2.6.32-131.12.1.el6.x86_64
URL: http://den.bofh.ca/~hume/ol_v3_fail_syslog.txt
Submission from: (NULL) (2001:410:a010:2:223:aeff:fe74:400e)
OpenLDAP 2.4.28 compiled with BerkeleyDB 5.2.36, attempting to
