similar to: Resource temporarily unavailable

We recently switched over mail servers to one running dovecot and postfix on RedHat Enterprise 6. The mail store is NFS on a NetApp filer, the index files are on local disk. We have about 6000 total active users, though not all of them access the system at the same time. All goes well for a while, then we start seeing errors like this in the log: dovecot: imap-login: Error:

On 08/01/2020 10:49, Eirik Rye wrote: > [...] In any case, the biggest issue is the one described in the original message in this thread, where logins are periodically failing for many for users: 2020-01-08T10:54:57.436400+01:00 imap dovecot: imap-login: Error: master(imap): net_connect_unix(imap) failed: Resource temporarily unavailable - http://wiki2.dovecot.org/SocketUnavailable

Hi, After upgrading Dovecot from version 2.2.27 to 2.3.9.2, we are sporadically seeing lots of these errors in the error log on many of our servers: imap-login: Error: master(imap): net_connect_unix(imap) failed: Resource temporarily unavailable - http://wiki2.dovecot.org/SocketUnavailable The issue is causing significant delays and/or timeouts on login. From what I can tell, this

On 07 Jan 2020, at 07:15, Dovecot Mailing List <dovecot at dovecot.org> wrote: > dovecot: master: Warning: service(imap-login): process_limit (16) reached, client connections are being dropped Is this an actual problem? Most client connections are idle, so I doubt if the occasional drop is noticed at all. Also, why a limit of 16? Have you tried, oh, 160 instead? -- "Master,

We are unfortunately still seeing a lot of these errors once the machine reaches a high number of concurrent users/logins (just below 20k simultaneous IMAP connections on a powerful 24 core machine with 128GB RAM): 2020-01-14T09:18:58.661349+01:00 dovecot: imap-login: Warning: net_connect_unix(imap) succeeded only after retrying - took 140330 us 2020-01-14T09:18:58.854692+01:00 dovecot:

Can you enable 'verbose_proctitle=yes' and maybe compare with ss -tp output? Aki > On 08/01/2020 11:58 Eirik Rye <rye at domeneshop.no> wrote: > > > On 08/01/2020 10:49, Eirik Rye wrote: > > [...] > > In any case, the biggest issue is the one described in the original > message in this thread, where logins are periodically failing for many > for

While I not certain that this is related to the problem we are experiencing, we are also (more rarely) seeing these: dovecot: master: Warning: service(imap-login): process_limit (16) reached, client connections are being dropped imap-login was set to process_limit=16, client_limit=1250 (for a total of 20000 concurrent clients) on 2.2.27. We never had any issues with this then. I tried

Uh. It's not actually supported to access same user concurrently from two servers even if you are using NFS. It will cause problems. You should use dovecot director or some other arrangement to make sure this does not happen. Aki > On 09/01/2020 16:56 Eirik Rye <rye at domeneshop.no> wrote: > > > As a workaround for the titular issue, I have tried enabling the >

Yes, I realize this. That is why we are introducing the directors to the cluster. We are also working on doing Dovecot LDA/LMTP delivery, to improve Dovecot's ability to react to new messages. Currently we are dropping email directly into the Maildir through other facilities, which works -fine-. I realize however that IDLE is most likely not working properly with

The load on our machines has gotten too high, so I started to see log messages that directed me to look at this page for config changes: https://pad.riseup.net/redirect#http%3A//wiki2.dovecot.org/SocketUnavailable One of the things I wanted to do on that page was to set the: service imap { service_count = 100 } but when I added that to the service imap block, and restarted dovecot, I see this

As a workaround for the titular issue, I have tried enabling the "imap-hibernate" service on a couple of servers to reduce the number of running imap processes. Since ~50-60% of clients are in IDLE at any one time, this allows us to reduce the number of running imap processes to less than half of what it was. After this I have yet to see the "net_connect_unix(imap)

> On 16/11/2020 13:44 ????? <morikawa-k6 at itec.hankyu-hanshin.co.jp> wrote: > > > We have upgraded dovecot from 2.0.9 (centos6) to 2.2.36 (centos8). > > If more than 1000 users log in, the following error will occur. > ------------------------- > Nov 16 11:33:00 xxxxxxxx dovecot[1361]: imap-login: Error: master(imap): > net_connect_unix(imap) failed: Resource

On 08/01/2020 11:09, Aki Tuomi wrote: > Can you enable 'verbose_proctitle=yes' and maybe compare with ss -tp output? Thanks for the response! What exactly did you want to compare? `ss -tp` does not appear to show cmdline/process title. I enabled it for one server, but will have to wait for users to reconnect and for the issue to reappear there. In the meantime, on another server

On 08/01/2020 01:47, @lbutlr wrote: > On 07 Jan 2020, at 07:15, Dovecot Mailing List <dovecot at dovecot.org> wrote: >> dovecot: master: Warning: service(imap-login): process_limit (16) reached, client connections are being dropped > > Is this an actual problem? Most client connections are idle, so I doubt if the occasional drop is noticed at all. I assume it would mean

Hello everyone, we have a huge problem with dovecot and IMAP connections. we got the following errors: 39665 today dovecot: imap-login: Error: master(imap): net_connect_unix(imap) failed: Resource temporarily unavailable - http://wiki2.dovecot.org/SocketUnavailable (client-pid=29066, client-id=1755, rip=IP, created 562 msecs ago, received 0/4 bytes) we thinks this may be a problem with

You need to configure stats service client limit and imap service client limit. Those are different services than imap-login service. Aki > On 17/11/2020 01:28 ????? <morikawa-k6 at itec.hankyu-hanshin.co.jp> wrote: > > > Aki-san > > I have already seen that page. > Is the setting method wrong? > > Is there any other tuning point? > > morikawa >

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:

With proctitles below. Strangely, Dovecot is reporting 12679 imap-login sockets in "pre-login" state, which is about 50% more than there are active TCP connections to the server (8271, of which 7546 are in "imap-login" process according to `ss -tp`). On another server, not currently experiencing this issue, the number of TCP sockets appears to more closely match the

I have version 2.0.0 and upgraded to 2.0.2 and after - this is happend: Raw backtrace: /opt/dovecot2/lib/dovecot/libdovecot.so.0 [0xb7e3425e] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0 [0xb7e342b5] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0 [0xb7e338d6] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0 [0xb7e31cb1] -> dovecot/pop3(client_handle_input+0x8e) [0x804be7e] ->

I did some more optimisation. Most performance hit in Dovecot do "for loop" in string operations. In one case (in message-parser.c) "for loop" has another "for" inside with the same variable used as iterator. This case is very hard to optimise by compiler. I do changes only in top functions listed in oprofile. Maybe I do more in future. Code was analysed and