similar to: replication hangs

Displaying 20 results from an estimated 8000 matches similar to: "replication hangs"

2014 Jan 25
1
Dsync Panic
Hi, Using dsync to backup my users' mailboxes (dovecot 2.2.10 on both sides), I sometimes encounter the following issue. Below is the output of: dsync -Dvf -u "user" -R backup ssh root at server.domain.tld dsync -u "user" doveadm(root): Debug: Loading modules from directory: /usr/local/lib/dovecot/doveadm doveadm(root): Debug: Skipping module doveadm_acl_plugin,
2013 Sep 25
1
still having dsync issues after upgrading to latest
Trying to migrate a bunch of users with mbox format to maildir format. dsync creates some directories, but otherwise does nothing. (Complained about the lack of "/" as separator until I added that to config, now is silent when running dsync except with the -D flag) I have tried dumping all the dovecot that came with my OS and built the latest sources, hoping I'd at least get a
2013 Nov 05
1
Problem migration from cyrus with imapc
Hi all, i have problem with namespace when i try to migrate from cyrus to dovecot with imapc. If i login to the old cyrus i get: telnet 192.168.8.164 143 Trying 192.168.8.164... Connected to 192.168.8.164. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot ready. a
2013 Feb 26
2
(no subject)
I've run into a problem with `doveadm backup` (2.2 rc2 and 20130226) I did not notice in 2.1.15 doveadm backup [-Dv] -R -u cyrtest1 at iai.uni-bonn.de -m INBOX imapc: => crashes (signal 6 with acl plugin configured, sig 11 without acl) If this is considered a bug (not just because of the crash but in the meaning of "my configuration should work") it would be great if it could be
2015 Feb 24
0
Dovecot 2.2.15, Panic: array.h: line 197 (array_idx_i): assertion failed: (idx * array->element_size < array->buffer->used)
Hi all Version: 2.2.15 OS: SLES11 SP3 x86_64 Problem with replication for some users: Log Server 1: Feb 24 09:29:42 v063ik dovecot: dsync-local(user at domain.com): Error: read(v063il.pnet.ch) failed: <no error> Log Server 2: Feb 24 09:29:42 v063il dovecot: dsync-server(user at domain.com): Panic: file ../../../src/lib/array.h: line 197 (array_idx_i): assertion failed: (idx *
2016 Dec 06
0
Panic: file dsync-mailbox-tree-sync.c: line 576 (node_mailbox_trees_cmp): assertion failed: (ret != 0)
Hi, Here is a crash that's happening using the latest Dovecot version (v2.2.27 on CentOS7 x86_64): We are using replication. Judging by the second server's logs, I believe this has something to do with the fact that we're using the lazy_expunge plugin. Every night after midnight, we purge the lazy_expunge namespace by running a command similar to following one on the main server
2013 Jan 17
1
dovecot nightly 20130117: dsync does returns "Name or service not known"
Hello. I have this settings of imapc: # doveconf -a | grep imapc imapc_features = imapc_host = imapc_list_prefix = imapc_master_user = imapc_max_idle_time = 29 mins imapc_password = imapc_port = 143 imapc_rawlog_dir = imapc_ssl = no imapc_ssl_ca_dir = imapc_ssl_verify = yes imapc_user = %u and try to sync mailbox on old server and new one: $ dsync -o imapc_user="user at example.org"
2015 Sep 03
0
Error: Raw backtrace: and Transaction log changed unexpectedly, can't get modseq
Hi there, i've got some errors in my log files # dovecot --version 2.2.9 Here the Log's:
2014 Dec 12
1
Dsync issues between Cyrus and Dovecot
Hello, I have some issues related with dsync when trying to perform two way synchronization between Cyrus and Dovecot. 1st time synchronization always works and email, folders, flags can be synced between these but once for example in dovecot side the user creates a folder, dsync fails with the following errors: Debug: brain M: Other brain should change mailbox INBOX/dove GUID
2014 May 08
1
Dsync via dovecot proxy
Hi All, I need to import mailboxes into my Director NFS setup via one of my director proxy's as doing a direct dsync to the backend mailstores appears to giving me NFS locking issues. It looks like it may be possible to do this using doveadm listeners. I have setup doveadm listeners on a test proxy and backend mailstore. I am not sure how to make the dsync proxy through to the backend
2015 Apr 20
4
doveadm-server hangs with 100% cpu usage
we have some replication issues. From time to time a doveadm-server process takes 100% cpu in the state recv_mailbox_tree_deletes on the replica. The process runs forever until it is manually killed. Strace on this process doesn't show anything. Sometimes we have several doveadm-server processes in this state, all for the same account, all with 100% CPU Load. The logfile on the master says:
2015 Feb 13
0
doveadm sync out of memory
On Feb 5, 2015, at 10:39 PM, Casey Stone <tcstone at caseystone.com> wrote: > Hello: > > I've been looking forward to getting my mail server up to Dovecot 2.2+ to be able to use the sync mechanism. I run my own mail server just for myself, with a few different accounts, and want to keep a master and backup server in sync. > > I'm running the Ubuntu server 14.04.1
2015 Feb 16
0
doveadm sync out of memory
On Feb 13, 2015, at 3:42 PM, FUSTE Emmanuel <emmanuel.fuste at thalesgroup.com> wrote: > Le 13/02/2015 16:19, Casey Stone a ?crit : >> On Feb 5, 2015, at 10:39 PM, Casey Stone <tcstone at caseystone.com> wrote: >> >>> Hello: >>> >>> I've been looking forward to getting my mail server up to Dovecot 2.2+ to be able to use the sync
2013 Apr 02
1
v2.2 getting NULL pointer reference with shared namespace in mailbox_tree?
> > With todays nightly: > > > > dsync(wsunpriv at iai.uni-bonn.de): Panic: file imapc-list.c: line 199 (imapc_list_get_vname): assertion failed: (strncmp(prefix, storage_name, prefix_len) == 0 && storage_name[prefix_len] == list->sep) > > Oh, and this would be good to solve too. What does it say with gdb: > > gdb dsync core > fr 5 > p prefix >
2015 Feb 13
2
doveadm sync out of memory
Le 13/02/2015 16:19, Casey Stone a ?crit : > On Feb 5, 2015, at 10:39 PM, Casey Stone <tcstone at caseystone.com> wrote: > >> Hello: >> >> I've been looking forward to getting my mail server up to Dovecot 2.2+ to be able to use the sync mechanism. I run my own mail server just for myself, with a few different accounts, and want to keep a master and backup server
2020 Feb 06
2
doveadm backup -R -m -s not picking up a new message
Good morning, I use ?doveadm backup -R -m foo -s $state? to create a local mirror of an imapc remote folder. When I run that command, wait for it to finish, deliver a new message to the remote folder, and run that command again, the new message does not get downloaded from the remote. I'll attach the rawlog, doveconf, etc at the end. Allow me first to summarize what I've already
2015 Feb 17
1
doveadm sync out of memory
Le 16/02/2015 20:40, Casey Stone a ?crit : > On Feb 13, 2015, at 3:42 PM, FUSTE Emmanuel <emmanuel.fuste at thalesgroup.com> wrote: > >> Le 13/02/2015 16:19, Casey Stone a ?crit : >>> On Feb 5, 2015, at 10:39 PM, Casey Stone <tcstone at caseystone.com> wrote: >>> >>>> Hello: >>>> >>>> I've been looking forward to
2019 Dec 06
0
[2.3.8] possible replication issue
Hello Timo, upgrading both replicators did the job! Both replicators now run v2.3.9 and replication works fine, all sync-jobs which queued up during the upgrading have been processed successfully. Thanks for the reassurement and all your great work with dovecot, Andreas Am 05.12.19 um 13:15 schrieb Timo Sirainen via dovecot: > I think there's a good chance that upgrading both will
2012 Jun 24
3
Mail migration to dovecot with doveadm backup
Hi, i try to migrate mails from a non dovecot imap server to a dovecot imap server with doveadm backup as described there: http://wiki2.dovecot.org/Migration/Dsync i first tried (local-mailbox port 18143 is the non dovecot imap server): /usr/bin/doveadm -o imapc_user=user at example.org -o imapc_password=imappw -o imapc_host=local-mailbox -o imapc_features=rfc822.size -o imapc_port=18143 -o
2019 Dec 05
2
[2.3.8] possible replication issue
I think there's a good chance that upgrading both will fix it. The bug already existed in old versions, it just wasn't normally triggered. Since v2.3.8 this situation is triggered on one dsync side, so the v2.3.9 fix needs to be on the other side. > On 5. Dec 2019, at 8.34, Piper Andreas via dovecot <dovecot at dovecot.org> wrote: > > Hello, > > upgrading to 2.3.9