Use ps to see if the psm State Manager is running on deneb :
(deneb) ~ % ps axw | grep psmUnless there is a line similar to the one marked below,
(deneb) ~ % ps ax | grep psm 21925 pts/22 S 0:00 script psm_record0513 21926 pts/22 S 0:00 script psm_record0513 ===>> 27871 pts/25 S 0:00 psm <<=== 27902 pts/25 S 0:00 psm deneb sc 27934 pts/25 S 0:00 grep psmpsm is not running and must be started.
If psm is running, but non-responsive to clients or otherwise behaving badly, use the PID (27871 in the example) to kill it:
(deneb) ~ % kill -INT 27871 (deneb) ~ % kill -INT 27902
(deneb) ~ % psm_win &
(deneb) ~ % psm &About 10 lines of usage messages will result; be sure they don't include a failure message, like:
psmManager: SM_E_BIND_FAILEDOne reason that psm might not start is resource depletion. Check, for example, that there are not excessive numbers of dead processes such as .dm (the EPICS GUI windows for MiniDAQ) hogging process slots.
(deneb) ~ % psm deneb sc &In this case, no output messages are expected for a successful startup.
(deneb) ~ % title psm logger
(deneb) ~ % psm -l deneb
(deneb) ~ % title TSI/MDQ Monitor
(deneb) ~ % psm deneb monitorYou should get a blank screen with a time stamp, the word ``status'', and the slow controls status:
15:43:17 status: sc_cmd ready sc_seq connected(MiniDAQ status shouldn't appear, because it has yet to be connected to psm).
(deneb) ~ % ps axw | grep psm
MiniDAQ and Run Control still have to be attached to psm; if MiniDAQ is being started from scratch, this will happen later, when the MiniDAQ processors are rebooted and Run Control is started.
Roy Bossingham, LBNL