Tag Archives: linux

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] 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

[Solved] Failed to Setup IP tables: Unable to enable SKIP DNAT rule: (iptables failed: iptables –wait -t na…

Leave a reply

Error message: Failed to Setup IP tables: Unable to enable SKIP DNAT rule: (iptables failed: iptables –wait -t nat -I DOCKER -i br-b1938128a963 -j RETURN: iptables: No chain/target/match by that name. (exit status 1))

reason: The error report after operating the Linux firewall on/off operate.

Solution:

restart docker via the following command:

service docker restart

VScode Error: extension failed XHR Failed (Ubuntu Virtual Machine)

Leave a reply

In the process of learning Linux embedded development, I encountered the following problems: after installing VS code in the Ubuntu virtual machine, it need to install appropriate plug-ins. At this point, vscode fails to expand XHR Failed, as shown in the figure:

And press the F1 key inside Vs code to open Developer:Toggle Developer Tools, enter the Console to query the reason, The error shown in the figure below appears (That is, Ubuntu system will point the domain name to the specified IP solve this problem):

After searching the Internet for many solutions, the following operations can solve the problem:

1. Open the hosts file in the Ubuntu terminal

sudo gedit /etc/hosts

2. Add the corresponding relationship between IP and domain name in the file as follows, and save the hosts file：

13.107.42.18 marketplace.visualstudio.com

3. Restart Ubuntu.

[Solved] Job for mysqld.service failed because the control process exited with error code

Leave a reply

When closing the virtual machine, and then reopening the virtual machine, The following error will appear when executing the command systemctl start mysqld to start the mysql service: Job for mysqld.service failed because the control process exited with error code. See “systemctl status mysqld.service” and “journalctl -xe” for details.
Insert picture description here
The above situation occurs because the virtual machine is shutting down, mysql service-related control process error, After my own learning and experience, I got a solution: First enter the specified directory/run, create a mysqld file in this directory, Then authorize this file, In this way, the mysql service can be started normally
Insert picture description here
In fact, when we install mysql, start When mysql service, use the command systemctl enable mysqld to set the boot to start automatically, the above error will not occur.

tuxedo Compile Background Common Error [How to Fix]

Leave a reply

Error 1: When compiling the service written by Proc, the header file cannot be found

Solution：

  • Execute the command first # find . -name “stddef.h” -print to find the storage path of stddef.h；
  • Review the content of the pcscfg.cfg file under $oracle_home/precomp/admin, Modify the content marked in red below to the storage path of stddef.h actually queried by the above find statement.

sys_include=(/usr/include,/usr/lib/gcc-lib/i486-suse-linux/2.95.3/include,/usr/lib/gcc-lib/i386-redhat-linux/2.96 /include)

Error 2: prompt “ORA-01031: insufficient privileges” when compiling background source files

Solution：

  • Log in with the oracle user,check the newsale user’s permission to use /home/oracle,execute the following command

$cd /home

$chmod –R 744 oracle

  • Grant write permissions to files such as tnsnames.ora under $ORACLE_HOME/network/admin.

 

Error 3: When compiling background source files, prompt “ORA-01034”

Problem symptoms:

“ORA-01034: ORACLE not available

ORA-27121: unable to determine size of shared memory segment

SVR4 Error: 13: Permission denied”

Solution:

Log in as the oracle user, execute the following command

$cd $ORACLE_HOME/bin

$ls -altr oracle #Modify if it is not the following permissions after viewing

$ chmod 6751 oracle

 

Error 4: When compiling background source files, prompts “ORA-01034, ORA-27101 and Linux Error: 2: No Such file or dirctory”

Solution：

Start oracle service and monitor.

 

Error 5: When compiling background source files, prompt “ORA-12705”

Solution：

Check whether the language configurations such as nls under the .bash_profile file are the same as the oracle user’s .bash_profile.

Error 6: When compiling background source files, prompt buildserver related errors

Solution：

Check whether the configuration and order related to tuxedo under the .bash_profile file are correct (Compare with the actual path).

Error 7: Compile background source files, prompt “You do not have a valid SDK license”

Solution：

Maybe the license of tuxedo is incorrect. Check whether the lic.txt under /home/tuxedo/Tuxedo 8.1/bealic has been overwritten, or check whether the TYPE= SDK in lic is correct, and the value of type is SDK.

Error 8: When compiling the ubbwinnt file, prompts “CMDTUX_TAT:868:ERROR :tmloadcf can not run on a non-master node”

Solution：

View the machine name in the ubbwinnt file, modify and recompile.

Error 9: When compiling the ubbwinnt file, prompts “CMDTUX_TAT:868:ERROR tmloadcf cannot run on an active node”

Solution：

Tmshutdown -y stop all services, and recompile.

Error 10: When the application starts and closes tmshutdown -y, reports “CMDTUX_CAT:764: ERROR: can’t attach to BB”

Solution：

Ipcrm, ipcs or restart the computer.

Error 11: When the application starts, prompts “CMDTUX_CAT:1685:ERROR:Application initialization failure”

Solution：

  • Check whether the server.ini file in the bin folder exists, whether its configuration is correct；
  • Check the oracle’s Whether related services are started；
  • Check if the ip address in ubbwinnt is correct；
  • bdmconfig is missing Times the same error.

Error 12: prompts “CMDTUX_CAT:816:ERROR:Connot exec, executable file not found” when the application starts up

Solution：

Check whether the executable file generated when the source file is compiled is missing in the bin folder. Also if the tuxconfig file is missing, it will also prompt a “GMDTUX_CAT:1360” error.

Error 13: “Application Initialization Error” when starting center or counter

Solution：

  • Check whether the BDE data source has settings, whether the settings are correct；
  • Check whether the configuration in setreg.reg is correct ；
  • Try another openfund.exe file.

 

Error 14: Client login failed, prompt “WTUXWS32.DLL not found, This application failed to start for this reason. Reinstalling the application may fix the problem”

Solution：

Check if the tuxedo patch has been installed, Check if the tuxedo runner path has been added to the path of the system environment variable. You can add the corresponding files that are prompted to be missing to “C:\WINDOWS\system32”.

Error 15: Use the new makefile file in 3.5, when compiling the background source file, an error is reported as shown below:

6f9bb6f7a97a4dff8d206d2d18cdfd01.png

Solution：

Check if the path in the .bash_profile file is the configured fbase path. Whether the fbase installation package upload is useful requires binary upload.

Error 16: When using the asar middleware, to compile the background source file, an error is reported as shown below:

be14e8d8eacc43e4ac80c60608a034fc.png

Solution：

Check if the fbase path is correctly configured in the .bash_profile file.

Error 17: When using the asar middleware, to compile the background source file, an error is reported as shown below:

f87e4693ec244c2ea6e85ab7c2137351.png

Solution：

json is not compiled successfully, Enter the json path to check whether the .lib folder is generated.

Error 18: The client login interface reports an error as shown below:

46e6df4fda8c40eabad5b7406a809a44.png

Solution：

Add F:\hs\fbase20\Fbase_win32\lib to the environment variable system variable path value; add F:\hs\fbase20\Fbase_win32\lib to the user variable lib value.

Error 19: Linux address settings

  1. View the network segment of this machine