topic Re: about registrar process in in Operating System - HP-UX

about registrar process in

wangmx — Mon, 07 Jun 2004 02:20:16 GMT

#top
System: hnubis3 Mon Jun 7 14:36:53 2004
Load averages: 16.20, 16.14, 15.94
174 processes: 89 sleeping, 85 running
Cpu states:
CPU LOAD USER NICE SYS IDLE BLOCK SWAIT INTR SSYS
0 13.32 5.4% 0.0% 94.6% 0.0% 0.0% 0.0% 0.0% 0.0%
1 17.20 4.2% 0.0% 95.8% 0.0% 0.0% 0.0% 0.0% 0.0%
2 16.91 5.0% 0.0% 95.0% 0.0% 0.0% 0.0% 0.0% 0.0%
3 17.36 7.0% 0.0% 93.0% 0.0% 0.0% 0.0% 0.0% 0.0%
--- ---- ----- ----- ----- ----- ----- ----- ----- -----
avg 16.20 5.4% 0.0% 94.6% 0.0% 0.0% 0.0% 0.0% 0.0%

Memory: 290288K (244248K) real, 567740K (489272K) virtual, 2010648K free Page# 1/6

CPU TTY PID USERNAME PRI NI SIZE RES STATE TIME %WCPU %CPU COMMAND
1 ? 21378 root 241 20 2268K 328K run 43:27 9.31 9.30 registrar
1 ? 21235 root 138 20 2268K 328K run 62:40 8.36 8.34 registrar
0 ? 20985 root 241 20 2268K 328K run 155:07 8.14 8.13 registrar
3 ? 21905 root 240 20 2268K 328K run 9:12 8.03 8.02 registrar
0 ? 21050 root 241 20 2268K 328K run 116:58 7.98 7.97 registrar
2 ? 21970 root 240 20 2268K 328K run 5:42 7.98 7.96 registrar
0 ? 21250 root 240 20 2268K 328K run 60:38 7.93 7.91 registrar
2 ? 21454 root 241 20 2268K 328K run 34:45 7.59 7.58 registrar
1 ? 21468 root 241 20 2268K 328K run 32:49 7.58 7.56 registrar
2 ? 21719 root 240 20 2268K 328K run 13:34 7.33 7.31 registrar
0 ? 22046 root 241 20 2268K 328K run 2:04 7.31 7.29 registrar
0 ? 21439 root 241 20 2268K 328K run 36:03 7.19 7.18 registrar
3 ? 21563 root 241 20 2268K 328K run 24:50 7.13 7.12 registrar
3 ? 21141 root 241 20 2268K 328K run 83:32 7.12 7.10 registrar
2 ? 21170 root 240 20 2268K 328K run 75:43 6.98 6.96 registrar
2 ? 21733 root 138 20 2268K 328K run 12:55 6.91 6.90 registrar
2 ? 21028 root 241 20 2268K 328K run 124:55 6.91 6.89 registrar
1 ? 21327 root 240 20 2268K 328K run 48:24 6.87 6.86 registrar
1 ? 21941 root 241 20 2268K 328K run 7:27 6.76 6.75 registrar
3 ? 21548 root 240 20 2268K 328K run 26:24 6.75 6.74 registrar
3 ? 21298 root 240 20 2268K 328K run 52:54 6.63 6.62 registrar
2 ? 21624 root 241 20 2268K 328K run 19:56 6.60 6.59 registrar
0 ? 21675 root 241 20 2268K 328K run 16:55 6.59 6.58 registrar
1 ? 21497 root 241 20 2268K 328K run 29:45 6.51 6.50 registrar
2 ? 21780 root 241 20 2268K 328K run 9:43 6.41 6.40 registrar
3 ? 21483 root 240 20 2268K 328K run 31:02 6.38 6.37 registrar
3 ? 21094 root 138 20 2268K 328K run 98:40 6.36 6.35 registrar
2 ? 21595 root 241 20 2268K 328K run 22:18 6.34 6.33 registrar
2 ? 21653 root 241 20 2268K 328K run 17:35 6.29 6.28 registrar
2 ? 21610 root 240 20 2268K 328K run 21:36 6.20 6.19 registrar
2 ? 22120 root 241 20 2268K 328K run 0:31 6.19 6.18 registrar
1 ? 21341 root 240 20 2268K 328K run 46:46 6.13 6.12 registrar
1 ? 21079 root 240 20 2268K 328K run 104:09 6.13 6.12 registrar

