Restarting ConsoleWorks after an abnormal shutdown

From TDiWiki

When you have had an abnormal shutdown of ConsoleWorks and are using the Pseudo Console console type, please follow these instructions before restarting ConsoleWorks.

(ConsoleWorks 3.x should clear any "child" processess during a normal shutdown)

For Unix/Linux

Before starting ConsoleWorks be sure there are no automatic actions or pseudo-consoles still running after the abnormal stop of ConsoleWorks. If you don't do this, when ConsoleWorks tries to restart, these auto action/pseudo console processes will still have open connections to the LMF server. The LMF server will believe that ConsoleWorks is still running and will not allow ConsoleWorks to restart.

The Auto actions would be running cwterm, and the SSH connections to look for would be running your chosen SSH client. (This Could be as simple as ps –ef |grep ssh) Example:

root 29112 1 0 Apr30 ? 00:00:00 /usr/bin/ssh root@scs1601-1.int.tditx.com -t -t connect port6

root 15485 1 0 May13 ? 00:00:00 /usr/bin/ssh root@scs1601-1.int.tditx.com -t -t connect port5

root 30139 1 0 May18 ? 00:00:00 /usr/bin/ssh root@scs1601-1.int.tditx.com -t -t connect port3

root 6730 1 0 May23 ? 00:00:00 /usr/bin/ssh root@scs1601-1.int.tditx.com -t -t connect port4

root 31916 1 0 May24 ? 00:00:00 /usr/bin/ssh root@scs1601-1.int.tditx.com -t -t connect port7

root 29304 29158 0 06:11 pts/12 00:00:00 /usr/bin/ssh root@scs1601-1.int.tditx.com -t -t connect port1

CWTerm isn’t usually the culprit in this scenario, but it’s still good to look for because in the years we’ve been doing this it has come up once or twice..

For the Windows environment

Simply restart Windows

For the OpenVMS environment

Perform a SHO SYS and clear the appropriate processes for your ssh client.

Since cwterm uses the SYS$BATCH queue, any jobs in the queue should not effect re-starting ConsoleWorks.