On 2020-04-29 16:47, Andrzej Kwiatkowski wrote:
Ok.
I was asking because of problem with low entropy on VM-s causing
performance issues with big installations.
I didn't have this issue, however as I said, my installation is really
small. If I needed more entropy I would think of using a hardw
W dniu 22.04.2020 o 10:19, Olaf Frączyk pisze:
> On 2020-04-22 09:16, Andrzej Kwiatkowski wrote:
>> W dniu 20.04.2020 o 16:11, Olaf Frączyk pisze:
>>> Hi,
>>>
>>> I'm running 3.0.5.
>>>
>>> I want to migrate to a new machine. I set up cyrus-imapd 3.0.13.
>>>
>>> The replication started but it didn'
On 2020-04-22 09:16, Andrzej Kwiatkowski wrote:
W dniu 20.04.2020 o 16:11, Olaf Frączyk pisze:
Hi,
I'm running 3.0.5.
I want to migrate to a new machine. I set up cyrus-imapd 3.0.13.
The replication started but it didn't transfer all mails.
The store isn't big 44GB, transferred was about 24
Yes, Michael was right - it works properly now. (I hope ;).
OK. I'll put it in the DAEMON section - this way I have only one point
where all stuff related to imap is started.
Thank you for explanation. Regards,
Olaf
On 2020-04-22 02:36, ellie timoney wrote:
I think Michael's got this pretty
On 2020-04-21 20:40, Michael Menge wrote:
Quoting Olaf Frączyk :
Yes, at the beginning I was also thinking if initial sync is
necessary, but there was nothing in docs about it, something started
replicating and I simply assumed it does initial resync. I'll try it
this evening. :)
Since y
W dniu 20.04.2020 o 16:11, Olaf Frączyk pisze:
> Hi,
>
> I'm running 3.0.5.
>
> I want to migrate to a new machine. I set up cyrus-imapd 3.0.13.
>
> The replication started but it didn't transfer all mails.
>
> The store isn't big 44GB, transferred was about 24 GB.
>
> In the logs I see:
>
Ol
I think Michael's got this pretty much covered -- you need to disable the
rolling replication for now, and then use sync_client -u (or if you're brave,
sync_client -A) to get an initial sync of everything. These two options work
entire-user-at-a-time, so they should detect and fix the problems
Quoting Olaf Frączyk :
Yes, at the beginning I was also thinking if initial sync is
necessary, but there was nothing in docs about it, something started
replicating and I simply assumed it does initial resync. I'll try it
this evening. :)
Since you use replication - are sieve scripts r
On 2020-04-21 16:00, Michael Menge wrote:
Hi,
Quoting Olaf Frączyk :
I managed to get strace on both sides, however it doesn't make me
wiser - there is nothing obvious for me.
Additionally I see that replication works more or less for new
messages, but older are not processed.
I have sev
Hi,
Quoting Olaf Frączyk :
I managed to get strace on both sides, however it doesn't make me
wiser - there is nothing obvious for me.
Additionally I see that replication works more or less for new
messages, but older are not processed.
I have several subfolders in my mailbox, some of the
I managed to get strace on both sides, however it doesn't make me wiser
- there is nothing obvious for me.
Additionally I see that replication works more or less for new messages,
but older are not processed.
I have several subfolders in my mailbox, some of them unreplicated. If I
change any
Quoting Olaf Frączyk :
Thank you for the telemetry hint :)
I don't use the syncserver - the replication is done via IMAP port
on the replica side. I have no idea how to have strace spawned by
cyrus master process. When I attach later to imapd using strace -p
I'm afraid some info already
Thank you for the telemetry hint :)
I don't use the syncserver - the replication is done via IMAP port on
the replica side. I have no idea how to have strace spawned by cyrus
master process. When I attach later to imapd using strace -p I'm afraid
some info already will be lost.
The syncserve
Hi,
Quoting Olaf Frączyk :
The current situation is:
1. Replica:
stopped and started the replica
no activity on replica - iotop and top show nothing
the only messages on replica is incoming connection from master
2. Master:
when I run sync_client -r I still get:
Apr 21 12:38:36 ifs sync_
The current situation is:
1. Replica:
stopped and started the replica
no activity on replica - iotop and top show nothing
the only messages on replica is incoming connection from master
2. Master:
when I run sync_client -r I still get:
Apr 21 12:38:36 ifs sync_client[29518]: Reprocessing sy
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 i
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]: mail
Hi Olaf
Quoting Olaf Frączyk :
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)
E
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
Hi,
I'm running 3.0.5.
I want to migrate to a new machine. I set up cyrus-imapd 3.0.13.
The replication started but it didn't transfer all mails.
The store isn't big 44GB, transferred was about 24 GB.
In the logs I see:
Apr 20 14:54:03 ifs sync_client[24239]: couldn't authenticate to backend
20 matches
Mail list logo
