SAP Knowledge Base Article - Preview

2411659 - Stderr log growthing quickly


The stderr*.log file is experiencing rapid growth, reaching an enormous size, such as over 100GB. This eventually leads to a scenario where the file system is completely filled.

The following known instances have been identified:

  1. The SAPHTTPA RFC trace (as referred to in KBA 1947876 - Set RFC trace) has been activated for an extended period. This is causing the stderr*.log file to expand quickly.
  2. The IGS is generating a large number of unnecessary entries in the stderr*.log. For instance, in the stderr*.log file, the entries look like this:
***LOG Q0I=> NiIWrite: WSASend (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 3948]
*** ERROR => NiIWrite: SiSendV failed for hdl 1 / sock 528
(SI_ECONN_BROKEN/10054; I4; ST; <IP of IGS server>:<port>) [nixxi.cpp 3948]



  • Operating System independent
  • Database independent
  • SAP NetWeaver
  • SAP Web Application Server for SAP S/4HANA
  • ABAP Platform 


ABAP platform all versions ; SAP NetWeaver all versions ; SAP Web Application Server for SAP S/4HANA all versions


stderr, SAPHTTPA RFC, IGS, NiIWrite: WSASend (10054: WSAECONNRESET: Connection reset by peer), igs/tracelevel , KBA , BC-CST-LL , Low Level Layers , 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.