similar to: 1.0alpha4: drowning in asserts/cores

Displaying 20 results from an estimated 2000 matches similar to: "1.0alpha4: drowning in asserts/cores"

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 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()
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:
2007 Apr 06
2
mbox sync/lock issue, rc28 and later
Help! I just noticed this error this morning, we have been getting a lot of these in rc28 and rc29, not in rc27 or before: Apr 6 07:22:52 karst dovecot: [ID 107833 mail.error] IMAP(jaearick): mbox file /var/mail/j/jaearick was modified while we were syncing, check your locking settings Pine coughed up an internal error, no core dump, and dovecot basically doubled the size of my mailbox by
2005 Dec 17
1
Re: dovecot Digest, Vol 32, Issue 42
If its too hard for them to setup the pop3 catch all, we can probably put some mapping in place to smtp froward mail to their server. This is more complex on our part so would prefer not to do it that way, but its an option and will require not setup on their part other than make sure their server does not accept mail for anyone other than our server. dovecot-request@dovecot.org wrote: >
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
2002 May 20
1
patch for bug 245?
Hi, Has a patch against 3.2.2p1 been posted for bug 245, the bug that gives the following syslog complaint? open /dev/tty failed - could not set controlling tty: No such device or address I hit this when upgrading from 3.1p1, solaris 8, using Sun Forte 6 C compiler. I would get authenticated at login, but my shell would never get going. I had to roll back to 3.1p1. ** Jeff A. Earickson,
2006 Jan 19
1
beta1: how to use quota plugin???
Hi, After searching gmane.mail.imap.dovecot on the topic, and wiki.dovecot.org, I'm still clueless on how to use RFC 2087 quotas in dovecot with the quota plugin. How come no wiki doc? My setup: Solaris 9, mbox format. Both the filesystem for INBOXes (/var/mail) and the user's home directories have filesystem-based quotas imposed. For example: % quota -v joeblow Disk quotas for
2005 Aug 29
1
dovecot/Active Directory/KRB client (OT)
Gang, For those who asked about making a Solaris system a Kerberos client to Active Directory, the magic document to have is: http://www.connectathon.org/seam1.0/files/c0101.htm See the section "How to Configure a SEAM Client Using a Windows 2000 KDC". SEAM was Sun's Kerberos client stuff in Solaris 8; it is just there as part of Solaris 9 and 10. These instructions apply if
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
2005 Jan 26
2
How to run in debug format for SSL testing?
Help, new to dovecot... I want to get some output from my test sessions to confirm that SSL pop and imap are working. How does one get debug output from dovecot? How does one see that dovecot is using SSL in a transaction? I configured dovecot 0.99.13 with: CC=gcc CPPFLAGS=-I/opt/openssl/include LDFLAGS=-L/opt/openssl/lib \ ./configure --prefix=/opt/dovecot --with-ssl=openssl \
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 Sep 05
2
1.0alpha1: too many open files
Help... Dovecot 1.0alpha1 hung up today with nothing working and the following spewing to my syslog: pipe() failed: Too many open files My setup: Solaris 9, just using imap, mbox format. The various "max" settings in dovecot.conf use the defaults. Suggestions on what to change in fovecot.conf to keep this from happening? Jeff Earickson Colby College
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
2005 Jul 05
1
dovecot 1 for production? which one?
Hi, I've been lurking on the list since Spring, planning to replace UW-IMAP with dovecot 1.0 sometime this summer. The recent thread on "1.0" has not given me a good feeling about seeing it before summer's end. So I wonder if I should use dovecot-1.0-test-xx code or dovecot-stable-[date] code (which seems to change every day, how stable is that???). This is confusing,
2006 Sep 05
1
rc7 crashing under heavy load
Help! Our students are back and they are pounding my dovecot server to death (ie "Login process died too early - shutting down" or "too many open files" type crash). I've had my third crash today. My setup: Solaris 10, imap and imaps, 3K users coming in via horde webmail. My current connection settings are: login_max_processes_count = 2048 login_max_connections = 4096
2005 Dec 14
2
1.0alpha5: fcntl() locking problem
Hi, My setup: Solaris 9, /var/mail is NFS mounted from another Solaris 9 box, home directories and dovecot index stuff is on local ufs filesystems. I upgraded from alpha4 to a5 about 36 hours ago. Dovecot is configured like so during the build: VERSION=1.0.alpha5 CC=gcc CFLAGS="-g -O" CPPFLAGS=-I/opt/openssl/include LDFLAGS=-L/opt/openssl/lib \ ./configure
2006 May 14
2
beta8: complaint about tilde at startup
Timo, After installing beta8 on Solaris 10 sparc and starting it for the first time, I noticed this in my syslog: May 14 19:35:45 emerald dovecot: [ID 475045 mail.info] Dovecot v1.0.beta8 starting up May 14 19:35:47 emerald dovecot: [ID 536776 mail.error] stat(~) failed: No such file or directory The only appearance of the tilde (~) in my dovecot.conf is here: default_mail_env =
2006 Nov 20
2
rc14 and rc15 performance issues
Hi, I am stuck at rc13 because rc14 and rc15 have both failed to keep up with imap connections on my (slow old) system. I have the problem where if a lot of people check their email at once (like at the top of the hour) then my load goes way up and things slow to a crawl. My setup: Solaris 10 on an E220R, mbox format, imap and imaps only. I also use "login_process_per_connection =
2007 Jan 25
2
rc18->rc19: read/unread/reply flags broken
Timo, This might be a bit vague, but I have noticed that rc19 seems to have broken the read/unread/reply flags in imap. My officemate has had problems with messages that are read and marked as read then mysteriously get remarked as unread the next time email is checked. I've had problems where I reply to a message and it does not get marked as "answered". We didn't see this