similar to: Dsync Panic

Hi, I have 2 Dovecot servers (2.2.10) which are replicating each other. Replication works fine except for one user. [root at dovecot2 ~]# doveadm -D sync -u username dovecot1 doveadm(root): Debug: Loading modules from directory: /usr/lib64/dovecot doveadm(root): Debug: Module loaded: /usr/lib64/dovecot/lib15_notify_plugin.so doveadm(root): Debug: Module loaded:

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

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

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"

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

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 *

Hi there, i've got some errors in my log files # dovecot --version 2.2.9 Here the Log's:

Hi Timo, little cosmetic bug report: using "verbose_proctitle = yes" shortens the proctitle of dsync to just "dsyn". Example: Note the whitespace instead of the 'c' in the proctitle: root at m-st-01:~# ps auwwwx | grep [d]syn virtmail 18141 13.0 0.1 49916 7952 pts/6 R+ 00:49 0:00 dsyn -v -u xxyyzz7 -R backup maildir:/staging/xxyyzz7/Maildir With

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:

Hi, we still migrate a couple of users from mbox to maildir. Most of them are fine without any problem. Some crash and dont get all mails synced. first I sync backup the mbox to a maildir-NEW, than copy mbox to a new name, mv maildir-NEW to maildir. Now some problematic mailusers miss some mails from the old mbox, so I start a dsync mirror and BAM crash. e.g.: dsync(s108019): Panic: file

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

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

Hi all, I'm receiving a reproducible dsync backup panic for some of my users. The error message is as follows: dsync-remote(user@<removed>): Panic: file dsync-brain-mailbox-tree-sync.c: line 111 (dsync_brain_mailbox_tree_sync_change): assertion failed: (brain->no_backup_overwrite) dsync-remote(user@<removed>): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x69b70)

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

Hi, some of our customers have discovered a replication issue after upgraded from 2.3.7.2 to 2.3.8. Running 2.3.8 several replication connections are hanging until defined timeout. So after some seconds there are $replication_max_conns hanging connections. Other replications are running fast and successful. Also running a doveadm sync tcp:... is working fine for all users. I can't see

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

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

Greetings, I've seen something like this in another thread, about a month ago, but we're running into this error pretty frequently when we run dsync backup. Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0 [0x39ccc5f1c0] -> /usr/lib64/dovecot/libdovecot.so.0(default_fatal_handler+0x35) [0x39ccc5f2a5] -> /usr/lib64/dovecot/libdovecot.so.0 [0x39ccc5ebb3] ->

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 mail stack which features Dovecot 2.2.9 (and Postfix). My setup is to use system users (userdb passwd /

On 20 Apr 2015, at 19:10, Dennis Kuhn <d.kuhn at heinlein-support.de> wrote: > > 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