1833934 Members
1663 Online
110063 Solutions
New Discussion

STM

 
SOLVED
Go to solution
John E. Goetz
Frequent Advisor

STM

Can STM be stopped and started from command line and are there any consequences of restarting this with applications running on the server?
9 REPLIES 9
James R. Ferguson
Acclaimed Contributor

Re: STM

Hi John:

You can do:

# /sbin/init.d/ems stop
# /sbin/init.d/ems start

Regards!

...JRF...
Patrick Wallek
Honored Contributor

Re: STM

You can also do:

# /sbin/init.d/diagnostic stop
# /sbin/init.d/diagnostic start

No there should not be any consequences to applications.
James R. Ferguson
Acclaimed Contributor

Re: STM

Hi (again) John:

Disregard my offering. If you look at '/sbin/init.d/ems' in the "stop" stanza you see:

print "This script does not stop the EMS Services"
...

Regards!

...JRF...
Aussan
Respected Contributor
Solution

Re: STM

hi John

To stop all EMS monitors while the system is running:

/etc/opt/resmon/lbin/monconfig
(choose "k" from menu to stop EMS)

To start EMS monitors while the system is running:(same but choose "e" to enable EMS)


To stop diagnostics while the system is running:

/sbin/init.d/diagnostic stop

To start diagnostics while the system is running:

/sbin/init.d/diagnostic start
The tongue weighs practically nothing, but so few people can hold it
Jeff_Traigle
Honored Contributor

Re: STM

And I've never known the diagnostics script to shut down the STM monitors either. It just kills diagmond. Only way I've seen to stop them all is to use /etc/opt/resmon/lbin/monconfig, which seems to require using it's menu.
--
Jeff Traigle
John E. Goetz
Frequent Advisor

Re: STM

I just tried running the commands that everyone has listed and the following sequence worked:

1) /etc/opt/resmon/lbin/monconfig
(choose "k" from menu to stop EMS)

2) /sbin/init.d/diagnostic stop

3) /sbin/init.d/diagnostic start

4) /etc/opt/resmon/lbin/monconfig
(choose "e" to enable EMS)


Thanks everyone for the quick responses.
Andrew Merritt_2
Honored Contributor

Re: STM

Hi John,
What's the reason for wanting to stop the monitors (assuming that's what you want to do, rather than stop STM)?

Just to confirm and clarify a little, the sequence you give in your last post will:

1) This stops the EMS HW monitors (not the whole of EMS)

2) This stops the diagnostic daemons (diagmond, diaglogd, and a couple of others (exactly which ones depends on the hardware)). The daemons are used by the EMS HW monitors, and also by STM when it runs.

3) This restarts the daemons

4) This restarts the EMS HW monitors.

The EMS framework is unaffected by any of these steps. If the STM interface is in use, it won't work while diagmond is disabled.

Andrew
Bill Hassell
Honored Contributor

Re: STM

If you are stopping EMS because one or more of the processes are eating up a lot of CPU time, you need to upgrade to the latest version (A.57.00). Otherwise, EMS consumes virtually no meaningful time while running.


Bill Hassell, sysadmin
Andrew Merritt_2
Honored Contributor

Re: STM

I'd second the recommendation to make sure you have a supported version installed, though the actual version depends on which version of HP-UX you are running.

The table of versions is here - http://www.docs.hp.com/en/diag/stm/stm_upd.htm#table

and you can download the latest from here -
http://www.software.hp.com/portal/swdepot/displayProductInfo.do?productNumber=B6191AAE

Andrew