similar to: Failed Assert in RC13 on FC4

My dovecot directors (v2.0.8) had 3 instances of these yesterday: imap-login: Panic: file ioloop.c: line 35 (io_add): assertion failed: (fd >= 0) master: Error: service(imap-login): child 17374 killed with signal 6 (core dumps disabled) imap-login: Panic: file ioloop.c: line 35 (io_add): assertion failed: (fd >= 0) master: Error: service(imap-login): child 1780 killed with signal 6

When we upgrade our kernels from 2.6.32.2 to 3.2.16 something strange has happened. On high traffic dovecot/auth looks like not responding. We found a lot of this lines at the log: dovecot: pop3-login: Error: net_connect_unix(pop3) failed: Resource temporarily unavailable (...) and clients stop authorizing Some other errors follow in the wake of: dovecot: pop3: Error: Raw backtrace:

I've had this working for over a month now with no problems. Then I suffered a power outage today, and now dovecot/auth dies as soon as I start dovecot. I've spent the past three hours searching google, but can't find even a hint at what's wrong with my server. As far as I can tell, this is the only thing that has failed after bringing the server back up when power was restored.

Aloha, again, Timo. Concerning the problem of copying within one folder... I'm still not sure it's not a problem I created myself, but I think it's caused by the use of the buffered IO routines in ostream-file.c ... you use io_add() to schedule write operations for later while simultanously reading new chunks from the very same file. This seems to confuse dovecot and make it write

Timo, Just this morning I upgraded from 2.0.6 to 2.0.7 (hg changeset 66a523135836). A few hours later we had some power problems that caused the networking to drop out at one site. The directors on the surviving site all had a few imap-login processes crash with the following error: Nov 23 09:15:30 cc-director1 dovecot: imap-login: Panic: file ioloop.c: line 35 (io_add): assertion failed: (fd

Occasionally, all of our directors get stuck in an endless loop. Likely triggered by some network event, but I haven't been able to isolate exactly what triggers it, and am unable to reproduce at the moment. When this happens, it makes the dovecot/director process on all directors unresponsive, making login impossible. Restarting dovecot "fixes" it. Here's the info collected

Hi all, We moved our Dovecot installation first of all to have all folders and inboxes on NetApps via NFS (with indexes local) then from a physical Solaris 8 4-way UltraSparc server running Dovecot 1.2.5 (32-bit) to a virtualised Ubuntu 8.04 64-bit server with a single virtual processor (in VMWare ESX 3.5) running Dovecot 1.2.8 (64-bit). Since the change, many of our users have experienced

After I activated disabling POP3 for one of my users (not user 'jos'), the following is in my logfile: Dec 3 16:03:33 webrz dovecot: IMAP(jos): Disconnected Dec 3 16:03:36 webrz dovecot: IMAP(jos): Disconnected in IDLE Dec 3 16:03:36 webrz dovecot: IMAP(jos): file ioloop.c: line 22 (io_add): assertion failed: (fd >= 0) Dec 3 16:03:36 webrz dovecot: child 74197 (imap) killed with

in dovecot 1.0RC13 after "Disconnected in IDLE" I get following Error: Nov 12 19:49:51 mini1 dovecot: IMAP(wolfgang): Disconnected in IDLE Nov 12 19:49:51 mini1 dovecot: IMAP(wolfgang): file ioloop.c: line 22 (io_add): assertion failed: (fd >= 0) Nov 12 19:49:51 mini1 dovecot: child 1301 (imap) killed with signal 6 dovecot is running with Mac OS 10.4.8 (PowerPC), Mailbox Format

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 7 Aug 2014, Ben Johnson wrote: > On 8/7/2014 11:14 AM, Steffen Kaiser wrote: >> one idea: http://www.tldp.org/LDP/abs/html/exitcodes.html >> >> exit code 134 would be in bash's meaning (if this website is >> correct all) some program died off signal 6. This would be Abort in >> Linux. >> >>

> On 1 Jul, 2016, at 10:52, Timo Sirainen <tss at iki.fi> wrote: > > On 01 Jul 2016, at 19:39, Adam Weinberger <adamw at adamw.org> wrote: >> >> Hi, >> >> 2.2.25 crashes on FreeBSD with a kqueue-related message. I see references to something similar (http://www.dovecot.org/list/dovecot/2012-February.txt) from a couple years ago. >> >> I

Don't remember if I already wrote about this. But ran into it tonibhg again. Logwatch as distributed with CentOS expects yum log files in different format. As result, logwatch will not report anything. The patch is really simple (and attached). Hopefully it'll be part of 4.3 (if not sooner). The upstream is not likely to patch it, since they don't distribute yum at all.

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc13.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc13.tar.gz.sig There's always time for one more release candidate. :) I was planning on releasing v1.1.0 a couple of minutes before summer solstice (23:59 UTC according to Wikipedia). Maybe it'll bring luck to the release. :) - mbox: Fixed a crash when adding a new X-IMAPbase:

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc13.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc13.tar.gz.sig There's always time for one more release candidate. :) I was planning on releasing v1.1.0 a couple of minutes before summer solstice (23:59 UTC according to Wikipedia). Maybe it'll bring luck to the release. :) - mbox: Fixed a crash when adding a new X-IMAPbase:

http://dovecot.org/releases/dovecot-1.0.rc13.tar.gz http://dovecot.org/releases/dovecot-1.0.rc13.tar.gz.sig I'll just keep on making new releases now whenever something important is fixed. Hopefully there shouldn't be many left anymore. Most of the bugs fixed in this release were found by stress testing with my imaptest tool (http://dovecot.org/tools/imaptest.c). If you're interested

http://dovecot.org/releases/dovecot-1.0.rc13.tar.gz http://dovecot.org/releases/dovecot-1.0.rc13.tar.gz.sig I'll just keep on making new releases now whenever something important is fixed. Hopefully there shouldn't be many left anymore. Most of the bugs fixed in this release were found by stress testing with my imaptest tool (http://dovecot.org/tools/imaptest.c). If you're interested

Here's a diff to call WSAWaitForMultipleEvents() repeatedly to check for events other than the first one returned. I've also added a map of io_t to events[] index so avoid the need for splay_search(). The value of event_count will change if a callback adds an event so we need to handle that. I've added a generation number to the splay tree head that gets incremented by io_del().

I think I'll just start making new releases whenever I've fixed something important. You'll have a while to report more bugs and then I'll make rc13 release, maybe in about 5 hours or maybe tomorrow. I updated already the nightly snapshot if you want to test the upcoming rc13. Changes so far: + deliver: If we're executing as a normal system user, get the HOME environment

Hello, I've installed dovecot-1.0.rc13 on FreeBSD-6.1 with LDA support. But I didn't found the /var/run/dovecot/auth-master file on my system. I need this file for the protocol lda { ... auth_socket_path = /var/run/dovecot-auth-master ... } settings in the /usr/local/etc/dovecot.conf. Does anyone has an idea? PS: On a older installation (dovecot-1.0.rc7) the file exists and

Hello, For those interested, I have released the NHW v0.3.0-rc13 new version. I am still continuing to fine-tune the nhw_kernel weights.This new version has then more precision and a better visual quality. More at: http://nhwcodec.blogspot.com/ Cheers, Raphael -------------- next part -------------- An HTML attachment was scrubbed... URL: