Category Archives: Linux

[Solved] libvirtd Error: virNetServerAddClient:271 : Too many active clients

error: virNetServerAddClient:271 : Too many active clients (20), dropping connection from 127.0.0.1; 0

Reason: The number of libvirt client links exceeds the maximum number allowed by libvirtd, causing new client links to be discarded
Solution: Temporary workaround: modify max_clients in /etc/libvirt/libvirtd.conf to be larger, then restart libvirtd
Long-term solution: locate the cause of client link overflow on the server

The following figure shows that the destruction of a large number of cvm sub machines on the server failed, resulting in client link overflow. The solution is to migrate the running cvm sub machines on the master machine, and then restart the master machine

[Solved] Linux error E: dpkg is broken, you must manually run ‘sudo dpkg –configure -a’ to resolve this issue

Executes the Linux commandsudo apt install curland reports an error:

E: dpkg is interrupted. You must manually run ‘sudo dpkg — configure – a’ to solve this problem

System version: Ubuntu 20.04 LTS

Solution: three-step command line

sudo rm /var/lib/dpkg/updates/*
sudo apt-get update
sudo apt-get upgrade

[Solved] ERROR: Subproject directory not found and gst-plugins-base.wrap file not found

gstreamer1.0-plugins-bad compile Error:

| Found pkg-config: /sd1/jarvis-workspace/build-jarvis-imx-fb-imx6ull/tmp/work/cortexa7t2hf-neon-mx6ul-poky-linux-gnueabi/gstreamer1.0-plugins-bad/1.16.3-r0/recipe-sysroot-native/usr/bin/pkg-config (0.29.2)
| Run-time dependency gstreamer-1.0 found: YES 1.16.3
| Run-time dependency gstreamer-base-1.0 found: YES 1.16.3
| Run-time dependency gstreamer-net-1.0 found: YES 1.16.3
| Run-time dependency gstreamer-controller-1.0 found: YES 1.16.3
| Run-time dependency gstreamer-pbutils-1.0 found: YES 1.16.3
| Run-time dependency gstreamer-allocators-1.0 found: YES 1.16.3
| Run-time dependency gstreamer-app-1.0 found: YES 1.16.3
| Run-time dependency gstreamer-audio-1.0 found: YES 1.16.3
| Run-time dependency gstreamer-fft-1.0 found: YES 1.16.3
| Run-time dependency gstreamer-riff-1.0 found: YES 1.16.3
| Run-time dependency gstreamer-rtp-1.0 found: YES 1.16.3
| Run-time dependency gstreamer-rtsp-1.0 found: YES 1.16.3
| Run-time dependency gstreamer-sdp-1.0 found: YES 1.16.3
| Run-time dependency gstreamer-tag-1.0 found: YES 1.16.3
| Run-time dependency gstreamer-video-1.0 found: YES 1.16.3
| Run-time dependency gstreamer-check-1.0 found: YES 1.16.3
| Found CMake: NO
| Run-time dependency gstreamer-gl-1.0 found: NO (tried pkgconfig and cmake)
| Looking for a fallback subproject for the dependency gstreamer-gl-1.0
| 
| meson.build:283:0: ERROR: Subproject directory not found and gst-plugins-base.wrap file not found
| 
| A full log can be found at /sd1/jarvis-workspace/build-jarvis-imx-fb-imx6ull/tmp/work/cortexa7t2hf-neon-mx6ul-poky-linux-gnueabi/gstreamer1.0-plugins-bad/1.16.3-r0/build/meson-logs/meson-log.txt
| ERROR: meson failed
| WARNING: exit code 1 from a shell command.
| ERROR: Execution of '/sd1/jarvis-workspace/build-jarvis-imx-fb-imx6ull/tmp/work/cortexa7t2hf-neon-mx6ul-poky-linux-gnueabi/gstreamer1.0-plugins-bad/1.16.3-r0/temp/run.do_configure.2066278' failed with exit code 1
ERROR: Task (/sd1/jarvis-workspace/layers/poky/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.16.3.bb:do_configure) failed with exit code '1'

Solution:

sudo apt install libva-dev

ERROR: This system does not support “RDRAND“ [How to Solve]

Problem phenomenon:

When running DPDK app programs in some environments, the following problems may occur:

Solution:

Before compiling, you can use the grep command in the DPDK root directory to check where there is a configuration setting about RDRAND, here there is a relevant configuration inside the first meson.build.

After opening the file, you can find that RDRAND is iterated through the optional_flags, so delete the above iterated items and recompile.

Summary:

The reason here is that RDRAND is an instruction set of CPUs. Not all CPUs support this instruction. In order to make the program universal, we can delete this configuration when compiling, so that we can run on CPUs that do not support RDRAND.

[Solved] Docker Filed to Start Container: Error response from daemon: network XXX not found 

[root@xxx dc-gitlab]# docker start cce932ba5dc2
Error response from daemon: network ase6cd78ccf7f24c49871653f2dd not found
Error: failed to start containers: css932ba5dd3

The above are error messages. The previous bridging is configured.

 

Solution:

docker-compose up -d --force-recreate

It can be solved.

Scene:

During the production launch, the port of the gitlab started by Docker cannot be accessed suddenly. It is OK to check the corresponding server listening port. It can be pinged, but the telnet port is not. In an hurry to go online, I had to restart the server and Docker, and then the above problem occurred.

[Solved] fatal error: cannot write PCH file: required memory segment unavailable

Error Message:

fatal error: cannot write PCH file: required memory segment unavailable
make[4]: *** [Makefile:1904: arm-eabi/bits/extc++.h.gch/O2g.gch] Error 1
make[4]: Leaving directory ‘/d/gnu/gcc-12.2.0-build/arm-eabi/libstdc+±v3/include’
make[3]: *** [Makefile:576: all-recursive] Error 1
make[3]: Leaving directory ‘/d/gnu/gcc-12.2.0-build/arm-eabi/libstdc+±v3’
make[2]: *** [Makefile:501: all] Error 2
make[2]: Leaving directory ‘/d/gnu/gcc-12.2.0-build/arm-eabi/libstdc+±v3’
make[1]: *** [Makefile:12620: all-target-libstdc+±v3] Error 2

 

 

Solution:

Downgrade your GCC pack, because there are some bugs in your current gcc-12.2.0. you can go to the official website or the following link to download it:

http://ftp.gnu.org/gnu/gcc/

[Solved] OCI runtime create failed: /usr/bin/nvidia-container-runtime did not terminate successfully: unknown

Docker build Image error:

OCI runtime create failed: /usr/bin/nvidia-container-runtime did not terminate successfully: unknown
Root cause: need to install nvidia-container-runtime
How to Solve:

1. Online installation

distribution=$(. /etc/os-release;echo $ID$VERSION_ID)
curl -s -L https://nvidia.github.io/nvidia-container-runtime/$distribution/nvidia-container-runtime.repo |\
tee /etc/yum.repos.d/nvidia-container-runtime.repo
yum install nvidia-container-runtime

2. If stuck on connecting to nvidia.github.io

1) yum -y install yum-utils

2) mkdir ~/nvidia && cd ~/nvidia

3) repotrack nvidia-container-runtime

4)rpm -Uvh –force –nodeps *.rpm

[Solved] OCI runtime create failed: runc create failed: unable to start container process:

OCI runtime create failed: run create failed: unable to start container process: exec: “env”: executable file not found in $PATH: unknown

The above error occurs when running the docker container.

Reason:
The image given to me by others has been decompressed, and I was told that I used load to load the image.

docker load < ***.tar

The command reports an error
The error message is: open/var/lib/locker/tmp/locker import - **************/repositories: no such file or directory.

So I used docker import to load the image, and surprisingly it loaded successfully, and there was no problem of 0kb as mentioned on the internet.

docker import ***.tar docker:v1

But there was a problem at runtime.

docker run

The following error message appears:
Error response from daemon: failed to create shim task: OCI runtime create failed: run create failed: disable to start container process: exec: "env": executable file not found in $PATH: unknown

Solution:

tar -xvf	***.tar

After decompression, load the image again. Success!

Failed to start firewalld.service: Unit is masked [How to Solve]

Centos7 failed to start firewall: Failed to start firewalld.service: Unit is masked.

Solution:

The error “Failed to start firewalld.service: Unit is masked.” appears when you run “systemctl start firewalld”. The service needs to be unlocked:

systemctl unmask firewalld.service
systemctl start firewalld