[Dovecot] Dsync Errors
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] -> dsync(dsync_brain_mailbox_tree_sync_change+0x41c) [0x42cc0c] -> dsync(dsync_brain_recv_mailbox_tree_deletes+0x10a) [0x42be7a] -> dsync(dsync_brain_run+0x4fc) [0x429cdc] -> dsync [0x42885b] -> dsync [0x4119ff] -> dsync(doveadm_mail_try_run+0x269) [0x411e09] -> dsync(main+0x358) [0x41a2c8] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x3f4281d994] -> dsync [0x4111c9]
We're running Dovecot 2.2.4 and the dsync command is this: dsync -u <username> backup maildir:/mnt/backups/<period>/<domain>/<username>
When this happens to a particular users account I delete the backup and let it rebuild, which works for awhile, but then it happens again, and it seems to happen to particular users.
Can you point me in the right direction to start troubleshooting this?
Thanks.
-- --Asai
On 2014-01-24 10:51 AM, Asai <asai@globalchangemusic.org> wrote:
We're running Dovecot 2.2.4 and the dsync command is this: dsync -u <username> backup maildir:/mnt/backups/<period>/<domain>/<username>
When this happens to a particular users account I delete the backup and let it rebuild, which works for awhile, but then it happens again, and it seems to happen to particular users.
Can you point me in the right direction to start troubleshooting this?
The first thing to do when experiencing problems like this is make sure you are on the current version of whatever point release you are running. In your case that would be 2.2.10. Then if you still experience the problem, come back and re-ask...
If you are unable to update due to some kind of 'LTS' restrictions enforced by your chosen OS, then your first line of support should be from them - otherwise, what is the point of using that OS?
Also, they would be the ones that would have to back-port any fixes from more recent releases to your 'stable' version.
--
Best regards,
Charles
The first thing to do when experiencing problems like this is make sure you are on the current version of whatever point release you are running. In your case that would be 2.2.10. Then if you still experience the problem, come back and re-ask...
OK, I upgraded to 2.2.10. Same thing. Is there some kind of debug routine I can run?
Maybe this error sheds some light on it:
Panic: file dsync-brain-mailbox-tree-sync.c: line 111 (dsync_brain_mailbox_tree_sync_change): assertion failed: (brain->no_backup_overwrite)
On 30.1.2014, at 11.06, Asai <asai@globalchangemusic.org> wrote:
Maybe this error sheds some light on it:
Panic: file dsync-brain-mailbox-tree-sync.c: line 111 (dsync_brain_mailbox_tree_sync_change): assertion failed: (brain->no_backup_overwrite)
Timo, you're amazing. Thank you.
--Asai
On 2/7/14 1:07 PM, Timo Sirainen wrote:
On 30.1.2014, at 11.06, Asai <asai@globalchangemusic.org> wrote:
Maybe this error sheds some light on it:
Panic: file dsync-brain-mailbox-tree-sync.c: line 111 (dsync_brain_mailbox_tree_sync_change): assertion failed: (brain->no_backup_overwrite) Fixed by http://hg.dovecot.org/dovecot-2.2/rev/fbc8fe46dfce
I see Timo addressed this problem with this reply ( from thread "[Dovecot] reproducible dsync backup panic (dovecot 2.2.7)/Fri Dec 20 00:37:21 EET 2013")/, but basically I don't understand how to go about doing this:
Can you get it to dump core and use
gdb /usr/bin/doveadm core bt full fr 5 p *change
/ The command I'm using to back up individual user's mail is something like: />/
/>/ sudo -u vmail dsync -v -uuser at server.com <http://dovecot.org/cgi-bin/mailman/listinfo/dovecot> -R backup ssh -i sshid-filelogin at server.com <http://dovecot.org/cgi-bin/mailman/listinfo/dovecot> sudo -u vmail dsync -v -uuser at server.com <http://dovecot.org/cgi-bin/mailman/listinfo/dovecot> / Probably an easier way would be if you could copy the local and remote mdboxes to e.g. /tmp/mdbox-local and /tmp/mdbox-remote. Then you should be able to do:
gdb --args doveadm -o mail=mdbox:/tmp/mdbox-local backup -R mdbox:/tmp/mdbox-remote run bt full fr 5 p *change
participants (3)
-
Asai
-
Charles Marcus
-
Timo Sirainen