Displaying 20 results from an estimated 600 matches similar to: "Making changes to dovecot log levels"
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
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
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:
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
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 Jul 20
1
Corrupted indices (and accidental checkin)
I've seen a number of corrupted-index problems pop up on our test-dovecot
servers (used by a few people at the office), and I'm wondering why corrupt
indices don't just automatically get deleted ? Something like:
if (!MAIL_INDEX_IS_IN_MEMORY(index)) {
unlink(index->filepath);
}
in src/lib-index/mail-index.c:mail_index_set_error() comes to mind. It
2005 May 16
2
Assertion Failure in mbox-sync.c
I've been getting a few of these errors on a couple different mboxes.
This is using the CVS version as of May 14.
So far, these are the only errors and it looks like most/all of the older
ones are gone. (maybe I shouldn't say that ;-)
dovecot: May 16 17:41:07 Error: 20973 IMAP(todd.bluegenesis.com): file mbox-sync.c: line 1165 (mbox_sync_handle_eof_updates): assertion failed:
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:
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
2006 Dec 14
2
604995471 7500 routers / upgrade issue
Hi Benjamin:
I think that the following link will give you an idea for what you need to
know:
http://www.cisco.com/warp/customer/620/roadmap_b.shtml
This is for the naming:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1818/products_tech_note09186a0080101cda.shtml
In this case 11.1CC goes to 12.0T and 12.0T migrate to 12.1 mainline. Do not
you worry you will not loose anything with the new
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
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 Jul 18
2
Assertion failure in mail-index-transaction.c
I just noticed one instance of this in the current CVS version:
dovecot: Jul 18 15:25:48 Error: 5962 IMAP(mailuser): mbox sync: Expunged
message reappeared in mailbox /mailhome/new/o/h/mailuser/mbox (UID 2834
< 2872)
dovecot: Jul 18 15:25:48 Error: 5962 IMAP(mailuser): file
mail-index-transaction.c: line 129 (mail_index_buffer_convert_to_uids):
assertion failed: (*seq != 0)
dovecot: Jul
2007 Sep 02
2
imap process consuming 100% CPU (Dovecot 1.0.3)
Hi,
I have yet another problem with Dovecot: sometimes (rarely, maybe
once every few days) one of the imap processes will 'hang',
consuming all available CPU time. It does not seem to 'finish' in any
reasonable amount of time (in one instance I waited a few days). This
process will not even exit gracefully, it needs to be killed with
'kill -9 <PID>'.
It has
2005 May 04
1
Problem (?) with 1.0-stable
... Version from April 26, gives me the following errors in the imap log
file :
dovecot: May 04 09:56:58 Error: IMAP(m6933192-4): file mbox-sync.c: line
1262 (mbox_sync_do): assertion failed: (sync_ctx->ibox->mbox_sync_dirty)
dovecot: May 04 09:56:58 Error: child 10721 (imap) killed with signal 6
This occurs sporadically and vanishes after some time. Is this something
to worry about or
2013 Apr 23
2
mailbox_list_index_parse_header crash
Hi,
I got all excited about IMAP NOTIFY support and tried enabling
mailbox_list_index on my server. Unfortunately, I rather quickly ran
into trouble of the segfault variety. This prevented me from doing
basic things like seeing the contents of some of my folders. Disabling
mailbox_list_index got me back up and running, but... darnit, that's
annoying. The only message I got in my log file
2005 May 03
1
Test68 and Namespaces
Hello List,
I am in the process of building a new mail system here. I am hoping to
eventually migrate my users from mbox storage to maildir. They have
been using mbox forever and would rather get used to maildir slowly.
So I have come upon the idea of using namespaces to provide the
different mailstores. Since this isn't available in the current
stable, or at least I could not figure
2010 Jul 24
1
Dsync error when working dir o-rwx
Hi,
I dont know why dsync requires o+rx in working dir, at least it could give
better error message when working dir has o-rwx.
# cd
# mkdir test
# cd test
# dsync -D -v -u 'info at example.org' -o 'mail_privileged_group=mail' -o
'mail_location=mbox:/email/info at example.org/mail:INBOX=/var/mail/info at example.org'
mirror 'maildir:~/Maildir'
dsync(info at
2013 Aug 05
1
Corrupted mboxes with v2.2.4, posix_fallocate and GFS2
Hi,
on a clustered Dovecot server installation that was recently moved from a
shared GPFS filesystem to GFS2, occasional corruptions in the users'
INBOXes started appearing, where a new incoming message would be appended
directly after a block of NUL bytes, and be scanned by dovecot as being
glued to the preceding message.
I traced this to the file extension operation performed in
2007 Oct 22
2
Problem in mbox-sync.c
We've just cut over to a new mail server running Dovecot 1.0.5.
The underlying OS is RHEL 5. User mailboxes are stored in Unix mbox
format on a local ext3 file system. The MTA on the system is the
default RedHat version of Sendmail 8.13.8 with procmail for local
delivery. We're using a combination of dotlock and fcntl style locking.
The output of "dovecot -n" for this system