Reference
What Is the ide_daemon.cfg File?
Description
- This file is used to enable or disable the listening port and specify the listening port and listening IP address.
- Find the file in the following paths:
- In the operating environment, find the ide_daemon.cfg file in ~/ide_daemon. ~ indicates the home directory of the ada process running user. For example, if the ada process is started by the HwHiAiUser user, the path is /home/HwHiAiUser/ide_daemon.
- On the server where Toolkit is installed, find the ide_daemon.cfg configuration file in /toolkit/tools/ide_daemon/conf in the Toolkit installation path.
- To have your configuration take effective:
In the operating environment, modify the ide_daemon.cfg file and restart the ada process for the modification to take effect. For details, see How Do I Restart the ada Process?
Configuration Options
Option |
Description |
|---|---|
SOCK_SWITCH |
Listening port enable
Default: 1 NOTE:
The following options take effect only when this option is set to 1. |
HOST_PORT |
Listening port number for starting the ada process. The ada process is deployed on the host. Therefore, this option is valid only in the configuration file on the host. Value range: 20000–25000 Default: 22118 |
HOST_IP |
Listening IP address for starting the ada process. Set this option to the IP address of the server where ADA is deployed. The ada process is deployed on the host. Therefore, this option is valid only in the configuration file on the host. This option has no default value. |
DEFAULT_TIME |
Whether to set the system time of the server where ADA is deployed to the default time (January 1, 2019). If the system time is later than December 27, 2018, this option is invalid. Setting the time to the default time is to ensure that the built-in ADX certificate of the system is within the validity period.
|
WORK_PATH |
Directory for storing the project, dataset, and other data. Defaults to ~, indicating the home directory of the user who starts the ada process. Note: It is recommended that the length of WORK_PATH be less than or equal to 1024 characters and the path name of each level be less than or equal to 255 characters. Ensure that the user who starts the ada process has read, write, and execute permissions on the path specified by WORK_PATH and its upper-level directory. |
LOG_PATH |
Path for storing operation logs of ADX. Defaults to ~/ide_daemon/log, where, ~ indicates the path specified by WORK_PATH. Note: It is recommended that the length of LOG_PATH be less than or equal to 1024 characters and the path name of each level be less than or equal to 255 characters. The path specified by LOG_PATH must exist; otherwise, the default value is used. Ensure that the user who starts the ada process has read, write, and execute permissions on the path specified by LOG_PATH. |
INSTALL_MODE |
Whether to allow a user of a group different from the ada running user to access Profiling. You are advised to retain the default setting.
|
CERT_EXPIRE |
Time for sending a certificate expiration notification. For example, if it is set to 60, the system sends a notification 60 days before the certificate expires. Defaults to 60 (days) . The value range is [1, 180]. |
CERT_CIPHER |
Secure encryption algorithms. Only ECDHE-RSA-AES256-GCM-SHA384 and ECDHE-RSA-AES128-GCM-SHA256 are supported. Default: ECDHE-RSA-AES256-GCM-SHA384,ECDHE-RSA-AES128-GCM-SHA256 |
TLS_OPTION |
Secure transmission protocol. Only TLSv1.2 and TLSv1.3 are supported. Default: TLSv1.2,TLSv1.3 |
SECU |
This option is modified when the ADX certificate is replaced. For details, see ADX Certificate Replacement Guide. |
STORE |
This option is modified when the ADX certificate is replaced. For details, see ADX Certificate Replacement Guide. |
What Do I Do If the Message "Ssl Verify Validity Failed" Is Displayed After the adc Command Is Executed?
Symptom
The following information is displayed after the adc command is executed:
SSL ide_daemon_client_cert.pem Certificate Is Out of 2018-12-13 10:40:15~2028-12-10 10:40:15 Validity Period Ssl Verify Validity Failed Remote Open failed, sock: -1 Remote Handle failed, err: -1
Cause Analysis
The default certificate of the ADX module is used, but the time of the server where the adc command is executed or that of the server where the ada process is executed is not within the validity period (2018-12-13 10:40:19 GMT to 2028–12-10 10:40:19 GMT) of the certificate.
Solution
Log in to the operating environment as the running user of the ada process, and check the time of the server where the adc command is executed or the server where the ada process runs on.
Run the following command:
date
If the returned time is not within the validity period (2018-12-13 10:40:19 GMT to 2028-12-10 10:40:19 GMT) of the default certificate, run the following command as the root user to set the time. Replace the example time in the following command as required.
date -s "2020-03-26 14:30:19 GMT"
What Do I Do If the Message "SSL connect error" Is Displayed After the adc Command Is Executed?
Symptom
The following information is displayed after the adc command is executed:
Peer Closed Connection During SSL Handshake, Status:-1 SSL connect error Create Reamote Sock Handle Failed Remote Open failed, sock: -1 Remote Handle failed, err: -1
Cause Analysis
The possible causes are as follows:
- The IP address or port number configured in the adc command is incorrect.
- The ada process is not started. As a result, the SSL connection fails.
- The listening port (22118 by default) for starting the ada process is disabled.
Solution
Log in to the operating environment as the ada process running user.
- Check whether the IP address or port number in the adc command is correct.
The port number is specified by HOST_PORT in the ~/ide_daemon/ide_daemon.cfg file. For details, see What Is the ide_daemon.cfg File?.
- Check whether the listening port (22118 by default) for starting the ada process is disabled.
You can enable or disable the port by configuring SOCK_SWITCH in the ~/ide_daemon/ide_daemon.cfg file. Setting SOCK_SWITCH to 0 disables the port, and setting SOCK_SWITCH to 1 enables the port. For details, see What Is the ide_daemon.cfg File?.
How Do I Restart the ada Process?
To restart the ada process, log in to the host as the root user, switch to ada process running user, and run the following commands in sequence:
- Query the ada process ID and the command to start the ada process.
ps -ef | grep adaThe following is an example of the query result.HwHiAiU+ 6907 1 0 Jun10 ? 00:08:43 /usr/local/Ascend/driver/tools/ada - Run the following command to stop the ada process. 6907 indicates the ada process ID. Replace it with the actual one.
kill -9 6907
- Start the ada process.If the message "ada is exist, don't start again" is displayed, the system has automatically started the ada process. In this case, you do not need to run the restart command again.
/usr/local/Ascend/driver/tools/adaTo restart the ada process in a container, run the following command:
/usr/local/Ascend/driver/tools/ada --docker
