Cleaning Up After a Dropped Connection

There are times when a network connection is dropped due to network congestion. Sometimes these dropped connections leave the NASIS process running which means that when you run NASIS again the data may still be locked by the initial NASIS session. When you click on the Object Status Locked indicator and it shows that you have the object locked, it may mean you have a old session still running.

Here are the instructions for cleaning up the old NASIS session:

1. Run NASISSecureAccess and open an Xterm.
    
2. In the xterm window, type: ps -fu your_loginid using your NASIS login. For example: ps -fu tcheever. You should see output similar to this:

   nasis2% ps -futcheever 
   
   UID      PID   PPID  C STIME    TTY    TIME CMD
   tcheever 17141 17140 0 08:37:19 pts/25 0:00 csh
   tcheever 29052 29051 0 07:02:34 pts/13 0:00 csh
   tcheever 29147 29126 0 07:05:18 ?      0:00 csh -c /nasis/nasis/bin/nasis
   tcheever 29048 29026 0 07:02:31 ?      0:00 csh -c /usr/openwin/bin/xterm
   tcheever 17137 17115 0 08:37:13 ?      0:00 csh -c /usr/openwin/bin/xterm
   tcheever 29150 29147 0 07:05:18 ?      0:02 /nasis/nasis/bin/nasisx
   tcheever 17140 17137 0 08:37:14 ?      0:00 /usr/openwin/bin/xterm
   tcheever 29051 29048 0 07:02:31 ?      0:00 /usr/openwin/bin/xterm
   
   nasis2%

3. In the CMD column, look for the “/nasis/nasis/bin/nasisx” process. If there is more than one nasisx process, be sure to find the oldest process by looking at the start times in the STIME column. When you have located the oldest /nasis/nasis/bin/nasisx process, look for its corresponding process id number in the PID column.
    
4. Kill the oldest nasisx process by typing: kill -1 PID (where the PID is the number you noted in Step 3).
   
   NOTE: DO NOT use kill -9 because it will may not clean-up the locked records within NASIS. Do not use kill levels other than 1 because they generate unnecessary core dump files for the Ft. Collins staff to analyze.