Re: Memory problem 2.4.17-2.1~bpo50+1
Some additional information:
1. when slapcat ends in a failure the entry wich causes the problem will
give always a problem:
/usr/sbin/slapcat -v -b "dc=example,dc=com" \
-a "(entryUUID=93056ad8-9993-102e-916b-d706e901a6df)"
...
<= entry_decode:
slap_str2undef_ad(vent_alarms:ytoxontzojy6im5vdglmesi7ytoyontzojy6il9fzgvzyyi7czowoiiio3m6ntoic291bmqio3m6mdoiijt9fq==):
AttributeDescription contains inappropriate characters
Note: "vent_alarms:..." is not correct: should be "event_alarms:..."
2. when slapcat ends in a failure, a restart of slapd solves the
problem. After a restart of slapd a full dump with slapcat gives no problem.
Op 17-8-2010 10:02, Ruud Baart schreef:
> Hello,
>
> Every night I dump the LDAP data in a ldif file. I do this for years and
> on several servers. Since the last upgrade van LDAP (slapd, ldap-utils,
> libldap-2.4-2) to version 2.4.17-2.1~bpo50+1 the dump fails with serious
> memory errors. As far as I can see it has nothing to do with the content
> of the LDAP.
>
> Command executed
> /usr/sbin/slapcat -c -b "dc=example,dc=com"
>
> Result:
> UNKNOWN attributeDescription
> "9ATOXO2E6NDP7CZOZOIJHCHAIO3M6NTOIDHVYYMEIO3M6NJOIAGVPZ2H0IJTPOJE7CZO1OIJ3AWR0ACI7ATOXO3M6NJOICGFYYW1ZIJTHOJI6E3M6NDOIDHLWZSI7CZOXMDOIBWLUAXNLYXJJACI7CZO2OIJWYXJHBXMIO2E6MDP7FX19F
> X0=" inserted.
> <= entry_decode: slap_str2undef_ad(add_source:): AttributeDescription
> contains inappropriate characters
--
Regards
R.J. Baart
Reply to: