[tcapulusdb knowledge base] common problems of tcapulusdb local deployment

【TcaplusDB The knowledge base 】TcaplusDB Local Release deployment FAQs

1. Container startup log report ：Failed to write channels, for shmctl

Question why ：

The shared memory setting of the container is too small , part Docker The default container shared memory size of version is 32M, and TcaplusDB The minimum value required for the container is 2G.

Solution ：

1. Use 3.53.1 The latest version of the mirror , Or a later version of the image ;
   1. Pass... When starting the container --shm-size=2G Displays the shared memory size of the specified container .

2. stay Debian The startup container in the system failed to start , Containers Exit Code = 139

Question why ：

The exit code currently encountered is 139 Scene , Most of them are mainframes vsyscall Set up questions

Solution ：

1. Debian Set up vsyscall Refer to http://helpcenter.onlyoffice.com/installation/mail-enabling-vsyscall.aspx;
2. Windows WSL2 Set up vsyscall Refer to https://zhuanlan.zhihu.com/p/256317180

3. Inside the container SSH, PWD And other commands and services are not available , Lead to TcaplusDB Some features are not available

Question why ：

At present, most of the reasons for this situation are that the master machine is turned on SELinux Enforce security policy , Cause... In the container SSH,PWD Wait until the command or service is unavailable . direct influence yes TcaplusDB Some of the functions that depend on these commands and services are not available , Such as surface clearing, etc .

Solution ：

Turn off the of the master SELinux Enforce security policy .

1. Temporarily Closed . setenforce 0
2. Permanent ban . edit /etc/selinux/config file , Set up SELINUX=Disabled, Restart the machine .

4. The network segment of the master computer is connected with Docker Container network segment conflict , Lead to Client Not connected to the service

Question why ：

In some environments , There may be a conflict between the master network segment and the container default network segment ,Docker The container usually defaults to the container, and the network segment is 192.168 perhaps 172.17, When the master is also in these network segments ,TcaplusDB The request sent from the master will be regarded as an intranet request , to Client Return to container IP Serve as a service IP, And in some circumstances （ Such as WSL）, The master cannot directly access the container IP, The service status is normal , But the client cannot connect to the server .

Solution ：

Create a network segment different from the master Docker The Internet , If the network segment of the master is 172.17, You can create a 192.168 The network segment Docker The Internet , And when you create a container , Specify to use this network .Docker The creation method of the network is as follows .

Execute the following command to create Docker The Internet .

sudo docker network create --driver=bridge --subnet=192.168.10.0/24 subnet_192_168_10

• 192.168.10.0/24 by Docker Network segment and mask definition .
• subnet_192_168_10 by Docker net name , Create container command --network This is the network name that follows .

---

TcaplusDB It's a distributed product of Tencent NoSQL database , The code for storage and scheduling is completely self-developed . With cache + Landing fusion architecture 、PB Levels of storage 、 Millisecond delay 、 Lossless horizontal expansion and complex data structure . At the same time, it has rich ecological environment 、 Easy migration 、 Extremely low operation and maintenance costs and five nine high availability features . Customer coverage game 、 Internet 、 government affairs 、 Finance 、 Manufacturing and the Internet of things .