topic Re: what to do with WBEM$ process in Operating System - OpenVMS

what to do with WBEM$ process

Byron Fowlkes — Fri, 05 Dec 2008 16:43:22 GMT

during last night's maintenance on network hardware a switch/router configuration changed and today our OpenVMS cluster has its performance being degraded by a process named WBEM$CPQNIC on all nodes.. what can I do to investigate this process.. degradation means that this process alone is usurping most available CPU cycles and affecting normal user tasks.. I have no knowledge of this service?

Re: what to do with WBEM$ process

Volker Halle — Fri, 05 Dec 2008 16:48:07 GMT

Byron,

looks like a looping process. Shutdown WBEM (=Insight Management Agent) and restart it:

$ @SYS$SPECIFIC:[WBEM]WBEM$SHUTDOWN

and

$ @SYS$SPECIFIC:[WBEM]WBEM$STARTUP

Here is the pointer to the WBEM page at the HP site:

http://h71000.www7.hp.com/openvms/products/mgmt_agents/

Volker.

Re: what to do with WBEM$ process

Byron Fowlkes — Fri, 05 Dec 2008 17:09:19 GMT

this answer seems to be correct.. after a bounce on each node this process subsided and things look much better now..I am unfamiliar with what this thing does but I certainly know more about it now.. much thanx Volker

Re: what to do with WBEM$ process

Hoff — Fri, 05 Dec 2008 17:13:29 GMT

That's a bug in one of the HP management agents.

If you have support in place, contact HP for help.

As part of calling up HP, you can sample the PCs (SHOW PROCESS /CONTINUOUS or such) to get an idea of what range of PCs are involved in what is probably a loop. Gather a dozen or two of the PC values.

You can also drop the process to priority zero and let it tussle with the idle process loop. Once you have some PCs, you can also then restart WBEM or force the process to suspend temporarily via SET PROCESS /SUSPEND, too.

When you contact HP, you'll be asked to confirm you are on the current version of the WBEM tools. If not, you'll be asked to upgrade to the current versions.

Re: what to do with WBEM$ process

Jan van den Ende — Fri, 05 Dec 2008 17:20:59 GMT

Byron,

from your Forum Profile:

I have assigned points to 10 of 2 responses to my questions.

Some dating back to 2006!

Maybe you can find some time to do some assigning?

http://forums1.itrc.hp.com/service/forums/helptips.do?#33

Mind, I do NOT say you necessarily need to give lots of points. It is fully up to _YOU_ to decide how many. If you consider an answer is not deserving any points, you can also assign 0 ( = zero ) points, and then that answer will no longer be counted as unassigned.
Consider, that every poster took at least the trouble of posting for you!

To easily find your streams with unassigned points, click your own name somewhere.
This will bring up your profile.
Near the bottom of that page, under the caption "My Question(s)" you will find "questions or topics with unassigned points " Clicking that will give all, and only, your questions that still have unassigned postings.

Thanks on behalf of your Forum colleagues.

PS. nothing personal in this. I try to post it to everyone with this kind of assignment ratio in this forum. If you have received a posting like this before please do not take offence none is intended!

PPS. Zero points for THIS entry, please.

Proost.

Have one on me.

jpe

Re: what to do with WBEM$ process

Zeni B. Schleter — Mon, 08 Dec 2008 16:06:01 GMT

For what it's worth we had seen the looping NIC process at our site as well. We have updated the WEBES software a couple of times since the last occurrence.

Re: what to do with WBEM$ process

Volker Halle — Mon, 08 Dec 2008 16:13:35 GMT

Zeni,

the WBEM$CPQNIC process belongs to the WBEM software (Web-Based Enterprise Management, Product kit name: Vxx_MGMTAGENTS), now being replaced by HP SMH (System Management Homepage).

WEBES (Web Based Enterprise Services) is a collection of Service Tools (SEA, CCAT).

Volker.

Re: what to do with WBEM$ process

Wim Van den Wyngaert — Tue, 09 Dec 2008 14:10:17 GMT

We reset our (old) webes stuff every night to prevent processes looping and memory eating.

We do :
stop desta
wait 1 minute
start desta
wait 2 minutes
start desta again because it sometimes fails the first time

fwiw

Wim