similar to: Upgrade 2.2.27 to 2.3.9.2: master(imap): net_connect_unix(imap) failed: Resource temporarily unavailable

Displaying 20 results from an estimated 4000 matches similar to: "Upgrade 2.2.27 to 2.3.9.2: master(imap): net_connect_unix(imap) failed: Resource temporarily unavailable"

2020 Jan 14
0
Upgrade 2.2.27 to 2.3.9.2: master(imap): net_connect_unix(imap) failed: Resource temporarily unavailable
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:
2020 Jan 07
0
Upgrade 2.2.27 to 2.3.9.2: master(imap): net_connect_unix(imap) failed: Resource temporarily unavailable
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
2020 Jan 08
2
Upgrade 2.2.27 to 2.3.9.2: master(imap): net_connect_unix(imap) failed: Resource temporarily unavailable
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
2020 Jan 09
2
Upgrade 2.2.27 to 2.3.9.2: master(imap): net_connect_unix(imap) failed: Resource temporarily unavailable
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)
2020 Jan 09
1
Upgrade 2.2.27 to 2.3.9.2: master(imap): net_connect_unix(imap) failed: Resource temporarily unavailable
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
2014 Feb 25
4
Dovecot upgrade 1 to 2 on Debian Squeeze : broken /var/run/dovecot
Hi, I just upgraded from version 1 to version on Debian Squeeze using their backports. Like I expected my dovecot1 config had to be converted using doveconf and this I did. However, I see problems with files inside directory: drwxr-xr-x 4 dovenull root 4096 Feb 25 20:35 /var/run/dovecot All of them were created owned by root:root rw. I tried to changed, for example : chown postfix:dovecot
2019 Mar 08
3
imap-hibernate not working
Hi, I follow different setup instructions and I can't make imap-hibernate work. I've tried vmail and dovecot as users, tried to set mode to 0666, without success. I'm using FreeBSD 11.2. Is imap-hibernate compatible with FreeBSD 11.2? My operational system: # uname -v FreeBSD 11.2-RELEASE-p9 #0: Tue Feb 5 15:30:36 UTC 2019 root at
2020 Jan 09
0
Upgrade 2.2.27 to 2.3.9.2: master(imap): net_connect_unix(imap) failed: Resource temporarily unavailable
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 >
2020 Jan 08
2
Upgrade 2.2.27 to 2.3.9.2: master(imap): net_connect_unix(imap) failed: Resource temporarily unavailable
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,
2013 Jun 12
1
Permission denied / missing +r perm
I have postfix configured to deliver mail to dovecot over lmtp into a mailbox that then is accessed over imap. The imap server is running as the user "mail". Whenever I run "postfix flush" I get in mail.log: > Jun 12 05:37:45 li212-205 dovecot: lmtp(21288): Connect from local > Jun 12 05:37:45 li212-205 spamd[18173]: prefork: child states: II > Jun 12 05:37:45
2020 Jan 08
2
Upgrade 2.2.27 to 2.3.9.2: master(imap): net_connect_unix(imap) failed: Resource temporarily unavailable
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
2020 Jan 08
0
Upgrade 2.2.27 to 2.3.9.2: master(imap): net_connect_unix(imap) failed: Resource temporarily unavailable
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
2015 Aug 25
2
IMAP hibernate feature committed
* Timo Sirainen <tss at iki.fi> 2015.08.25 17:28: > >> ==> /var/log/dovecot/dovecot.log <== > >> Aug 25 09:42:07 nihlus dovecot: imap(tlx at leuxner.net): Error: net_connect_unix(/var/run/dovecot/imap-hibernate) failed: Permission denied > >> Aug 25 09:42:07 nihlus dovecot: imap(tlx at leuxner.net): Error: Couldn't hibernate imap client: Couldn't
2015 Aug 26
5
IMAP hibernate feature committed
* Timo Sirainen <tss at iki.fi> 2015.08.25 22:21: > There's no good default setting here. It depends on your userdb settings and/or mail_uid setting. So for example if your imap processes are running as vmail user, you should set service imap-hibernate { unix_listener imap-hibernate { user = vmail } }. Then again if you are using system users (or otherwise multiple UIDs) it gets more
2012 Dec 18
6
dovecot index errors since 2.1.12
Hi, After upgrading to dovecot 2.1.12, I see a lot of these errors: # 2.1.12: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-279.14.1.el6.x86_64 x86_64 CentOS release 6.3 (Final) # Filesystem: ext4 with mdbox storage Dec 10 15:21:04 mail dovecot: imap(user at example.org): Error: Cached message size smaller than expected (5010 < 8192) Dec 10 15:21:04 mail dovecot: imap(user at example.org):
2012 Aug 31
1
New log entries with 2.0.19?
I just upgraded my Ubuntu server from 11.10 to 12.04.1 and that upgraded Dovecot to 2.0.19. For some reason I'm getting a lot more (5 times) disconnect in IDLE and inactivity time outs. I'm using only IMAP with two users. Both users access the server from multiple devices, phone, tablet and desktop computer. I had previously set the max_userip_connections to 20 and rarely got the
2011 Jan 12
2
Problem after migration dovecot 1.2 -> dovecot 2.0
I have migrated from dovecot 1.2 to dovecot 2.0. When I connect via telnet to 110 port of the dovecot server the client hangs: telnet 192.168.4.80 110 Trying 192.168.4.80... /Connected to 192.168.4.80. Escape character is '^]'./ In syslog I got the following error: /Jan 12 12:14:44 buzon dovecot: imap-login: Error: auth: connect(login) in directory / failed: Permission denied
2018 Oct 19
2
imap-hibernate returned failure: Failed to parse client input: Invalid peer_dev_minor value
Yes, After I changed mode and user/group Oct 18 19:17:50 server dovecot: imap(email at example.com)<57613><VVXuZ4N4avOASO/q>: Error: kevent(-1) for notify remove fail ed: Bad file descriptor Oct 18 19:17:50 server dovecot: imap(email at example.com)<57613><VVXuZ4N4avOASO/q>: Error: close(-1) for notify remove failed: Bad file descriptor Oct 18 19:17:50 server dovecot:
2010 Nov 21
2
dovecot/imap-login TLS?
# ps auxwww|egrep -i imap-login dovenull 11879 1.4 0.9 83484 77656 ? S Nov20 19:12 dovecot/imap-login [822 connections (822 TLS)] What exactly is TLS in this context? All connections from imap -> imap-login? All clients connecting to an imap process? -- Ralf Hildebrandt Gesch?ftsbereich IT | Abteilung Netzwerk Charit? - Universit?tsmedizin Berlin Campus Benjamin Franklin
2012 Jun 14
1
disable_plaintext_auth = no as no effect on IMAP/POP3 logins
Hello In my installation the disable_plaintext_auth does not appear to take effect. I can see that the value is correct using doveconf -a but it doesn't change anything. Whenever attempting to log in using IMAP I get this: * BAD [ALERT] Plaintext authentication not allowed without SSL/TLS, but your client did it anyway. If anyone was listening, the password was exposed. ls NO