TeamInspector initializes all services required to run the product during the installation process. These services include: master service, web service (Apache Tomcat service), and job service. For various reasons one or more of the services might fail to start at the time of initialization.
If you experience a problem when you start TeamInspector, such as an inability to access the user interface, perform tasks, view data, or run builds, verify that all the services are started on the servers on which TeamInspector is installed.
To start all the services, run the cycleServices command at the TeamInspector master server command-line. Run the command on any remote build servers on which the TeamInspector job service is installed, if the job service failed to start.
If you want more information about which services failed to start during initialization, view the wrapper logs. TeamInspector maintains a wrapper log for each service to record initialization events. For more information about these logs, see TeamInspector Log Files in the online help.
On a Linux server, if you run the TeamInspector installer a second or subsequent time from the same terminal session in which the initial installation was run, TeamInspector attempts another new installation, with unpredictable results. For example, if you want to run the installer to perform an upgrade and are in the session in which TeamInspector was installed earlier, TeamInspector starts a new installation and will fail to migrate any existing data created since the first installation. You might also experience a problem with installation if multiple users are logged on with the root account while you are installing TeamInspector.
The following tips serve as a guide to avoiding these installation issues:
The TeamInspector product uses port numbers in the 9000 series. For example, the TeamInspector web interface runs within Apache Tomcat and uses port number 9080 as the default port. If you encounter problems connecting to or using TeamInspector, verify that you do not have a port conflict.
You can change the port that TeamInspector uses for the web dashboard by modifying the server.xml file in the TeamInspector/tomcat/conf installation directory. Open this file and search for the entry port="9080". Change this to a port that is not in use, and is greater than 1024, and then restart the Apache Tomcat TeamInspector service. This service also uses port 9005 for local shutdown support.
During the installation process, TeamInspector sets a default port value of 21 for the FTP services it uses in remote build environments. Ensure that this port is not already in use in your environment. If a port conflict exists, you will experience problems retrieving the artifacts from TeamInspector builds that occur on remote build servers.
You can change the FTP port setting on the Configuration page in the TeamInspector Dashboard.
If you remove the product installation and the uninstall procedure does not complete successfully, it could result in problems when reinstalling. Use the following tips to ensure a successful uninstall procedure:
If you have installed only the TeamInspector job service on a server, and run the uninstall program to remove the job service installation, the TeamInspector uninstall program might fail to remove all folders in the installation directory.
If you observe folders remaining in the TeamInspector installation directory after uninstalling the job service, manually remove the folders.