On Sun, Apr 16, 2017 at 06:20:06PM +0000, henson@acm.org wrote:

On Mon, Apr 03, 2017 at 02:44:48PM +0100, Howard Chu wrote: =20

...

You should probably switch to a non-optimized build. The backtrace you posted initially had most parameters optimized out, which also makes things harder to trace.

=20 Well, as luck (8-/) would have it, it crashed both yesterday and today on the non-optimized build. Here are the full backtraces from both cores, I hope they provide some clue as to what's going on. Let me know if you want me to do any more post mortem debugging on the cores. Thank=

s

much. =20 =20 Core was generated by `/usr/lib64/openldap/slapd -u ldap -g ldap -h lda=

ps:// ldap://'.

Program terminated with signal SIGSEGV, Segmentation fault. (gdb) bt full #6 0x00000000004c84b4 in syncrepl_message_to_op (si=3D0x16e4630, op=3D=

0x7fac037fd730, msg=3D0x7fabfc4a1560)

at /var/lib/portage/tmp/portage/net-nds/openldap-2.4.44-r1/work/ope=

nldap-2.4.44/servers/slapd/syncrepl.c:2394

#7 0x00000000004c31cd in do_syncrep2 (op=3D0x7fac037fd730, si=3D0x16e4=

630)

at /var/lib/portage/tmp/portage/net-nds/openldap-2.4.44-r1/work/ope=

nldap-2.4.44/servers/slapd/syncrepl.c:1013

    bdn =3D {bv_len =3D 44, bv_val =3D 0x7fabfc492bea "reqStart=3D2=

0170415103641.000016Z,cn=3Daccesslog"}

=20 =20 Core was generated by `/usr/lib64/openldap/slapd -u ldap -g ldap -h lda=

ps:// ldap://'.

Program terminated with signal SIGSEGV, Segmentation fault. (gdb) bt full #6 0x00000000004c84b4 in syncrepl_message_to_op (si=3D0x1ea8970, op=3D=

0x7fa0b59f1730, msg=3D0x7fa0a012df60)

at /var/lib/portage/tmp/portage/net-nds/openldap-2.4.44-r1/work/ope=

nldap-2.4.44/servers/slapd/syncrepl.c:2394

#7 0x00000000004c31cd in do_syncrep2 (op=3D0x7fa0b59f1730, si=3D0x1ea8=

970)

at /var/lib/portage/tmp/portage/net-nds/openldap-2.4.44-r1/work/ope=

nldap-2.4.44/servers/slapd/syncrepl.c:1013

    bdn =3D {bv_len =3D 44, bv_val =3D 0x7fa0a0422609 "reqStart=3D2=

0170416103057.000005Z,cn=3Daccesslog"}

Hi Paul, could you post the two accesslog entries (or at least an outline) referenced in the backtrace? - reqStart=3D20170415103641.000016Z,cn=3Daccesslog - reqStart=3D20170416103057.000005Z,cn=3Daccesslog

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

Thanks, Ondrej

--=20 Ond=C5=99ej Kuzn=C3=ADk Senior Software Engineer Symas Corporation http://www.symas.com Packaged, certified, and supported LDAP solutions powered by OpenLDAP