Apply Changes When Exalead CloudView Has Stopped

In rare cases, a severe configuration conflict can prevent Exalead CloudView from starting. As a result, the standard tools to apply changes are unavailable. For this scenario, use the buildgct emergency configuration application tool.

See Also
Identifying Configuration Issues
How Saving and Applying Changes Work
Compare Configuration Versions
Roll Back to a Previous Configuration
  1. Stop Exalead CloudView on all servers.
  2. Edit the configuration files to fix the error.
  3. Run <DATADIR>/bin/buildgct.
  4. If it fails, continue editing.
  5. Restart the master host.
  6. Wait for the master host to fully start.
  7. Restart the other hosts, if any.

    Important: Do not use buildgct except for the previous procedure, especially for multihost deployments. The buildgct tool does not contact the other hosts to synchronize the configurations, so it can cause severe inconsistencies in the product configuration.