SAP Knowledge Base Article - Preview

3379182 - LNX: system hang with call "__GI___open64" on top of C-stack

Symptom

SAP application server gets hang intermittently.

Stack trace dumped into work process traces shows it is stuck in while accessing the security storage file.

M  ------------------ C-STACK ----------------------
dw.sapR1P_D00[S](LinStackBacktrace+0xa9)[0x555bb49396c4,0x7b66c4]
dw.sapR1P_D00[S](LinStack+0x4d)[0x555bb493c6ba,0x7b96ba]
dw.sapR1P_D00[S](CTrcStack2+0x4b)[0x555bb4938466,0x7b5466]
dw.sapR1P_D00[S](ThStackHandler()+0x2f5)[0x555bb47b3d03,0x630d03]
dw.sapR1P_D00[S](DpTrcOnOff(int)+0x32b)[0x555bb472b8eb,0x5a88eb]
<signal handler called> [0x7f8c3836f630,0xf630]
libc.so.6[S](__GI___open64+0x2d)[0x7f8c3808191d,0xef91d]
libc.so.6[S](__GI__IO_file_fopen+0xd0)[0x7f8c3800d520,0x7b520]
libc.so.6[S](__fopen_internal+0x74)[0x7f8c38000ca4,0x6eca4]
dw.sapR1P_D00[S](fopenU16+0xc5)[0x555bb6b55f15,0x29d2f15]
dw.sapR1P_D00[S](rsecssfs_FileOpen+0x7b)[0x555bb60240a9,0x1ea10a9]
dw.sapR1P_D00[S](RSecSSFsListRecords+0x9e)[0x555bb6029daa,0x1ea6daa]
dw.sapR1P_D00[S](rsecxdb__FillSecStoreFsBuffer+0xb1)[0x555bb6b73921,0x29f0921]
dw.sapR1P_D00[S](rsecxdb__GetKey+0xdf)[0x555bb6b7492f,0x29f192f]
dw.sapR1P_D00[S](rsecxdb__read_and_migrate+0x19b)[0x555bb6b7514b,0x29f214b]
dw.sapR1P_D00[S](RSecDReadItemEx+0xbf)[0x555bb6b75e5f,0x29f2e5f]
dw.sapR1P_D00[S](LocFunc_ReadKeyFromDB.constprop.0+0x86)[0x555bb6b69886,0x29e6886]

<snipped>

M  ------------------ c-stack end ------------------


Read more...

Environment

  • SAP system on Linux server

Product

SAP S/4HANA 2022

Keywords

__GI___open64, __GI__IO_file_fopen, __fopen_internal, fopen, hang, stuck , KBA , BC-OP-LNX , Linux , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.