PRM (C.02.01) - prm3d hoggig CPU

[Alzhy]

We initially noticed this on mostly idle systems.. prm3d would constantly hit 100% CPU util... Then last weekend, in a busy system it gobbled up CPU resources... AFAIK, we have all the latest and greatest PRM related patches applied..

prm3d is supposedly the agent that allows for remote administration of PRM. We have not used prm yet nor do we have actve PRM ocnfigurations anywhere... What could possibly trigger its high CPU cycles?

[Marco Santerre]

I have also noticed that in the past, but due to the the fact that I'm not using PRM, I went and disabled it in /etc/rc.config.d

[melvyn burnard]

prm3d gets started automatically, whether you are using PRM or not.
If you are not using it, simply do:
Change PRM_RMTCONF variable from 1
(default)to 0:

PRM_RMTCONF=0
then do
/sbin/init.d/prm stop
/sbin/init.d/prm start

If you DO need to use it, which version of PRM and which version of HP-UX are you using?
swkist -l product |grep PRM

[Alzhy]

We are using HPUX 11i OEUR JUN 2003 which contains C.02.01 release of PRM. HWE/QPK 09/03 applied as well as all other *** rated patches pertinent to our environment...

[melvyn burnard · Accepted solution]

Ok, this is the version of PRM htat exhibits this issue, hte newer version, due out in March, will not have thi sproblem.
The fix is to eihter turn prm3d off see my previous post) or install the latest 1.4.X JRE from

http://www.hp.com/go/java

Installing the RTE will install /opt/java1.4 onto your system. Then you must link /opt/prm/bin/jre to /opt/java1.4:

# cd /opt/prm/bin
# mv jre jre.bk
# ln -s /opt/java1.4/jre jre

prm3d must now be restarted via:
kill -9 pid
/sbin/init.d/prm start

You can doublecheck to ensure the correct version of JRE is running:

kill -3 pid

Check the /var/opt/prm/prm3d.log.


Or await hte newer version in March.

[Jeff Schussele]

Hi,

To add to Melvyn's last post, I'd like to point out that IF you do go to Java 1.4.X - go to at least Java 1.4.1.04 or higher as all Java 1.4 prior have a security warning.

My 2 cents,
Jeff

[Jeff Schussele]

Hi Nelson,

And another note on Melvyn's post.

Reverse the order of his steps.
Do the prm stop *before* you edit the conf file.

IF you do them in the order he listed, you'll get an error stating that the PRM_RMTCONF=0 & it won't stop it.

Rgds,
Jeff

[Jonathan Fears]

I just want to add a few notes to this discussion. First, prm3d is not the cause of the CPU hogging, but rather the manner through which pthread issues in JRE 1.4.1.00 are seen. It has been fixed in JAVA version 1.4.1.01. The expected AR0304 release of PRM will contain JRE 1.4.2 which also contains the fix.
If you are not doing remote management of PRM, killing prm3d and changing the value of PRM_RMTCONF to 0 in the /etc/rc.config.d/prm file is the best solution. Putting a newer Java on the system and creating the symlink is also a viable solution, but can have other implications when/if PRM is ugraded on the system.

[Alzhy]

Melvyn Burnard, Any update on this?

We have re-imaged our systems with the DEC 2003 Release, latest patches (CPM) and we are still seeing this ...

[Jonathan Fears]

Above I had stated the fix was going out with Java 1.4.1.01 according to an issue opened against the Java product. I looked at the Decemeber 2003 release and it contains Java 1.4.1.02.02. I am not sure why the problem is still occurring (maybe something surrounding the security issues with Java 1.4.X that are resolved in 1.4.1.04).

If you are not doing remote mgmt with PRM, again it is best just to stop prm3d
(prm3d -stop) and change the PRM_RMTCONF option to 0 in /etc/rc.config.d/prm. If you are using it, follow Melvyn's commands in an earlier post with Java 1.4.2. This is the Java version bundled with PRM 2.2 and it does not exhibit this problem.

[derek b smith_1]

Hi all.... I would like to know what prm3d is exactly other than it name? I want detail!thanks!

derek

[Jonathan Fears]

prm3d is the remote management daemon for PRM. This daemon must be running on the remote systems that you would like to manage when using PRM's GUI, xprm. By default, the TCP/IP port used for remote connections is 9610. You can override this by starting prm3d on the command line with a different port number.

[Alzhy]

I turn it off on all our 11i Enterprise servers since we do local prm configurations anyways.

We also do command line loads of the config as well as enabling/disabling of resource management.

[derek b smith_1]

I know what it is called , but is there a link so I can get some detail like what it is used for?

[Alzhy]

http://docs.hp.com/hpux/onlinedocs/B8733-90011/B8733-90011.html

[Jonathan Fears]

I'm not sure what level of detail you are looking for. The document linked to above does go into different management scenarios for xprm but not necessarily information about prm3d itself. If you still have other questions, please post them.

[derek b smith_1]

the link is all I needed thanks!