Displaying 20 results from an estimated 400 matches similar to: "another assertion failure in dovecot 1.1.7 mbox-sync-rewrite: (mails[idx].from_offset == start_offset)"
2008 Dec 04
1
assertion failed in 1.1.7 file mbox-sync.c: line 1305 (mbox_sync_handle_eof_updates)
Dovecot 1.1.7 is running so smoothly that I gave up checking its log
files daily. :)
I've just had a look, and among the usual
"IMAP(username): FETCH for mailbox Sent UID xx got too little data: xx vs xx"
messages (that means that unfortunately sometimes some messages are
still written truncated) I saw this assertion failure:
file mbox-sync.c: line 1305
2006 Nov 12
2
assertion failed: (need_space == (uoff_t)-mails[idx].space)
I'm running Dovecot dovecot-1.0.r13 on FreeBSD (FreeBSD 6.1-RELEASE-
p10). Mail is stored in mbox format (dovecot.conf after the msg).
Procmail delivers mail to subfolders under ~/.mail, locking using
dotfiles. One folder in particular for one user has an mbox file
~/.mail/Cron.
Quite often, I'll see that procmail processes are stacking up because
~/.mail/Cron.lock exists, and
2005 Nov 24
0
New Assert Failure
Here's a new one with CVS version from 2005-11-03.
The mbox size is currently 42951945 bytes.
dovecot: Nov 24 12:05:50 Error: 11520 imap(username):
Unexpectedly lost From-line at offset 33979772 from mbox file
/mailhome/new/a/l/username/mbox
dovecot: Nov 24 12:05:50 Error: 11520 imap(username): file
mbox-sync-rewrite.c: line 552 (mbox_sync_rewrite): assertion failed:
2007 Jan 05
2
Dovecot rc15 crash in mbox-sync-update.c
Here is another crash we've been seeing recently in rc15 on Solaris 10.
(gdb) bt full
#0 0xff1c12a4 in ?? ()
No symbol table info available.
#1 0xff140040 in ?? ()
No symbol table info available.
#2 0x000786a8 in t_buffer_alloc (size=688976) at data-stack.c:346
__PRETTY_FUNCTION__ = "file %s: line %"
#3 0x00078190 in t_pop () at data-stack.c:149
frame_block = (struct
2007 Mar 07
3
1.0.rc26 released
http://dovecot.org/releases/dovecot-1.0.rc26.tar.gz
http://dovecot.org/releases/dovecot-1.0.rc26.tar.gz.sig
Most importantly this should fix mbox problems in recent RCs.
* Changed --with-headers to --enable-header-install
* If time moves backwards only max. 5 seconds, sleep until we're back
in the original present instead of killing ourself. An error is
still logged.
- IMAP: With
2007 Mar 07
3
1.0.rc26 released
http://dovecot.org/releases/dovecot-1.0.rc26.tar.gz
http://dovecot.org/releases/dovecot-1.0.rc26.tar.gz.sig
Most importantly this should fix mbox problems in recent RCs.
* Changed --with-headers to --enable-header-install
* If time moves backwards only max. 5 seconds, sleep until we're back
in the original present instead of killing ourself. An error is
still logged.
- IMAP: With
2005 Aug 16
2
test80: assert/core debug info
Timo,
Attached is gdb information from core dumps related to the
following assert in test-80:
IMAP(username): file mbox-sync-update.c: line 442
(mbox_sync_update_header_from): assertion failed: (ctx->mail.uid == 0 ||
ctx->mail.uid_broken || ctx->mail.uid == mail->uid)
My setup: Solaris 9, mbox format. test-80 compiled with
gcc 4.0.1 using the following configure options:
CC=gcc
2008 Aug 25
2
Dovecot 1.1.2
Hello,
I upgraded dovecot to 1.1.2 this weekend and i get those errors:
grep dovecot /var/log/net/maillog |grep Panic | cut -d " " -f 11-100|
sort | uniq -c | sort -rn
7547 file index-sync.c: line 39: assertion failed:
(seq_range_exists(&ibox->recent_flags, uid))
89 file index-mail.c: line 1091: assertion failed: (!
mail->data.destroying_stream)
18 file
2005 Sep 01
0
another assert/core with 1.0alpha1
Same as reported before:
Assert:
IMAP(user): file mbox-sync-update.c: line 442
(mbox_sync_update_header_from): assertion failed: (ctx->mail.uid == 0 ||
ctx->mail.uid_broken || ctx->mail.uid == mail->uid)
Setup: 1.0alpha1 on Solaris 9, built with gcc 4.0.1
Debug output of the core is attached.
Jeff Earickson
Colby College
-------------- next part --------------
Script started on
2005 Aug 26
0
1.0alpha1: assert and core
Hi,
I've been running 1.0alpha1 in production since August 18, and
got my first assert and core yesterday. Otherwise it has been
running flawlessly.
My setup: Sun E220R, Solaris 9, compiled dovecot with gcc 4.0.1,
configured dovecot like so:
#!/usr/bin/sh
VERSION=1.0-alpha1
CC=gcc CFLAGS="-g -O" CPPFLAGS=-I/opt/openssl/include LDFLAGS=-L/opt/openssl/lib \
./configure
2005 Oct 28
3
Asserion Failure in Current CVS
Just installed the version from CVS as of Oct. 27.
I noticed three problems quite quickly:
Still seeing "(imap) killed with signal 14"
My INBOX closed with "access error" after reading it for a bit. There's
nothing in the logs or anything, but this hasn't happened for quite a
while now. There where quite a lot of incoming messages at the time and
I was marking
2011 Apr 04
1
Dovecot IMAP repeatedly disconnects
Hi,
I'm running dovecot-1.0.7-7.el5 on a CentOS 5.5x64 server, accessed
through Thunderbird clients. Thunderbird is reporting constant
disconnections from the server; the maillog shows constant repeats of
Apr 4 16:39:21 holly dovecot: imap-login: Login: user=<?user?>,
method=PLAIN, rip=::ffff:172.31.255.193, lip=::ffff:172.31.255.1
Apr 4 16:39:21 holly dovecot: IMAP(?user?): mbox
2007 Mar 02
2
rc25: need_space assert, core
Timo,
I see where at least one other person reported this, but here goes.
I went from rc24 to rc25 this morning, and I got an assert and core
from my own mailbox withing five minutes:
Mar 2 06:52:26 karst dovecot: [ID 107833 mail.error] IMAP(jaearick): file mbox-sync-rewrite.c: line 408: assertion failed: (need_space == (uoff_t)-mails[idx].space)
Mar 2 06:52:26 karst dovecot: [ID 107833
2007 Mar 05
3
Bug: mbox-sync-parse.c: line 228
[root at mail postfix]# dovecot --version
1.0.rc25
[root at mail postfix]# dovecot -n
# /usr/local/etc/dovecot.conf
ssl_cert_file: /usr/share/ssl/certs/dovecot.pem
ssl_key_file: /usr/share/ssl/private/dovecot.pem
login_dir: /usr/local/var/run/dovecot/login
login_executable: /usr/local/libexec/dovecot/imap-login
mbox_write_locks: fcntl
auth default:
passdb:
driver: pam
userdb:
driver:
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 <=
2007 Mar 28
2
assertion failed (1.0-rc27)
Under Dovecot 1.0-rc27 on Solaris 10 we noticed this error today affecting
one of our users repeatedly:
Mar 28 14:02:01 myhost dovecot: IMAP(myuser): file mbox-sync-rewrite.c: line 423 (mbox_sync_read_and_move): assertion failed: (need_space == (uoff_t)-mails[idx].space)
Mar 28 14:02:01 myhost dovecot: IMAP(myuser): Raw backtrace: 0x7ac54 -> 0x42cd4 -> 0x3e968 -> 0x3f54c -> 0x3f980
2004 Sep 29
2
UIDL bug
I noticed a problem with handling UIDL msgnumber in test46.
If you do "UIDL 1" on a POP3 connection it returns the UID of the message
followed by a dot and an error message. I made 2 changes:
I added the following line to line 527 of src/pop3/commands.c
ctx->message = message;
I changed line 559 from:
if (list_uids_iter(client, ctx))
to:
if (!list_uids_iter(client, ctx))
2018 Dec 28
0
[PATCH v1 1/2] virtio_pci: use queue idx instead of array idx to set up the vq
When find_vqs, there will be no vq[i] allocation if its corresponding
names[i] is NULL. For example, the caller may pass in names[i] (i=4)
with names[2] being NULL because the related feature bit is turned off,
so technically there are 3 queues on the device, and name[4] should
correspond to the 3rd queue on the device.
So we use queue_idx as the queue index, which is increased only when the
2003 Apr 21
0
Patch for zero content-length
mbox-index.c uses a zero content length as a flag for an invalid
Content-Length: header. Unfortunately zero is also a valid value for
Content-Length. The patch below attempts to address the problem.
*** mbox-index.h.orig Tue Apr 15 09:04:02 2003
--- mbox-index.h Sun Apr 20 11:42:12 2003
***************
*** 19,24 ****
--- 19,25 ----
struct istream *input;
uoff_t
2014 Oct 29
2
2.2.15 Panic in mbox_sync_read_next_mail()
It might not be a fault in dovecot, as the user is accessing the folder locally
with alpine while also running imap-sessions. However it would have been nice
with a more graceful action than panic?
The panic is preceeded by
Error: Next message unexpectedly corrupted in mbox file PATH
Panic: file mbox-sync.c: line 152 (mbox_sync_read_next_mail): assertion failed: