Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Recovering CSO Services

Recovering a CSO Service

If the components_health.sh script detects any service as unhealthy, then you can recover the service using the recovery.sh script.

  1. From the CSO directory, run the recovery.sh script:
  2. Specify the component (number) that needs to be recovered.

The recovery script starts the recovery process for the specified component (saltstack in this example). The following is a sample output of the messages that are displayed. A recovery completion message is displayed after the component is recovered.

If the recovery.sh script detects an issue with the k8 virtual machine when recovering the kubernetes component, then it displays an error message as shown in the following sample output:

You can run the deploy.sh script to replace the k8 virtual machine.

Replacing Virtual Machines for KVM Hypervisor

You can replace only a k8 virtual machine. To replace a k8 virtual machine:

  1. Run the ./deploy.sh script from the CSO directory
  2. Enter 2 at the prompt. A list of k8 virtual machines that can be replaced are displayed.
  3. Specify the IP of the k8 virtual machine, which is corrupted and must be replaced.

    The virtual machine is spawned again.

Note:

If a power cycle occurs on the physical servers, the vrr becomes unhealthy.

The following is a sample output that shows the vrr status as unhealthy:

Run the recovery.sh script again to bring the vrr back online. The following is a sample output of the recovery process: