KB41800: How to start the Intelligence Server when the Intelligence Server is stuck in the state "starting" or "stopping" on Linux and UNIX systems in MicroStrategy 9.4.x-10.x

The Intelligence Server can become stuck in the state of "Starting" of "Stopping". To resolve the issue follow these steps:
Step 1: The Process ID must be obtained for the Intelligence Server service.
Refer to the following tech note for additional information on how to obtain the Process ID:
KB13293: How to obtain the process ID (PID) of the MicroStrategy Intelligence Server Universal 9.x and 10.x process running on Unix/Linux. 
 
Step 2: Kill the process using the Process ID.
This can be achieved by running the following command:
 

kill -9 "The Process ID here"

 
Step 3: Check the state of the Intelligence Server service
This can be achieved by running the following command

./mstrctl -s IntelligenceServer gs

 
If the state shows either "Starting" or "Stopping" proceed to Step 4. If the state shows "Stopped" proceed to Step 5.
 
Step 4: The "status-iserver.xml" must either be edited, renamed, or deleted.
The "status-iserver.xml" file contains the state information of the Intelligence Server. There are three options that are available:
1. Edit the "status-iserver.xml" file but changing the value between the <state> and </state> tags to read "Stopped"
2. Delete the "status-iserver.xml" file which will cause a new file to be generated when the Intelligence Server service is started
3. Rename the "status-iserver.xml" file which will cause a new file to be generated when the Intelligence Server service is started.
 
Step 5: Start the Intelligence Server service
The Intelligence Server service can be started by running the following command:

./mstrctl -s IntelligenceServer start

 
If there are multiple instances of Service Manager running, the additional Service Manager services need to be killed by finding their Process IDs and using the kill command, or by restarting the machine.