Download as pdf or txt
Download as pdf or txt
You are on page 1of 2

SAP Knowledge Base Article

2482846 - Standalone Gateway, YELLOW, Running but not responding


Component: BC-CST-GW (Basis Components > Client/Server Technology > Gateway/CPIC), Version: 2,
Released On: 29.10.2018

Symptom
The status of standalone gateway process is yellow Running but not responding.
SAPMMC:

sapcontrol -nr <instance number> -function GetProcessList:

GetProcessList
OK
name, description, dispstatus, textstatus, starttime, elapsedtime, pid
gwrd, Gateway, YELLOW, Running but not responding, <time stamp>, 0:36:08, <pid>

Normally, you will see following error in sapstartsrv trace log.

sapstartsrv.log

*** ERROR => GwMonDispStatistic: GwMonBufRequest failed [gwxxmon.c 847]


GwMonBufRequest: monitor disabled
GwMonReleaseGwConnection: handle=32
NiICloseHandle: shutdown and close hdl 32/sock 14
*** ERROR => GwMonDumpInfo: GwMonBufRequest failed [gwxxmon.c 1892]
GwMonDumpInfo: action=DUMP_ADM, index=0, dest=2
GwMonBufRequest: command=DUMP

Cause
sapstartsrv is not able to get the status of standalone gateway

Resolution
Possibility 1): gw/monitor parameter

Parameter gw/monitor determines whether the gateway can be monitored by a client or not.
Possible value of gw/monitor:
gw/monitor = 0 (in principle no query)
gw/monitor = 1 (local query only)
gw/monitor = 2 (local and remote query)
if gw/monitor = 0 is defined in Standalone Gateway profile, gateway monitoring is disabled and you will see following trace
log in gateway trace log (dev_rd), sapstartsrv is not able to get gateway status, you therefore get "YELLOW, Running but not
responding" results.

dev_rd:

GwIExecMonCmd:received monitor command from <host> [IP], not allowed (gw/monitor=0)

You should delete gw/monitor = 0 from Standalone Gateway profile, restart sapstartsrv service by "sapcontrol -nr <ins.no> -
function RestartService". Then, sapstartsrv is able to monitor Standalone Gateway and "Running but not responding"
symptom will be solved.
Possibility 2): Standalone Gateway itself
From sapstack result and level 3 gateway trace, you will notice that it is hanging at GwICheckConnPending

sapstack <pid of gateway>

#0 0x00000000005d5db3 in GwICheckConnPending() ()
#1 0x0000000000688aab in nlsui_main ()
#2 0x00000000005b95da in main ()

dev_rd(level 3)

(... ...)

GwICheckRoutes: check routes (120 secs)


GwICheckConnPending: check pending connections (60 secs)
GwICheckConnPending: check pending client hdl (#<number>) (60 secs)

This is a kernel bug. The correction of the issue has been released with SAP Note 2513365.

Attributes
Key Value

Other Components Basis Components > Client/Server Technology > Startup Service (BC-CST-STS)

This document refers to


SAP Note/KBA Component Title

2513365 BC-CST-GW sapcontrol : gwrd, Gateway, YELLOW, Running but not responding

You might also like