Displaying 20 results from an estimated 600 matches similar to: "1.0a3: assert and core dump"
2005 Oct 21
1
1.0alpha4: mbox-lock asserts and cores
Timo,
I upgraded from alpha3 to alpha4 yesterday, and I am seeing
a few of the following asserts:
imap(user): file mbox-lock.c: line 379 (mbox_lock_fcntl):
assertion failed: (lock_type == F_UNLCK)
Gdb info on a couple of the cores is attached. It looks
like the arg lock_type for mbox_lock_fcntl() is not getting
passed in correctly, like the enum "enum mbox_lock_type type"
in
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
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 <=
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
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
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
2006 May 22
1
beta8: cores on corrupted index file
Timo,
I saw a couple of these cores over the weekend. The syslog says:
May 21 19:04:48 emerald dovecot: [ID 107833 mail.error] IMAP(user): Corrupted index cache file /home/students/s/user/.imap/sent-mail-apr-2004/dovecot.index.cache: indexid changed
With a resulting core file from imap at this time. I also discovered
a remaining lock file on the person's imap file:
-rw------- 1 user
2006 Mar 06
1
asserts and cores in beta3
My setup: Solaris 9, built with gcc 4.0.2 (I now have gcc 4.1
installed on my system, but have not rebuilt dovecot). A
couple of asserts and cores in the last few days:
Mar 1 09:25:13 emerald dovecot: [ID 107833 mail.error] imap(tmwillia): file mbox-sync.c: line 1471 (mbox_sync_do): assertion failed: (!sync_ctx->mbox->mbox_sync_dirty || (flags & MBOX_SYNC_UNDIRTY) == 0)
Mar 1
2005 Jul 26
1
1.0 stable 20050725 assert, signal 6
Hi,
I was brave enough to upgrade from UW-imap to stable 1.0 20050725
today for our IMAP service. I have seen a few of the following in
my syslog:
Jul 26 15:37:18 emerald dovecot: [ID 107833 mail.error] IMAP(bjkupke): file mbox
-sync-update.c: line 372: assertion failed: (ctx->mail.uid == 0 || ctx->mail.uid
== mail->uid)
Jul 26 15:37:18 emerald dovecot: [ID 684838 mail.error] child
2017 Sep 16
2
dsync panic in mbox_lock
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 (mbox_lock):
assertion failed: (lock_type == F_RDLCK || mbox->mbox_lock_type !=
F_RDLCK)
Abort
User is not overquota, and filesystem
2007 Jan 25
1
X-UID gaps cause Dovecot/IMAP to hang
Hi,
When the Dovecot 1.0.rc19 IMAP server encounters X-UID headers with
gaps in them, it hangs indefinitely. I've attached a sample mailbox (in
mbox format) which repeatably exhibits this behavior. The mbox contains
only three messages with the following X-UIDs in order: 774, 785, 787.
If I remove the X-UID headers from each message, Dovecot handles the
mailbox without any problems. UW-IMAP
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
2006 Jan 24
0
1.0beta2: mbox_sync assert
Timo,
My first assert in beta2. Syslog said:
Jan 24 09:57:16 emerald dovecot: [ID 107833 mail.error] imap(user): Cached message offset 94625 is invalid for mbox file /var/mail/m/user
Jan 24 09:57:16 emerald dovecot: [ID 107833 mail.error] imap(user): file mbox-sync.c: line 1471 (mbox_sync_do): assertion failed: (!sync_ctx->mbox->mbox_sync_dirty || (flags & MBOX_SYNC_UNDIRTY) == 0)
Gdb
2005 Dec 19
0
alpha5: assert and core
My setup: Solaris 9, dovecot built with gcc 4.0.2. Mailboxes on
remote NFS file mount from another S9 box (mbox format), index files
local disk. IMAP usage only. Dovecot build like so:
VERSION=1.0.alpha5
CC=gcc CFLAGS="-g -O" CPPFLAGS=-I/opt/openssl/include \
LDFLAGS=-L/opt/openssl/lib \
./configure --prefix=/opt/dovecot.$VERSION --with-ssl=openssl \
--with-ssldir=/opt/openssl/ssl
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
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
2005 Oct 18
1
1.0alpha3: assert and core
Hi,
An assert and core with 1.0alpha3 on Solaris 9, mbox format,
imap only, compiled with gcc 4.0.1. The syslog message was:
imap(user): file message-body-search.c: line 393
(message_body_search_ctx): assertion failed: (input->v_offset <=
part->physical_pos)
gdb core dump analysis is attached.
Jeff Earickson
Colby College
-------------- next part --------------
Script started on
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
2007 Nov 09
1
Compiz starts, but no 3D effects
I just installed Compiz on Ubuntu Feisty (Gutsy does not work on my
hardware as per the release notes) via the
http://ppa.launchpad.net/amaranth/ubuntu repo, which is the repo
suggested in the compiz-fusion website. The machine is a Dell Inspiron
E1505 / 6400 with the horrible ATI X1400 graphics card and 1680x1050
monitor. I installed XGL and the proprietary ATI driver, a combination
that worked
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