Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

How to deal with the problem of unsuccessful database startup under Docker

2025-01-16 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >

Share

Shulou(Shulou.com)05/31 Report--

This article mainly explains "how to deal with the problem of unsuccessful database startup under Docker". The explanation in this article is simple and clear, easy to learn and understand. Please follow the ideas of Xiaobian to study and learn "how to deal with the problem of unsuccessful database startup under Docker" together.

Event background: During the database installation test in cooperation with Inspur Cloud Lab, Inspur reported that the database service could not be started after the silent installation of the database. The error message is as follows:

User environment: Galaxy Kirin 7.4, Godson environment

First, start processing foreground startup error, using yum for installation.

Execute command: yum -y install openssl*

Following implementation:

Could not load a transcoding service

Since the user is installing the database under Docker, ask the user why the operating system of the image and the host respectively, the user tells that the host is Galaxy Kirin 7.4, and the image is Centos 7.0; therefore, it is recommended that the user try to change the operating system of the image to the same operating system as the host.

After a while, the user informed that the database boot was successful after changing the mirrored operating system.

In addition, in the process of processing the problem, two files under the bin directory were found. libssl.so libcrypto.so These two files can be replaced with the files under/usr/lib 64/libssl.so or copied directly when missing.

The test process is as follows:

(1) First find the file location

(3) Delete libssl.so libcrypto.so from/opt/dmdbms/bin.

(4) Copy the relevant files under/usr/lib64 to the bin directory. and modify permissions.

(5) Restart database service successfully

Thank you for reading, the above is the content of "how to deal with the unsuccessful database startup problem under Docker". After studying this article, I believe everyone has a deeper understanding of how to deal with the unsuccessful database startup problem under Docker. The specific use situation still needs to be verified by practice. Here is, Xiaobian will push more articles related to knowledge points for everyone, welcome to pay attention!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Database

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report