SAP Knowledge Base Article - Preview

2536904 - Sapstartsrv does not accept new requests due to pending CLOSE_WAIT entries

Symptom

  • Sapstartsrv process no longer accept connections and no longer responds to web method requests.
  • Attempts to issue web method commands to the affected process turns out like below example:

sapcontrol -nr 00 -function GetSystemInstanceList

FAIL: NIECONN_BROKEN (Broken pipe), NiRawWrite failed in plugin_sapfsend()

  • At OS / network level, it is possible to find many unfinished connections on which the affected sapstartsrv process acts as server:

netstat -nap | grep 50013

tcp 1 0 <server_IP>:50013 <client_IP>:19571 CLOSE_WAIT 122984/sapstartsrv
tcp 1 0 <server_IP>:50013 <client_IP>:29525 CLOSE_WAIT 122984/sapstartsrv
tcp 1 0 <server_IP>:50013 <client_IP>:19608 CLOSE_WAIT 122984/sapstartsrv
(...)

*** SAPSTARTSRV process listens on port 5$$13 where the $$ stands for the instance number.
*** The port "50013" was used in this example as the affected sapstartsrv was the one associated with instance "00".


Read more...

Environment

  • SAP Netweaver
  • ABAP Startup framework
  • UNIX based Operating Systems

Product

SAP NetWeaver all versions

Keywords

startup, SUM, webmethod, connection, socket, sapstream, sapcontrol, intialization, , KBA , BC-CST-STS , Startup Service , BC-NET , Formerly used for network tests , 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.