Insight Remote Support
cancel
Showing results for 
Search instead for 
Did you mean: 

ISEE spawning /etc/opt/resmon/lbin/registrar processes

SOLVED
Go to solution
Richard Murden
Regular Advisor

ISEE spawning /etc/opt/resmon/lbin/registrar processes

We installed ISEE, ISEEPlatform_A.03.50.854_HP-UX_B.11.00_32+64.depot and have the latest stm v29 on 11.00. After about a day ISEE began spawning the registrar processes that were taking up huge amount of CPU causing or DNS to fail. Anybody know why the processes were spawned. Is this normal?
9 REPLIES
Frauke Denker_2
Esteemed Contributor

Re: ISEE spawning /etc/opt/resmon/lbin/registrar processes

Hello,
the latest version for the STM for HPUX 11.0 is A.44.00 (march 2004), A.29 from December 2001, which is the minimum Diagnostic level for ISEE. But anyway this should not be the reason for this error. ISEE should not caused the registrar using so much CPU time. Have you checked the /var/opt/resmon/log/registrar.log for any hints? How ofter does this error occure. Does it occur even if ISEE is not installed? Have you tried to restart EMS?
Regards
Frauke
Richard Murden
Regular Advisor

Re: ISEE spawning /etc/opt/resmon/lbin/registrar processes

I have attached the registrar.log file. It references dm_stape but we have had no problems with our tape drives. There area few other errors that I am not sure of. This is the first time we had the registrar processes out there tat I know of. We had just installed ISEE the other day so everyone believes its ISEE. I talked to HP and they had me comment out the registrar process out of the inetd.conf file saying it is some of TCPIP thing that is no longer used. ISEE is now running with no problems so I am beginning to believe that is wasn't ISEE that spawned the processes.
Thanks,
Richard
Mic V.
Esteemed Contributor

Re: ISEE spawning /etc/opt/resmon/lbin/registrar processes

The registrar process is/was part of EMS, the event monitoring service. At any rate, it definitely pre-dates ISEE by a number of years.
What kind of a name is 'Wolverine'?
Frauke Denker_2
Esteemed Contributor
Solution

Re: ISEE spawning /etc/opt/resmon/lbin/registrar processes

Hello Richard,
the registrar is definitely needed for EMS, without this process ISEE will not work correctly. For the version A.29 a patch is needed for EMS (PHSS_28843), it might help to install this. In addition you should restart EMS using the following procedure:
1) Stop the registar if neccesary by commenting out the 1 entries in /etc/inetd.conf and re-reading the inetd configuration with inetd -c

2) Issue ps -ef | grep registrar to check if any registrar processes are remaining still, kill them if necessary

3) Stop monitoring
# /etc/opt/resmon/lbin/monconfig
Select (K)ill (disable) monitoring

ATTENTION! Within a Serviceguard Cluster, package dependencies might be configured, which could cause a package to switch,
in case a resource would go to a DOWN state.
In case EMS is stopped, this resource would be considered to be DOWN and the package would switch.
If you are unsure, follow the instructions in the document before you go ahead!

4) Issue ps -ef | grep monitor to check if any monitors are still running, kill them if necessary


5) Stop p_client
Comment out the p_client entry in /etc/inittab :
# vi /etc/inittab

6) Change the following line
ems4:3456:respawn:/etc/opt/resmon/lbin/p_client
to
#ems4:3456:respawn:/etc/opt/resmon/lbin/p_client

7) Reread /etc/inittab :
# init q


8) Issue ps -ef | grep p_client to check if p_client is still running, if yes kill the process


9) Delete the persistence files and pipes
# cd /etc/opt/resmon/persistence
# rm p*
# rm m*
# cd /etc/opt/resmon/pipe
# rm *


10) Have diagnostics remap the system hardware
#cstm
cstm>remap
cstm>quit

Allow enough time for remap to finish before restarting the monitors.
When the remap is in progress you get the message ***Remap in progress*** when issuing map at the cstm prompt;
when the remap has finished the map is displayed when issuing the command map at the cstm prompt.
It might take up to a few minutes depending on the amount of hardware connected.


11) Clean up monitor flags in the diagnostics directory
# cd /var/stm/data/tools/monitor
# rm *.hwa


12) Re-enable registrar in /etc/inetd.conf and run inetd -c


13) Restart p_client
# vi /etc/inittab
Change the following line
#ems4:3456:respawn:/etc/opt/resmon/lbin/p_client
back to
ems4:3456:respawn:/etc/opt/resmon/lbin/p_client

14) Re-read /etc/inittab :
# init q


15) Restart the EMS monitors
# /etc/opt/resmon/lbin/monconfig
Select (E)nable Monitoring

It might be a good idea to update the diagnostics. Be careful if this is a service guard cluster when you try to uninstall the support tools. If the above procesure help resolving the registrar problem, you can update the support toolssimply by doing a swinstall for the new version without an previous uninstall.

Regards
Frauke
Richard Murden
Regular Advisor

Re: ISEE spawning /etc/opt/resmon/lbin/registrar processes

Thanks for th einformation. I have completed the steps and will let you know in a few days if that resolved the problem. So far, its doing well!
Thanks,
Richard
Richard Murden
Regular Advisor

Re: ISEE spawning /etc/opt/resmon/lbin/registrar processes

Thanks, it worked!
Richard
ronnie summers
Occasional Visitor

Re: ISEE spawning /etc/opt/resmon/lbin/registrar processes

I followed this process and freed up some needed space in root file system. After, I am not seeing a registrar process running with a #ps -ef |grep registrar. Can you advise?
Avinash20
Honored Contributor

Re: ISEE spawning /etc/opt/resmon/lbin/registrar processes

Start the diagmond process:
/usr/sbin/stm/uut/bin/sys/diagmond
Then enable EMS:
/etc/opt/resmon/lbin/monconfig
Select (E)nable Monitoring
"Light travels faster than sound. That's why some people appear bright until you hear them speak."
Shankaraiah
Occasional Visitor

Re: ISEE spawning /etc/opt/resmon/lbin/registrar processes

Richard,

i have similer issue on my production system.
i tried your Exact procedure on my test system and i failed to see registrar process.

How do i start it again?

# ps -ef |grep registrar
root 21589 17986 1 11:08:09 pts/1 0:00 grep registrar
# /usr/sbin/stm/uut/bin/sys/diagmond
# ps -ef |grep registrar
root 21599 17986 1 11:08:27 pts/1 0:00 grep registrar
# /etc/opt/resmon/lbin/monconfig



============================================================================
=================== Event Monitoring Service ===================
=================== Monitoring Request Manager ===================
============================================================================

EVENT MONITORING IS CURRENTLY ENABLED.
EMS Version : A.04.20
STM Version : A.49.10

============================================================================
============== Monitoring Request Manager Main Menu ==============
============================================================================

Note: Monitoring requests let you specify the events for monitors
to report and the notification methods to use.

Select:
(S)how monitoring requests configured via monconfig
(C)heck detailed monitoring status
(L)ist descriptions of available monitors
(A)dd a monitoring request
(D)elete a monitoring request
(M)odify an existing monitoring request
(E)nable Monitoring
(K)ill (disable) monitoring
(H)elp
(Q)uit
Enter selection: [s] E



============================================================================
======================= Enable Monitoring ========================
============================================================================


This may take a while...

Waiting for changes in monitoring requests or in hardware configuration
to take effect...


EVENT MONITORING IS CURRENTLY ENABLED.



============================================================================
============== Monitoring Request Manager Main Menu ==============
============================================================================

Note: Monitoring requests let you specify the events for monitors
to report and the notification methods to use.

Select:
(S)how monitoring requests configured via monconfig
(C)heck detailed monitoring status
(L)ist descriptions of available monitors
(A)dd a monitoring request
(D)elete a monitoring request
(M)odify an existing monitoring request
(E)nable Monitoring
(K)ill (disable) monitoring
(H)elp
(Q)uit
Enter selection: [s] Q
# ps -ef |grep registrar
root 22077 17986 2 11:09:35 pts/1 0:00 grep registrar