Symptom
Important: This article intends to provides RCA for a crash event that fits the criteria explained below. It does not aim to resolve an ongoing startup problem.
SAP NetWeaver application server running at a Unix-like operating system becomes unstable and crashes. The following information can be found at the traces of the kernel processes:
- Work process trace (dev_w*):
*** ERROR => e=43 semop(1114127,(0,0,0),(0,1,0),2) (43: Identifier removed) [evtux.c 1121] - Dispatcher trace (dev_disp):
*** ERROR => e=22 semop(851975,(0,-1,6144),1) (22: Invalid argument) [semux.c 577]
*** ERROR => DpITmSlotAllocate: SemRq [dpxxtool2.c 4391]
*** ERROR => e=22 semop(851975,(0,-1,6144),1) (22: Invalid argument) [semux.c 577]
*** DP_FATAL_ERROR => DpTmDisconnect: SemRq
*** DISPATCHER EMERGENCY SHUTDOWN *** - ICM trace (dev_icm):
*** ERROR => e=43 semop(2293811,(16,0,0),(16,1,0),2) (43: Identifier removed) [evtux_mt.c 1121]
*** ERROR => EvtWtRst(16997) failed: 1 [mpixx_mt.c 6199]
*** ERROR => IcmMpiWatchDogThread: MpiSelSelect failed(rc=3): cleanipc was called for this instance [icxxthr_mt.c 1512]
*** IcmMpiWatchDogThread: exit thread ***
(...)
*** ERROR => e=22 semop(1081358,(0,-1,6144),1) (22: Invalid argument) [semux_r_mt.c 577]
*** ERROR => DpRqIPutIntoQ: SemRq (rc=1) [dpxxqueu_mt. 590]
Please note that ICM already provides the cause by explicitly writing: "cleanipc was called for this instance"
Read more...
Environment
- SAP NetWeaver
- Unix-like Operating systems
Product
Keywords
KBA , BC-CST-DP , Dispatcher, Task Handler , BC-OP-LNX , Linux , BC-OP-AIX , IBM AIX , BC-OP-HPX , HP-UX , BC-OP-SUN , SUN Solaris , 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.