If sync_client cannot contact the replica server (or if there is some
other error that it can't recover from) then it 'bails out' and stops
running.
I guess the idea being that sync_client can't do aynthing until you fix
the problem.
We run monitoring software that lets us know if sync_client dies, and
attempts to restart it for us.
-Patrick
On Tue, 20 Dec 2005, Patrice wrote:
Hi,
yesterday evening my replication was working on my test system.
I unplugged network and came back today , plugged it again.
I tried to send an email but this one wasn't replicated on the replica. (I
waited a few minutes and my sync_repeat_interval is 60)
I made a "ps aux" and saw that the 2 processes sync_client where not existing
that was the cause of no replication.
my authentication is made via saslauthd on another server on openldap
if authentication cannot be made, it seems that sync_client die
I launched by hand:
su - cyrus -c "/cyrus-imap/bin/sync_client -r"
--> sync ok
and now 2 processes sync_client now are running.
here is my config for replication:
sync_host: 192.168.1.2
sync_authname: cyrus
sync_password: xxxxxxxxxx
sync_machineid: 1
sync_log: yes
sync_repeat_interval: 60
and ideas about this behavior ?
thanks in advance
Patrice
----
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
----
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
