How to stop/start/restart the Discovery appliance services? |
The Discovery services can be started or stopped from the UI or from the command line. 1- From the appliance UI: In cluster case, go to Administration > Control, then click on "Restart Cluster Services". For more details, see this documentation page.
In standalone appliance case, go to Administration > Control, then click on "Restart Appliance Service". For more details, see this documentation page. 2- From the command line: Connect to the appliance using ssh and login as user tideway.
STOP THE SERVICES: Option 1: Execute "tw_cluster_control --cluster-stop-services"
Option 2: Execute the steps below (on each members in cluster case) CentOS/RHEL 7/OL9:
tw_service_control --stop sudo systemctl stop cluster sudo systemctl stop omniNames sudo systemctl stop appliance CentOS/RHEL 6: sudo /sbin/service tideway stop sudo /sbin/service cluster stop sudo /sbin/service omniNames stop sudo /sbin/service appliance stop In rare cases, a process may be stuck and not end cleanly. To check for this, run the command: ps -ef | grep python If some processes are stuck, kill the python processes with the command: kill -9 <pid> There are two privileged processes owned by root 7490 1 0 Sep21 ? 00:00:00 python /usr/tideway/python/privileged/main.pyc --daemon start root 7495 7490 0 Sep21 ? 01:02:43 python /usr/tideway/python/privileged/main.pyc --daemon start It is not necessary to kill these privileged processes. However, killing these processes will cause no harm. START THE SERVICES: Option 1: Execute "tw_cluster_control --cluster-start-services"
Option 2: Execute the steps below (on each members in cluster case) CentOS/RHEL 7/OL9:
sudo systemctl start appliance sudo systemctl start omniNames sudo systemctl start cluster tw_service_control --start CentOS/RHEL 6: sudo /sbin/service appliance start sudo /sbin/service omniNames start sudo /sbin/service cluster start sudo /sbin/service tideway start |