3587703 - Signal 11 occurs in LDAP over SSL/TLS binding calls - SAP ASE

• ASE errorlog reports a signal 11 related to LDAP over SSL/TLS operations.
• After this signal 11 happens, ASE may not accept new connections via LDAP over SSL/TLS.
• You can find a Current process infected with signal 11 (SIGSEGV) message with a stack trace, but the fault function is always (null) like below.
  
  Address 0x(nil) (), siginfo (code, address) = (1, 0x(nil))
  Current process (0x0) infected with signal 11 (SIGSEGV)
  
  Address 0x0x00007f0b6738635c ((null)+0x7f0b6738635c), siginfo (code, address) = (1, 0x0x00000000ffffffff)
  Current process (0x0) infected with signal 11 (SIGSEGV)

• The signal 11 contains the following stack trace patterns.

kisignal
(null)
....repeatedly.....
(null)
ldap_sasl_bind
ldap_simple_bind
kl__ldap_asyn_bind
kladminbind
kllookupdn
klbindfuncalt
ubcExecute
kbctMain
krtctskRun
ktskRun
ktRTCThreadMain
end of stack trace
Blocking call executing on behalf of XXXXXXX failed with exception
upsleepgeneric
ubcWaitForCompletion
undo_blockingcall_thread
ulauthreq
login__ldapauth
login__checkauth
simple_handshake
login_handshake
login

• SAP Adaptive Server Enterprise (ASE) 16.0 SP04 PL04
• Linux
• LDAP over SSL/TLS (LDAPS)

830532, CR#830532, #830532, hang, alloc_handle, ldap_int_tls_connect, LDAPS , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Problem