During the course of troubleshooting, Support may request that you restart the Replicated services that manage Terraform Enterprise installations. Taking this action will not affect the Terraform Enterprise application. It will only restart the Replicated services. The process for restarting Replicated services is different depending on whether Terraform Enterprise is an individual installation or a clustered installation. Both processes are detailed below.
Depending on the operating system that Terraform Enterprise is running on, this may be accomplished one of two ways. For each, the first step will be to connect to the instance using SSH. Once connected, run the following commands that correspond with your system’s init system.
sudo service replicated restart sudo service replicated-operator restart sudo service replicated-ui restart
sudo systemctl restart replicated replicated-operator replicated-ui
In a clustered installation, the Replicated services are deployed using Kubernetes, and thus may exist on multiple nodes. Due to this, the approach to restarting the services is slightly different and does not depend on the instances’ init systems.
In order to restart the Replicated services,
kubectl must be configured to communicate with the cluster’s API endpoint. By default, the
root user has access to run
kubectl commands when logged into a node via SSH. Once configured, the following command will delete the Replicated pods and allow the services to be restarted.
kubectl delete pods --all-namespaces --selector app=replicated