> On 17/08/2022 00:57 EEST Joseph Tam wrote:
>
>
> From: Aki Tuomi
>
> > The *default* configuration for service config is usually just fine.
>
> > Is there some reason you decided to modify it in first place?
>
>
> Are you asking me, or the OP?
>
>
> I guess the blunt answer is
From: Aki Tuomi
> The *default* configuration for service config is usually just fine.
> Is there some reason you decided to modify it in first place?
Are you asking me, or the OP?
I guess the blunt answer is ignorance on my part. However, I pointed
out that the docs about this setting is
As
https://doc.dovecot.org/configuration_manual/service_configuration/#client-limit
says, 0 means to apply default_client_limit, which defaults to 100.
Aki
> On 16/08/2022 20:11 EEST fil...@digirati.com.br
> wrote:
>
>
> currently the client_limt is at zero, and I believe this is
currently the client_limt is at zero, and I believe this is unlimited
service config {
chroot =
client_limit = 0
drop_priv_before_exec = no
executable = config
extra_groups =
group =
idle_kill = 1 mins
privileged_group =
process_limit = 0
process_min_avail = 16
protocol =
Can you try increasing client_limit for service config, to maybe, say, 1000?
There should be no reason to have lots of multiple config processes, so it
sounds more like the client limit is being reached.
Aki
> On 16/08/2022 19:03 EEST fil...@digirati.com.br
> wrote:
>
>
> The only thing I
The only thing I had initially configured was vsz_limit, but as the
number of clients grew, the number of dovecot/config processes grew, and
with that I added idle_kill and service_count to try to minimize the use
of ram memory
In dovecot 2.2.33.2 , another server, has the same amount of
> On 16/08/2022 03:40 EEST Joseph Tam wrote:
>
>
> > I'm having strange behavior in dovecot 2.3.16.
> > It's opening dozens of dovecot/config process and consuming all server
> > memory. Normally each process consumes between 700Mb and 1Gb of ram.
> >
> > Would anyone have an idea about
> I'm having strange behavior in dovecot 2.3.16.
> It's opening dozens of dovecot/config process and consuming all server
> memory. Normally each process consumes between 700Mb and 1Gb of ram.
>
> Would anyone have an idea about this?
>
> service config {
>vsz_limit = 2048M
>idle_kill =
> "filipe@digirati" == filipe@digirati com br
> writes:
filipe@digirati> I tested the suggestion to decrease the service_count and the
accounts
filipe@digirati> stopped logging in, then I gradually increased it to 500, and
now it's
filipe@digirati> working. But the dovecot/config
Hello,
I tested the suggestion to decrease the service_count and the accounts
stopped logging in, then I gradually increased it to 500, and now it's
working. But the dovecot/config processes are still being created, there
has been no change for the better.
Now I have an error constantly
> "filipe@digirati" == filipe@digirati com br
> writes:
filipe@digirati> I'm having strange behavior in dovecot 2.3.16.
filipe@digirati> It's opening dozens of dovecot/config process and consuming
all server
filipe@digirati> memory. Normally each process consumes between 700Mb and 1Gb
for what's it is worth
i am not running any vsize on the config
service config {
unix_listener config {
user = vmail
}
}
i'm just running defaults
i do use vsz_limit elsewhere main to curve the replication processes ??
never had an issue 2.3.17 / 18 / 19
never used 16 (fyi)
12 matches
Mail list logo
