Re: dovecot/config processes open, and consuming all memory
> 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 ignorance on my part. However, I pointed
>
> out that the docs about this setting is somewhat misleading -- it's used
>
> to limit any potential memory leaks for long-lived processes by ensuring
>
> it terminates periodically.
>
>
> I read this and thought to myself "this is a good thing to do", without
>
> realizing that it would have the opposite effect as lingering clients
>
> could delay service termination indefinitely. The side effect is many
>
> new processes are spawned to handle new clients, and eventually
>
> the maximum process limit is reached, and chaos ensues.
>
>
> So for services like imap-login and others that can have lingering
>
> clients, the only sensible values for service_limit is {0,1}. If you
>
> set service_limit>1, the asymptotic behaviour is like service_limit=1,
>
> and process_limit would have to be adjusted accordingly.
>
>
> The docs can explain this rather wordy and subtle explanation of
>
> service_limit, or service_limit can be constrained to values {0,1} so that
>
> others don't blunder along the same path I did.
>
>
> Joseph Tam
Thanks for the feedback, and sharing this.
Aki
Re: dovecot/config processes open, and consuming all memory
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 somewhat misleading -- it's used
to limit any potential memory leaks for long-lived processes by ensuring
it terminates periodically.
I read this and thought to myself "this is a good thing to do", without
realizing that it would have the opposite effect as lingering clients
could delay service termination indefinitely. The side effect is many
new processes are spawned to handle new clients, and eventually
the maximum process limit is reached, and chaos ensues.
So for services like imap-login and others that can have lingering
clients, the only sensible values for service_limit is {0,1}. If you
set service_limit>1, the asymptotic behaviour is like service_limit=1,
and process_limit would have to be adjusted accordingly.
The docs can explain this rather wordy and subtle explanation of
service_limit, or service_limit can be constrained to values {0,1} so that
others don't blunder along the same path I did.
Joseph Tam
Re: dovecot/config processes open, and consuming all memory
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 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 =
> service_count = 100
> type = config
> unix_listener config {
> group =
> mode = 0600
> user =
> }
> user =
> vsz_limit = 2 G
> }
>
> On 16/08/2022 18:06, Aki Tuomi wrote:
> > 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.
Re: dovecot/config processes open, and consuming all memory
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 =
service_count = 100
type = config
unix_listener config {
group =
mode = 0600
user =
}
user =
vsz_limit = 2 G
}
On 16/08/2022 18:06, Aki Tuomi wrote:
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.
Re: dovecot/config processes open, and consuming all memory
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 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 accounts (+
> or -30 thousand) but there is only one dovecot/config process and every
> dovecot does not consume more than 5Gb
>
> On 16/08/2022 06:20, Aki Tuomi wrote:
> >> 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 this?
> >>>
> >>> service config {
> >>> vsz_limit = 2048M
> >>> idle_kill = 60s
> >>> service_count = 1024
> >>> }
> >> Not sure it's related, but if you have service_count not 0 or 1, there
> >> is a strange interaction
> >> with other limits that could cause processes to hang around. My
> >> description of problem
> >>
> >> https://www.mail-archive.com/dovecot%40dovecot.org/msg85850.html
> >>
> >> Your situation is slgihtly different (service not imap_login, and
> >> idle_kill timeout should reduce
> >> lingering processes that caused my problem), but try setting
> >> service_limit to either 0 or
> >> 1 and see if your problem goes away, or gets worse.
> >>
> >> You can also see how many file descriptors are being held by the
> >> config process, and
> >> see the behaviour over time (e.g. monitor /proc/{pid}/fd/*); maybe
> >> that will give you a clue
> >> as to what the config process is doing.
> >>
> >> Joseph Tam
> > The *default* configuration for service config is usually just fine. Is
> > there some reason you decided to modify it in first place?
> >
> > Aki
Re: dovecot/config processes open, and consuming all memory
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 accounts (+
or -30 thousand) but there is only one dovecot/config process and every
dovecot does not consume more than 5Gb
On 16/08/2022 06:20, Aki Tuomi wrote:
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 this?
service config {
vsz_limit = 2048M
idle_kill = 60s
service_count = 1024
}
Not sure it's related, but if you have service_count not 0 or 1, there
is a strange interaction
with other limits that could cause processes to hang around. My
description of problem
https://www.mail-archive.com/dovecot%40dovecot.org/msg85850.html
Your situation is slgihtly different (service not imap_login, and
idle_kill timeout should reduce
lingering processes that caused my problem), but try setting
service_limit to either 0 or
1 and see if your problem goes away, or gets worse.
You can also see how many file descriptors are being held by the
config process, and
see the behaviour over time (e.g. monitor /proc/{pid}/fd/*); maybe
that will give you a clue
as to what the config process is doing.
Joseph Tam
The *default* configuration for service config is usually just fine. Is there
some reason you decided to modify it in first place?
Aki
Re: dovecot/config processes open, and consuming all memory
> 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 this?
> >
> > service config {
> >vsz_limit = 2048M
> >idle_kill = 60s
> >service_count = 1024
> > }
>
> Not sure it's related, but if you have service_count not 0 or 1, there
> is a strange interaction
> with other limits that could cause processes to hang around. My
> description of problem
>
> https://www.mail-archive.com/dovecot%40dovecot.org/msg85850.html
>
> Your situation is slgihtly different (service not imap_login, and
> idle_kill timeout should reduce
> lingering processes that caused my problem), but try setting
> service_limit to either 0 or
> 1 and see if your problem goes away, or gets worse.
>
> You can also see how many file descriptors are being held by the
> config process, and
> see the behaviour over time (e.g. monitor /proc/{pid}/fd/*); maybe
> that will give you a clue
> as to what the config process is doing.
>
> Joseph Tam
The *default* configuration for service config is usually just fine. Is there
some reason you decided to modify it in first place?
Aki
Re: dovecot/config processes open, and consuming all memory
> 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 = 60s
>service_count = 1024
> }
Not sure it's related, but if you have service_count not 0 or 1, there
is a strange interaction
with other limits that could cause processes to hang around. My
description of problem
https://www.mail-archive.com/dovecot%40dovecot.org/msg85850.html
Your situation is slgihtly different (service not imap_login, and
idle_kill timeout should reduce
lingering processes that caused my problem), but try setting
service_limit to either 0 or
1 and see if your problem goes away, or gets worse.
You can also see how many file descriptors are being held by the
config process, and
see the behaviour over time (e.g. monitor /proc/{pid}/fd/*); maybe
that will give you a clue
as to what the config process is doing.
Joseph Tam
Re: dovecot/config processes open, and consuming all memory
> "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 processes are still being
created, there
filipe@digirati> has been no change for the better.
So maybe you can give us more background on this setup. How many
users are you supporting? How many mailboxes? What is your backend
mailbox format? Maybe you need to share your dovecot config as well.
Have you tried upgrading to 2.3.19.1 as well?
So when you say "the accounts stopped logging in" does that mean your
users started having problems logging into the system? Does that mean
IMAP sessions timed out?
filipe@digirati> Now I have an error constantly appearing in the mail.err file
filipe@digirati> Aug 15 14:19:34 box6 dovecot: imap(USER_NAME): Error: Error
reading
filipe@digirati> configuration: read(/run/dovecot/config) failed:
read(size=8192) failed:
filipe@digirati> Interrupted system call - Also failed to read config by
executing
filipe@digirati> doveconf: /run/dovecot/config is a UNIX socket (path is from
CONFIG_FILE
filipe@digirati> environment)
Have you stopped and completely restarted your dovecot setup when you
made the config changes?
filipe@digirati> Aug 15 14:19:34 box6 dovecot: imap(USER_NAME): Error: Error
reading
filipe@digirati> configuration: read(/run/dovecot/config) failed:
read(size=8192) failed:
filipe@digirati> Interrupted system call - Also failed to read config by
executing
filipe@digirati> doveconf: /run/dovecot/config is a UNIX socket (path is from
CONFIG_FILE
filipe@digirati> environment)
filipe@digirati> Aug 15 14:19:34 box6 dovecot: imap(USER_NAME): Error: Error
reading
filipe@digirati> configuration: read(/run/dovecot/config) failed:
read(size=8192) failed:
filipe@digirati> Interrupted system call - Also failed to read config by
executing
filipe@digirati> doveconf: /run/dovecot/config is a UNIX socket (path is from
CONFIG_FILE
filipe@digirati> environment)
filipe@digirati> On 14/08/2022 22:24, John Stoffel wrote:
>>> "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 of ram.
>>
>> filipe@digirati> Would anyone have an idea about this?
>>
>> filipe@digirati> service config {
>> filipe@digirati> vsz_limit = 2048M
>> filipe@digirati> idle_kill = 60s
>> filipe@digirati> service_count = 1024
>> filipe@digirati> }
>>
>> I wonder why you have the service count so high? I'd drop it down, or
>> do you really have 1025 connections in 60 seconds?
>>
>> From the docs:
>>
>>
>> service_count
>>
>> Number of client connections to handle until the process kills
>> itself. 0 means unlimited. 1 means only a single connection is handled
>> until the process is stopped - this is the most secure choice since
>> there’s no way for one connection’s state to leak to the next one. For
>> better performance this can be set higher, but ideally not unlimited
>> since more complex services can have small memory leaks and/or memory
>> fragmentation and the process should get restarted eventually. For
>> example 100..1000 can be good values.
>>
>> So maybe drop it down to 100 for now and see how that works for you.
>>
>>
>> filipe@digirati> pstree
>> filipe@digirati> systemd─┬─ModemManager───2*[{ModemManager}]
>> filipe@digirati> ├─agetty
>> filipe@digirati> ├─cron
>> filipe@digirati> ├─dbus-daemon
>> filipe@digirati> ├─dovecot─┬─anvil
>> filipe@digirati> │ ├─6*[auth]
>> filipe@digirati> │ ├─46*[config]
>> filipe@digirati> │ ├─1212*[imap]
>> filipe@digirati> │ ├─155*[imap-login]
>> filipe@digirati> │ ├─12*[lmtp]
>> filipe@digirati> │ ├─38*[log]
>> filipe@digirati> │ ├─10*[managesieve]
>> filipe@digirati> │ ├─19*[pop3]
>> filipe@digirati> │ ├─3*[pop3-login]
>> filipe@digirati> │ └─18*[stats]
>>
>>
>> filipe@digirati> root 45831 0.0 1.1 774688 752732 ? S 09:31
>> 0:31
>> filipe@digirati> dovecot/config
>> filipe@digirati> root 388792 0.0 1.1 775060 753276 ? S 14:00
>> 0:15
>> filipe@digirati> dovecot/config
>> filipe@digirati> root 510685 0.0 1.1 775384 753604 ? S 15:06
>> 0:20
>> filipe@digirati> dovecot/config
>> filipe@digirati> root 675638 0.0 1.1 775348 753620 ? S 16:56
>> 0:15
>> filipe@digirati> dovecot/config
>> filipe@digirati> root 795375 0.0 1.1 775460 753516 ? S 18:03
>> 0:07
>>
Re: dovecot/config processes open, and consuming all memory
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 appearing in the mail.err file
Aug 15 14:19:34 box6 dovecot: imap(USER_NAME): Error: Error reading
configuration: read(/run/dovecot/config) failed: read(size=8192) failed:
Interrupted system call - Also failed to read config by executing
doveconf: /run/dovecot/config is a UNIX socket (path is from CONFIG_FILE
environment)
Aug 15 14:19:34 box6 dovecot: imap(USER_NAME): Error: Error reading
configuration: read(/run/dovecot/config) failed: read(size=8192) failed:
Interrupted system call - Also failed to read config by executing
doveconf: /run/dovecot/config is a UNIX socket (path is from CONFIG_FILE
environment)
Aug 15 14:19:34 box6 dovecot: imap(USER_NAME): Error: Error reading
configuration: read(/run/dovecot/config) failed: read(size=8192) failed:
Interrupted system call - Also failed to read config by executing
doveconf: /run/dovecot/config is a UNIX socket (path is from CONFIG_FILE
environment)
On 14/08/2022 22:24, John Stoffel wrote:
"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
of ram.
filipe@digirati> Would anyone have an idea about this?
filipe@digirati> service config {
filipe@digirati> vsz_limit = 2048M
filipe@digirati> idle_kill = 60s
filipe@digirati> service_count = 1024
filipe@digirati> }
I wonder why you have the service count so high? I'd drop it down, or
do you really have 1025 connections in 60 seconds?
From the docs:
service_count
Number of client connections to handle until the process kills
itself. 0 means unlimited. 1 means only a single connection is handled
until the process is stopped - this is the most secure choice since
there’s no way for one connection’s state to leak to the next one. For
better performance this can be set higher, but ideally not unlimited
since more complex services can have small memory leaks and/or memory
fragmentation and the process should get restarted eventually. For
example 100..1000 can be good values.
So maybe drop it down to 100 for now and see how that works for you.
filipe@digirati> pstree
filipe@digirati> systemd─┬─ModemManager───2*[{ModemManager}]
filipe@digirati> ├─agetty
filipe@digirati> ├─cron
filipe@digirati> ├─dbus-daemon
filipe@digirati> ├─dovecot─┬─anvil
filipe@digirati> │ ├─6*[auth]
filipe@digirati> │ ├─46*[config]
filipe@digirati> │ ├─1212*[imap]
filipe@digirati> │ ├─155*[imap-login]
filipe@digirati> │ ├─12*[lmtp]
filipe@digirati> │ ├─38*[log]
filipe@digirati> │ ├─10*[managesieve]
filipe@digirati> │ ├─19*[pop3]
filipe@digirati> │ ├─3*[pop3-login]
filipe@digirati> │ └─18*[stats]
filipe@digirati> root 45831 0.0 1.1 774688 752732 ? S 09:31
0:31
filipe@digirati> dovecot/config
filipe@digirati> root 388792 0.0 1.1 775060 753276 ? S 14:00
0:15
filipe@digirati> dovecot/config
filipe@digirati> root 510685 0.0 1.1 775384 753604 ? S 15:06
0:20
filipe@digirati> dovecot/config
filipe@digirati> root 675638 0.0 1.1 775348 753620 ? S 16:56
0:15
filipe@digirati> dovecot/config
filipe@digirati> root 795375 0.0 1.1 775460 753516 ? S 18:03
0:07
filipe@digirati> dovecot/config
filipe@digirati> root 798754 0.2 1.1 775592 753712 ? S 18:05
0:30
filipe@digirati> dovecot/config
filipe@digirati> root 1082696 0.2 1.1 774892 753216 ? S 21:10
0:07
filipe@digirati> dovecot/config
filipe@digirati> root 1098433 0.4 1.1 774924 753244 ? S 21:33
0:07
filipe@digirati> dovecot/config
filipe@digirati> root 1109255 0.9 1.1 774924 753344 ? S 21:50
0:07
filipe@digirati> dovecot/config
filipe@digirati> root 1112976 2.0 1.1 774956 753528 ? S 21:57
0:07
filipe@digirati> dovecot/config
filipe@digirati> root 1114137 3.0 1.1 775028 753308 ? S 21:59
0:07
filipe@digirati> dovecot/config
filipe@digirati> root 1115382 5.4 1.1 774924 753496 ? S 22:01
0:06
filipe@digirati> dovecot/config
filipe@digirati> root 1883627 0.0 1.1 759120 728832 ? S Aug11
0:07
filipe@digirati> dovecot/config
filipe@digirati> root 1889705 0.0 1.8 1251460 1221872 ? S Aug11
0:11
filipe@digirati> dovecot/config
filipe@digirati> root 1895022 0.0
Re: dovecot/config processes open, and consuming all memory
> "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
of ram.
filipe@digirati> Would anyone have an idea about this?
filipe@digirati> service config {
filipe@digirati> vsz_limit = 2048M
filipe@digirati> idle_kill = 60s
filipe@digirati> service_count = 1024
filipe@digirati> }
I wonder why you have the service count so high? I'd drop it down, or
do you really have 1025 connections in 60 seconds?
>From the docs:
service_count
Number of client connections to handle until the process kills
itself. 0 means unlimited. 1 means only a single connection is handled
until the process is stopped - this is the most secure choice since
there’s no way for one connection’s state to leak to the next one. For
better performance this can be set higher, but ideally not unlimited
since more complex services can have small memory leaks and/or memory
fragmentation and the process should get restarted eventually. For
example 100..1000 can be good values.
So maybe drop it down to 100 for now and see how that works for you.
filipe@digirati> pstree
filipe@digirati> systemd─┬─ModemManager───2*[{ModemManager}]
filipe@digirati> ├─agetty
filipe@digirati> ├─cron
filipe@digirati> ├─dbus-daemon
filipe@digirati> ├─dovecot─┬─anvil
filipe@digirati> │ ├─6*[auth]
filipe@digirati> │ ├─46*[config]
filipe@digirati> │ ├─1212*[imap]
filipe@digirati> │ ├─155*[imap-login]
filipe@digirati> │ ├─12*[lmtp]
filipe@digirati> │ ├─38*[log]
filipe@digirati> │ ├─10*[managesieve]
filipe@digirati> │ ├─19*[pop3]
filipe@digirati> │ ├─3*[pop3-login]
filipe@digirati> │ └─18*[stats]
filipe@digirati> root 45831 0.0 1.1 774688 752732 ? S 09:31
0:31
filipe@digirati> dovecot/config
filipe@digirati> root 388792 0.0 1.1 775060 753276 ? S 14:00
0:15
filipe@digirati> dovecot/config
filipe@digirati> root 510685 0.0 1.1 775384 753604 ? S 15:06
0:20
filipe@digirati> dovecot/config
filipe@digirati> root 675638 0.0 1.1 775348 753620 ? S 16:56
0:15
filipe@digirati> dovecot/config
filipe@digirati> root 795375 0.0 1.1 775460 753516 ? S 18:03
0:07
filipe@digirati> dovecot/config
filipe@digirati> root 798754 0.2 1.1 775592 753712 ? S 18:05
0:30
filipe@digirati> dovecot/config
filipe@digirati> root 1082696 0.2 1.1 774892 753216 ? S 21:10
0:07
filipe@digirati> dovecot/config
filipe@digirati> root 1098433 0.4 1.1 774924 753244 ? S 21:33
0:07
filipe@digirati> dovecot/config
filipe@digirati> root 1109255 0.9 1.1 774924 753344 ? S 21:50
0:07
filipe@digirati> dovecot/config
filipe@digirati> root 1112976 2.0 1.1 774956 753528 ? S 21:57
0:07
filipe@digirati> dovecot/config
filipe@digirati> root 1114137 3.0 1.1 775028 753308 ? S 21:59
0:07
filipe@digirati> dovecot/config
filipe@digirati> root 1115382 5.4 1.1 774924 753496 ? S 22:01
0:06
filipe@digirati> dovecot/config
filipe@digirati> root 1883627 0.0 1.1 759120 728832 ? S Aug11
0:07
filipe@digirati> dovecot/config
filipe@digirati> root 1889705 0.0 1.8 1251460 1221872 ? S Aug11
0:11
filipe@digirati> dovecot/config
filipe@digirati> root 1895022 0.0 1.8 1253280 1224284 ? S Aug11
0:11
filipe@digirati> dovecot/config
filipe@digirati> root 1900690 0.0 1.8 1255684 1227528 ? S Aug11
0:12
filipe@digirati> dovecot/config
filipe@digirati> root 1905648 0.0 1.8 1257880 1229912 ? S Aug11
0:12
filipe@digirati> dovecot/config
filipe@digirati> root 1910857 0.0 1.8 1259156 1231552 ? S Aug11
0:12
filipe@digirati> dovecot/config
filipe@digirati> root 1914332 0.0 1.1 764328 736552 ? S Aug11
0:20
filipe@digirati> dovecot/config
filipe@digirati> root 2343896 0.0 1.8 1259472 1231516 ? S Aug11
0:12
filipe@digirati> dovecot/config
filipe@digirati> root 2346351 0.0 1.8 1259472 1231836 ? S Aug11
0:13
filipe@digirati> dovecot/config
filipe@digirati> root 2348559 0.0 1.1 764704 736440 ? S Aug11
0:14
filipe@digirati> dovecot/config
filipe@digirati> root 2445701 0.0 1.1 764276 736540 ? S Aug11
0:19
filipe@digirati> dovecot/config
filipe@digirati> root 2572525 0.0 1.1 764640 736880 ? S Aug11
0:18
filipe@digirati> dovecot/config
filipe@digirati> root 2734251 0.0 1.1 764776 737696 ? S Aug11
0:08
Re: dovecot/config processes open, and consuming all memory
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)
maybe 2048M is insufficent system wide, try increasing 10 1g ?
Happy Friday !!!
Thanks - paul
Paul Kudla
Scom.ca Internet Services
004-1009 Byron Street South
Whitby, Ontario - Canada
L1N 4S3
Toronto 416.642.7266
Main 1.866.411.7266
Fax 1.888.892.7266
Email p...@scom.ca
On 8/12/2022 6:06 PM, dovecot-boun...@dovecot.org 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 this?
service config {
vsz_limit = 2048M
idle_kill = 60s
service_count = 1024
}
pstree
systemd─┬─ModemManager───2*[{ModemManager}]
├─agetty
├─cron
├─dbus-daemon
├─dovecot─┬─anvil
│ ├─6*[auth]
│ ├─46*[config]
│ ├─1212*[imap]
│ ├─155*[imap-login]
│ ├─12*[lmtp]
│ ├─38*[log]
│ ├─10*[managesieve]
│ ├─19*[pop3]
│ ├─3*[pop3-login]
│ └─18*[stats]
root 45831 0.0 1.1 774688 752732 ? S 09:31 0:31
dovecot/config
root 388792 0.0 1.1 775060 753276 ? S 14:00 0:15
dovecot/config
root 510685 0.0 1.1 775384 753604 ? S 15:06 0:20
dovecot/config
root 675638 0.0 1.1 775348 753620 ? S 16:56 0:15
dovecot/config
root 795375 0.0 1.1 775460 753516 ? S 18:03 0:07
dovecot/config
root 798754 0.2 1.1 775592 753712 ? S 18:05 0:30
dovecot/config
root 1082696 0.2 1.1 774892 753216 ? S 21:10 0:07
dovecot/config
root 1098433 0.4 1.1 774924 753244 ? S 21:33 0:07
dovecot/config
root 1109255 0.9 1.1 774924 753344 ? S 21:50 0:07
dovecot/config
root 1112976 2.0 1.1 774956 753528 ? S 21:57 0:07
dovecot/config
root 1114137 3.0 1.1 775028 753308 ? S 21:59 0:07
dovecot/config
root 1115382 5.4 1.1 774924 753496 ? S 22:01 0:06
dovecot/config
root 1883627 0.0 1.1 759120 728832 ? S Aug11 0:07
dovecot/config
root 1889705 0.0 1.8 1251460 1221872 ? S Aug11 0:11
dovecot/config
root 1895022 0.0 1.8 1253280 1224284 ? S Aug11 0:11
dovecot/config
root 1900690 0.0 1.8 1255684 1227528 ? S Aug11 0:12
dovecot/config
root 1905648 0.0 1.8 1257880 1229912 ? S Aug11 0:12
dovecot/config
root 1910857 0.0 1.8 1259156 1231552 ? S Aug11 0:12
dovecot/config
root 1914332 0.0 1.1 764328 736552 ? S Aug11 0:20
dovecot/config
root 2343896 0.0 1.8 1259472 1231516 ? S Aug11 0:12
dovecot/config
root 2346351 0.0 1.8 1259472 1231836 ? S Aug11 0:13
dovecot/config
root 2348559 0.0 1.1 764704 736440 ? S Aug11 0:14
dovecot/config
root 2445701 0.0 1.1 764276 736540 ? S Aug11 0:19
dovecot/config
root 2572525 0.0 1.1 764640 736880 ? S Aug11 0:18
dovecot/config
root 2734251 0.0 1.1 764776 737696 ? S Aug11 0:08
dovecot/config
root 2740980 0.0 1.1 764768 737244 ? S Aug11 0:17
dovecot/config
root 2899925 0.0 1.1 764624 737760 ? S Aug11 0:43
dovecot/config
root 3517063 0.0 1.1 764984 738004 ? S Aug11 0:09
dovecot/config
root 3541465 0.0 1.1 765224 738756 ? S Aug11 0:07
dovecot/config
root 3545589 0.0 1.1 766452 740408 ? S Aug11 0:06
dovecot/config
root 3549259 0.0 1.1 766796 741048 ? S Aug11 0:07
dovecot/config
root 3553902 0.0 1.1 767812 742284 ? S Aug11 0:07
dovecot/config
root 3558080 0.0 1.1 768440 743524 ? S Aug11 0:08
dovecot/config
root 3562091 0.0 1.1 769224 744424 ? S Aug11 0:07
dovecot/config
root 3568721 0.0 1.1 769388 744888 ? S Aug11 0:07
dovecot/config
root 3573024 0.0 1.1 770048 745904 ? S Aug11 0:08
dovecot/config
root 3578416 0.0 1.1 770836 746736 ? S Aug11 0:06
dovecot/config
root 3581765 0.0 1.1 771948 748492 ? S Aug11 0:06
dovecot/config
root 3585837 0.0 1.1 772828 749860 ? S Aug11 0:07
dovecot/config
root 3590276 0.0 1.1 773560 750520 ? S Aug11 0:07
dovecot/config
root 3594640 0.0 1.1 774612 752552 ? S Aug11 0:08
dovecot/config
root 3597417 0.0 1.1 774968 753076 ? S Aug11 0:35
dovecot/config
root 4116314 0.0 1.9 1280496 1258580 ? S 05:31 0:13
