Woke up this morning to an unwanted Christmas present :(, one of my ldap servers had crashed with a segfault:

Core was generated by `/usr/lib64/openldap/slapd -u ldap -g ldap -h ldaps:// ldap://'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x0000000000485c61 in modify_add_values () [Current thread is 1 (Thread 0x7f50727fd700 (LWP 15556))] (gdb) where #0 0x0000000000485c61 in modify_add_values () #1 0x00007f526dfccd0c in mdb_modify_internal () from /usr/lib64/openldap/openldap/back_mdb.so #2 0x00007f526dfce134 in mdb_modify () from /usr/lib64/openldap/openldap/back_mdb.so #3 0x000000000049c2ea in overlay_op_walk () #4 0x000000000049c441 in ?? () #5 0x000000000048d938 in ?? () #6 0x00000000004915d7 in ?? () #7 0x0000000000495793 in ?? () #8 0x0000000000433037 in ?? () #9 0x00007f5272c83a32 in ?? () from /usr/lib64/libldap_r-2.4.so.2 #10 0x00007f52722ce494 in start_thread () from /lib64/libpthread.so.0 #11 0x00007f52719c6edd in clone () from /lib64/libc.so.6

The last bit in the log was an update, then it ended:

Dec 25 03:31:03 fosse slapd[3333]: conn=561646 op=3 MOD dn="uid=aapriest,ou=user,dc=csupomona,dc=edu " Dec 25 03:31:03 fosse slapd[3333]: conn=561646 op=3 MOD attr=csupomonaEduPersonExpiration

When I saw the alert on my phone when I woke up I assumed it would have something to do with the memberOf overlay issues I was already looking into but this seems different.

I restarted it and it synced right back up from the failover master and seems to be ok now. Does this pop out as anything known and possibly resolved in head? Thanks...