On 14/12/2023 12:38 EET Max Nikulin manikulin@gmail.com wrote:
On 06/12/2023 18:06, Max Nikulin wrote:
dovecot[72165]: auth-worker: Error: fatal error: failed to reserve page summary memory dovecot[72165]: auth-worker: Error: dovecot[72165]: auth-worker: Error: runtime stack: dovecot[72165]: auth-worker: Error: runtime.throw({0x7f552c418194?, 0x7f552c1feb10?}) dovecot[72165]: auth-worker: Error: runtime/panic.go:1047 +0x5f fp=0x7f552c1feac0 sp=0x7f552c1fea90 pc=0x7f552c28a53f dovecot[72165]: auth-worker: Error: runtime.(*pageAlloc).sysInit(0x7f552c5f6fd0)
For the case that somebody will get this thread in search engine results:
I have found another thread describing similar errors due to a custom PAM module for 2 factor authentication:
dovecot: lmtp: Error: fatal error: failed to reserve page summary memory https://dovecot.org/pipermail/dovecot/2020-September/119952.html Thu Sep 17 12:20:12 EEST 2020 https://dovecot.org/pipermail/dovecot/2020-October/120108.html Thu Oct 8 18:04:26 EEST 2020
Perhaps Go is not the best language to implement PAM modules if memory footprint is not expected to be large. On the other hand e.g. argon2 hashes may be really memory hungry, so vsz_limit must be set to appropriate value.
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
You can set service auth and service auth-worker vsz_limit to 2G, that is usually enough for PAM and Argon2.
Aki