https://bugs.openldap.org/show_bug.cgi?id=9932
Issue ID: 9932
Summary: Sync failing between two LDAP servers
Product: OpenLDAP
Version: 2.4.58
Hardware: x86_64
OS: Linux
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: shikhar81(a)gmail.com
Target Milestone: ---
Hi Team,
We have noticed a sync issue in our environment.
We have two production servers namely A and B and two DR servers namely C and
D.
A and B are in bi-directional sync
A and C are in bi-directional sync
B and D are in bi-directional sync
Since the last few days the sync between A and C and B and D has broken and we
are unable to see any concrete error in logs
Just to add here that server A and server B are in the same subnet and server C
& server D are in a different subnet. However, this setup has been working fine
since the last many years with no issues at all.
Since the last few days the connection has broken as mentioned earlier.
Now we also tried to initiate a sync between C and D (DR servers) which are in
the same subnet. But still it is not syncing and we get a "no connection" error
message in the logs after trying for 2-3 hrs.
Can you please suggest what can be done here.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9928
Issue ID: 9928
Summary: ldap_search_ext_s always hangs on 2.6.3
Product: OpenLDAP
Version: 2.6.3
Hardware: All
OS: Mac OS
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: libraries
Assignee: bugs(a)openldap.org
Reporter: filipe.custodio(a)gmail.com
Target Milestone: ---
Created attachment 920
--> https://bugs.openldap.org/attachment.cgi?id=920&action=edit
Minimal AD query that consistently hangs on ldap_search_ext_s call
Dear Experts,
When using ldap_search_ext_s() from libldap v2.6.3 to do a simple search on our
production Windows Domain Controller, the client consistently hangs forever.
Using ldap_search_ext() & ldap_result() also hangs after delivering the first
information item. It seems the client is left waiting, not realising no more
results are coming from the server.
Using the development image from Oct. 9 2022, the ldap_search_ext_s() call
works, although it gives an "Operations Error".
Shall I deploy the new libldap from the development branch in our production
environment to solve this problem or is there another way around the issue?
Best regards,
Filipe Custódio
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9919
Issue ID: 9919
Summary: The use of a separate section for cold code can cause
linking issues on macOS
Product: LMDB
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: liblmdb
Assignee: bugs(a)openldap.org
Reporter: mh-bcrayqnc(a)glandium.org
Target Milestone: ---
See e.g. https://github.com/llvm/llvm-project/issues/52767
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9365
Issue ID: 9365
Summary: Mem leaks with Æ-DIR providers
Product: OpenLDAP
Version: 2.4.53
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: michael(a)stroeder.com
Target Milestone: ---
Created attachment 772
--> https://bugs.openldap.org/attachment.cgi?id=772&action=edit
valgrind output on openSUSE Tumbleweed x86_64
An Æ-DIR installation with self-compiled OpenLDAP 2.4.53 on Debian (now
buster) has memory leak issues on the Æ-DIR providers. The read-only
consumers do not have this issue. The provider config is more complex
with more overlays and more ACLs.
In this production deployment slapd is automatically restarted (by monit) when
memory consumption reaches 80%. Thus monitoring clearly shows a frequent saw
tooth pattern.
I've also tested on openSUSE Tumbleweed x86_64 with a RE24 build [1] by running
slapd under control of valgrind for a couple of minutes continously sending
simple bind operations (additional to the monitoring and other back-ground jobs
running).
Find valgrind output of my first attempt attached.
Does that make sense at all?
--
You are receiving this mail because:
You are on the CC list for the issue.