Re: (ITS#8609) segfault in mods.c - modify_add_values

[henson@acm.org]

On Wed, Apr 19, 2017 at 05:37:35PM +0100, OndÅ?ej Kuzník wrote:

> could you post the two accesslog entries (or at least an outline)
> referenced in the backtrace?

That's weird. I can't find these exact entries. Based on the username, I
found ones that are very close to the timestamp, but ones that match
these exact timestamps do not exist. Last time Quanah asked me to look
up the matching accesslog entry from the crash I believe I was able to
find it.

> - reqStart=20170415103641.000016Z,cn=accesslog

dn: reqStart=20170415103641.000068Z,cn=accesslog
objectClass: auditModify
structuralObjectClass: auditModify
reqStart: 20170415103641.000068Z
reqEnd: 20170415103641.000069Z
reqType: modify
reqSession: 792228
reqAuthzID: cn=idmgmt,ou=user,ou=service,dc=cpp,dc=edu
reqDN: uid=brandonl,ou=user,dc=cpp,dc=edu
reqResult: 0
reqMod: eduPersonAffiliation:=
reqMod: eduPersonPrimaryAffiliation:=
reqMod: cppEduPersonAffiliation:=
reqMod: entryCSN:= 20170415103641.599920Z#000000#000#000000
reqMod: modifiersName:= cn=idmgmt,ou=user,ou=service,dc=cpp,dc=edu
reqMod: modifyTimestamp:= 20170415103641Z
reqEntryUUID: 8b33981d-25ee-4f7b-b439-41c273e94b61
entryUUID: b132db96-9ebe-4ee5-9fd2-5257b0c352d2
creatorsName: cn=accesslog
createTimestamp: 20170415103641Z
entryCSN: 20170415103641.599920Z#000000#000#000000
modifiersName: cn=accesslog
modifyTimestamp: 20170415103641Z

> - reqStart=20170416103057.000005Z,cn=accesslog

dn: reqStart=20170416103057.000045Z,cn=accesslog
objectClass: auditModify
structuralObjectClass: auditModify
reqStart: 20170416103057.000045Z
reqEnd: 20170416103057.000046Z
reqType: modify
reqSession: 54887
reqAuthzID: cn=idmgmt,ou=user,ou=service,dc=cpp,dc=edu
reqDN: uid=aaalmora,ou=user,dc=cpp,dc=edu
reqResult: 0
reqMod: eduPersonAffiliation:=
reqMod: eduPersonPrimaryAffiliation:=
reqMod: cppEduPersonAffiliation:=
reqMod: entryCSN:= 20170416103057.530384Z#000000#000#000000
reqMod: modifiersName:= cn=idmgmt,ou=user,ou=service,dc=cpp,dc=edu
reqMod: modifyTimestamp:= 20170416103057Z
reqEntryUUID: 153aa3e7-cc27-48ce-b6f2-e14215348941
entryCSN: 20170416103057.530384Z#000000#000#000000
entryUUID: b0c18fef-134e-4c8e-b073-fcdff58d3d93
creatorsName: cn=accesslog
createTimestamp: 20170416103057Z
modifiersName: cn=accesslog
modifyTimestamp: 20170416103057Z

> I assume you are still running the same code in production, correct?

Yes. It actually crashed 4 days in a row :(, the two days I provided
backtraces for and then the following two days. Just for something to do
I slapcat'd the db and accesslog and reloaded it after the fourth day in
case there was some weird mdb corruption or something. It hasn't crashed
since, but it crashes randomly so that could be meaningless <sigh>. I
wouldn't think reloaded the db would have affected finding the matching
accesslog entries but that is something different than last time too.
And of course now this is the non-optimized build.

Thanks...