FAQs
FAQs
Date 2021-07-02 FAQs FAQs Contents
Contents
1 WARNING or FAIL Returned in the Software Package Integrity Verification...... 1 2 Failed to Install Library Files...... 4 3 No Data Collected on Certain Tab Pages During Memory Access Analysis on CentOS 7.6 (Standard Kernel)...... 6 4 Failed to Perform a System Resource Scheduling Analysis Task (Attach to Process Type)...... 8 5 Common Upgrade Failures...... 9 6 "Without the graphviz component, the system does not support this function" Displayed in the Code Flow Area of a Hotspot Function Analysis or Resource Scheduling Analysis Task...... 10 7 Failed to Run Analysis Tasks on HUAWEI Public Cloud...... 12 8 Failed to Run Hotspot Function Performance Analysis, Resource Scheduling Analysis, Microarchitecture Analysis Tasks on UVP VMs...... 13 9 Failed to Add a Node...... 14 10 Node Status Changes to Version Unmatched After an Upgrade...... 16 11 Failed to Associate Assembly Instructions with Hotspot Functions in the Dynamic Library on EulerOS...... 18 12 Failed to Perform an I/O Analysis Task...... 19 13 Insufficient Drive Space...... 27 14 Using the PGO Optimizer for Compilation...... 28 15 Upgrade Failure in Ubuntu...... 29 16 Failed to Log In to the Java Profiler After the Tool Is Installed...... 31 17 Failed to Collect HPC Task Data on Ubuntu...... 33 18 Node Status Changes to Offline...... 36
2021-07-02 ii FAQs 1 WARNING or FAIL Returned in the Software FAQs Package Integrity Verification
1 WARNING or FAIL Returned in the Software Package Integrity Verification
If a WARNING or FAIL result is returned in the integrity verification of a software package, the verification fails. Rectify the fault by referring to the handling suggestions described in Table Verification results and handling suggestions.
Table 1-1 Verification results and handling suggestions Verificatio Displayed Information (Example) Verif Handling n Result icati Suggestion Descriptio on n Res ult
The gpg: Signature made Thu Jan 9 15:29:06 PASS N/A signature 2014 CST using RSA key ID 27A74824 verificatio gpg: Good signature from "OpenPGP n is signature key for Huawei software (created successful on 30th Dec,2013)
The gpg: Signature made Thu Jan 9 15:29:06 FAIL Download signature 2014 CST using RSA key ID 27A74824 the target verificatio gpg: BAD signature from "OpenPGP file again. n fails. signature key for Huawei software (created on 30th Dec,2013)
The public gpg: Signature made Thu Jan 9 15:20:01 FAIL Download key cannot 2014 CST using RSA key ID 27A74824 the public be found. gpg: Can't check signature: public key not key again. found For details, see "Verifying the Software Package Integrity".
2021-07-02 1 FAQs 1 WARNING or FAIL Returned in the Software FAQs Package Integrity Verification
Verificatio Displayed Information (Example) Verif Handling n Result icati Suggestion Descriptio on n Res ult
The gpg: Signature made Thu Jan 9 15:29:06 WAR After signature 2014 CST using RSA key ID 27A74824 NIN checking verificatio gpg: Good signature from "OpenPGP G that the key n is signature key for Huawei software (created ID is successful, on 30th Dec,2013)
The gpg: no signed data FAIL Download correspon gpg: can't hash datafile: No data the target ding file again. source file cannot be found.
The gpg: Signature made 04/24/13 10:50:29 CST FAIL Download signature using RSA key ID 133B64E5 an updated has gpg: Expired signature from " OpenPGP target file. expired. signature test key
The gpg: Signature made 06/13/13 11:14:49 CST WAR Download signature using RSA key ID 133B64E5 NIN the latest verificatio gpg: Good signature from " OpenPGP G public key n is signature test key
2021-07-02 2 FAQs 1 WARNING or FAIL Returned in the Software FAQs Package Integrity Verification
Verificatio Displayed Information (Example) Verif Handling n Result icati Suggestion Descriptio on n Res ult
The N/A WAR Download correspon NIN the ding G signature file signature correspondin file cannot g to the be found target file. in the source file.
2021-07-02 3 FAQs FAQs 2 Failed to Install Library Files
2 Failed to Install Library Files
Symptom During library file installation, a message indicating library file installation failure is displayed.
Possible Causes The dependency library file does not match the OS version.
Procedure ● If the following types of library files fail to be installed, manually install library files that match the OS version and then reinstall the tool. – glibc – openssl – libffi-devel ● If other types of library files fail to be installed, manually install library files that match the OS version and restart the tool. For details about how to restart the tool, see "Restarting the System Profiler". The following steps use the perl-devel library file as an example.
Step 1 Check the installation failure message.
Step 2 Check the logs generated during the installation. The following is an example.
2021-07-02 4 FAQs FAQs 2 Failed to Install Library Files
Step 3 The preceding information shows that libdb-5.3.21-25.e17.aarch64 has been installed on the current server, and perl-devel-5.16.3-294.el7_6.aarch64 is the file of the required version. Obtain and install the perl- devel-5.16.3-294.el7_6.aarch64.rpm file and restart the tool.
----End
2021-07-02 5 3 No Data Collected on Certain Tab Pages During FAQs Memory Access Analysis on CentOS 7.6 (Standard FAQs Kernel)
3 No Data Collected on Certain Tab Pages During Memory Access Analysis on CentOS 7.6 (Standard Kernel)
Symptom
Data about the DDR access bandwidth, L3C access bandwidth, and hit ratio is not collected when a memory access statistics analysis task is executed on CentOS 7.6 (standard kernel).
Possible Causes
SELinux is enabled in the current system and the driver for collecting data cannot be installed. Disable SELinux before using this function.
Procedure ● Disabling SELinux temporarily a. Run the sestatus command to query the SELinux status. If the value of Current mode is enforcing, the SELinux enforcing mode is enabled. b. Run the following command to set the SELinux mode to permissive: setenforce 0 c. Run the sestatus command to query the SELinux status. If the value of Current mode is permissive, the SELinux enforcing mode is disabled temporarily.
NO TICE
The settings become invalid after the server is restarted. When the tool is used, service exceptions may occur.
● Disabling SELinux permanently a. Run the sestatus command to query the SELinux status. If SELinux status is enabled, SELinux is enabled.
2021-07-02 6 3 No Data Collected on Certain Tab Pages During FAQs Memory Access Analysis on CentOS 7.6 (Standard FAQs Kernel)
b. Run the following command to open the /etc/selinux/config file: vi /etc/selinux/config c. Press i to enter the edit mode and change SELINUX=enforcing to SELINUX=disabled. d. Press Esc, type :wq, and press Enter to save the settings and exit. e. Run the reboot command to restart the server. f. Run the sestatus command to query the SELinux status. If SELinux status is disabled, SELinux is disabled.
2021-07-02 7 FAQs 4 Failed to Perform a System Resource Scheduling FAQs Analysis Task (Attach to Process Type)
4 Failed to Perform a System Resource Scheduling Analysis Task (Attach to Process Type)
Symptom During the creation of a system resource scheduling analysis task, the task type is set to Attach to Process and the PID is set to the OS process ID. As a result, the task fails. The following error information is displayed in data analysis logs.
Possible Causes If the Linux kernel version is earlier than V4.15-rc1, data collection may fail during system resource scheduling analysis. As a result, the task fails.
Procedure Upgrade the kernel version to V4.15-rc1.
2021-07-02 8 FAQs FAQs 5 Common Upgrade Failures
5 Common Upgrade Failures
Table 5-1 Common upgrade failures and handling suggestions Failure Possible Causes Handling Suggestion
Failed to install The drive space is Check the size of the /opt directory the new version. insufficient. (tool installation directory) or the root directory.
Backup failed. The drive space is Check the size of the /opt directory insufficient. (tool installation directory) or the root directory.
2021-07-02 9 6 "Without the graphviz component, the system does not support this function" Displayed in the FAQs Code Flow Area of a Hotspot Function Analysis or FAQs Resource Scheduling Analysis Task
6 "Without the graphviz component, the system does not support this function" Displayed in the Code Flow Area of a Hotspot Function Analysis or Resource Scheduling Analysis Task
Symptom
The message "Without the graphviz component, the system does not support this function" is displayed in the Code Flow area, as shown in Figure 6-1.
Figure 6-1 Code Flow area
Possible Causes
The graphviz component is not installed on the OS.
Procedure
Installation of the graphviz component requires a local image source or network image source of the OS.
2021-07-02 10 6 "Without the graphviz component, the system does not support this function" Displayed in the FAQs Code Flow Area of a Hotspot Function Analysis or FAQs Resource Scheduling Analysis Task
NO TICE
Installing the graphviz of a later version may cause an upgrade of certain system library components (such as libc6 and libdb) to a later version. The upgraded system library components may affect running of other functions and software (for example, running of systemd may become abnormal). Consider the impact of the system library upgrade on your running environment when determine whether to install and upgrade the graphviz component.
To install the graphviz component, perform the following steps (using a local CentOS 7.6 image source as an example):
Step 1 Configure the OS image source. Step 2 Run the following command to install the graphviz component: yum -y install graphviz Step 3 Run the following command to check whether the installation is successful: rpm -qa | grep graphviz If the following information is displayed, the installation is successful.
graphviz-2.30.1-21.el7.aarch64
----End
2021-07-02 11 FAQs 7 Failed to Run Analysis Tasks on HUAWEI Public FAQs Cloud
7 Failed to Run Analysis Tasks on HUAWEI Public Cloud
Symptom An analysis task on HUAWEI public cloud fails and the error message "sudo perf record" is displayed, as shown in Figure 7-1.
Figure 7-1 Analysis task failure
Possible Causes HUAWEI public cloud does not support data collection from the Performance Monitoring Unit (PMU), therefore, the Kunpeng Hyper Tuner cannot perform collection and analysis on the cloud.
2021-07-02 12 8 Failed to Run Hotspot Function Performance FAQs Analysis, Resource Scheduling Analysis, FAQs Microarchitecture Analysis Tasks on UVP VMs
8 Failed to Run Hotspot Function Performance Analysis, Resource Scheduling Analysis, Microarchitecture Analysis Tasks on UVP VMs
Symptom A hotspot function performance analysis, resource scheduling analysis, or microarchitecture analysis task fails to be executed on a UVP VM, and the error message "sudo -n perf record -o xxx failed" is displayed, as shown in Figure 8-1.
Figure 8-1 Analysis task failure
Possible Causes In the configuration file of the UVP VM environment, pmu is set to off.
Procedure Set pmu in the configuration file of the UVP VM environment to on. (If pmu is not set in the configuration file, data collection from the PMU is enabled by default.)
2021-07-02 13 FAQs FAQs 9 Failed to Add a Node
9 Failed to Add a Node
Symptom
"Failed to add node because the node already exists" is displayed.
Possible Causes
The node has been added to the server, or the System Profiler has been installed on the server.
Procedure ● If the System Profiler has been installed on the server to which a node is to be added, log in to the server and uninstall it. For details, see "Uninstallation". After the System Profiler is uninstalled, add the node again.
NO TE
● Before uninstalling the System Profiler, ensure that the System Profiler on the server is not in use. ● If the tool fails to be uninstalled, manually delete the /home/malluma/ malluma_conf/malluma_install.ini file, malluma user, /home/malluma directory, and /opt/hyper_tuner directory. ● If the node has been added to the server, log in to the server, uninstall the node, and add it again. To uninstall a node, perform the following steps: a. Use an SSH remote login tool to log in to the Linux CLI as the system user.
NO TE
This step must be performed as the root user. If you log in as a common system user, run the su command to switch to the root user and perform subsequent operations. b. Run the following command to go to the node installation directory. (/opt/malluma is the node installation directory. Replace it with the actual directory.) cd /opt/malluma
2021-07-02 14 FAQs FAQs 9 Failed to Add a Node
c. Run the following command to uninstall the node: ./malluma_uninstall.sh
NO TE
If the node fails to be uninstalled, manually delete the /home/malluma/ malluma_conf/malluma_install.ini file, malluma user, /home/malluma directory, and /opt/malluma directory from the node.
2021-07-02 15 FAQs 10 Node Status Changes to Version Unmatched FAQs After an Upgrade
10 Node Status Changes to Version Unmatched After an Upgrade
Symptom After the upgrade, the node status displayed on the Node Management page is Version unmatched.
Possible Causes During the upgrade, incorrect node server authentication information is entered. As a result, the node fails to be upgraded.
Procedure ● On the web server, run the upgrade script for the nodes reporting the error. a. Run the following command to go to the tool installation directory. (/opt/hyper_tuner is the default tool installation directory. Replace it with the actual directory.) cd /opt/hyper_tuner b. Run the following command to upgrade the nodes reporting the error: bash deal_agent_mismatch.sh
NO TE
During the upgrade, enter the following information for each node to be upgraded: ● User name for adding the node ● Absolute installation path of the node ● Absolute path of the SSH private key file and password of the SSH private key file or password of the root user for logging in to the node server ● On the Node Management page, delete the nodes and add them again. If a node fails to be deleted on the web page, log in to the node server to manually uninstall the node. To uninstall a node, perform the following steps: a. Use an SSH remote login tool to log in to the Linux CLI as the system user.
2021-07-02 16 FAQs 10 Node Status Changes to Version Unmatched FAQs After an Upgrade
NO TE
This step must be performed as the root user. If you log in as a common system user, run the su command to switch to the root user and perform subsequent operations. b. Run the following command to go to the node installation directory. (/opt/malluma is the node installation directory. Replace it with the actual directory.) cd /opt/malluma c. Run the following command to uninstall the node: ./malluma_uninstall.sh
NO TE
If the node fails to be uninstalled, manually delete the /home/malluma/ malluma_conf/malluma_install.ini file, malluma user, /home/malluma directory, and /opt/malluma directory from the node.
2021-07-02 17 11 Failed to Associate Assembly Instructions with FAQs Hotspot Functions in the Dynamic Library on FAQs EulerOS
11 Failed to Associate Assembly Instructions with Hotspot Functions in the Dynamic Library on EulerOS
Symptom
After a resource scheduling analysis and hotspot function performance analysis task is successfully executed, no data about the source code and assembly instructions of the function is displayed on the page.
Possible Causes
On EulerOS, the operating system running user malluma of the Kunpeng Hyper Tuner does not have the execute permission on the objdump and readelf commands. As a result, the start address and end address of the associated function fail to be obtained.
Procedure
Log in to the server as the root user and grant the execute permission on the objdump and readelf commands for the malluma user.
Step 1 Run the following commands to view the locations of the objdump and readelf executable files:
which objdump
which readelf
Step 2 Run the following commands to grant the execute permission for the malluma user:
chmod o+x /usr/bin/objdump
chmod o+x /usr/bin/readelf
----End
2021-07-02 18 FAQs FAQs 12 Failed to Perform an I/O Analysis Task
12 Failed to Perform an I/O Analysis Task
Symptom
An I/O analysis task fails. The error message is "system not support, please open ftrace." Check whether the system supports ftrace and whether ftrace is enabled.
Possible Causes
The OS kernel version does not support Ftrace.
Procedure
NO TE
Ftrace is a tracing tool built in the Linux kernel and has been added to mainstream kernels since the kernel version 2.6.27. You can use Ftrace to debug or analyze events that occur in the kernel. Ftrace provides different tracers for different scenarios, such as tracing kernel function calls, tracing context switching, viewing the duration when interrupts are disabled, tracing the delay in the kernel mode, and tracing performance problems. System developers can use Ftrace to trace and debug kernels to find the root causes of the problems in the kernels and rectify the problems. In addition, users who are interested in kernels can use Ftrace to observe the activities in kernels and understand the working mechanism of kernels.
Perform the following steps to recompile the kernel:
Step 1 Enable the kernel to support Ftrace. 1. Before using Ftrace, compile it into the kernel. The kernel/trace/Makefile file in the kernel source code directory provides configuration items related to Ftrace, as listed in Table 12-1.
Table 12-1 Configuration items related to Ftrace
N Configuration Item o.
1 CONFIG_FUNCTION_TRACER
2021-07-02 19 FAQs FAQs 12 Failed to Perform an I/O Analysis Task
N Configuration Item o.
2 CONFIG_FUNCTION_GRAPH_TRACER
3 CONFIG_CONTEXT_SWITCH_TRACER
4 CONFIG_NOP_TRACER
5 CONFIG_SCHED_TRACER
6 ...
Many configuration items are related to Ftrace. Different tracers have different configuration items. Different configuration items have different dependencies. The kernel/trace/Kconfig file in the kernel source code directory describes these dependencies. You can refer to the Makefile and Konfig files and select the required tracer. 2. Generally, it is more intuitive to use make menuconfig when configuring the kernel. Take kernel 2.6.33.1 as an example. To compile Ftrace into the kernel, select Kernel hacking and Tracers, as shown in Figure 12-1 and Figure 12-2.
Figure 12-1 Linux Kernel Configuration – Kernel hacking
2021-07-02 20 FAQs FAQs 12 Failed to Perform an I/O Analysis Task
Figure 12-2 Linux Kernel Configuration – Tracers
3. The Tracers menu lists the tracers supported by the kernel, as shown in Figure 12-3. You can select the tracers as required.
Figure 12-3 Tracers supported by the kernel
CA UTION
On a 32-bit x86 server, do not select Optimize for size (see Figure 12-5) in the General setup menu (see Figure 12-4) during compilation. Otherwise, the Kernel Function Graph Tracer option in is not displayed on the screen shown in Figure 12-3. This is because in the Konfig file, the FUNCTION_GRAPH_TRACER configuration item has a special dependency condition depends on !X86_32 || !CC_OPTIMIZE_FOR_SIZE for a 32-bit x86 server.
2021-07-02 21 FAQs FAQs 12 Failed to Perform an I/O Analysis Task
Figure 12-4 General setup
Figure 12-5 Optimize for size
4. Ftrace provides access interfaces for the user mode through debugfs. Therefore, debugfs needs to be compiled into the kernel. To activate the support for debugfs for the kernel, set CONFIG_DEBUG_FS to y in the kernel configuration file (.config). You can also run the make menuconfig command and select Debug Filesystem in the Kernel hacking menu to support debugfs, as shown in Figure 12-6.
2021-07-02 22 FAQs FAQs 12 Failed to Perform an I/O Analysis Task
Figure 12-6 Debug Filesystem
5. After the configuration is complete, compile and install the new kernel, and then start the new kernel. After the support for Ftrace is activated for the kernel, the -pg option of the compiler is used during kernel compilation. This option is defined in the kernel/trace/Makefile file, as shown in the following figure. ifdef CONFIG_FUNCTION_TRACER ORIG_CFLAGS := $(KBUILD_CFLAGS) KBUILD_CFLAGS = $(subst -pg,,$(ORIG_CFLAGS)) ... endif ... Using the -pg option adds a lot of debugging information to the compiled kernel image. Generally, the support for Ftrace is activated only in the development and test phase to debug the kernel and fix bugs. The kernel eventually used for release will disable the -pg option and will not be able to use Ftrace.
Step 2 Access Ftrace through debugfs. 1. Ftrace provides access interfaces for the user mode through debugfs. After debugfs is activated during kernel configuration, the /sys/kernel/debug directory is created. The debugfs file system is mounted to this directory. To mount debugfs to the directory, add the following content to the /etc/ fstab file: debugfs /sys/kernel/debug debugfs defaults 0 0 You can also mount debugfs to the directory when the operating system is running. mount -t debugfs nodev /sys/kernel/debug 2. After the support for Ftrace is activated for the kernel, the /sys/kernel/ debug/tracing directory is created in debugfs. This directory contains the Ftrace control and output files, as shown in Figure 12-7. The files and directories in this directory vary according to the settings of Ftrace during kernel compilation.
2021-07-02 23 FAQs FAQs 12 Failed to Perform an I/O Analysis Task
Figure 12-7 Files in the tracing directory
----End
Data Files of Ftrace There are many files and directories in the /sys/kernel/debug/trace directory. Some of them are shared by various tracers, and some are used by a specific tracer. Generally, the echo command is used to change the values of these data files. You can also use the functions related to file reading and writing in the program to change the values of these files. Table 12-2 describes only some data files of Ftrace. For details about the usage of other data files of Ftrace, see the documents in the Documentation/trace directory in the kernel source code package and the source files in the kernel/trace directory.
Table 12-2 Data files of Ftrace File Description
README Provides a short usage guide that shows the sequence of Ftrace operation commands. You can run the cat command to view the file to understand the general operation process.
current_tracer Used to set or display the current tracer. You can run the echo command to write the name of another tracer to this file to switch to the tracer. After the system starts, the default value of the file is nop, that is, no tracing operation is performed. After a trace task is executed for a period of time, you can reset the tracer by writing nop to the file.
available_tracers Records the list of tracers that are compiled into the kernel. You can run the cat command to view the content. The tracers contained in this file correspond to the options activated in Figure 12-3. The tracer name written into the current_tracer file must be in the tracer name list in the available_tracers file.
2021-07-02 24 FAQs FAQs 12 Failed to Perform an I/O Analysis Task
File Description
trace Provides an interface for viewing the obtained trace information. You can run the cat command to view the traced kernel activity records in this file. You can also save the content of the file as a record file for future use.
tracing_enabled Used to configure whether the tracer specified in the current_tracer file can trace the calling of kernel functions. ● 0: disables tracing. ● 1 (default value): enables tracing.
set_graph_functi The setting of set_graph_function must clearly display the on function of the calling relationship. The displayed information structure is similar to the code of the C language. In this way, the kernel operation process can be analyzed more intuitively. This file is used when the function_graph tracer is used. By default, a calling relationship sequence is generated for all functions. You can write this file to specify the functions that require special attention.
buffer_size_kb Used to set the size of the trace buffer used by a single CPU. Tracers write traced information into the buffer. The trace buffer of each CPU is of the same size. The trace buffer is a ring buffer. If too much information is traced, historical information will be overwritten by new information. NOTE To change the value of the file, set the value in the current_tracer file to nop.
tracing_on Used to control the pause of tracing. Sometimes, you can write 0 to the file to disable the trace function temporarily when observing certain events. In such case, the newer part in the trace buffer is related to the concerned events. You can write 1 to the file to continue the tracing.
available_filter_f Records the kernel functions that can be traced currently. The unctions activities of the functions that are not listed in this file cannot be traced.
set_ftrace_filter Used after dynamic Ftrace is enabled and (CONFIG_DYNAMIC_FTRACE is selected) during kernel set_ftrace_notra compilation. The set_ftrace_filter file is used to specify the ce functions to be traced, and the set_ftrace_notrace file is used to specify the functions not to be traced. If a function name appears in both files, the execution of the function is not traced. The two files also support simple expressions with wildcards so that you can specify multiple target functions at a time with one expression. The value of set_ftrace_notrace is null by default, that is, all kernel functions can be traced. NOTE The names of the functions to be written into the two files must be included in the available_filter_functions file.
2021-07-02 25 FAQs FAQs 12 Failed to Perform an I/O Analysis Task
Ftrace Tracers Ftrace contains multiple tracers to trace different types of information, such as information about process scheduling and interrupt disabling. You can obtain from the available_tracers file the list of trackers supported by the kernel. When compiling the kernel, you can see the options corresponding to the trackers supported by the kernel, as described in Figure 12-3.
Table 12-3 Ftrace tracers Tracer Description
nop The nop tracer does not trace any kernel activities. You can write nop to the current_tracer file to delete the previously used tracers and clear the previously collected trace information, that is, refresh the trace file.
function The function tracer can trace the execution of kernel functions. In the set_ftrace_filter file, you can specify the functions to be traced.
function_gr The function_graph tracer can display the call relationship aph diagram of functions similar to C source code. In this way, the function call relationship diagram is intuitive. In the set_graph_function file, you can specify the functions for which call flowcharts are to be generated.
sched_swit The sched_switch tracer can trace process scheduling activities in ch the kernel.
irqsoff and The irqsoff and preemptoff trackers respectively trace the code for preemptoff disabling interrupts and the code for forbidding process preemption, and record the maximum duration for disabling interrupts. The preemptirqsoff tracker can be considered as a combination of the two trackers.
Ftrace also supports other tracers, such as initcall, ksym_tracer, mmiotrace, and sysprof. The Ftrace framework allows users to add new tracers. You can refer to the documents in the Documentation/trace directory of the kernel source code package and the source files in the kernel/trace directory to understand the usage of other tracers and the method for adding new tracers.
2021-07-02 26 FAQs FAQs 13 Insufficient Drive Space
13 Insufficient Drive Space
Symptom The tool displays a message indicating that the storage space is insufficient and needs to be manually cleared.
Possible Causes The workspace or drive space is insufficient.
Procedure
Step 1 Perform operations based on the information displayed on the page. For details, see "Error Code". Step 2 If the node space is insufficient, determine the node type based on the node IP address and the following figure. Generally, the node deployed during the tool installation is the first node in the list, and the port, user name, or installation path parameters do not exist. The preceding information exists on the remote node deployed using the node management function.
Figure 13-1 Node list
Step 3 Perform operations based on the node type. For details, see "Error Code".
----End
2021-07-02 27 FAQs FAQs 14 Using the PGO Optimizer for Compilation
14 Using the PGO Optimizer for Compilation
Symptom After a microarchitecture task is created, a message "Use PGO for compilation." is displayed when you view the Summary tab page of the analysis result.
Possible Causes The PGO optimizer is needed for compilation. Profile-Guided Optimization (PGO) improves application performance by reducing cache-thrashing, reorganizing code layout, reducing code length, and reducing branch mispredictions.
Procedure
Step 1 Add the -fprofile-generate=
----End
2021-07-02 28 FAQs FAQs 15 Upgrade Failure in Ubuntu
15 Upgrade Failure in Ubuntu
Symptom Versions later than V2.2.T3 fail to be upgraded in the Ubuntu OS.
Possible Causes The upgrade script Upgrade does not contain the HOME=/root environment variable.
Procedure
Step 1 Run the following command to go to the directory where the new Kunpeng Hyper Tuner installation package is stored. (Replace /home with the actual directory.) cd /home Step 2 Decompress the installation package. In the command, x.x.x indicates the version. tar -zxvf Hyper-Tuner-x.x.x.tar.gz Step 3 Go to the directory where the decompressed installation package is saved. cd Hyper_tuner Step 4 Decompress the software package again. In the command, x.x.x indicates the version. tar -zxvf Hyper-Tuner-x.x.x.tar.gz Step 5 Go to the directory where the decompressed installation package is stored. cd Hyper_tuner Step 6 Obtain the upgrade entry function in the new software package: cp –rf ./Upgrade /opt/hyper_tuner Step 7 Go to the installation directory of the Kunpeng Hyper Tuner of the old version. (/opt/hyper_tuner is the installation directory of the old version. Replace it with the actual directory.) cd /opt/hyper_tuner
2021-07-02 29 FAQs FAQs 15 Upgrade Failure in Ubuntu
Step 8 Run the following command to upgrade the tool. (Replace /home with the actual directory.) ./Upgrade upgrade /home/Hyper_tuner/Hyper-Tuner-x.x.x.tar.gz
----End
2021-07-02 30 FAQs 16 Failed to Log In to the Java Profiler After the Tool FAQs Is Installed
16 Failed to Log In to the Java Profiler After the Tool Is Installed
Symptom
After the tool is installed, users can successfully log in to Kunpeng Hyper Tuner, but fail to log in to Java Profiler. The output of the netstat -anp | grep 9090 command shows that port 9090 is not occupied.
NO TE
If no information is displayed, the port is not occupied. In the preceding command, 9090 indicates the internal module communication port number of Java Profiler, which is set during the installation. Change it as required.
Possible Cause
In the Linux operating system, securerandom.source=file:/dev/random is configured in the $JAVA_HOME/conf/security/java.security file by default. The random pool of file:/dev/random depends on the number of system interrupts. Therefore, when the number of system interrupts is less than the threshold, the /dev/random device is locked always, and the process that attempts to read data enters the waiting state. As a result, the startup of the Java Profiler service is delayed.
Procedure
Step 1 Run the following command to modify the java.security file:
vi $JAVA_HOME/conf/security/java.security
Step 2 Locate the following code: securerandom.source=file:/dev/random
Press i to enter the editing mode and change the code after the equal sign to file:/dev/urandom.
securerandom.source=file:/dev/urandom
Press Esc, enter :wq, and press Enter to save the change and exit.
2021-07-02 31 FAQs 16 Failed to Log In to the Java Profiler After the Tool FAQs Is Installed
Step 3 Run the following command to restart the tool: systemctl restart thor
----End
2021-07-02 32 FAQs FAQs 17 Failed to Collect HPC Task Data on Ubuntu
17 Failed to Collect HPC Task Data on Ubuntu
The python scripting function in the perf script is disabled on Ubuntu 13.04 and later. As a result, data fails to be collected in an HPC analysis task. To support this function on Ubuntu, recompile and replace the perf in the OS.
Step 1 Use an SSH tool to remotely log in to the Linux CLI as the root user. Step 2 Run the uname -r command to view the current kernel version.
In this example, the kernel version is 4.15.0. Step 3 Run the following command to download the perf version matching the kernel. mkdir /home/linux_kernel cd /home/linux_kernel apt-get update In apt-get source linux-source-
Step 4 Compile the perf. Run the following command to check what packages are missing in the current version. cd /home/linux_kernel/linux_4.15.0/tools/perf make
2021-07-02 33 FAQs FAQs 17 Failed to Collect HPC Task Data on Ubuntu
If the console displays a message indicating that some packages are missing, install those as prompted.
The python scripting function requires python-dev libelf-dev libunwind-dev libaudit-dev libslang2-dev.
Run the following commands to install the packages:
apt-get install python-dev libelf-dev libunwind-dev libaudit-dev libslang2-dev
make
make install
The command output shows that the libaudit, libelf, libpython, libslang, libunwind, lzma, and bpf are enabled.
Step 5 Run the following commands to check whether the compilation is successful:
cd /home/linux_kernel
2021-07-02 34 FAQs FAQs 17 Failed to Collect HPC Task Data on Ubuntu
/home/linux_kernel/linux-4.15.0/tools/perf/perf record /home/linux_kernel/linux-4.15.0/tools/perf/perf script -g python If a perf-script.py file is generated in the directory, the compilation is successful.
Step 6 Run the following command to replace the existing perf. Then the python scripting function is available on Ubuntu. cp /home/linux_kernel/linux-4.15.0/tools/perf/perf /usr/bin
----End
2021-07-02 35 FAQs FAQs 18 Node Status Changes to Offline
18 Node Status Changes to Offline
Symptom The node status changes from online to offline.
Possible Causes The server and agent certificates of the node are not updated synchronously.
Procedure
Step 1 Regenerate a certificate. Click Generate Certificate on the Agent service certificate page to generate a certificate. Step 2 Check the node information. Check whether the offline node is a local IP node or a manually added node. If the node is a local IP node, perform steps 3 and 4. If the node is manually added, perform only step 4. Step 3 Replace the certificate. Replace the server certificate of the offline node. Replace the agent certificate of the offline node. Step 4 Check the node status. After a period of time, the node status changes to online.
----End
2021-07-02 36