Skip to Content

dev_w5 growing incredibly fast

Dear experts,

I would like to share with you another quite annoying issue, which we are experiencing in our landscape.

Now the suffering system is a DEV BW ABAP instance. As said in the title, dev_w5 is growing very very

fast, it has twice filled up the filesystem and caused the system to hang...

The contents of the file are:

I MpiIEvtOpen: retry with next key

I *** ERROR => no more free event-flags. [mpixx.c 5876]

I {root-id=8010E03E596C1EE39EC13F73B724DD66}_{conn-id=554F3B826476490FE1000000AC123F1C}_1

I MpiIEvtOpen: retry with next key

I *** ERROR => no more free event-flags. [mpixx.c 5876]

I {root-id=8010E03E596C1EE39EC13F73B724DD66}_{conn-id=554F3B826476490FE1000000AC123F1C}_1

I MpiIEvtOpen: retry with next key

I *** ERROR => no more free event-flags. [mpixx.c 5876]

I {root-id=8010E03E596C1EE39EC13F73B724DD66}_{conn-id=554F3B826476490FE1000000AC123F1C}_1

I MpiIEvtOpen: retry with next key

I *** ERROR => no more free event-flags. [mpixx.c 5876]

I {root-id=8010E03E596C1EE39EC13F73B724DD66}_{conn-id=554F3B826476490FE1000000AC123F1C}_1

I MpiIEvtOpen: retry with next key

I *** ERROR => no more free event-flags. [mpixx.c 5876]

I {root-id=8010E03E596C1EE39EC13F73B724DD66}_{conn-id=554F3B826476490FE1000000AC123F1C}_1

I MpiIEvtOpen: retry with next key

I *** ERROR => no more free event-flags. [mpixx.c 5876]

I {root-id=8010E03E596C1EE39EC13F73B724DD66}_{conn-id=554F3B826476490FE1000000AC123F1C}_1

I MpiIEvtOpen: retry with next key

I *** ERROR => no more free event-flags. [mpixx.c 5876]

I {root-id=8010E03E596C1EE39EC13F73B724DD66}_{conn-id=554F3B826476490FE1000000AC123F1C}_1

I MpiIEvtOpen: retry with next key

I *** ERROR => no more free event-flags. [mpixx.c 5876]

I {root-id=8010E03E596C1EE39EC13F73B724DD66}_{conn-id=554F3B826476490FE1000000AC123F1C}_1

I have found a few notes regarding this problem, but it is about the ICM and WebDispatcher, not about a dialog

process. Notes 2000428 (for oracle Linux, but we are running on Solaris 10), 715400 and 1608350 (recommending

to use Kernel 7.01, we are already at 7.21 patch 201).

I sent note 715400 to our Solaris admins, but they said that it is not valid for Solaris 10.


Based on a screenshot from SM50, I think that the Solution Manager is causing the issue:


Please advise what to do ? I can stop the work process, but I'm not sure that this will help... Kindly advise quickly,

because as soon as I leave the office, the system will be down again in just a few hours...

Many thanks!

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Posted on May 12, 2015 at 12:19 PM

    Hi,

    It seems that this work process is "trapped" in some kind of infinite loop.

    Please execute "kill -USR2 23295" (at OS level), wait for a few seconds (5 - 10 seconds), then execute "kill -USR1 23295".

    These kill signals will not terminate the process. USR2 will increase the trace level by 1, while USR1 decreases the trace level by 1. The SAP note 112 describes this.

    Share the level 2 trace entries here.

    After you've captured the level 2 trace successfully, you can try restarting this work process through SM50, as a workaround.

    Regards,

    Isaías

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on May 12, 2015 at 12:45 PM

    Hello Symon,

    How many work processes do you have ? Can you please review note: 9942 - Maximum number of work processes


    Regards,

    Siddhesh

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on May 14, 2015 at 11:01 AM

    Have you tried reducing the trace level from SM50 for this work process.

    Once done, kill it from OS level.

    Regards,

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.