Rocksolid Light

groups  faq  privacy  How to post  login

Message-ID:  

You possess a mind not merely twisted, but actually sprained.

rocksolid / de.comm.software.mailserver / postfix queue file write error / amavis Can't allocate memory

SubjectAuthor
* postfix queue file write error / amavis Can't allocate memoryUlli Horlacher
+- Re: postfix queue file write error / amavis Can't allocate memoryMarco Moock
+* Re: postfix queue file write error / amavis Can't allocate memoryTim Ritberg
|`* Re: postfix queue file write error / amavis Can't allocate memoryUlli Horlacher
| `* Re: postfix queue file write error / amavis Can't allocate memoryTim Ritberg
|  `- Re: postfix queue file write error / amavis Can't allocate memoryPeter J. Holzer
`* Re: postfix queue file write error / amavis Can't allocate memoryPeter J. Holzer
 `- Re: postfix queue file write error / amavis Can't allocate memoryTim Ritberg

1
Subject: postfix queue file write error / amavis Can't allocate memory
From: Ulli Horlacher
Newsgroups: de.comm.software.mailserver
Organization: University of Stuttgart, FRG
Date: Thu, 14 Mar 2024 07:55 UTC
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!news.datentrampelpfad.de!thinkmo.de!news.uni-stuttgart.de!.POSTED!not-for-mail
From: frams...@rus.uni-stuttgart.de (Ulli Horlacher)
Newsgroups: de.comm.software.mailserver
Subject: postfix queue file write error / amavis Can't allocate memory
Date: Thu, 14 Mar 2024 07:55:49 +0000 (UTC)
Organization: University of Stuttgart, FRG
Lines: 77
Message-ID: <usuai5$64i$1@news2.informatik.uni-stuttgart.de>
X-Trace: news2.informatik.uni-stuttgart.de 1710402949 6290 129.69.1.129 (14 Mar 2024 07:55:49 GMT)
X-Complaints-To: rusnews@informatik.uni-stuttgart.de
NNTP-Posting-Date: Thu, 14 Mar 2024 07:55:49 +0000 (UTC)
User-Agent: tin/2.6.3-20231224 ("Banff") (Linux/5.15.0-97-generic (x86_64))
View all headers

Ich bekomme auf einem meiner Systeme immer wieder mal solche Mails:

From: Mail Delivery System <MAILER-DAEMON@ZZZZZZ.ZZ>
To: Postmaster <postmaster@ZZZZZZ.ZZ>
Subject: Postfix SMTP server: errors from
mail-pg1-f196.google.com[209.85.215.196]
Date: Tue, 12 Mar 2024 10:26:33 +0100 (CET)

Transcript of session follows.

Out: 220 ZZZZZZ.ZZ ESMTP Postfix (Ubuntu)
In: EHLO mail-pg1-f196.google.com
Out: 250-ZZZZZZ.ZZ
Out: 250-PIPELINING
Out: 250-SIZE 33554432
Out: 250-VRFY
Out: 250-ETRN
Out: 250-STARTTLS
Out: 250-ENHANCEDSTATUSCODES
Out: 250-8BITMIME
Out: 250-DSN
Out: 250 CHUNKING
In: STARTTLS
Out: 220 2.0.0 Ready to start TLS
In: EHLO mail-pg1-f196.google.com
Out: 250-ZZZZZZ.ZZ
Out: 250-PIPELINING
Out: 250-SIZE 33554432
Out: 250-VRFY
Out: 250-ETRN
Out: 250-ENHANCEDSTATUSCODES
Out: 250-8BITMIME
Out: 250-DSN
Out: 250 CHUNKING
In: MAIL FROM:<XXXXXXX@gmail.com> SIZE=8489
Out: 250 2.1.0 Ok
In: RCPT TO:<YYYYYYYY@ZZZZZZ.ZZ>
Out: 250 2.1.5 Ok
In: BDAT 8489 LAST
Out: 451 4.3.0 Error: queue file write error
In: QUIT
Out: 221 2.0.0 Bye

For other details, see the local mail logfile

root@zzzzzz:/var/log# cat mail.err
2024-03-12 10:27:33 amavis[52116]: (52116-01) (!!)AV: ALL VIRUS SCANNERS FAILED

root@zzzzzz:/var/log# grep ' 10:27' mail.log
2024-03-12 10:27:21 amavis[52116]: (52116-01) (!)ClamAV-clamd av-scanner FAILED: run_av error: ask_daemon_internal: Exceeded allowed time at (eval 124) line 657.\n
2024-03-12 10:27:21 amavis[52116]: (52116-01) (!)WARN: all primary virus scanners failed, considering backups
2024-03-12 10:27:33 amavis[52116]: (52116-01) (!)run_av (ClamAV-clamscan) FAILED - unexpected exit 2, output="LibClamAV Error: mpool_malloc(): Can't allocate memory (262144 bytes).\nLibClamAV Error: cli_mpool_strdup(): Can't allocate memory (28 bytes).\nLibClamAV Error: cli_loadhash: Problem parsing database at line 367034\nLibClamAV Error: Can't load daily.hsb: Malformed database\nLibClamAV Error: cli_tgzload: Can't load daily.hsb\nLibClamAV Error: Can't load /var/lib/clamav/daily.cld: Malformed database\nLibClamAV Error: cli_loaddbdir(): error loading database /var/lib/clamav/daily.cld\nERROR: Malformed database"
2024-03-12 10:27:33 amavis[52116]: (52116-01) (!)ClamAV-clamscan av-scanner FAILED: /usr/bin/clamscan unexpected exit 2, output="LibClamAV Error: mpool_malloc(): Can't allocate memory (262144 bytes).\nLibClamAV Error: cli_mpool_strdup(): Can't allocate memory (28 bytes).\nLibClamAV Error: cli_loadhash: Problem parsing database at line 367034\nLibClamAV Error: Can't load daily.hsb: Malformed database\nLibClamAV Error: cli_tgzload: Can't load daily.hsb\nLibClamAV Error: Can't load /var/lib/clamav/daily.cld: Malformed database\nLibClamAV Error: cli_loaddbdir(): error loading database /var/lib/clamav/daily.cld\nERROR: Malformed database" at (eval 124) line 951.
2024-03-12 10:27:33 amavis[52116]: (52116-01) (!!)AV: ALL VIRUS SCANNERS FAILED
2024-03-12 10:27:36 amavis[53998]: (52116-01) SA info: util: setuid: ruid=112 euid=112 rgid=121 119 121 egid=121 119 121
2024-03-12 10:27:36 amavis[52116]: (52116-01) Blocked SPAM {RejectedInbound}, [209.85.215.196]:51315 [209.85.215.196] <XXXXXXX@gmail.com> -> <YYYYYYYY@ZZZZZZ.ZZ>, Message-ID: <CAJoHSaGkFiwVhjnhJkzyWusZKGYt1b_AfKCy-Zm76CC3Q5+-sQ@mail.gmail.com>, mail_id: OlY3GFNNwphy, Hits: 7.378, size: 8691, dkim_sd=20230601:gmail.com, 303784 ms

root@zzzzzz:/var/log# free -h
total used free shared buff/cache available
Mem: 5.8Gi 2.1Gi 1.6Gi 1.0Mi 2.1Gi 3.4Gi
Swap: 0B 0B 0B

Wieso "Can't allocate memory (262144 bytes)"? 260 kB?!?

--
Ullrich Horlacher Server und Virtualisierung
Rechenzentrum TIK
Universitaet Stuttgart E-Mail: horlacher@tik.uni-stuttgart.de
Allmandring 30a Tel: ++49-711-68565868
70569 Stuttgart (Germany) WWW: https://www.tik.uni-stuttgart.de/

Subject: Re: postfix queue file write error / amavis Can't allocate memory
From: Marco Moock
Newsgroups: de.comm.software.mailserver
Organization: A noiseless patient Spider
Date: Thu, 14 Mar 2024 08:04 UTC
References: 1
Path: i2pn2.org!i2pn.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: mm+use...@dorfdsl.de (Marco Moock)
Newsgroups: de.comm.software.mailserver
Subject: Re: postfix queue file write error / amavis Can't allocate memory
Date: Thu, 14 Mar 2024 09:04:59 +0100
Organization: A noiseless patient Spider
Lines: 7
Message-ID: <usub3b$1g2ie$4@dont-email.me>
References: <usuai5$64i$1@news2.informatik.uni-stuttgart.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 14 Mar 2024 08:05:00 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="e6f4fdaeb1993510e7a7ff2ec7e2da2c";
logging-data="1575502"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+VwM0uHZR2pRG4MVgeaNoU"
Cancel-Lock: sha1:X3bha1oPxAaQDLYbSvKS0ut1MaQ=
View all headers

Am 14.03.2024 schrieb Ulli Horlacher <framstag@rus.uni-stuttgart.de>:

> In: BDAT 8489 LAST

Schalte mal testweise BDAT/CHUNKING ab und teste, ob das weiterhin
auftritt.

Subject: Re: postfix queue file write error / amavis Can't allocate memory
From: Tim Ritberg
Newsgroups: de.comm.software.mailserver
Date: Thu, 14 Mar 2024 08:26 UTC
References: 1
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!reader5.news.weretis.net!news.tota-refugium.de!.POSTED!not-for-mail
From: tim...@server.invalid (Tim Ritberg)
Newsgroups: de.comm.software.mailserver
Subject: Re: postfix queue file write error / amavis Can't allocate memory
Date: Thu, 14 Mar 2024 09:26:39 +0100
Message-ID: <usucbv$1bhod$1@tota-refugium.de>
References: <usuai5$64i$1@news2.informatik.uni-stuttgart.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 14 Mar 2024 08:26:39 -0000 (UTC)
Injection-Info: tota-refugium.de;
logging-data="1427213"; mail-complaints-to="abuse@news.tota-refugium.de"
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:lZD78/2rOj/hS7zUfqwzvBKp2WU=
In-Reply-To: <usuai5$64i$1@news2.informatik.uni-stuttgart.de>
X-User-ID: eJwNy8kBwDAIA7CVuOzQcSiE/Udo9Recyj5BMLDYijk9UDel5n0sJH1NX1AAieq1MY0q/invBwV0EDE=
Content-Language: de-DE
View all headers

Am 14.03.24 um 08:55 schrieb Ulli Horlacher:

>
> Wieso "Can't allocate memory (262144 bytes)"? 260 kB?!?
Was sagt: cat /proc/sys/vm/overcommit_memory?

Tim

Subject: Re: postfix queue file write error / amavis Can't allocate memory
From: Ulli Horlacher
Newsgroups: de.comm.software.mailserver
Organization: University of Stuttgart, FRG
Date: Thu, 14 Mar 2024 10:45 UTC
References: 1 2
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!news.datentrampelpfad.de!thinkmo.de!news.uni-stuttgart.de!.POSTED!not-for-mail
From: frams...@rus.uni-stuttgart.de (Ulli Horlacher)
Newsgroups: de.comm.software.mailserver
Subject: Re: postfix queue file write error / amavis Can't allocate memory
Date: Thu, 14 Mar 2024 10:45:21 +0000 (UTC)
Organization: University of Stuttgart, FRG
Lines: 21
Message-ID: <usukg1$8il$1@news2.informatik.uni-stuttgart.de>
References: <usuai5$64i$1@news2.informatik.uni-stuttgart.de> <usucbv$1bhod$1@tota-refugium.de>
X-Trace: news2.informatik.uni-stuttgart.de 1710413121 8789 129.69.1.129 (14 Mar 2024 10:45:21 GMT)
X-Complaints-To: rusnews@informatik.uni-stuttgart.de
NNTP-Posting-Date: Thu, 14 Mar 2024 10:45:21 +0000 (UTC)
User-Agent: tin/2.6.3-20231224 ("Banff") (Linux/5.15.0-97-generic (x86_64))
View all headers

Tim Ritberg <tim@server.invalid> wrote:
> Am 14.03.24 um 08:55 schrieb Ulli Horlacher:
>
>>
>> Wieso "Can't allocate memory (262144 bytes)"? 260 kB?!?
> Was sagt: cat /proc/sys/vm/overcommit_memory?

2

Aber es ist eigentlich immer genug Speicher da:

total used free shared buff/cache available
Mem: 5.8Gi 2.1Gi 1.2Gi 3.0Mi 2.5Gi 3.4Gi
Swap: 0B 0B 0B

--
Ullrich Horlacher Server und Virtualisierung
Rechenzentrum TIK
Universitaet Stuttgart E-Mail: horlacher@tik.uni-stuttgart.de
Allmandring 30a Tel: ++49-711-68565868
70569 Stuttgart (Germany) WWW: https://www.tik.uni-stuttgart.de/

Subject: Re: postfix queue file write error / amavis Can't allocate memory
From: Tim Ritberg
Newsgroups: de.comm.software.mailserver
Date: Thu, 14 Mar 2024 11:22 UTC
References: 1 2 3
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!reader5.news.weretis.net!news.tota-refugium.de!.POSTED!not-for-mail
From: tim...@server.invalid (Tim Ritberg)
Newsgroups: de.comm.software.mailserver
Subject: Re: postfix queue file write error / amavis Can't allocate memory
Date: Thu, 14 Mar 2024 12:22:52 +0100
Message-ID: <usummc$1bhoc$1@tota-refugium.de>
References: <usuai5$64i$1@news2.informatik.uni-stuttgart.de>
<usucbv$1bhod$1@tota-refugium.de>
<usukg1$8il$1@news2.informatik.uni-stuttgart.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 14 Mar 2024 11:22:52 -0000 (UTC)
Injection-Info: tota-refugium.de;
logging-data="1427212"; mail-complaints-to="abuse@news.tota-refugium.de"
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:9wDl6UcRuPe/+RvBU22Nu2WTkO8=
Content-Language: de-DE
In-Reply-To: <usukg1$8il$1@news2.informatik.uni-stuttgart.de>
X-User-ID: eJwVx8ERwDAIA7CVcABDxyFpvP8IveqndIKngslIpUrBaLXVWu3vNvxZ4My5OzjAbU9ZPhAGHwdHEGg=
View all headers

Am 14.03.24 um 11:45 schrieb Ulli Horlacher:
> Tim Ritberg <tim@server.invalid> wrote:
>> Am 14.03.24 um 08:55 schrieb Ulli Horlacher:
>>
>>>
>>> Wieso "Can't allocate memory (262144 bytes)"? 260 kB?!?
>> Was sagt: cat /proc/sys/vm/overcommit_memory?
>
> 2
>
> Aber es ist eigentlich immer genug Speicher da:
>
> total used free shared buff/cache available
> Mem: 5.8Gi 2.1Gi 1.2Gi 3.0Mi 2.5Gi 3.4Gi
> Swap: 0B 0B 0B
>

Nope. Diese Anzeige zeigt das Problem nicht:
https://www.kernel.org/doc/Documentation/vm/overcommit-accounting

Stell auf 0 und das Problem müsste weg sein.

Tim

Subject: Re: postfix queue file write error / amavis Can't allocate memory
From: Peter J. Holzer
Newsgroups: de.comm.software.mailserver
Organization: LUGA
Date: Thu, 14 Mar 2024 21:49 UTC
References: 1
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!newsfeed.xs3.de!tahina.priv.at!news.luga.at!.POSTED.212.17.106.130!not-for-mail
From: hjp-usen...@hjp.at (Peter J. Holzer)
Newsgroups: de.comm.software.mailserver
Subject: Re: postfix queue file write error / amavis Can't allocate memory
Date: Thu, 14 Mar 2024 22:49:31 +0100
Organization: LUGA
Message-ID: <slrnuv6s7e.e09n.hjp-usenet4@trintignant.hjp.at>
References: <usuai5$64i$1@news2.informatik.uni-stuttgart.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Injection-Info: vinge.luga.at; posting-host="212.17.106.130";
logging-data="22466"; mail-complaints-to="usenet@vinge.luga.at"
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:QAArCB/xy5d5P6fRxaShZIobDZI=
View all headers

On 2024-03-14 07:55, Ulli Horlacher <framstag@rus.uni-stuttgart.de> wrote:
> Ich bekomme auf einem meiner Systeme immer wieder mal solche Mails:
[...]
> 2024-03-12 10:27:33 amavis[52116]: (52116-01) (!)run_av (ClamAV-clamscan) FAILED - unexpected exit 2, output="LibClamAV Error: mpool_malloc(): Can't allocate memory (262144 bytes).\nLibClamAV Error: cli_mpool_strdup(): Can't allocate memory (28 bytes).\nLibClamAV Error: cli_loadhash: Problem parsing database at line 367034\nLibClamAV Error: Can't load daily.hsb: Malformed database\nLibClamAV Error: cli_tgzload: Can't load daily.hsb\nLibClamAV Error: Can't load /var/lib/clamav/daily.cld: Malformed database\nLibClamAV Error: cli_loaddbdir(): error loading database /var/lib/clamav/daily.cld\nERROR: Malformed database"
> 2024-03-12 10:27:33 amavis[52116]: (52116-01) (!)ClamAV-clamscan av-scanner FAILED: /usr/bin/clamscan unexpected exit 2, output="LibClamAV Error: mpool_malloc(): Can't allocate memory (262144 bytes).\nLibClamAV Error: cli_mpool_strdup(): Can't allocate memory (28 bytes).\nLibClamAV Error: cli_loadhash: Problem parsing database at line 367034\nLibClamAV Error: Can't load daily.hsb: Malformed database\nLibClamAV Error: cli_tgzload: Can't load daily.hsb\nLibClamAV Error: Can't load /var/lib/clamav/daily.cld: Malformed database\nLibClamAV Error: cli_loaddbdir(): error loading database /var/lib/clamav/daily.cld\nERROR: Malformed database" at (eval 124) line 951.
[...]
>
> root@zzzzzz:/var/log# free -h
> total used free shared buff/cache available
> Mem: 5.8Gi 2.1Gi 1.6Gi 1.0Mi 2.1Gi 3.4Gi
> Swap: 0B 0B 0B
>
>
> Wieso "Can't allocate memory (262144 bytes)"? 260 kB?!?

256. Dürfte wohl die Chunk-Größe des Allokators sein. Das ist nicht die
Gesamtgröße des Prozesses, sondern die Größe des Requests, der nicht
mehr bedient werden konnte (quasi der Tropfen, der das Fass zum
Überlaufen brachte).

Läuft ClamAV vielleicht mit restriktiven Resource-Limits?

hp

Subject: Re: postfix queue file write error / amavis Can't allocate memory
From: Peter J. Holzer
Newsgroups: de.comm.software.mailserver
Organization: LUGA
Date: Thu, 14 Mar 2024 22:06 UTC
References: 1 2 3 4
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!newsfeed.xs3.de!tahina.priv.at!news.luga.at!.POSTED.212.17.106.130!not-for-mail
From: hjp-usen...@hjp.at (Peter J. Holzer)
Newsgroups: de.comm.software.mailserver
Subject: Re: postfix queue file write error / amavis Can't allocate memory
Date: Thu, 14 Mar 2024 23:06:56 +0100
Organization: LUGA
Message-ID: <slrnuv6t80.e09n.hjp-usenet4@trintignant.hjp.at>
References: <usuai5$64i$1@news2.informatik.uni-stuttgart.de>
<usucbv$1bhod$1@tota-refugium.de>
<usukg1$8il$1@news2.informatik.uni-stuttgart.de>
<usummc$1bhoc$1@tota-refugium.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Injection-Info: vinge.luga.at; posting-host="212.17.106.130";
logging-data="22466"; mail-complaints-to="usenet@vinge.luga.at"
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:fFPv0fhWpyAaUWWucRiHjnF3cuU=
View all headers

On 2024-03-14 11:22, Tim Ritberg <tim@server.invalid> wrote:
> Am 14.03.24 um 11:45 schrieb Ulli Horlacher:
>> Tim Ritberg <tim@server.invalid> wrote:
>>> Am 14.03.24 um 08:55 schrieb Ulli Horlacher:
>>>> Wieso "Can't allocate memory (262144 bytes)"? 260 kB?!?
>>> Was sagt: cat /proc/sys/vm/overcommit_memory?
>>
>> 2
>>
>> Aber es ist eigentlich immer genug Speicher da:
>>
>> total used free shared buff/cache available
>> Mem: 5.8Gi 2.1Gi 1.2Gi 3.0Mi 2.5Gi 3.4Gi
>> Swap: 0B 0B 0B
>>
>
> Nope. Diese Anzeige zeigt das Problem nicht:
> https://www.kernel.org/doc/Documentation/vm/overcommit-accounting

Zitat:

| 2 - Don't overcommit. The total address space commit
| for the system is not permitted to exceed swap + a
| configurable amount (default is 50%) of physical RAM.

Hier also 0 GB + 5.8 GB * 0.5 = 2.9 GB.

Zum Zeitpunkt des Aufrufs waren 2.1 GB "used". Reserviertes Virtual
Memory ist vermutlich um einiges größer, die Wahrscheinlichkeit, dass
das vor einiger Zeit an der 2.9 GB-Grenze angestoßen ist, ist also nicht
vernachlässigbar.

> Stell auf 0 und das Problem müsste weg sein.

Alternativ könnte man auch an vm.overcommit_ratio bzw.
vm.overcommit_kbytes drehen und/oder dem System ein bisschen Swapspace
gönnen.

Aber es hat schon seinen Grund, warum overcommit_memory=0 der Default
ist.

hp

Subject: Re: postfix queue file write error / amavis Can't allocate memory
From: Tim Ritberg
Newsgroups: de.comm.software.mailserver
Date: Fri, 15 Mar 2024 08:14 UTC
References: 1 2
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!reader5.news.weretis.net!news.tota-refugium.de!.POSTED!not-for-mail
From: tim...@server.invalid (Tim Ritberg)
Newsgroups: de.comm.software.mailserver
Subject: Re: postfix queue file write error / amavis Can't allocate memory
Date: Fri, 15 Mar 2024 09:14:20 +0100
Message-ID: <ut100s$1cgkc$1@tota-refugium.de>
References: <usuai5$64i$1@news2.informatik.uni-stuttgart.de>
<slrnuv6s7e.e09n.hjp-usenet4@trintignant.hjp.at>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Fri, 15 Mar 2024 08:14:20 -0000 (UTC)
Injection-Info: tota-refugium.de;
logging-data="1458828"; mail-complaints-to="abuse@news.tota-refugium.de"
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:ojDPbBGPHR+i37qBM8escPYBsjY=
Content-Language: de-DE
X-User-ID: eJwNysEBwCAIA8CVAEPajoMR9h/B3vty0akHTCInZ9csNf1F0dXmtU2gZVl8ff4r9VhEOwY8Fy0cEZ4=
In-Reply-To: <slrnuv6s7e.e09n.hjp-usenet4@trintignant.hjp.at>
View all headers

Am 14.03.24 um 22:49 schrieb Peter J. Holzer:

> 256. Dürfte wohl die Chunk-Größe des Allokators sein. Das ist nicht die
> Gesamtgröße des Prozesses, sondern die Größe des Requests, der nicht
> mehr bedient werden konnte (quasi der Tropfen, der das Fass zum
> Überlaufen brachte).
>
> Läuft ClamAV vielleicht mit restriktiven Resource-Limits?
>
> hp

So sieht einer meiner MXer nur mit Postfix, Amavis mit Spamassassin und
ClamAV aus:
https://i.imgur.com/kuqGaHc.png

2 GB Ram + Swap und ohne Swap würde es gar nicht laufen.

Tim

rocksolid / de.comm.software.mailserver / postfix queue file write error / amavis Can't allocate memory

1
server_pubkey.txt

rocksolid light 0.9.136
clearnet tor