EMS process p_client using 40-70% of CPU Processing

[Laurie A. Krumrey]

Hi All,

One of my dba's is concerned that a process
he see's p_client (from EMS) is using 40-70% of
the hp-ux 11.0 CPU processing (using glance).

I think EMS is running and I am not sure if it's set up right or if in fact we really need
it. My dba wants the p_client to stop running
or use less processing resources.

Can someone give me some information here on
EMS? I have read the documentation and I
am not sure if it's set up right. Can I do
anything to stop p_client from running?

Do I really need EMS if I don't know what's it's doing.

This is what happens when you let your technical end-users use glance..They see stuff
they don't like (ie. p_client) and then they
want you to justify why it's using so much
CPU Time...As if it's hurting their Oracle Jobs..

Anyway, if someone could shead some light on this subject for me it would be greatly
appriecated.

TIA,
Laurie

[eran maor · Accepted solution]

Hi laurie

i found a doc about p_client that is taking a lot of cpu.

it happen becuase someone copy the system from another system.

i m sending you a doc if this is your case

i can also tell you that you dont have to run the EMS monitor if you are not using it
EMS monitor give you details about hardware problem and you can also config it to watch diff software

if you want to stop the EMS do this

1. edit the file /etc/rc.config.d/ems
and change the EMS_ENABLED to zero

2. to stop the ems :
/sbin/init.d/diagnostic stop

[Laurie A. Krumrey]

What do you mean someone copy the system from
another system? Do you mean Disk Mirroring?

Does this EMS work with the Predictive software
package? I'm tempted to just stop this EMS
stuff, since I am not too sure about it.

Laurie

[Pedro Sousa]

The EMS is a feature from Online Diagnostics.
I advise you not to stop it forever, because it's very helpfull on some situations by preventing some future problems. It helped me 2/3 times.
p_client is the "persistence file" that is in charge of restarting the EMS daemons if in some case they were stopped.
Install these HP recommended patches:
PHSS_20684
PHSS_22225
PHSS_22896

Good luck.

[Laurie A. Krumrey]

Well we don't have Predictive Support running
and set up right now, so I tried to stop
EMS and I did the above, however p_client
is still running and it won't let me kill the
process because it's tied to pid 1. ps -ef | grep p_client

root 18695 1 0 10:05:09 ? 0:55 /etc/opt/resmon/lbin/p_client

TIA,
Laurie

[Bob Hochstetler]

The p_client process is respawned from the /etc/inittab file (under the ems4 entry). I once had to comment that line out temporarily to keep p_client from restarting interfering with a 3rd party software product we were evaluating.

[Patrick Gorman]

Hi Laurie,

EMS is the Event Monitoring System, it works in conjunction with Predictive and the Diagnostics. You don't necessarily have to run or configure Predictive to have EMS running on your system. If you have your support through HP you should have your CE configure Predictive for you. The idea is that these tools monitor your system and look for two things; A) potential problems, and B) real problems that exist now. EMS should not be using that much CPU, I would agree with the earlier assessment to install or research patches that might apply to your situation.

If you feel that your business does not require event notification than you may want to go ahead and turn off EMS. If your system is running a business critical application, you should have some automated messaging and management solutions installed.