From: "Clément Lassieur" <clement@lassieur.org>
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: 32631@debbugs.gnu.org
Subject: bug#32631: the Dovecot service stops working
Date: Fri, 07 Sep 2018 14:58:15 +0200 [thread overview]
Message-ID: <87va7hlb14.fsf@lassieur.org> (raw)
In-Reply-To: <87lg8dtsmx.fsf@gmail.com>
Hi Oleg,
Oleg Pykhalov <go.wigust@gmail.com> writes:
> Hello Clément,
>
> Clément Lassieur <clement@lassieur.org> writes:
>
> […]
>
>>>>>> Sometimes the Dovecot service stops working, which is difficult to
>>>>>> notice.
>>>>>
>>>>> When it “stops working”, does the Shepherd service go down? Does “herd
>>>>> status dovecot” shows that it was respawned? Is the dovecot process
>>>>> still around?
>>>>
>>>> The dovecot process is still around, yes. I has happened several times
>>>> already (maybe 5),
>
> Do you mean the warning you posted before?
I meant that my dovecot process stopped working 5 times already.
> --8<---------------cut here---------------start------------->8---
> Sep 4 11:47:12 mail2 dovecot: master: Warning: service(imap-login): process_limit (100) reached, client connections are being dropped
> --8<---------------cut here---------------end--------------->8---
>
> The ‘dovecot-configuration’ record has a ‘default-process-limit’ which
> is setted to 100 by default. Could you try to increase it?
Well, I can, but that wouldn't fix the problem. Two dovecot clients
shouldn't consume 100 processes.
> Also a ‘process_limit’ configuration string is described on Dovecot Wiki.
>
> https://wiki.dovecot.org/LoginProcess
Thank you very much for that information, I'll have a look.
Clément
next prev parent reply other threads:[~2018-09-07 12:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 10:27 bug#32631: the Dovecot service stops working Clément Lassieur
2018-09-06 9:11 ` Ludovic Courtès
2018-09-06 12:49 ` Clément Lassieur
2018-09-06 20:31 ` Ludovic Courtès
2018-09-06 21:05 ` Clément Lassieur
2018-09-07 12:10 ` Oleg Pykhalov
2018-09-07 12:58 ` Clément Lassieur [this message]
2018-09-26 16:53 ` Clément Lassieur
2018-11-10 18:33 ` Clément Lassieur
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87va7hlb14.fsf@lassieur.org \
--to=clement@lassieur.org \
--cc=32631@debbugs.gnu.org \
--cc=go.wigust@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.