Information Technology Reference
In-Depth Information
Stopping and Starting CWSI Campus Processes
The following command-line scripts control the CWSI Campus processes:
stopcwsiserver
stops the CWSI daemons.
startcwsiserver
starts the CWSI daemons.
To use these scripts, you must be signed in as the administrator on Windows NT or as root on UNIX
operating systems. Open a command prompt or shell window. Enter
stopcwsiserver
to stop the CWSI
Campus server processes. When the prompt returns, all the daemons have been stopped. To restart the
processes, enter
startcwsiserver
and wait until the prompt returns.
Losing the Connection to EventChannel
If an error occurs stating that you have lost connection to EventChannel, follow these steps:
Step 1
From the command prompt or shell window, enter
pdshow AniServer
to determine whether AniServer
is still running. If it is not running, continue with Step 3.
Step 2
Check the start and stop time to determine whether AniServer was restarted while CWSI Campus was
running. If AniServer did go down without your knowledge, open the ani.log file to determine the cause.
Step 3
From the command prompt or shell window, enter
pdshow EventChannel
to determine whether
EventChannel is running. If EventChannel is not running, continue with Step 5.
Step 4
Check the start and stop time to determine whether EventChannel was restarted while CWSI Campus
was running. If AniServer had been restarted, EventChannel is reset, which terminates the connection
between the CWSI Campus client and Event Channel.
Step 5
If either AniServer or EventChannel are not running, follow these steps:
•
Exit CWSI Campus.
•
Enter the
startcwsiserver
command.
•
Start CWSI Campus.
Starting CWSI Campus
If you have difficulty starting the CWSI Campus applications, follow the tips in these subsections.
If you have just restarted your computer and cannot log in to <Hostname>AniServer, the ANI server
might not be ready to receive messages. Wait a few minutes, and then try to log in again.
If you still cannot log in, refer to the previous section of “Troubleshooting Information for CiscoWorks
2000 Installation and Setup.” That section includes detailed steps for resolving this error on Windows
NT and UNIX systems.
Identifying a Corrupt Database
A corrupt database cannot be easily identified. In past versions of CWSI Campus, symptoms included a
connection that hangs or intermittent hanging. However, these problems have been resolved. Currently,
the only way to know definitively whether the database is corrupt is to look at the ani.log file. If many
SQL exceptions and errors are present in the ani.log, the database may be corrupt.
