This document describes how to start the Cisco Information Server (CIS) with a command session script from a Jetty web server interface. This method is used in order to troubleshoot a CIS startup failure if you cannot find any error details in the cs_server.log or the cs_monitor.log.
There are no specific requirements for this document.
The information in this document is based on the CIS Versions 6.2.x and earlier.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
When you attempt to troubleshoot a startup failure, you can start the CIS in Foreground Console mode in order to:
- Generate a more detailed output of the server startup failure.
- Remove the monitor daemon from the process, which might be an element in the failure.
- Allow the core server to run, which eliminates the need for the monitor daemon to call and verify the server process.
Start the CIS from the Jetty Web Server Interface
Complete these steps in order to start the CIS from the Jetty web server interface:
- Stop the CIS server with the usual method in order to turn off the CIS monitor daemon.
- From a Secure Shell (SSH) session, enter the install_dir>\bin\composite_server.bat server run command. No output appears in the foreground when you enter this command.
- If a CLI prompt does not appear, then the server has started successfully. If you immediately see a CLI prompt, then a startup failure has occurred. In order to view the failure output, navigate to <install dir> > logs > cs_server.out.<date-time>.
- Log in with your studio or client application in order to confirm that the startup is successful.
- Press Ctrl-C in order to terminate the server session from the console.