Log in to the CSP first node, switch to user root, and run the following command:
1. Certificate decryption method
Note: If the /opt/csp/package/scripts/cert/aaa.key file already exists, skip step 1.
Decryption method:
openssl rsa -in /opt/csp/package/scripts/cert/tls.key.pwd -passin pass:CSPEdge@1234 -out /opt/csp/package/scripts/cert/aaa.key
The following figure shows an example.
2. Import environment variables.
cert="-k --key /opt/csp/package/scripts/cert/aaa.key --cert /opt/csp/package/scripts/cert/tls.crt --cacert /opt/csp/package/scripts/cert/ca.crt"
3. Obtain the IP address of the ICTS_CCN_MASTER container.
grep ICTS_MASTER /opt/csp_service_ip.ini
The following figure shows an example.
4. Obtain the IP address of the active ChinaSoft International node.
curl -k -X GET $cert https://{IP}:20031/hasen/cad/v1/leader obtained in step 3
The following figure shows an example.
5. Query container instance information.
curl -k -X GET $cert https://{IP}:20031/hasen/cad/v1/deployer/instances | python -m json.tool > /home/cspexpert/instance.log obtained in step 4
The following figure shows an example.
6. View failed components.
Run vim /home/cspexpert/instance.log to search for the name of the container that is being created on the CSP portal container page and check the failedComponent value.
7. View the logs of the component that fails to be installed and locate the error cause.
Note: The node where logs of each component are located is the same as the node where the container is located. You can query the node where the container is located in the Host IP Address column on the container page of the CSP portal.
ChinaSoft International logs:
hasen, RM:
/opt/csp/icts_ccn/logs/master/hares/*
/opt/csp/icts_ccn/logs/agent/hares/*
Canal:
/opt/csp/icts_ccn/logs/master/Canal/*
/opt/csp/icts_ccn/logs/agent/Canal/*
elara:
/usr/local/icts_ccn/elara/logs/elaractl.log
docker:
/var/log/messages
