resmon process

[james gould]

Have a total of 32 process of the following
on the server

/etc/opt/resmon/lbin/registrar

Timestamp is from May 28th on all processes

Wondering how to correct or stop all of these
from running.

I think the process is used for event monitoring.

Had a power outage and the system took a hit
a couple of weeks ago, and the system has been
rebooted many times.

[Sridhar Bhaskarla]

James,

"registrar" process is invoked by inetd process. To confirm it look at the parent process of them and match with the the PID of inetd.

You can kill them all. It is used by EMS. If this system is part of serviceguard, you may see them running frequently.

-Sri

[james gould]

Thanks for the info.

We are running service guard on the server.

Can all of the process be killed, and if
so will it start to spawn more processes?

Right now the cluster software is not up on
this server, but we do have mount points
up on the secondary server.

[Sridhar Bhaskarla]

You can safely kill these processes as the cluster is down. Keep watching the processes and if they re-spawn and stay again, then you may have to look at your patches.

-Sri

[Joseph Loo]

hi,

please refer to this KB for restarting EMS:

http://www1.itrc.hp.com/service/cki/search.do?category=c0&mode=id&searchString=kbrc00010215&searchCrit=exactphrase&docType=Security&docType=Patch&docType=EngineerNotes&docType=BugReports&docType=Hardware&docType=ReferenceMaterials&docType=ThirdParty&search.x=43&search.y=7

if unable to view, look for KBRC00010215 under Technical Knowledge Base.

regards.

[Andrew Merritt_2]

A couple of things to check:

- Make sure you have a recent version of EMS and the OnlineDiags

- have a look at the log files in /etc/opt/resmon/log to see if something is being logged that explains why so many registrar processes are being started.

One thing in those files would be to look for responses in the client.log file with
Monitor Reply = RM_NO_MONITOR_FOUND