My Oracle Support Banner

OID 11g Ldapd Server Process Repeatedly Crashing and Restarting After Setting High Level Debug (orcldebugflag=117440511) with Log Error: Recieved signal = 11, shutting down (Doc ID 1984009.1)

Last updated on MAY 06, 2021

Applies to:

Oracle Internet Directory - Version 11.1.1 and later
Information in this document applies to any platform.

Symptoms

Clustered Oracle Internet Directory (OID) 11g with latest OID Bundle Patch applied, and using OID Multimaster (MMR) Replication between the clusters.

OID ldapd server process is crashing and restarting repeatedly.

After enabling logging to orcldebugflag=117440511(*) observed the repeated crashes when checking server logs, every couple minutes:

[2015-01-29T13:10:29-06:00] [OID] [TRACE:16] [] [OIDLDAPD] [host: <HOSTNAME>] [pid: <PID>] [tid: <TID>] [ecid: <ECID>] ServerWorker (REG):[[
BEGIN
ConnID:21 mesgID:4 OpID:3  OpName:add ConnIP: ConnDN:cn=replication dn,orclreplicaid=<HOSTNAME>_<SID>,cn=replication configuration
gslfadADoAdd:conn=21 op=3 ADD dn="cn=<DB>,cn=OracleContext,dc=<COMPANY>,dc=com
"
2015-01-29T13:10:29 * gslbndnWithEscChar: origDN:<cn=<DB>,cn=OracleContext,dc=<COMPANY>,dc=com
> NormDn:
2015-01-29T13:10:29 * gslusrReplDecodeVal:bv_val:<string>
     chg_no:32628 server:danlrlb940_oidstl1d1 op_time:20150129040342z guid:<guid> pguid:
2015-01-29T13:10:29 * gsltxpcProcTxnCtl * Entry
2015-01-29T13:10:29 * gsltxpcProcTxnCtl * Exit
2015-01-29T13:10:29 * gsldpSearchStart * BASE = "cn=oraclecontext,dc=<COMPANY>,dc=com" SCOPE = 0
2015-01-29T13:10:29 * gsldfbsFetchBaseObjs * BASE = "cn=oraclecontext,dc=<COMPANY>,dc=com"
2015-01-29T13:10:29 * gsldfbsFetchBaseObjs * RevBaseDN = ""
RevParentDN = "dc=com,dc=<COMPANY>,"
ParentDN = "dc=<COMPANY>,dc=com"
2015-01-29T13:10:29 * gsldfbsFetchBaseObjs * RDN[0] = "cn=oraclecontext"
2015-01-29T13:10:29 * gsldfbsFetchBaseObjs * RDN[1] = "dc=<COMPANY>"
2015-01-29T13:10:29 * gsldfbsFetchBaseObjs * RDN[2] = "dc=com"
2015-01-29T13:10:29 * Base Search Sql: SELECT /*+ USE_NL(store) USE_NL(dn) INDEX(store EI_ATTRSTORE) INDEX(dn RP_DN) ORDERED */ store.entryid,AttrName,NVL(AttrVal,' '),attrkind,NVL(attrstype, ' '),NVL(AttrVer,' ') FROM CT_DN dn, ds_attrStore store WHERE (dn.rdn = :szCommonName AND dn.parentdn = :szBaseDomain) AND store.entryid = dn.entryid
2015-01-29T13:10:29 * Bind variables: :szCommonName = "cn=oraclecontext", :szBaseDomain = "dc=com,dc=<COMPANY>,"
2015-01-29T13:10:29 * Base Search Completed with: 100
2015-01-29T13:10:29 * gslbndnWithEscChar: origDN: NormDn:
2015-01-29T13:10:29 * gslsbaCheckRDNinEntry Entry RDN=cn=<DB>
2015-01-29T13:10:29 * gslbadCheckRDNinDN: <DB> = valBuf, normdn= <DB>
2015-01-29T13:10:29 * gslbadCheckRDNinDN:match = TRUE, attrVal = <DB>, normvalue = <DB>
2015-01-29T13:10:29 * gslbndnWithEscChar: origDN: NormDn:
2015-01-29T13:10:29 * [gslsbscRetCatalogAlias] Attribute orclnetdescstring is not indexed
2015-01-29T13:10:29 * [gslsbscRetCatalogAlias] Attribute creatorsname is not indexed
2015-01-29T13:10:29 * [gslsbscRetCatalogAlias] Attribute modifytimestamp is not indexed
2015-01-29T13:10:29 * [gslsbscRetCatalogAlias] Attribute createtimestamp is not indexed
2015-01-29T13:10:29 * Updating retry_cnt asr change log (success), sql=update asr_chg_log set retry_cnt = decode(retry_cnt, 1, -1, retry_cnt - 1)     where chg_no = :lpChangeNo AND retry_cnt != -1 AND server = :lpSrvr
2015-01-29T13:10:29 * 2015-01-29T13:10:29 * Recieved signal = 11, shutting down
END
]]

The error can occur on random OID entries (e.g., with OID used for tnsnames / database servicename entries only).

All nodes were rebooted after a mandatory OS patching, and the crashing temporarily stopped on one of the nodes only, but returned soon after.

Also cleared out and purged HIQ, as the error occurs immediately after an update to asr_chg_log.

Tried a relink of OID/LDAP client and server, to no help.


After further testing, OID is only crashing with the debug level value set high (117440511) and the replication server running.

It no longer crashes once debug is set to low level (1).


(*)Note: One requirement is to capture log data (including all operations, the client IP, the connection DN, the DN that was operated on, result code, search filters, etc), and this is the reason why the high level debug was applied.

Changes

Set high level debug in OID server.

Cause

To view full details, sign in with your My Oracle Support account.

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

In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.