Szerző: Jeremy HarrisDátum: 2022-01-11 09:43 UTC Címzett: exim-usersTárgy: Re: [exim] Exim 4.95: growth kern.openfiles
On 11/01/2022 09:08, Mikhail Golub via Exim-users wrote:
> Exim 4.95 running on FreeBSD 12.3
> Growing gradually kern.openfiles
>
> # exim -bV
> Exim version 4.95 #1 (FreeBSD 12.3) built 11-Jan-2022 08:36:14
> 8418 - pid of exim main process.
> # ps ax | grep exim
> 8418 - Ss 2:49,48 /usr/local/sbin/exim -bd -q5m
>
>
> # fstat -p 8418
> USER CMD PID FD MOUNT INUM MODE SZ|DV R/W
> mailnull exim 8418 text / 1123592 -rwsr-xr-x 1339784 r
> mailnull exim 8418 wd / 401303 drwxr-x--- 512 r
> mailnull exim 8418 root / 2 drwxr-xr-x 1024 r
> mailnull exim 8418 0
> mailnull exim 8418 1 /dev 16 crw-rw-rw- null rw
> mailnull exim 8418 2 /dev 16 crw-rw-rw- null rw
> mailnull exim 8418 3* local dgram fffff80003ec0600
> mailnull exim 8418 4* internet stream tcp fffff800183a97b0
> mailnull exim 8418 5 / 1457089 drwxr-xr-x 512 r
> mailnull exim 8418 6 / 1446342 -rw-r--r-- 5593 r
> mailnull exim 8418 7 / 1457089 drwxr-xr-x 512 r
> mailnull exim 8418 8 / 1446340 -rw-r--r-- 1675 r
> mailnull exim 8418 9 / 722335 drwxr-xr-x 512 r
> mailnull exim 8418 10 / 2327639 drwxr-xr-x 512 r
> mailnull exim 8418 11 / 2327640 -rw-r--r-- 710164 r
> mailnull exim 8418 12 / 722335 drwxr-xr-x 512 r
> mailnull exim 8418 13 / 2327639 drwxr-xr-x 512 r
> mailnull exim 8418 14 / 2327640 -rw-r--r-- 710164 r
> mailnull exim 8418 15 / 722335 drwxr-xr-x 512 r
> mailnull exim 8418 16 / 2327639 drwxr-xr-x 512 r
> mailnull exim 8418 17 / 2327640 -rw-r--r-- 710164 r
> mailnull exim 8418 18 / 722335 drwxr-xr-x 512 r
> mailnull exim 8418 19 / 2327639 drwxr-xr-x 512 r
> mailnull exim 8418 20 / 2327639 drwxr-xr-x 512 r
> mailnull exim 8418 21 / 2327639 drwxr-xr-x 512 r
> ...
>
> inum 2327639 - /usr/local/share/certs/
> exim 23760 mailnull 2852r VDIR 0,85 512 2327639 /usr/local/share/certs
Thank you for looking into this; it's the first concrete information I've
had on an issue that has affected several people. Knowing the path is useful,
and also the confirmation that the daemon process is involved.
Your initial workaround should be to periodically restart the daemon.
If you have any info on the rate of growth, this would also help.
From the path, I'm guessing it'll be one per hour.
--
Cheers,
Jeremy