similar to: "pipe() failed: Too many open files"

hi, do somebody tell me, where i could find information about samba restrictions compared with Windows Server. I' m trying to write a small paper for school, which describe a comarison between samba and Windows Server. I heard for example, that 1-Samba is not adapted for great nets? 2-Samba has not a "system management server" like windows? 3-Remote Procedure Calls (RPCs) has been

Hi all! Do anybody has a full working environment using externip on an asterisk box behind a nat? I tried with two diferent boxes (Elastix-1.4.24 e Trixbox-1.4.22-3)and the asterisk do not replace neither contact, neither sdp headers info with the externip informed on sip.conf general parameters. I used these two statements: externip=XXX.XXX.XXX.XXX localnet=192.168.200.0/255.255.255.0 Do

I rewrote much of the kqueue code since the old code didn't handle properly the case when both input and output I/O handlers were added to the same file descriptor with different callbacks. This is done commonly in Dovecot, so I'm wondering why more people didn't complain about problems with it.. :) I don't anyway have access to any BSDs so the code is completely untested. Please

Hi, We have a issue with a server pretty much just running dovecot, there's about 250gb of maildirs which has about 200 simultaneous connections to it running on freebsd 7. The machine has stayed up for about 8 days before it panics but sometimes panics after about 24 hours. We are running a PAE kernel (with ULE scheduler) as the machine has 2 (4 core processors) and 8gb of ram, dovecot is

A few weeks back I upgraded my mail server to -STABLE from a 4.2-STABLE incarnation that had been running for years. Part of recompiling everything on the box involved disassociating my use of the sendmail port I was using and to use the base sendmail in -STABLE. -STABLE builds with libmilter, so I simply recompiled one of my milter clients with the milter headers, objs, etc that were produced

Hi, I would like to submit the attached patch. It implements IO loop using FreeBSD's kqueue/kevent syscalls. It is based on snapshot of CVS HEAD as of 2005-12-12. I could only give it limited testing on FreeBSD 5.4 but it works fine so far. Vaclav Haisman -------------- next part -------------- diff -rN -u old-dovecot-cvs/autogen.sh new-dovecot-cvs/autogen.sh ---

Apparently Dovecot with kqueue ioloop enabled causes random crashes in FreeBSD 9.1. Anyone else noticed something like that? I'm wondering if Dovecot's kqueue code has a bug somewhere (I can't find it) or could it be that FreeBSD itself has a bug? Anyway it seems to be returning events for filters that have already been removed.

dovecot: Nov 24 12:49:06 Panic: IMAP(user): file ioloop-notify- kqueue.c: line 66 (event_callback): assertion failed: (io->refcount == 1) dovecot: Nov 24 12:49:06 Error: IMAP(user): Raw backtrace: 2 imap 0x0000000100068e82 default_fatal_finish + 41 -> 3 imap 0x0000000100068eed i_syslog_fatal_handler + 0 -> 4 imap 0x0000000100068687 i_info + 0 -> 5 imap

Sorry if this is a repeat query. I am running dovecot 1.0.2 under NetBSD/i386 (3.1 and 4.0ish). I use maildirs, and deliver into them with procmail. For clients I use Gnus (CVS head) mostly and thunderbird, and also the gnome mail-notification status applet (4.0). Gnus fixed a bug in the last few months where exiting a group didn't unselect the folder and thus didn't necessarily push

Hi, I've seen some chatter on NFS boards about kqueue being more reliable than inotify when used in NFSv3 and NFSv2. The chatter is a bit old so I don't know if it is true anymore. Anyone have pro/con experience with dovecot on the inotify/kqueue question when using NFS storage? I realize that kqueue is probably a bit slower and causes some delay with IDLE. Also, it may not really

I posted some questions a few months back and received lots of great help in getting my dovecot/postfix/LDAP setup working. Initially, I ran into the pipe failed too many open files error. I am running this setup on OpenBSD/sparc64 4.1-stable and so I put dovecot in its own class and upped the maxfiles setting for that class. This was back with dovecot 1.0 and everything worked fine. I

So, apparently the original kqueue code was working fine after all, although it was much more complex than it really needed to be. So, this time there's a really simple and pretty kqueue implementation: http://dovecot.org/nightly/dovecot-latest.tar.gz Tested that it seems to work with FreeBSD. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc

On 16-07-03 03:30:36, Timo Sirainen wrote: > On 02 Jul 2016, at 03:30, Adam Weinberger <adamw at adamw.org> wrote: > > > >>> Jul 1 10:07:27 imap dovecot: master: Panic: kevent(EV_ADD, READ, 54) failed: Bad file descriptor > >>> > >>> It's not dumping core, and I get the message even with "protocols =" > >>> >

Hello Dovecot, Version: dovecot-1.0-test61 OS: FreeBSD 5.3-RELEASE i386 Client: Mozilla Thunderbird 1.0 (on WinXP, FreeBSD & Mac OS X) The maillog entries concerning me: - Jan 30 16:16:37 venus dovecot: imap-login: Login: user [10.6.8.3] Jan 30 16:16:37 venus dovecot: imap-login: couldn't remove filter with kqueue: Bad file descriptor Jan 30 16:16:37 venus dovecot: IMAP(user):

> 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

Hey, I noticed that there was an ioloop "module" (if we can call it that) for select and poll and decided to add one for kqueue (aka kevent) BSDs high performance descriptor multiplexing API. I haven't done any of the configure glue stuff but the code is complete and works well. kqueue is available on all recent versions of FreeBSD, NetBSD, OpenBSD and Darwin (and therefore MacOS

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 get: Jul 1 10:07:27 imap dovecot: master: Panic: kevent(EV_ADD, READ, 54) failed: Bad file descriptor It's not dumping core, and I get the message even with "protocols =" Downgrading back to 2.2.24

Hi, I recently switched from courier imap to dovecot. With courier I had a working IDLE setup that informed me immediately when new mail arrived. With Dovecot it is different, sometimes i get an immediate result but most of the time it takes a rather long time for the notification to return to the client. For testing purposes I set mailbox_idle_check_interval = 1 and i now get the same

Hi to ALL! I have dovecot-1.0r7 installed on FreeBSD 6.1, using kqueue and Maildir (<20 mailboxes, < 0,5 Gb size). Periodically CPU load of imap processes increasing up to 60-80%. Is it normall behavior or not? May be somebody had such kind of problems? -- ? ?????????, ?????? ????? ??? "???????" : ?????????? ??, WEB-?????????? +7 (495) 589 68 81 +7 (926) 575 22 11

i use dovecot 2 under FreeBSD (dovecot2-2.2.15 compiled from ports). tried both with kqueue enabled or not. everything works very fast, EXCEPT fetching big mail. tried multiple clients (thunderbird on windows, alpine on the same server, alpine on other unix server connected by 1Gb/s LAN) and fetching peaks at 1MB/s. NO SSL! could you please point me where to search for a problem. hints: