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
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/hosts2. 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.com3. Restart Ubuntu.
Solution：
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)
Solution：
$cd /home
$chmod –R 744 oracle
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
Solution：
Start oracle service and monitor.
Solution：
Check whether the language configurations such as nls under the .bash_profile file are the same as the oracle user’s .bash_profile.
Solution：
Check whether the configuration and order related to tuxedo under the .bash_profile file are correct (Compare with the actual path).
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.
Solution：
View the machine name in the ubbwinnt file, modify and recompile.
Solution：
Tmshutdown -y stop all services, and recompile.
Solution：
Ipcrm, ipcs or restart the computer.
Solution：
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.
Solution：
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”.
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.
Solution：
Check if the fbase path is correctly configured in the .bash_profile file.
Solution：
json is not compiled successfully, Enter the json path to check whether the .lib folder is generated.
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.
After successfully building Linux, installing the required dependency libraries, and installing WPS and WRF. Run an instance simulation.
./ungrib.exe reports an error that libpng16.so.16 cannot be found.
The error is as follows：
./ungrib.exe: error while loading shared libraries: libpng16.so. 16: cannot open shared object file: No such file or directory
sudo vim /etc/ld.so.conf
Add statement: /home/tian/Software/libpng-intel/lib
sudo ldconfig
Go to ./ungrib.exe to run successfully
When installing Nignx
Installing the GCC compiler
yum install -y gcc
Report an error as below:
Error: Package: glibc-headers-2.17-317.el7.x86_64 (base)
Requires: glibc = 2.17-317.el7
Installed: glibc-2.17-322.el7_9.i686 (@c6-update)
glibc = 2.17-322.el7_9
Available: glibc-2.17-317.el7.i686 (base)
glibc = 2.17-317.el7
Error: Package: glibc-devel-2.17-317.el7.x86_64 (base)
Requires: glibc = 2.17-317.el7
Installed: glibc-2.17-322.el7_9.i686 (@c6-update)
glibc = 2.17-322.el7_9
Available: glibc-2.17-317.el7.i686 (base)
glibc = 2.17-317.el7
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Show one installed version higher than the required version
Resolved by downgrading.
yum downgrade glibc glibc-devel glibc-common glibc-headers
Installation success!
Installed:
gcc.x86_64 0:4.8.5-44.el7
Dependency Installed:
cpp.x86_64 0:4.8.5-44.el7 glibc-devel.x86_64 0:2.17-317.el7 glibc-headers.x86_64 0:2.17-317.el7 kernel-headers.x86_64 0:3.10.0-1160.el7 libmpc.x86_64 0:1.0.1-3.el7
mpfr.x86_64 0:3.1.1-4.el7
Complete!
keystone install error: Failed to parse /etc/keystone/keystone.conf: at /etc/keystone/keystone.conf:687, No ‘:’ or ‘=’ found in assignment: ‘connection’
Reason: The connection is not = or colon
Modified
Note the keyistone format
Create a cron task, the error is as follows:
# crontab -e no crontab for root - using an empty one Error detected while processing /root/.vimrc: line 2: E492: Not an editor command: Plug 'scrooloose/nerdtree' Press ENTER or type command to continue
Solution:
1. Open ~/.bashrc and insert the following red line in the file:
2. Effective source ~/.bashrc
Finish.
Phenomenon:
./configure --prefix=/usr/local/python3.6
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for python3.6... no
checking for python3... no
checking for python... python
checking for --enable-universalsdk... no
checking for --with-universal-archs... no
checking MACHDEP... linux
checking for --without-gcc... no
checking for --with-icc... no
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/tmp/Python-3.6.13':
configure: error: C compiler cannot create executables
See `config.log' for more details
Solution:
1. View log
# cat config.log |grep error
gcc: error: unrecognized command line option '-V'
gcc: fatal error: no input files
gcc: error: unrecognized command line option '-qversion'
gcc: fatal error: no input files
/usr/libexec/gcc/x86_64-redhat-linux/4.8.5/cc1: error while loading shared libraries: libmpfr.so.4: cannot open shared object file: No such file or directory
configure:4005: error: in `/tmp/Python-3.6.13':
configure:4007: error: C compiler cannot create executables
Missing libmpfr.so.4 File
2. Install mpfr
Package name:mpfr-3.1.1-4.el7.x86_64
~# yum install mpfr-3.1.1-4.el7.x86_64 -y
......
Verification:
~# ll /usr/lib64/libmpfr.so.4
libmpfr.so.4 libmpfr.so.4.1.1
~# ll /usr/lib64/libmpfr.so.4
lrwxrwxrwx 1 root root 16 Sep 7 22:26 /usr/lib64/libmpfr.so.4 -> libmpfr.so.4.1.1
Finally, the problem is solved
Case description:
In the cluster of KingbaseES V8R3 cluster The error message “ERROR: md5 authentication failed; DETAIL: password does not match” often appears in the log. This case shows the cause of this error.
Applicable version:KingbaseES V8R3
Problem phenomenon:
cluster.log:
Analysis: 1, when the system user connects to port 9999 to execute “show pool_nodes”, you need to access the cluster kingbasecluster service and verify the user’s identity by cluster_password.
As shown below: cluster.log information 
2. The password of the system user needs to be verified by the database sys_hba.conf (the password is encrypted by md5). 
As shown below: cluster.log information 
3. And port 9999 corresponds to the kingbasecluster service, which also needs to be verified by the md5 password in the cluster_password file. 
4. If the database password and the password in cluster_password do not match, you cannot log in.
5. This error message does not affect the health detection of the background database by kingbasecluster. 
Problem-solving:
When changing the database user system password in the cluster.
1、Modify the password of the system user in the database.
2, also need to modify the password of system user in cluster_password by sys_md5 tool.
3, you need to modify the password of system in the recovery.done and recovery.conf configuration files.Cause of the problem
VCS 2016 requires gcc4.8 and g++4.8, while VBoxGuestAdditions-6.1 – * * requires version 4.9+ to install (the ‘-fstack-protector-strong compilation option need to be supported).
Solution:
1. Check the version through
ls /usr/bin/gcc*. If not, install the corresponding version;
2. Then use the following command to perform version management
sudo update-alternatives –install /usr/bin/gcc gcc /usr/bin/gcc-5 100
3. Switch the new version of gcc with the following command
sudo update-alternatives –config gcc
4. Reinstall the VBoxGuestAdditions tool
cd /opt/VBoxGuestAdditions-6.1.36/init
sudo vboxadd setup
5. Finally, the problem was solved by re-hanging it in the directory
An error was reported when starting the KVM virtual machine on the command line: startup failed, and the default network could not be found
[root@localhost ~]# virsh start centos7.0
error: Failed to start domain centos7.0
error: Network not found: no network with matching name 'default'
However, there was a default network before, and an error was reported when it was restarted after a night. First, find the path of default.xml,
[root@localhost ~]# find/-name "default.xml"
/run/libvirt/storage/default.xml
/etc/libvirt/storage/default.xml
/etc/libvirt/storage/autostart/default.xml
/usr/share/backgrounds/default.xml
/usr/share/libvirt/networks/default.xml
It can be seen that there are many xml files. Select those related to network and libvirt for execution
[root@localhost ~]# virsh net-define /usr/share/libvirt/networks/default.xml
Network default defined from /usr/share/libvirt/networks/default.xml
[root@localhost ~]# virsh net-start default
Network default started
Start successfully, check:
[root@localhost ~]# virsh net-list
Name State Autostart Persistent
----------------------------------------------------------
default active no yes
Finally, just start the KVM virtual machine:
[root@localhost ~]# virsh start centos7.0
Domain centos7.0 started
The graphical interface has also been viewed successfully:
ERROR: ld.so: object ‘/$LIB/libonion.so‘ from /etc/ld.so.preload
1. An error was reported when executing certbot — nginx automatic certificate configuration today, as shown in the following figure
2. Processing method
echo "" > /etc/ld.so.preload #the solution is very simple