stm cpe_em consuming high cpu
If cpe_em has gone AWOL, you can stop,start it to get it working again:
CPU TTY PID USERNAME PRI NI SIZE RES STATE TIME %WCPU %CPU COMMAND
4 ? 4515 root 237 20 7736K 1460K run 5774:16 98.58 98.41 cpe_em
sdpr@root:>/etc/opt/resmon/lbin/monconfig
============================================================================
=================== Event Monitoring Service ===================
=================== Monitoring Request Manager ===================
============================================================================
EVENT MONITORING IS CURRENTLY ENABLED.
EMS Version : A.04.20.23
STM Version : C.58.00
============================================================================
============== 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] K
============================================================================
======================= Disable Monitoring =======================
============================================================================
Hardware event monitoring watches the system for hardware problems. If
you shut this facility down, the system will no longer be able to alert
you to many hardware problems.
In addition, if ServiceGuard is configured to use hardware event monitoring
to determine the health of your system, then disabling monitoring may cause
it to consider this system as having failed. This will result in a package
failover. Type "h" for help to find out more about the implications of
shutdown on ServiceGuard.
Furthermore, if you have used the Event Monitoring Service (EMS) Graphical
User Interface (GUI) within the System Administration Manager (SAM) to
configure the event monitors, this configuration will not be saved, and no
actual monitoring will take place until hardware event monitoring is
re-enabled and you add the monitoring requests back again using the EMS
GUI. Event monitoring resources show up in the EMS GUI under the resource
class "status".
Are you sure you wish to disable event monitoring?
{(Y)es,(N)o,(H)elp} [n] Y
This may take a while...
EVENT MONITORING IS CURRENTLY DISABLED.
============================================================================
============== 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.