Hi Quanah,
Understood. Unfortunately, we are experiencing the issue. Here is my configuration.
*On Master:* database mdb suffix "dc=georgetown,dc=edu" . dbnosync FALSE checkpoint 128 5 maxsize 108993459200
# Replication overlay syncprov syncprov-checkpoint 10 5 syncprov-sessionlog 100
*On the Replica:* syncrepl rid=132 provider=ldaps://aaa-master-1.uis.georgetown.edu:636/ type=refreshAndPersist keepalive=300:5:5 retry="5 5 300 +"
How do we go about fixing this?
Thanks, Suresh
On Fri, Jan 17, 2025 at 2:30 PM Quanah Gibson-Mount quanah@fast-mail.org wrote:
--On Friday, January 17, 2025 10:51 AM -0700 Thomas Pritchard pritchardtw@gmail.com wrote:
I have not experienced the master crashing but I have also experienced stalled replication regularly over the last 2 years. We've been on 2.46 and have keep alive enabled. We were hoping an upgrade would resolve the problem but it seems to exist on latest versions as well. I am also on aws ec2 instances.
I've been running OpenLDAP in AWS on EC2 instances for the last 3 years at two different companies, and have never encountered this behavior.
--Quanah
--On Friday, January 17, 2025 2:45 PM -0500 Suresh Veliveli Suresh.Veliveli@georgetown.edu wrote:
Hi Quanah,
Understood. Unfortunately, we are experiencing the issue. Here is my configuration.
On Master: database mdb suffix "dc=georgetown,dc=edu" . dbnosync FALSE checkpoint 128 5 maxsize 108993459200
# Replication overlay syncprov syncprov-checkpoint 10 5 syncprov-sessionlog 100
On the Replica: syncrepl rid=132 provider=ldaps://aaa-master-1.uis.georgetown.edu:636/ type=refreshAndPersist
keepalive=300:5:5 retry="5 5 300 +"
How do we go about fixing this?
Looks like you're using the deprecated slapd.conf files, which can have interesting issues because they may not properly order directives. Without the full slapd.conf for both provider and consumer (minus sensitive data like passwords), there's not a lot for me to go off of here.
--Quanah
openldap-technical@openldap.org
-
Quanah Gibson-Mount -
Suresh Veliveli