Resolving resources stuck in “restarting” status

Occasionally a node, application layer, or entire environment can get stuck with a status of “restarting” in the control panel. This is usually due to a miscommunication between the platform and the container itself and not because the container has failed to restart. If this occurs, please try the following to resolve:

  1. Restart the entire environment
  2. Stop/start the environment
  3. Open the environment topology manager and make a minor change to the configured cloudlets for the resource that is stuck in “restarting” status

If none of these resolve the problem, please contact support.