similar to: dsync panic in mbox_lock

Displaying 20 results from an estimated 200 matches similar to: "dsync panic in mbox_lock"

2017 Sep 16
0
dsync panic in mbox_lock
> On September 16, 2017 at 5:28 AM Emmanuel Dreyfus <manu at netbsd.org> wrote: > > > Hello > > I am trying to setup replication with dovecot-2.2.29.1, and for some > users, I get a reproductible panic: > > # doveadm -v -o plugin/mail_replica=remoteprefix:root at mail2.example.net > sync -d -u jdoe > dsync-local(jdoe): Panic: file mbox-lock.c: line 799
2017 Sep 17
1
dsync panic in mbox_lock
Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > We have seen this before but so far the actual bug has not been > reproducible for us. Can you post your doveconf -n Here it is: https://ftp.espci.fr/shadow/manu/conf.log > and also logs with > doveadm -Dv -o plugin/mail_replica=remoteprefix:root at mail2.example.net > sync -d -u jdoe https://ftp.espci.fr/shadow/manu/sync.log
2014 Aug 26
0
Running dsync results in Panic: file mbox-lock.c: line 799 (mbox_lock)
Hello, I'm converting our system to use dovecot. As part of the migration we need to convert existing mbox'es to Maildir format. I'm using latest Dovecot2 available as FreeBSD pkg - 2.2.13. I'm trying to use dsync, which results in: ./dsync -vfu ppaczyn -o mail_location=mbox:~/mail:INBOX=/var/mail/ppaczyn mirror maildir:~/Maildir dsync(ppaczyn): Panic: file mbox-lock.c: line 799
2016 Aug 28
2
Dsync config help
Hi, I?m having a hard time with the?http://wiki2.dovecot.org/Replication ?page. - for a master-master setup, does the configuration need to be mirrored on both masters? - after aggregating unrelated sections of the wiki page, there seems to be 3 different values for ?mail_replica": - "remote?: for SSH - ?remoteprefix": for SSH wrapper - ?tcp?: for?TCP connection using
2013 Apr 23
3
Using dsync to export mail to remote IMAP account
I've read the web/man pages on dsync, but it's not clear to me whether dsync can be used to export (rather than import) a user's mailbox to a remote non-dovecot IMAP account. (The intention is to use it whenever a user leaves and wants to copy their local mail to Google or whatever. I currently use uw-imapd's mailutil -- it works, but it's dreadfully slow.) As a first crack
2016 Sep 01
2
Dsync config help
I was able to workaround the ?Error: sync: /var/run/dovecot/auth-userdb: Configured passdbs don?t support credentials lookups (to see if user is proxied, because doveadm_port is set)? problem:? => I simply disabled ?doveadm_port? and added the port number at the end of the remote URL in ?mail_replica? Replication seems to work although I have regular errors (idk if they are related to each
2011 Aug 21
2
Fixing split brain
Hi Consider the typical spit brain situation: reading from file gets EIO, logs say: [2011-08-21 13:38:54.607590] W [afr-open.c:168:afr_open] 0-gfs-replicate-0: failed to open as split brain seen, returning EIO [2011-08-21 13:38:54.607895] W [fuse-bridge.c:585:fuse_fd_cbk] 0-glusterfs-fuse: 1371456: OPEN() /manu/netbsd/usr/src/gnu/dist/groff/doc/Makefile.sub => -1 (Input/output
2016 Apr 21
2
Setting up replication?
On 4/21/2016 12:01, Timo Sirainen wrote: > On 21 Apr 2016, at 19:51, Knute Johnson <dovecot at knutejohnson.com> wrote: >> On 4/21/2016 04:33, Aropalo Tommi wrote: >>>> I'm trying to set up replication between two servers and I've hit a >>>> snag. I have two users and am using mbox files. If anybody has a >>>> sample config file for a
2020 Oct 11
2
Preparing for replication: dsync-local(testaccount): Panic: file mbox-lock.c
I am preparing a bit for setting up replication. However when I manually try to dsync an account, the first time I execute this[1] command it seems to be ok. The 2nd time I am getting this error[2]. If I add -1 (one way syncing) the error disappears. Does this mean I will have problems with setting up replication between these two servers? [1] [@ ~]# doveadm sync -n inbox -u testaccount
2017 Sep 26
3
dsync: assert panic on mbox // no INBOX sync on hybrid mbox/maildir
Hi, This (hopefully!) might be a case of user error, as I'm new to dovecot... Alternatively it might be some confusion in an index, since I've been mucking about trying different things in my configuration files and had frequent crashes. I'm trying to sync 2 (LAN) hosts, ideally to have full automatic replication happening. They both have hybrid mbox INBOX and maildir++ folders,
2013 May 31
1
dsync assert failure in 2.2.2
Hi, with 2.2.2 and today's hg, dsync crashes with dsync(root): Panic: file ../../../../../src/lib-storage/index/mbox/mbox-lock.c: line 797 (mbox_lock): assertion failed: (lock_type == F_RDLCK || mbox->mbox_lock_type != F_RDLCK) when I run USER=root 2.2-hg/bin/dsync -c etc/dovecot.conf -f -o mail_location=mbox:/tmp/imap/fwadmin.tmp:INBOX=/tmp/imap/fwadmin.tmp/INBOX mirror
2005 Apr 27
0
Assertion Failures in Current CVS version
I've attached a few assertion errors in imap. Any fixes or advice on where to look are appreciated. This is with the CVS version, current as of April 27. Todd Burroughs -------------- next part -------------- dovecot: Apr 27 00:00:45 Error: 5714 IMAP(chairman): file mail-index-transaction.c: line 808 (mail_index_update_ext): assertion failed: (seq > 0 && (seq <=
2005 Oct 14
0
1.0a3: assert and core dump
Timo, A rare assert and core dump out of 1.0alpha3. My setup: Solaris 9, mbox format, using imap only. Built dovecot with gcc 4.0.1. The syslog for this was: Oct 14 11:57:56 emerald dovecot: [ID 107833 mail.info] imap-login: Login: user=<epmccull>, method=PLAIN, rip=137.146.210.59, lip=137.146.210.52, TLS Oct 14 11:58:56 emerald dovecot: [ID 107833 mail.info] imap-login: Login:
2016 Apr 21
2
Setting up replication?
On 4/21/2016 04:33, Aropalo Tommi wrote: >> I'm trying to set up replication between two servers and I've hit a >> snag. I have two users and am using mbox files. If anybody has a >> sample config file for a simple system like mine I would really be >> grateful to see it. >> Thanks, >> The error I'm getting is: >> Mar 23 14:07:31 knute2
2005 Nov 18
0
Two new Assert Failures
These two are from CVS version as of 2005-11-03. There have only been these two asserts and we've had over 45000 logins. ---------------------------------------------------------------------- dovecot: Nov 16 13:35:34 Error: 18439 imap(username): Corrupted transaction log file /mailhome/new/c/h/username/.imap/INBOX/dovecot.index.log: Append with UID 53103, but next_uid = 53104 dovecot: Nov
2014 May 16
0
syncing problems Dovecot 2.2.13
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
2013 Sep 13
1
glusterfs-3.4.1qa2 released
RPM: http://bits.gluster.org/pub/gluster/glusterfs/3.4.1qa2/ SRC: http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.4.1qa2.tar.gz This release is made off jenkins-release-42 -- Gluster Build System
2020 Oct 12
0
Preparing for replication: dsync-local(testaccount): Panic: file mbox-lock.c
<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div class="default-style"> Replication is not supported with mbox format. You can only do unidirectional sync out of mbox. </div> <div class="default-style"> <br> </div> <div
2005 Sep 18
1
Can't connect to auth server at default: Connection refused
We've being running with Dovecot 1.0-stable since Tuesday, and on the whole it's gone very well (meaning nobody's noticed!). My best estimate is we're using half the disk accesses and 2/3 the CPU of UW-IMAP/Qpopper. We've quite a mixture of error messages in the logs, the most worrying of which is that several times we've had a few seconds of "xxx-login: Can't
2005 Sep 19
1
Two strange behaviours with dovecot+postfix+squirrelmail
Hi all, About a week ago I was forced to migrate my main (production) email server from RH9 to Centos4.1. The installation has dovecot-0.99.11 + postfix-2.1.5 and >600 mbox accessed email accounts. Number 1. Some users accessing thru squirremail (installed in my webserver) can read their INBOX at /var/spool/mail directory but when trying to delete a message they receive the following error