Symptom
System failed to start(Dispatcher status is Gray Stopped):
Following traces can be seen from dev_disp trace file:
... ...
*** ERROR => DpHdlDeadWp: W<XX> (pid <XXX>) died (severity=X, status=XXXXX, action=) [dpxxwp.c XXXX]
DpTraceWpStatus: child (pid=<XXX>) exited with exit code 255
*** WARNING => DpHdlDeadWp: W<XX> was inside a critical section (semaphor) [dpxxwp.c XXXX]
... ...
*** DP_FATAL_ERROR => DpWpCheck: no more work processes
*** DISPATCHER EMERGENCY SHUTDOWN ***
... ...
And following traces can be seen from work process trace file (dev_wX):
... ...
A PXA: using abap/buffersize XXXXXXXX
A abStoreSetDiagMode: set ABAP mm diag mode to OFF
O ab_pbinit: max_map_count = XXXXXXXX: ok.
O ab_pbinit: Program generation trace switched on.
O
O ---PXA-------------------------------------------
O PXA INITIALIZATION
O ab_pbinit: System page size: 4kb, total admin_size: XXXXXX kb, dir_size: XXXXXX kb.
I
I <Timestamp>
I *** ERROR => shmget(10106,XXXXXXXXX,2016) (22: Invalid argument) [shmux.c XXXX]
... ...
Read more...
Environment
64-bit Linux OS
Keywords
KBA , BC-CST-DP , Dispatcher, Task Handler , 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.