Failed to Install Library Files

Symptom

During library file installation, a message indicating library file installation failure is displayed.

Possible Cause

The dependency library file does not match the OS version.

Troubleshooting 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.

The following steps use the perl-devel library file as an example.

1. Check the installation failure message.
   Figure 1 Failure message
   
2. Check the logs generated during the installation. The following is an example.
   Figure 2 Installation log
   
3. The preceding information shows that libdb-5.3.21-25.el7.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.
   Restart the tool by restarting the gunicorn_framework/gunicorn_plugin/devkit_nginx service. The following uses devkit_nginx as an example:

   • root user

     systemctl restart devkit_nginx

   • Common users

     bash /home/test01/DevKit/tools/service_management.sh restart devkit_nginx

   

   • /home/test01: Replace the example installation directory with the actual one.
   • If you run a command on the server to restart a service, refresh the front-end page to display the updated task information.
   • If the tool is installed in a container, you can run service_management.sh to manage the service based on the installation method for a common user.