Displaying 20 results from an estimated 300 matches similar to: "1.0alpha4: mbox-lock asserts and cores"
2005 Nov 30
0
F_UNLCK assertion
Hello,
> 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)
I'm getting this error too after upgrading to alpha4.
> Gdb info on a couple of the cores is attached. It looks
> like the arg lock_type for mbox_lock_fcntl()
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
2005 Oct 24
0
1.0alpha4: drowning in asserts/cores
Timo,
I have had to drop back to alpha3 because I found a pile
of core files on my imap server this morning, from the
weekend. They are all from the assert:
imap(user): file mbox-lock.c: line 379 (mbox_lock_fcntl):
assertion failed: (lock_type == F_UNLCK)
I reported this issue to the list last Friday. Help...
Jeff Earickson
Colby College
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:
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 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 <=
2005 Sep 19
0
1.0alpha2: two asserts/cores
Hi,
Two cores over the weekend, same assert message in syslog:
imap(user): file message-body-search.c: line 393
(message_body_search_ctx): assertion failed: (input->v_offset <=
part->physical_pos)
Setup: Solaris 9, imap usage only, mbox format, dovecot compiled
with gcc 4.0.1.
gdb sessions of the two core files attached. Let me know if you
need further analysis of the cores.
2008 Oct 04
2
Dovecot 1.1.3 crash & backtrace
Backtrace:/usr/local/libexec/dovecot/imap
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB
2018 Dec 04
0
[2.3.4] Segmentation faults
> On 04 December 2018 at 16:46 Joan Moreau via dovecot <dovecot at dovecot.org> wrote:
>
>
> Hi
>
> How to solve this ?
>
> So many similar segfaults
>
> Thank you
>
> On 2018-11-30 06:11, Joan Moreau wrote:
>
> > ANother (very very long) example :
> >
> > # gdb /usr/libexec/dovecot/indexer-worker
2010 Oct 10
1
Dovecot 2.0 lock upgrade assertion failure
Hi!
I've now seen this assertion failure from lmtp (most frequent), pop3
(next frequent), and imap (rarely). It didn't start happening until the
number of accounts on the server was increased into the 10k-25k range.
It happens when index->file_lock is a read lock and mail_index_lock is
called asking for a write lock. Dovecot 2.x dies at the assertion on
line 62 of mail-index-lock.c
2018 Dec 04
0
[2.3.4] Segmentation faults
We don't consider it as "very early beta". We consider it production ready. It is bit more work to set up though.
Aki
> On 04 December 2018 at 17:16 Joan Moreau <jom at grosjo.net> wrote:
>
>
> Thanks for mySql
>
> For Squat vs Solr, Solr does not reach Squat by very far in terms of
> results : If I setup Solr, and search (via the search in Roundbube
2018 Dec 04
0
Squat
Yes, but the bottom line is that Squat does the job needed for end
users, Solr does not
On 2018-12-04 16:53, Michael Slusarz wrote:
>> On December 4, 2018 at 8:18 AM Aki Tuomi <aki.tuomi at open-xchange.com> wrote:
>>
>> We don't consider it as "very early beta". We consider it production ready. It is bit more work to set up though.
>
> FWIW, Squat
2004 Jul 20
3
Bug? 1.0.0-test28 NFS locking problems
Hi
Slight problem - linux 2.4 running dovecot, Solaris 2.8 home directory
server. Full lockd support etc.
I had to make the following code patches (at end of mail for clarity) to
get dovecot to read the users mbox files at all.
1) fcntl with F_SETLKW will not work against a Solaris 2.8 server as
proved with a small test program. Other forms of fcntl (ie F_SETLK) are
OK.
I noticed there are
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 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 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
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 Sep 07
0
1.0alpha1: new assert/core
Hi,
I saw a new assert and core dump today in 1.0alpha1.
Setup is Solaris 9, dovecot built with gcc 4.0.1, running
as imap server for mbox format. The syslog said:
IMAP(user): file message-body-search.c: line 393 (message_body_search_ctx): assertion failed: (input->v_offset <= part->physical_pos)
A gdb analysis of the core dump is attached. BTW, I save
core dumps in case you need
2017 Aug 16
1
dotlock causing crashes
OS: CentOS 7 x86_64
Dovecot version: 2.2.31 (65cde28) (GhettoForge RPM)
Filesystem: GlusterFS, but working on changing that. Only one server is receiving activity.
Was getting messages about corrupt dovecot.map.index files. Changed to dotlock from fcntl to try to fix that.
Reading symbols from /usr/libexec/dovecot/imap...(no debugging symbols found)...done.
[New LWP 74012]
Core was generated by