|
Description
|
If the KDC is configured to use LDAP as the kdb store and "sunw_dbprop_enable" is set to true in /etc/krb5/kdc.conf the kadmind daemon will core:
Dec 13 06:29:11 soe-280r-4 kadmind[10700](Warning): Warning, current KDB plugin does
not support iprop, continuing with iprop disabled
soe-280r-4# mdb /var/core/kadmind.10706.core
Loading modules: [ libc.so.1 libuutil.so.1 ld.so.1 ]
> $C
ffbfe5e8 libc.so.1`strlen+0x50(ff257ed7, ffbff338, ffbfeba1, 0, 0, 0)
ffbff278 libc.so.1`sprintf+0x40(ffbff35f, 7fffffff, 7ffffc00, 0, 29d2, ff257ce8)
ffbff2e8 libkadm5srv.so.1`klog_vsyslog+0x80(6, 1dcf0, ffbffbfc, fee52a00, ff26b1cc,
ffbff350)
ffbffb50 libkadm5srv.so.1`krb5_klog_syslog+0x1c(6, 1dcf0, 5ea78, 1a004, 1a000, 1dcf0
)
ffbffbb0 main+0xdc4(20800, 21400, 0, 21000, 6, ffbfff06)
ffbffde8 _start+0x108(0, 0, 0, 0, 0, 0)
>
The core was seen on S10u5 but clearly also affects Nevada. The root may be the following line in ovsec_kadmd.c:
938 krb5_klog_syslog(LOG_WARNING,
939 gettext("%s Warning, current KDB "
940 "plugin does not support iprop, continuing "
941 "with iprop disabled"));
Note the '%s' but no string is supplied to the func. It should probably read:
938 krb5_klog_syslog(LOG_WARNING,
939 gettext("%s Warning, current KDB "
940 "plugin does not support iprop, continuing "
941 "with iprop disabled"), whoami);
|
