similar to: ioloop.c panic

Hi, still using 2.2.9, I've two directors, and these directors use both IPv4/IPv6 addresses. `host directors.<domain>` returns one A and AAA for each of the two directors: directors.<domain> has address 149.x.y.96 (director1) directors.<domain> has address 149.x.y.97 (director2) directors.<domain> has IPv6 address

On 13 Oct 2015, at 22:31, Heiko Schlittermann <hs at schlittermann.de> wrote: > > Hi, > > still using 2.2.9, I've two directors, and these directors > use both IPv4/IPv6 addresses. > > `host directors.<domain>` returns one A and AAA for each > of the two directors: > > directors.<domain> has address 149.x.y.96 (director1)

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

Hi Timo, Upgraded to 2.0.14 last night for the director-related features and I noticed an oddity in the logs: Sep 28 09:53:21 director2 dovecot: master: Warning: service(ipc): client_limit reached, client connections are being dropped Sep 28 09:53:56 director1 dovecot: master: Warning: service(ipc): client_limit reached, client connections are being dropped Sep 28 09:54:23 director2 dovecot:

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

Hi, I've almost finished my new director based setup, but in the first test I discovered that imap and lmtp connections were not always being proxied to the same server. After some research now I think that the main problem is that in imap connections users connect as 'username' while lmtp connections are as 'username at mailserver'. In my current setup I receive mail via

pop3-login process have some error like that log: dovecot: pop3-login: file ioloop.c: line 22 (io_add): assertion failed: (fd >= 0) dovecot: child 4648 (login) killed with signal 6 Any idea ? Thanks -- Net4all S.A. Dominique Feyer Administrateur Syst?me Ch. de la Colline 5bis CH-1007 Lausanne dfeyer at net4all.ch

Is there a specific order in which one has to add servers to director_mail_servers, Let's say I have 20 loadbalanced director servers (I dont, but for arguments sake). I want to add 5 servers to director_mail_servers. If I do this by restarting each director server 1 by 1 with an updated conf, it seems the 5 new servers dont get added. Or at least I dont get what makes it work eventually.

When Dovecot is in proxy mode, the client sends along the original connection endpoints in an ID command. Is there any chance 'doveadm who' could use this to display the original connection source? As it currently stands, all I see is a bunch of connections from the proxy. Thanks! --- Brandon 'Brad' Davidson Virtualization Systems Administrator University of Oregon Information

I'm a little confused about how public namespaces work with subscriptions. If I set subscriptions=no and subscribe to the folders, the subscription entries go into the user's private subscription file and that's fine. However, I am unable to pull their status with the LIST-EXTENDED extension. Normal listing works OK: A0004 LIST "" "*" RETURN (STATUS (MESSAGES

Hello, I'm using dovecot 2.2.9 and a director/backend setup. On the director I've the LMTP in proxy mode, mapping the users to one of the backends. The backends to quota check and return the OverQuota message already at RCPT TO time. Here is what I typed, connected to the director Connection to director1 2525 port [tcp/*] succeeded! 220 director1.rz.hs-example.de Dovecot

Dear all, We would like to setup, if possible, for example: We have 4 example groups, we various users in those groups: Directors director1,director2 Support manager1,support1,support2,support3 Enquiries manager2,enquiry1,enquiry2,enquiry3 Accounts manager3, accounts1,account2 Shared Mailboxes: Support: Support, user1, user2, user3 Accounts: Directors, Support So basically, we want 2

Hello, i have a setup with two director servers pointing to two backends. I don't care that much for load balancing, my main goal is high availability. CRAM-MD5 auth is working fine if I connect directly to the backends, but the director only supports AUTH=PLAIN because of the static passdb. director config: > passdb { > driver = static > args = nopassword=y proxy=y > } >

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:

Heiko Schlittermann <hs at schlittermann.de> (Mi 14 Okt 2015 00:10:50 CEST): > Timo Sirainen <tss at iki.fi> (Di 13 Okt 2015 23:49:20 CEST): > ? > > > > Proxying in general does check that hostname matches the SSL certificate, because both the hostname and IP address are sent to login process. So it should work in a way that host=<hostname> and

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

Hello, ioloop->highest_fd is used by ioloop-select.c only, so its handling can be moved out of generic ioloop code. Attached patch (agains -test35) does exactly this. Please consider applying. Best regards. -- Andrey Panin | Linux and UNIX system administrator pazke at donpac.ru | PGP key: wwwkeys.pgp.net -------------- next part -------------- diff -urpNX /usr/share/dontdiff -x Makefile

Hi I'm doing: doveadm force-resync -S director1:1234 -A "*" The director gives this error: Jul 06 16:17:29 auth: Error: Trying to iterate users, but userdbs don't support it Jul 06 16:17:29 doveadm: Error: User listing returned failure Jul 06 16:17:29 doveadm: Error: Failed to iterate through some users The director has "iterate_query" set -- Tom

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