#ps -ef|grep registrar
root 21065 1267 253 02:52:47 ? 110:28 /etc/opt/resmon/lbin/registrar
root 21170 1267 253 04:16:50 ? 75:44 /etc/opt/resmon/lbin/registrar
root 22017 1267 251 13:41:06 ? 3:21 /etc/opt/resmon/lbin/registrar
root 22046 1267 250 14:05:07 ? 2:05 /etc/opt/resmon/lbin/registrar
root 21563 1267 255 09:16:59 ? 24:52 /etc/opt/resmon/lbin/registrar
root 21407 1267 249 07:16:55 ? 39:09 /etc/opt/resmon/lbin/registrar
root 21155 1267 251 04:04:50 ? 79:29 /etc/opt/resmon/lbin/registrar
root 21298 1267 255 05:52:53 ? 52:55 /etc/opt/resmon/lbin/registrar
root 21327 1267 251 06:16:54 ? 48:26 /etc/opt/resmon/lbin/registrar
root 21108 1267 253 03:28:48 ? 92:27 /etc/opt/resmon/lbin/registrar
root 21905 1267 253 12:17:04 ? 9:14 /etc/opt/resmon/lbin/registrar
root 21221 1267 249 04:52:51 ? 66:27 /etc/opt/resmon/lbin/registrar
root 20999 1267 253 02:04:46 ? 142:47 /etc/opt/resmon/lbin/registrar
root 21126 1267 255 03:40:49 ? 87:41 /etc/opt/resmon/lbin/registrar
root 21235 1267 251 05:04:51 ? 62:42 /etc/opt/resmon/lbin/registrar
root 21363 1267 255 06:40:54 ? 45:08 /etc/opt/resmon/lbin/registrar
root 21094 1267 255 03:16:48 ? 98:41 /etc/opt/resmon/lbin/registrar
root 21050 1267 249 02:40:47 ? 116:59 /etc/opt/resmon/lbin/registrar
root 21704 1267 251 11:05:02 ? 14:57 /etc/opt/resmon/lbin/registrar
root 21341 1267 251 06:28:54 ? 46:47 /etc/opt/resmon/lbin/registrar
root 21610 1267 251 09:53:00 ? 21:37 /etc/opt/resmon/lbin/registrar
root 21577 1267 255 09:28:59 ? 23:45 /etc/opt/resmon/lbin/registrar
root 21079 1267 250 03:04:48 ? 104:11 /etc/opt/resmon/lbin/registrar
root 21184 1267 251 04:28:50 ? 71:50 /etc/opt/resmon/lbin/registrar
root 22120 1267 251 14:29:07 ? 0:32 /etc/opt/resmon/lbin/registrar
root 21378 1267 251 06:52:55 ? 43:29 /etc/opt/resmon/lbin/registrar
root 21675 1267 253 10:41:01 ? 16:57 /etc/opt/resmon/lbin/registrar
root 21519 1267 253 08:40:58 ? 28:35 /etc/opt/resmon/lbin/registrar
root 21970 1267 251 13:05:05 ? 5:44 /etc/opt/resmon/lbin/registrar
root 21919 1267 255 12:29:04 ? 8:18 /etc/opt/resmon/lbin/registrar
root 21595 1267 253 09:40:59 ? 22:20 /etc/opt/resmon/lbin/registrar
root 21483 1267 249 08:16:57 ? 31:03 /etc/opt/resmon/lbin/registrar
root 21312 1267 251 06:04:53 ? 51:15 /etc/opt/resmon/lbin/registrar
root 20875 1267 251 01:45:10 ? 161:44 /etc/opt/resmon/lbin/registrar
root 22170 22145 1 14:37:17 pts/tf 0:00 grep registrar
root 21548 1267 255 09:04:58 ? 26:26 /etc/opt/resmon/lbin/registrar
root 21468 1267 255 08:04:57 ? 32:50 /etc/opt/resmon/lbin/registrar
root 21624 1267 252 10:05:00 ? 19:58 /etc/opt/resmon/lbin/registrar
root 21028 1267 251 02:28:47 ? 124:57 /etc/opt/resmon/lbin/registrar
root 22106 1267 248 14:17:07 ? 1:14 /etc/opt/resmon/lbin/registrar
root 21766 1267 253 11:53:03 ? 10:46 /etc/opt/resmon/lbin/registrar
root 21639 1267 253 10:17:00 ? 19:06 /etc/opt/resmon/lbin/registrar
root 21250 1267 250 05:16:52 ? 60:40 /etc/opt/resmon/lbin/registrar
root 21690 1267 255 10:53:01 ? 15:35 /etc/opt/resmon/lbin/registrar
root 21014 1267 249 02:16:46 ? 132:24 /etc/opt/resmon/lbin/registrar
root 21999 1267 255 13:29:06 ? 4:08 /etc/opt/resmon/lbin/registrar
root 21454 1267 251 07:52:56 ? 34:47 /etc/opt/resmon/lbin/registrar
root 21719 1267 255 11:17:02 ? 13:35 /etc/opt/resmon/lbin/registrar
root 21534 1267 253 08:52:58 ? 27:16 /etc/opt/resmon/lbin/registrar
root 21733 1267 253 11:29:02 ? 12:57 /etc/opt/resmon/lbin/registrar
root 21421 1267 255 07:28:56 ? 37:51 /etc/opt/resmon/lbin/registrar
root 22032 1267 249 13:53:06 ? 2:45 /etc/opt/resmon/lbin/registrar
root 21206 1267 249 04:40:51 ? 68:56 /etc/opt/resmon/lbin/registrar
root 21985 1267 248 13:17:05 ? 5:07 /etc/opt/resmon/lbin/registrar
root 21751 1267 251 11:41:03 ? 11:44 /etc/opt/resmon/lbin/registrar
root 21653 1267 251 10:29:01 ? 17:37 /etc/opt/resmon/lbin/registrar
root 21141 1267 253 03:52:49 ? 83:33 /etc/opt/resmon/lbin/registrar
root 21780 1267 255 12:05:03 ? 9:44 /etc/opt/resmon/lbin/registrar
root 21264 1267 253 05:28:52 ? 57:57 /etc/opt/resmon/lbin/registrar
root 21941 1267 251 12:41:04 ? 7:28 /etc/opt/resmon/lbin/registrar
root 21439 1267 255 07:40:56 ? 36:04 /etc/opt/resmon/lbin/registrar
root 21392 1267 253 07:04:55 ? 40:57 /etc/opt/resmon/lbin/registrar
root 21497 1267 249 08:28:57 ? 29:46 /etc/opt/resmon/lbin/registrar
root 21283 1267 251 05:40:52 ? 55:22 /etc/opt/resmon/lbin/registrar
root 20985 1267 249 01:52:46 ? 155:08 /etc/opt/resmon/lbin/registrar
root 21956 1267 253 12:53:05 ? 6:44 /etc/opt/resmon/lbin/registrar

