SAP Knowledge Base Article - Preview

2411659 - Stderr log growthing quickly

Symptom

One of stderr*.log is growthing very fast and has huge size, e.g. more than 100GB, this results in file system full situation finally.

So far we have the following known cases reported into BC-CST component:

1. SAPHTTPA RFC trace ("Set RFC trace" in note 1947876) is enabled for a long tiem. Stderr*.log file is growthing very fast due to this.

2. IGS writes a lot of unnecessary entries in stderr*.log.
e.g in stderr*.log:
***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]

 


Read more...

Environment

Release and OS platform independed.

Keywords

stderr , 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 ONE Support launchpad (Login required).

Search for additional results

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