[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
mdb_put failed: MDB_MAP_FULL
- To: "openldap-technical@openldap.org" <openldap-technical@openldap.org>
- Subject: mdb_put failed: MDB_MAP_FULL
- From: Prentice Bisbal <pbisbal@pppl.gov>
- Date: Tue, 21 Jan 2020 16:44:43 -0500
- Content-language: en-US
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pppl.gov; s=google; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=bJ2YvRvIxDslC4qM7ixZe/AiFcMV6V2quNTlOUgN050=; b=MDII6MNxzoBTQ1kdWZO80ykGX7SY2P7IA1QT8QmuL7l7kIBmEZ28ocnEfMgfGNWgTV BSy8QL7Of69AI9Q0BcbwlNaqdgxpuaGh1Ebkj3IoXLtJS5+K+2NFO05f7q4UVFjCSQRD dVUdrAuZPbnZV3fKguGLWN+8iEaZ/C4DFWQxM=
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.3.0
I've temporarily fixed my Kerberos problem (I think) by using k5start to
start slapd in debug mode:
k5start -f /etc/krb5.keytab host/voltron-b.pppl.gov -- /usr/sbin/slapd
-d 1634
When I do this, I no longer see the SASL auth failures, but now I'm
seeing this error. Does this mean there are too many members in the
group "trbatch"?
mdb_id2entry_put: mdb_put failed: MDB_MAP_FULL: Environment mapsize
limit reached(-30792) "cn=trbatch,ou=groups,dc=unix,dc=pppl,dc=gov"
5e27700b null_callback : error code 0x50
5e27700b syncrepl_entry: rid=001 be_modify failed (80)
sasl_generic_write: want=71, written=71
--
Prentice