removed service stop & restart sections

since it is in the appendix

docs/trouble_shooting/trouble_shooting.rst

@@ -124,98 +124,3 @@ automatically initiated for the existing compute session. You must explicitly
 start the SSH/SFTP service in the desired container to establish the SFTP
 connection.
 
-Service unreachable
--------------------
-
-Some backend services may have been down. Try to stop and restart services by
-following guide on start/stop/restart <service-name> service.
-
-
-Start/stop/restart Manager service
-----------------------------------
-
-SSH into Manager node, and run either of following command.
-
-.. code-block:: shell
-
-   systemctl start backendai-manager
-   systemctl stop backendai-manager
-   systemctl restart backendai-manager
-
-Start/stop/restart Agent service
---------------------------------
-
-SSH into Agent node, and run either of following command.
-
-.. code-block:: shell
-
-   systemctl start backendai-agent
-   systemctl stop backendai-agent
-   systemctl restart backendai-agent
-
-Start/stop/restart Console-Server service
------------------------------------------
-
-SSH into Console-Server node, and run either of following command.
-
-.. code-block:: shell
-
-   systemctl start backendai-console-server
-   systemctl stop backendai-console-server
-   systemctl restart backendai-console-server
-
-Start/stop/restart database
----------------------------
-
-SSH into DB node, and run either of following command. Note that <project>
-should be manually written if it was provided when launching the service. It can
-be checked by running ``docker ps | grep postgres`` and see the name prefix for
-the corresponding container or something like that.
-
-.. code-block:: shell
-
-   docker-compose -f docker-compose.hs.postgres.yaml -p <project> up -d
-   docker-compose -f docker-compose.hs.postgres.yaml -p <project> down
-   docker-compose -f docker-compose.hs.postgres.yaml -p <project> restart
-
-Start/stop/restart Redis
-------------------------
-
-SSH into Redis node, and run either of following command. Note that <project>
-should be manually written if it was provided when launching the service. It can
-be checked by running ``docker ps | grep redis`` and see the name prefix for
-the corresponding container or something like that.
-
-.. code-block:: shell
-
-   docker-compose -f docker-compose.hs.redis.yaml -p <project> up -d
-   docker-compose -f docker-compose.hs.redis.yaml -p <project> down
-   docker-compose -f docker-compose.hs.redis.yaml -p <project> restart
-
-Start/stop/restart Etcd
------------------------
-
-SSH into Etcd node, and run either of following command. Note that <project>
-should be manually written if it was provided when launching the service. It can
-be checked by running ``docker ps | grep etcd`` and see the name prefix for
-the corresponding container or something like that.
-
-.. code-block:: shell
-
-   docker-compose -f docker-compose.hs.etcd.yaml -p <project> up -d
-   docker-compose -f docker-compose.hs.etcd.yaml -p <project> down
-   docker-compose -f docker-compose.hs.etcd.yaml -p <project> restart
-
-Start/stop/restart WSProxy
---------------------------
-
-SSH into WSProxy node, and run either of following command. Note that <project>
-should be manually written if it was provided when launching the service. It can
-be checked by running ``docker ps | grep proxy`` and see the name prefix for
-the corresponding container or something like that.
-
-.. code-block:: shell
-
-   docker-compose -f docker-compose.hs.wsproxy.simple.yaml -p <project> up -d
-   docker-compose -f docker-compose.hs.wsproxy.simple.yaml -p <project> down
-   docker-compose -f docker-compose.hs.wsproxy.simple.yaml -p <project> restart