Hi,
I have 3 local servers and 1 remote server. All servers are configured for Mirror mode replications. Every night replication stops on the remote server. Once I delete the database on the remote, start services replication works fine, the next morning I have to go through the same process. The remote server is a VM image of one of the local servers. They hosing company changed the host name, IP address and allowed communication via a VPN tunnel between them and us.
These is my replication entry in slapd.conf
#mirrormode TRUE mirrormode on # define the provider to use the syncprov overlay # (last directives in database section)
syncrepl rid=006 provider=ldap://192.168.60.42 tls_cert=/etc/pki/tls/certs/ldap-tls.curry.edu.cert.pem tls_key=/etc/pki/tls/private/ldap-tls.curry.edu.key.pem tls_cacert=/etc/pki/tls/certs/cacert.pem tls_reqcert=demand searchbase="dc=curry,dc=edu" schemachecking=on timelimit=unlimited sizelimit=unlimited type=refreshAndPersist retry="60 +"
Thanks
--On Wednesday, August 21, 2013 2:27 PM -0400 "Darouichi, Aziz" adarouic@post03.curry.edu wrote:
Hi,
I have 3 local servers and 1 remote server. All servers are configured for Mirror mode replications. Every night replication stops on the remote server. Once I delete the database on the remote, start services replication works fine, the next morning I have to go through the same process. The remote server is a VM image of one of the local servers. They hosing company changed the host name, IP address and allowed communication via a VPN tunnel between them and us.
OpenLDAP version?
I would also suggest you set TCP timeouts in the syncrpel configs, assuming linux:
keepalive=240:10:30
is what I use.
--Quanah
--
Quanah Gibson-Mount Lead Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
--On Wednesday, August 21, 2013 11:49 AM -0700 Quanah Gibson-Mount quanah@zimbra.com wrote:
I would also suggest you set TCP timeouts in the syncrpel configs, assuming linux:
keepalive=240:10:30
TCP keepalive even. ;)
--Quanah
--
Quanah Gibson-Mount Lead Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
Yes , Linux RHEL 5_3 and openldap-2.4.33
-----Original Message----- From: Quanah Gibson-Mount [mailto:quanah@zimbra.com] Sent: Wednesday, August 21, 2013 2:50 PM To: Darouichi, Aziz; openldap-technical@openldap.org Subject: Re: Mirrormode replication
--On Wednesday, August 21, 2013 2:27 PM -0400 "Darouichi, Aziz" adarouic@post03.curry.edu wrote:
Hi,
I have 3 local servers and 1 remote server. All servers are configured for Mirror mode replications. Every night replication stops on the remote server. Once I delete the database on the remote, start services replication works fine, the next morning I have to go through the same process. The remote server is a VM image of one of the local servers. They hosing company changed the host name, IP address and allowed communication via a VPN tunnel between them and us.
OpenLDAP version?
I would also suggest you set TCP timeouts in the syncrpel configs, assuming linux:
keepalive=240:10:30
is what I use.
--Quanah
--
Quanah Gibson-Mount Lead Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
--On Wednesday, August 21, 2013 2:53 PM -0400 "Darouichi, Aziz" adarouic@post03.curry.edu wrote:
Yes , Linux RHEL 5_3 and openldap-2.4.33
So add a keepalive to your syncrepl statement. You may also wish to upgrade, given there were fixes for MMR in 2.4.34. May as well jump to 2.4.36. ;)
--Quanah
--
Quanah Gibson-Mount Lead Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
I added keepalive to syncrepl and will monitor tomorrow.
Thank you -----Original Message----- From: Quanah Gibson-Mount [mailto:quanah@zimbra.com] Sent: Wednesday, August 21, 2013 2:57 PM To: Darouichi, Aziz; openldap-technical@openldap.org Subject: RE: Mirrormode replication
--On Wednesday, August 21, 2013 2:53 PM -0400 "Darouichi, Aziz" adarouic@post03.curry.edu wrote:
Yes , Linux RHEL 5_3 and openldap-2.4.33
So add a keepalive to your syncrepl statement. You may also wish to upgrade, given there were fixes for MMR in 2.4.34. May as well jump to 2.4.36. ;)
--Quanah
--
Quanah Gibson-Mount Lead Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
Thanks for the tip, so far replication has not aborted within last 24 hours after the change.
-----Original Message----- From: Quanah Gibson-Mount [mailto:quanah@zimbra.com] Sent: Wednesday, August 21, 2013 2:57 PM To: Darouichi, Aziz; openldap-technical@openldap.org Subject: RE: Mirrormode replication
--On Wednesday, August 21, 2013 2:53 PM -0400 "Darouichi, Aziz" adarouic@post03.curry.edu wrote:
Yes , Linux RHEL 5_3 and openldap-2.4.33
So add a keepalive to your syncrepl statement. You may also wish to upgrade, given there were fixes for MMR in 2.4.34. May as well jump to 2.4.36. ;)
--Quanah
--
Quanah Gibson-Mount Lead Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
openldap-technical@openldap.org