Menu
▾
▴
#146 OpenDKIM assertion error when using LDAP
I just upgraded from OpenDKIM 2.6.0 to 2.7.0. Now OpenDKIM will no longer start, throwing the following assertion:
opendkim: search.c:95: ldap_pvt_search: Assertion `ld != ((void *)0)' failed.
/opt/zimbra/bin/zmopendkimctl: line 65: 24313 Aborted $odk -x
$config -u zimbra
Failed to start opendkim: 0
I have a feeling I know what this is. Can you get a stack trace? I don't have an LDAP system configured so you'll get there faster than I will.
Program received signal SIGABRT, Aborted.
0x00007ffff5b03a75 in raise () from /lib/libc.so.6
(gdb) bt
#0 0x00007ffff5b03a75 in raise () from /lib/libc.so.6
#1 0x00007ffff5b075c0 in abort () from /lib/libc.so.6
#2 0x00007ffff5afc941 in __assert_fail () from /lib/libc.so.6
#3 0x00007ffff7323b3f in ldap_pvt_search (ld=0x0, base=0x7ffffffe9770 "", scope=2, filter=0x7ffffffe9b80 "(DKIMIdentity=\\2a)", attrs=0x651df0, attrsonly=0, sctrls=0x0, cctrls=0x0,
timeout=0x7ffffffe96f0, sizelimit=0, deref=-1, msgidp=0x7ffffffe95d8) at search.c:95
#4 0x00007ffff7323d9a in ldap_pvt_search_s (ld=0x0, base=0x7ffffffe9770 "", scope=2, filter=0x7ffffffe9b80 "(DKIMIdentity=\\2a)", attrs=0x651df0, attrsonly=0, sctrls=0x0, cctrls=0x0,
timeout=0x7ffffffe96f0, sizelimit=0, deref=-1, res=0x7ffffffe9740) at search.c:174
#5 0x00007ffff7323d0f in ldap_search_ext_s (ld=0x0, base=0x7ffffffe9770 "", scope=2, filter=0x7ffffffe9b80 "(DKIMIdentity=\\2a)", attrs=0x651df0, attrsonly=0, sctrls=0x0, cctrls=0x0,
timeout=0x7ffffffe96f0, sizelimit=0, res=0x7ffffffe9740) at search.c:150
#6 0x0000000000424304 in dkimf_db_walk (db=0x651890, first=true, key=0x0, keylen=0x0, req=0x7ffffffe9fd0, reqnum=2) at opendkim-db.c:6058
#7 0x000000000040d0f0 in dkimf_config_load (data=0x6514d0, conf=0x650010, err=0x7fffffffe560 "", errlen=1025) at opendkim.c:8196
#8 0x000000000041ba72 in main (argc=5, argv=0x7fffffffea68) at opendkim.c:16310
Sent Quanah a patch. I believe this has uncovered a logic fault in dkimf_db_open() with respect to opening LDAP handles.
After patch, OpenDKIM starts and I can send email again.
Fix for this bug included in new release.