Sync after replica restarted...
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: ... syncclientcmd=/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
Re: Plugin loading in libsasl
On Wed, Jul 17, 2013 at 1:02 PM, Alexey Melnikov alexey.melni...@isode.comwrote: On 16/07/2013 14:23, Ondřej Surý wrote: Hi, Hi Ondřej, I have realized one quite serious problem in plugin loading with recent SONAME bump. The plugins are versioned, but the library ignores that and looks for .so files in the plugins directory. This basically prevents the gradual transitioning from one SONAME to another, since at one point in time you have to replace the plugins with one version or another. I would propose to change the mechanism to look for: .so.SONAME How can libsasl library know expected SONAME information? I expect that one should be able to compute it at compile time from the info passed to libtool. O. -- Ondřej Surý ond...@sury.org
Jenkins build is back to normal : cyrus-imapd-master #1342
See http://ci.cyrusimap.org/job/cyrus-imapd-master/1342/
Re: Sync after replica restarted...
Quoting Karl Pielorz kpielorz_...@tdx.co.uk: 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: ... syncclientcmd=/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'. Bevor you run sync_client -r you should run sync_client -r -f /PATH_TO_SYNC_DIR/log-33213 to sync what was left form the old sync process and confirm that the exit code is 0 (echo $?) than you can delete log-33213 The Sync_client will catch up if you miss syncing log-33213, but it can lead to some errors if sync_client tries to sync some mailboxes that have not been created on the replic. Regards Michael M.MengeTel.: (49) 7071/29-70316 Universität Tübingen Fax.: (49) 7071/29-5912 Zentrum für Datenverarbeitung mail: michael.me...@zdv.uni-tuebingen.de Wächterstraße 76 72074 Tübingen
