Directory Server 5.2 Patch 6 crashes when using Kerberos/GSSAPI on Solaris 10 (Doc ID 1329728.1)

Last updated on SEPTEMBER 16, 2016

Applies to:

Oracle Directory Server Enterprise Edition - Version: 5.2 SP6 and later   [Release: 5.0 and later ]
Information in this document applies to any platform.

Symptoms

As this is a crash issue the last lines of the access log that would show the SASL bind are within the core file, and would therefore not show in the access log file.

If the Directory Server crashes but no core file is produced, you may need to change the coreadm settings on your operating system to allow core dumps. You also need to provide enough disk space for the core file. For help on coreadm settings, please see this document "Configuring the Operating System to Generate Core Files" which is part of the Gathering Debug Data for Directory Server documentation.

http://download.oracle.com/docs/cd/E19850-01/820-0437/6nc66m9ql/index.html

You can then use a crash enabled Dirtracer (Doc ID 1291443.1) or pkgapp (Doc ID 1274584.1) script to capture the core data. From this data there will be a pstack, grep in the pstack for a line that comes from the crashing thread.

For this problem, DS 5.2 crashes and generates a core file with the following stack trace:

(----------------- lwp# 41 / thread# 41 --------------------
ffffffff7f05c2fc realfree (1008439b0, 6b732c636e3d636f, 183d60, 6b732c636e3d636c, ffffffff7f1e0000, 1008439a0) + 70
ffffffff7f05cc78 cleanfree (0, 1833e4, ffffffff7f1eeb90, ffffffff6ed36d9c, ffffffff7f1e0000, ffffffff7f1eec78) + 68
ffffffff7f05bcb0 _malloc_unlocked (3d0, 0, 0, 8, ffffffff7f1eae00, 0) + 11c
ffffffff7f05bb74 malloc (3c8, 20d0, 1844e4, ffffffff7f207710, ffffffff7f1e0000, 2000) + 64
ffffffff6e62bb3c aes_alloc_keysched (ffffffff6f11e368, 0, ffffffffffffffff, fffffffffffffff8, 0, 10020cbb9) + 4
ffffffff6e61f274 soft_aes_crypt_init_common (103c5fa10, ffffffff6f11e518, 103c545e8, 0, 10020cb70, 0) + 30
ffffffff6e6159f0 C_EncryptInit (0, ffffffff6f11e518, 103c545e8, 1, 0, 0) + 138
ffffffff6ed39530 krb5int_aes_encrypt (1003f2df0, 10029e710, 0, ffffffff6f11e628, ffffffff6f11e618, 97e) + 144
ffffffff6ed37058 krb5_derive_key (1003f2df0, ffffffff6eeab0f0, 10029e710, 10029e6e0, ffffffff6f11e708, 1002f2450) + 144
ffffffff6ed36d9c init_der(Bived_keydata (1003f2df0, ffffffff6eeab0f0, 10029e710, b, ffffffff6f11e820, ffffffff6f11e818) + a0
ffffffff6ed37218 krb5_dk_decrypt_maybe_trunc_hmac (1003f2df0, ffffffff6eeab0f0, ffffffff6eeab178, 10029e710, b, 0) + 3c
ffffffff6ed371c8 krb5int_aes_dk_decrypt (ffffffff6f11ea90, 10029e2b0, ffffffff6eeab178, 10029e710, b, c) + 30
ffffffff6ed330a8 krb5_c_decrypt (1003f2df0, 10029e710, b, 0, 10029e2a0, ffffffff6f11ea90) + 15c
ffffffff6ed79bec decrypt_authenticator (1003f2df0, 10029e290, 100411a40, 1, ffe0, c) + 60
ffffffff6ed795a4 krb5_rd_req_decoded_opt (1003f2df0, ffffffff6f11ee78, 10029e290, 1002aaae8, 0, 0) + dc
ffffffff6ed79b40 krb5_rd_req_decoded (1003f2df0, ffffffff6f11ee78, ffffffff6f11ee70, 1002aaae8, 100537978, 1) + 28
ffffffff6ed20e84 krb5_732430005 (1003f2df0, ffffffff6f11ee70, 0, 10020ca30, ffffffff6f11f128, 0) + 4b4
ffffffff74c045c4 gss_accept_sec_context (ffffffff6f11f118, 1004a4088, 0, ffffffff6f11f128, 0, 1004a4090) + 1e0
ffffffff74f025b8 gssapi_server_mech_step (1004a4080, 0, 103b91b18, f(Bfff0000, ffffffff6f11f4c0, ffffffff6f11f4bc) + 2b8
ffffffff7dd110f4 sasl_server_step (103b90f40, 103b917b0, 400, ffffffff6f11f4c0, ffffffff6f11f4bc, 0) + 124
ffffffff7dd10eb0 sasl_server_start (103b90f40, 1002a7d98, 103b91b18, ffffffff75006088, ffffffff6f11f4c0, ffffffff6f11f4bc) + 260
ffffffff7ea2a600 ids_sasl_check_bind (103b91d58, 0, 0, ffffffff71001a50, ff00, ffffffff71001a50) + 260
ffffffff7ea2bee0 bind_core_pb (103b91d58, 103b93fb8, 0, 0, 100843630, 1002179f8) + 248
ffffffff7ea39bb8 dispatch_operation_core_pb (103b91d58, 103b91d58, 3, ffffffff7eb57d38, 0, 920) + 16c
ffffffff7ea25f80 ???????? (ffffffff71001a50, 103b93fb8, 1, 60, 2, 200000)
ffffffff7ea2628c ldap_frontend_main_using_core_api (ffffffff71001a50, 103b93fb8, 2, 1002ec220, 1002aae30, 0) + fc
ffffffff7ea272d4 ???????? (220, 0, ffffffffffffffff, 800, 9a8, 100832cd0)
ffffffff7d636d84 _pt_root (100257c30, 20000, 0, 0, 20000, ffffffff6f11ff48) + d4
ffffffff7f0c88e0 _lwp_start (0, 0, 0, 0, 0, 0)

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms