- Community Home
- >
- Services
- >
- Insight Remote Support
- >
- Re: ISEE spawning /etc/opt/resmon/lbin/registrar p...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-06-2005 05:14 AM
тАО01-06-2005 05:14 AM
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-06-2005 10:21 PM
тАО01-06-2005 10:21 PM
Re: ISEE spawning /etc/opt/resmon/lbin/registrar processes
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2005 01:31 AM
тАО01-07-2005 01:31 AM
Re: ISEE spawning /etc/opt/resmon/lbin/registrar processes
Thanks,
Richard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2005 03:51 AM
тАО01-07-2005 03:51 AM
Re: ISEE spawning /etc/opt/resmon/lbin/registrar processes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-09-2005 08:51 PM
тАО01-09-2005 08:51 PM
Solutionthe 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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2005 07:07 AM
тАО01-10-2005 07:07 AM
Re: ISEE spawning /etc/opt/resmon/lbin/registrar processes
Thanks,
Richard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-22-2005 08:34 AM
тАО02-22-2005 08:34 AM
Re: ISEE spawning /etc/opt/resmon/lbin/registrar processes
Richard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-19-2006 08:55 AM
тАО10-19-2006 08:55 AM
Re: ISEE spawning /etc/opt/resmon/lbin/registrar processes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-28-2007 11:13 PM
тАО05-28-2007 11:13 PM
Re: ISEE spawning /etc/opt/resmon/lbin/registrar processes
/usr/sbin/stm/uut/bin/sys/diagmond
Then enable EMS:
/etc/opt/resmon/lbin/monconfig
Select (E)nable Monitoring
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-31-2008 11:32 AM
тАО12-31-2008 11:32 AM
Re: ISEE spawning /etc/opt/resmon/lbin/registrar processes
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