Replication failed 3.0.5 -> 3.0.13, now 3.0.13->3.0.13
Olaf Frączyk
olaf at navi.pl
Tue Apr 21 05:18:39 EDT 2020
I also found out that when I see on master:
Apr 21 11:12:38 ifs sync_client[27996]: IOERROR: zero length response to
MAILBOXES (idle for too long)
Apr 21 11:12:38 ifs sync_client[27996]: IOERROR: zero length response to
RESTART (idle for too long)
Apr 21 11:12:38 ifs sync_client[27996]: Error in do_sync(): bailing out!
Bad protocol
Apr 21 11:12:38 ifs sync_client[27996]: Processing sync log file
/var/lib/imap/sync/log-run failed: Bad protocol
I also get on the replica:
Apr 21 11:12:38 skink1 imap[5775]: Connection reset by peer, closing
connection
But I also see, that before it happens, there is no activity both on the
replica and on the master for some time.
So maybe the imap server process is not recovering correctly in the
longlock situation?
On 2020-04-21 11:07, Olaf Frączyk wrote:
> Hi,
>
> When I run sync_client -r on the master I see the following on the
> replica:
>
> Apr 21 10:56:15 skink1 imap[5775]: mailbox: longlock navi.pl!user.olaf
> for 1.7 seconds
> Apr 21 10:56:20 skink1 imap[5775]: mailbox: longlock
> navi.pl!user.piotr for 2.0 seconds
> Apr 21 10:56:23 skink1 imap[5775]: mailbox: longlock navi.pl!user.olaf
> for 2.9 seconds
> Apr 21 10:56:26 skink1 imap[5775]: mailbox: longlock
> navi.pl!user.piotr for 3.0 seconds
>
> The mailboxes have several GB in Inbox folder and several GB in
> subfolders. The inbox folders have about 20,000 messages, the
> subfolders upto 15,000
>
> Could it cause problems?
>
> Maybe I should move the sync_client from START section to SERVICES, it
> seems that it is not automatically restarted
>
> On 2020-04-21 08:47, Michael Menge wrote:
>> Hi Olaf
>>
>>
>> Quoting Olaf Frączyk <olaf at navi.pl>:
>>
>>> Hi,
>>>
>>> I upgraded to 3.0.13 but it didn't help.
>>>
>>> This time it copied about 18GB
>>>
>>> in the logs I still see:
>>>
>>> 1 - inefficient replication
>>>
>>> 2 - IOERROR: zero length response to MAILBOXES (idle for too long)
>>> IOERROR: zero length response to RESTART (idle for too long)
>>> Error in do_sync(): bailing out! Bad protocol
>>>
>>> But I have no idea what can I do next and why it fails
>>>
>>> Apr 21 02:24:46 ifs sync_client[12656]: IOERROR: zero length
>>> response to MAILBOXES (idle for too long)
>>> Apr 21 02:24:46 ifs sync_client[12656]: IOERROR: zero length
>>> response to RESTART (idle for too long)
>>> Apr 21 02:24:46 ifs sync_client[12656]: Error in do_sync(): bailing
>>> out! Bad protocol
>>
>> do you see any errors on the syncserver side. The error look like the
>> sync_client is waiting for a reply of the server.
>>
>>
>>
>>
>>
>> --------------------------------------------------------------------------------
>>
>> M.Menge Tel.: (49) 7071/29-70316
>> Universität Tübingen Fax.: (49) 7071/29-5912
>> Zentrum für Datenverarbeitung mail:
>> michael.menge at zdv.uni-tuebingen.de
>> Wächterstraße 76
>> 72074 Tübingen
>>
>> ----
>> Cyrus Home Page: http://www.cyrusimap.org/
>> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
>> To Unsubscribe:
>> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
> ----
> Cyrus Home Page: http://www.cyrusimap.org/
> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
> To Unsubscribe:
> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
More information about the Info-cyrus
mailing list