- Gold, 750 points or more
This similar issue has happened twice now. The basic problem is LMS 2.6's "dmgtd stop" fails to stop all procs before shutting itself down. So it leaves a trail of procs in CLOSE_WAIT that never time out, even after I tried adjusting on-the-fly with "/usr/sbin/ndd -set /dev/tcp tcp_time_wait_interval 60000". "/opt/CSCOpx/bin/dbstop.pl all" does no good.
So eventually I tried to turn to /etc/rc2.d/K90dmgtd. Last time I tried it (unsure whether I used the stop or kill option), it killed both of my SSH sessions, sshd/telnetd/inetd, the EMC storage manager daemon, but left the box pingable. Tonight, thinking it was a coincidence last time, I tried it again, given the CLOSE_WAITs above. This time ./K90dmgtd stop
returned "Daemon Management is not running." Then as soon as I issued "./K90dmgtd kill", I got "INFO: Terminating all the processes launched by dmgr", followed by immediate termination of that particular SSH session. My 2nd SSH session remains alive. No new telnet/ssh connection is accepted however. I imagine I'd have to reboot the server again.
Looks like you're missing two files from the end of /etc/rc.config.d/CiscoRMCtrl:
Since I've isolated (and reproduced) the most likely cause of the non-CiscoWorks process termination, you do not need to modify the dmgtd script further.
IPM evolved from CiscoWorks Blue, and many of the things that used to happen there were carried over. This is all going away in LMS 3.0 when IPM is put under dmgtd control.