Sync after replica restarted...

Karl Pielorz kpielorz_lst at tdx.co.uk
Wed Jul 17 05:55:28 EDT 2013


Hi,

We have our pair of 2.4.17 servers running quite nicely. I had to re-start 
the replica server this morning, and the master has this logged:

"
Jul 17 10:36:17 sync_client[33213]: COMPRESS received NO response: 
Compression already active: DEFLATE
Jul 17 10:36:17 sync_client[33213]: Failed to enable compression, 
continuing uncompressed
Jul 17 10:37:39 sync_client[33213]: Error in do_sync(): bailing out! Bad 
protocol
Jul 17 10:37:39 sync_client[33213]: Processing sync log file 
/vol/hamster/imap/sync/log-33213 failed: Bad protocol
"

Ok, that's probably because the replica was restarting. However now it's 
restarted - the master doesn't seem to be pushing any more data to the 
replica :(

In the 'sync' directory I have an ever growing 'log' file - and 'log-33213' 
(which I presume is what was in use by the process that failed - i.e. that 
matches the PID above).

How do I restart replication?

In cyrus.conf I have:

"
...
syncclient    cmd="/usr/local/cyrus/bin/sync_client -r"
...
"

Can I just do:

"
su cyrus
/usr/local/cyrus/bin/sync_client -r
"

To restart that process? - It's not listed in 'ps ax | grep sync_client'.

Thanks,

-Karl



More information about the Cyrus-devel mailing list