2535340 - ABAP processes of instance [ABAP: UNKNOWN] did not start after 10:10 minutes. with 28: No space left on device in dispatcher trace file while installing a additional dialog instance. | SAP Knowledge Base Article

SAP Knowledge Base Article - Preview

2535340 - ABAP processes of instance [ABAP: UNKNOWN] did not start after 10:10 minutes. with 28: No space left on device in dispatcher trace file while installing a additional dialog instance.

Symptom

  • While installing additional application instance(Dialog Instance) you will face below error :

 <html> <head> </head> <body> <p> An error occurred while processing option <i>SAP NetWeaver 7.0 including Enhancement Package 1 Support Release 1 > Software Life-Cycle Options > Additional SAP System Instances > Oracle > Dialog Instance( Last error reported by the step: ABAP processes of instance  [ABAP: UNKNOWN] did not start after 10:10 minutes. Giving up.)</i>. You can now: </p> <ul> <li> Choose <i>Retry</i><br>to repeat the current step. </li> <li> Choose <i>Log Files</i><br>to get more information about the error. </li> <li> Stop the option and continue later. </li> </ul> <p> Log files are written to /tmp/sapinst_instdir/NW701/LM/AS/ORA/DI. </p> </body> </html>

L_B640.tmp.png

  • When we check in sapinst_dev.log we can see the entries as :

sapinst_dev.log:

INFO 2017-09-14 13:27:31.334 (root/sapinst) (startInstallation) [/bas/749_REL/bc_749_REL/src/ins/SAPINST/impl/src/modlib/iaxxbjsmod.cpp:83] id=modlib.jslib.childAppReturn
Execution of the command "/usr/sap/SID/DXX/exe/sapcontrol -prot NI_HTTP -nr xx -function GetProcessList" finished with return code 0. Output:

<DATE> <TIME>
GetProcessList
OK
name, description, dispstatus, textstatus, starttime, elapsedtime, pid
disp+work, Dispatcher, GRAY, Stopped, , , 20118
igswd_mt, IGS Watchdog, GREEN, Running, 2017 09 14 13:17:20, 0:10:11, 20119

ERROR 2017-09-14 13:27:31.565 (root/sapinst) (startInstallation) [/bas/749_REL/bc_749_REL/src/ins/SAPINST/impl/src/sapinst/CSiStepExecute.cpp:1117] id=controller.stepExecuted errno=FCO-00011
The step start with step key |NW_DI|ind|ind|ind|ind|0|0|NW_DI_Instance|ind|ind|ind|ind|di|0|start was executed with status ERROR ( Last error reported by the step: ABAP processes of instance EBP/D03 [ABAP: UNKNOWN] did not start after 10:10 minutes. Giving up.).

  • Above error points that the dispatcher is in grey status. Later when we check in dispatcher trace file we can see the entries as :

dev_disp :

*** ERROR => e=28 semget(3039988,1,2016) (28: No space left on device) [evtux.c 640]
*** ERROR => DpWpEvtInit: EvtCreate (rc=1) [dpxxwp.c 521]
*** DP_FATAL_ERROR => DpSapEnvInit: DpWpEvtInit
*** DISPATCHER EMERGENCY SHUTDOWN ***


Read more...

Environment

  • SAP NETWEAVER 7.0 , 7.1 , 7.2 , 7.3 , 7.4 , 7.5

 

Product

SAP enhancement package 1 for SAP NetWeaver 7.0

Keywords

kernel.shmmax  , e=28 semget ,  EvtCreate , DP_FATAL_ERROR , DpSapEnvInit , disp+work, Dispatcher, GRAY, DISPATCHER EMERGENCY SHUTDOWN , installing additional instance , startInstallation , ABAP: UNKNOWN did not start after 10:10 minutes. Giving up , controller.stepExecuted errno=FCO-00011 , KBA , BC-INS-UNX , Installation Unix , BC-CST-DP , Dispatcher, Task Handler , 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.