imapd Is Continually Dumping Core (Doc ID 1353094.1)

Last updated on SEPTEMBER 14, 2016

Applies to:

Oracle Communications Messaging Server - Version 5.2.0 and later
Information in this document applies to any platform.
***Checked for relevance on 11-Mar-2013***

Symptoms

Frequent imapd core dumps:
  - causing system to stop automatically restarting
  - cluster failover
  - often core dump immediately after restart
  - thus, even manual restart is useless

The output from pstack shows the thread that crashed looked like:

----------------- lwp# 8175 / thread# 8175 --------------------
ffffffff7b600588 memmove (10705a6c0, fffffffefa2019fd, 31bf, 4bd6, 103fff9b3, 10007f835) + 108
ffffffff7d81d31c ASock_Buffer (10705a6c0, fffffffefa2019fd, 31bf, 80808080, ff0000, 80808080) + 7c
0000000100053b84 __1cOindex_fetchmsg6FpnIimap_ctx_LLILLiI_i_ (10f56bd60, 19fd, 31bf, 0, 1, c800) + 9ac
00000001000541f8 __1cSindex_fetchsection6FpnIimap_ctx_LpcpkcLLiI_i_ (10f56bd60, 4bd6, 10ac3fe20, fffffffea0e9e590, 0, 0) + 638
000000010005a078 __1cQindex_fetchreply6FpnIimap_ctx_pnHmailbox_Ipv_i_ (100185fa8, 10f56c278, b9a, ffffffff6a813698, ffffffff2b906a00, 0) + 1bc8
000000010005303c __1cRindex_forsequence6FpnIimap_ctx_pnHmailbox_pcipF13Ipv_i5_i_ (10f56bd60, 10f56c278, 103f3d78e, 1, 1000584b0, ffffffff6a813698) + 52c
000000010004be20 __1cLindex_fetch6FpnIimap_ctx_pnHmailbox_pcipnLfetchargs_t__i_ (10f56bd60, 10f56c278, 103f3d78e, 1, ffffffff6a813698, 0) + 120
000000010002e668 __1cJcmd_fetch6FpnIimap_ctx_pc2i_v_ (10f56bd60, 103f3d780, 103f3d78e, 1, 8, 101010101010101) + 650
000000010001bab0 __1cLprocess_cmd6FpnIimap_ctx_ipGpv_v2_i_ (10f56bd60, 20, 1000202b0, 10f56bd60, ff0000, 80808080) + fa0
00000001000201f8 firstcmdline (10f56bd60, 0, ffffffff7b94a340, 1002fddf4, ffffffff2b906a00, 0) + cd0
ffffffff7d80f6f0 GDispCx_Dispatch (1002fdd48, 106423de8, 103b68298, 0, 0, 0) + 208
ffffffff7d810068 GDispCx_InternalWork (103b68298, 14000, 0, 0, ffffffff7d80fce0, 1) + 388
ffffffff7b7d8254 _lwp_start (0, 0, 0, 0, 0, 0)


And dbx showed:

t@8175 (l@8175) terminated by signal BUS (object specific hardware error)
0xffffffff7b600588: _memmove+0x0108: ldub [%o1 + %o0], %o4
Current function is ASock_BufferInternal
1470 memmove(me->pBufed + me->nBufedAmt, pBuf, nLen);

Changes

Recent patch installation required failing the application over from one node of the cluster to the other.

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