Long-Term Supported Versions


    Q1: An error occurs when the train command is used to train a model, and the message "training data failed" is displayed.

    Cause: Only one type of data is collected by using the **collection **command.

    Solution: Collect data of at least two data types for training.

    Q2: The atune-adm cannot connect to the atuned service.

    Possible cause:

    1. Check whether the atuned service is started and check the atuned listening address.

      # systemctl status atuned
      # netstat -nap | atuned
    2. The firewall blocks the atuned listening port.

    3. The HTTP proxy is configured in the system. As a result, the connection fails.


    1. If the atuned service is not started, run the following command to start the service:

      # systemctl start atuned
    2. Run the following command on the atuned and atune-adm servers to allow the listening port to receive network packets. In the command, 60001 is the listening port number of the atuned server.

      # iptables -I INPUT -p tcp --dport 60001 -j ACCEPT
      # iptables -I INPUT -p tcp --sport 60001 -j ACCEPT
    3. Run the following command to delete the HTTP proxy or disable the HTTP proxy for the listening IP address without affecting services:

      # no_proxy=$no_proxy, Listening IP address

    Q3: The atuned service cannot be started, and the message "Job for atuned.service failed because a timeout was exceeded." is displayed.

    Cause: The hosts file does not contain the localhost information.

    Solution: Add localhost to the line starting with in the /etc/hosts file. localhost localhost.localdomain localhost4 localhost4.localdomain4

    Bug Catching

    Buggy Content

    Bug Description

    Submit As Issue

    It's a little complicated....

    I'd like to ask someone.


    Just a small problem.

    I can fix it online!

    Bug Type
    Specifications and Common Mistakes

    ● Misspellings or punctuation mistakes;

    ● Incorrect links, empty cells, or wrong formats;

    ● Chinese characters in English context;

    ● Minor inconsistencies between the UI and descriptions;

    ● Low writing fluency that does not affect understanding;

    ● Incorrect version numbers, including software package names and version numbers on the UI.


    ● Incorrect or missing key steps;

    ● Missing prerequisites or precautions;

    ● Ambiguous figures, tables, or texts;

    ● Unclear logic, such as missing classifications, items, and steps.


    ● Technical principles, function descriptions, or specifications inconsistent with those of the software;

    ● Incorrect schematic or architecture diagrams;

    ● Incorrect commands or command parameters;

    ● Incorrect code;

    ● Commands inconsistent with the functions;

    ● Wrong screenshots.

    Risk Warnings

    ● Lack of risk warnings for operations that may damage the system or important data.

    Content Compliance

    ● Contents that may violate applicable laws and regulations or geo-cultural context-sensitive words and expressions;

    ● Copyright infringement.

    How satisfied are you with this document

    Not satisfied at all
    Very satisfied
    Click to create an issue. An issue template will be automatically generated based on your feedback.
    Bug Catching
    编组 3备份