how to slove it ?
thank you

Re: about registrar process in

John Carr_2 — Mon, 07 Jun 2004 02:54:14 GMT

Hi

what do you wish to solve ?

John.

Re: about registrar process in

Manish Srivastava — Mon, 07 Jun 2004 03:41:35 GMT

Hi,

I found the following documentation which might be helpful to you.

http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B7609-90015/B7609-90015_top.html&con=/hpux/onlinedocs/B7609-90015/00/00/8-con.html&toc=/hpux/onlinedocs/B7609-90015/00/00/8-toc.html&searchterms=/etc/opt/resmon/lbin/registrar&queryid=20040607-023724

manish

Re: about registrar process in

wangmx — Mon, 07 Jun 2004 04:12:32 GMT

Question:
1,what is registrar process?
2,why is the number of registrar so many?
3,Can i shutdown the process?

thanks
mx

Re: about registrar process in

Anita Kelkar — Mon, 07 Jun 2004 23:00:14 GMT

Hi ,
This is the server process , used in the event monitoring system (EMS) . This server process "registrar" is spawned to fulfill the client request. So this indicates that . on your machine there is a possibility that some active client is available.
If you are not using the Event monitoring Services , and you just want to get rid of this , you can remove the entry in inetd.conf "registrar stream tcp nowait root /etc/opt/resmon/lbin/registrar /etc/opt/resmon/lbin/registrar" and execute the #inetd -c (force to read the configure file )

If you want to use EMS services and solve this problem, I think you better contact HP support center.

thanks
anita

Re: about registrar process in

Bill Hassell — Tue, 08 Jun 2004 06:32:41 GMT

1,what is registrar process?

It is a daemon that coordinates errors from hardware drivers with the online diagnostics (EMS and STM).

2,why is the number of registrar so many?

This is not normal at all. I would guess that this is due to a bad installation of the diagnostics or lack of patches. Use your SupportPlus CDROM to install the latest version. The diagnostics install file is under the CDROM directory DIAGNOSTICS.

3,Can i shutdown the process?

The easiest way is to use swremove. However, I would never do this on a production machine as you will no longer see any early warnings about hardware problems. Update your EMS/STM diagnostics package.

Re: about registrar process in

wangmx — Tue, 08 Jun 2004 22:16:59 GMT

Hi,
Thanks in advance first
Yestday,I have call HP Support Center.they are Solving now.I will reply the answer when HP tell me.

MX
best Regards,

Re: about registrar process in

wangmx — Thu, 10 Jun 2004 01:34:42 GMT

hi,all
yesterday,HP Support Center login the host and deal with the problem.the process as below:
Stop the registar if neccesary by commenting out the 2 entries
in /etc/inetd.conf and re-reading the inetd configuration with
'inetd -c'. Kill any remaining registrar processes.

- Stop monitoring

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

Kill any monitor processes which are left over.

- Stop p_client

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

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

Reread /etc/inittab :
# init q

Check if p_client is still running, if yes kill the process.

- Delete the persistence files and pipes

# cd /etc/opt/resmon/persistence
# rm p*
# rm m*
# cd /etc/opt/resmon/pipe
# rm *

- Have diagnostics remap the system hardware

# cstm
cstm>remap
cstm>quit

Allow enough time for remap to finish before restarting the monitors.

- Clean up monitor flags in the diagnostics directory

# cd /var/stm/data/tools/monitor
# rm *.hwa

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

- 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

Re-read /etc/inittab :

# init q

- Restart the EMS monitors

# /etc/opt/resmon/lbin/monconfig
Select (E)nable Monitoring