Work notes-the process of how to deal with service problems

If there is a problem with drhel31, troubleshoot:

1. Http://drhel31.test.com:25400/ checks whether these services are available or not, mainly looking at the information in the ServiceNodeInstances (SAAS) area.

2. Http://drhel31.test.com:7080/getApiGWDetail checks whether these services are up or not.

3, if the service that should be up is not up, restart it on the corresponding 33prime35 machine.

Restart tomcat sudo / etc/init.d/tomcat6 restart on 4, 3, 3, 35

5, services in non-tomcat containers, and some services that can be restarted on 33

Sudo / etc/init.d/test-sioserver restart

Test-apigwd

Test-elasticsearchd

Test-sioserver

Test-slbgateway

Test-tfsd

Test-zookeeperd

6, services in non-tomcat containers, and some services that can be restarted on 35.

Test-sioserver

Test-slbgateway

Test-zookeeperd

7. If the service found on 1 and 2 is not found under / etc/init.d/test* of 33pj35, it means that the service is not installed. The service should be pre-installed, sudo bb install tfsd (service name)

8, but if you want to restart the service in tomcat alone, you have to restart it with the command of curl.

All services under the / opt/test/tomcat6/webapps/ path can be restarted using curl.

The restart process is as follows:

Curl-u 3JBYBOHlQAfixW7q:NdDkrm30g8HQelWA "localhost:8080/mgmtomcatmgr/stop?path=/activitystream"

Curl-u 3JBYBOHlQAfixW7q:NdDkrm30g8HQelWA "localhost:8080/mgmtomcatmgr/start?path=/activitystream"

Where:

3JBYBOHlQAfixW7q:NdDkrm30g8HQelWA, these two parameters

From file / opt/test/tomcat6/conf/tomcat-users.xml