Tag Archives: TCP/IP

[Solved] failed to set bridge addr: “cni0“ already has an IP address different from xxxx

failed to set bridge addr: “cni0“ already has an IP address different from xxxx

Recently, when debugging Kubernetes to add or delete a node, and then deploying Pod on this node, a network card address error exception occurred. The troubleshooting solution for this exception is as follows:

Error:

(combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox “745720ffb20646054a167560299b19bb9ae046fe6c677b5d26312b89a26554e1”: failed to set bridge addr: “cni0” already has an IP address different from 172.20.2.1/24

Solution:

Delete the node without restarting the node server, restart the node server (in this case, it is usually caused by the server cache, restart the server on it)
After restarting the server or not, delete the wrong NIC on the node and wait for the system to rebuild automatically, the operation process is as follows.

sudo ifconfig cni0 down    
sudo ip link delete cni0

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

[Solved] Mybatis Error: CannotFindDataSourceException: dynamic-datasource can not find primary datasource

Problem background

When using mybatis, an error is reported that the master data source cannot be found:

org.mybatis.spring.MyBatisSystemException: nested exception is org.apache.ibatis.exceptions.PersistenceException: 
### Error updating database.  Cause: com.baomidou.dynamic.datasource.exception.CannotFindDataSourceException: dynamic-datasource can not find primary datasource
### The error may exist in com/lanran/transactional/dao/PaymentMapper.java (best guess)
### The error may involve com.lanran.transactional.dao.PaymentMapper.insertBatchSomeColumn
### The error occurred while executing an update
### Cause: com.baomidou.dynamic.datasource.exception.CannotFindDataSourceException: dynamic-datasource can not find primary datasource

Solution

1. Because the multi-source configuration dependency of mybatisplus is added, but the configuration file does not write the related configuration of multi-source, an error is reported

        <dependency>
            <groupId>com.baomidou</groupId>
            <artifactId>dynamic-datasource-spring-boot-starter</artifactId>
            <version>3.5.0</version>
        </dependency>

Method 1: if you don’t use multi-source configuration, remove this dependency
Method 2: application set multi-source configuration

server:
  port: 40001

spring:
  datasource:
    druid:
      stat-view-servlet:
        enabled: true
    dynamic:
      # Configure the global druid parameter, please configure as needed
      druid:
        initial-size: 5
        max-active: 8
        min-idle: 3
        max-wait: 1000
        validation-query: 'select 1'
      datasource:
        master:
          username: root
          password: 123456
          url: jdbc:mysql://localhost:3306/test?useUnicode=true&characterEncoding=utf-8&useSSL=true&serverTimezone=UTC
          driver-class-name: com.mysql.cj.jdbc.Driver
        slave_1:
          username: root
          password: 123456
          url: jdbc:mysql://localhost:3306/test2?useUnicode=true&characterEncoding=utf-8&useSSL=true&serverTimezone=UTC
          driver-class-name: com.mysql.cj.jdbc.Driver

[Solved] ERROR OGG-01232 Receive TCP params error: TCP/IP error 104 (Connection reset by peer), endpoint:

Solution 1:
due to the inconsistency between the ports of the source end and the destination end,
the error message of the source end is error ogg-01232 receive TCP params error: TCP/IP error 104 (connection reset by peer), endpoint: 10.238.83.44:7847

Edit the process and view the configured ports

edit params 42P3  42P3 is the port number

The information configured in the discovery process is rmthost 10.238.83.44 mgrport 7839, compress

It is inconsistent with the port reporting an error. Modify the port Edit params 42p3 to prompt port 7847. Then restart the process start 42p3

Solution 2:
after modifying the port or starting the process, it indicates that the previous port is normal (the port of the destination end is the same as that of the source end)

Just delete the line of port and write it again Edit params 42p3 , and restart start 42p3 after writing

Solution 3:
roll forward the source side delivery process to a file and generate a new file point

alter extract 42P3, etrollover

[Solved] harbor Error: because it doesn‘t contain any IP SANs

Bloggers encounter an interesting error when using Harbor:

Error response from daemon: Get https://192.168.2.250:443/v2/: x509:

cannot validate certificate for 192.168.2.250 because it doesn’t contain any IP SANs

Error reporting means: error response from the daemon: G ethttps://192.168.2.250:443/v2/: X509: unable to validate 192.168 2.250 because it does not contain any IP SAN

Blogger Harbor Address 192.168.2.250, using 443 as the secure port.

[reason]:

Docker was unable to validate the certificate for the private repository.

[solution]:

Don’t panic when you encounter a problem. Just hit the king and you’ll know how to solve it. I solved it this way:

1. Edit the docker configuration file (/etc/docker/daemon.JSON)

2. Add “secure registers”: [“192.168.2.250:443”], and specify the address and port of the harbor image warehouse.

3. Restart the docker service and the problem can be solved.

If it still cannot be solved, leave a message in the comment area.

device no response, device descriptor read/64, error -71

Recently, I was porting rtl8723du to rk356x, and I encountered some problems in this process. Today, I recorded the problem as described in the title. This problem was recognized by the kernel when I plugged the WiFi module into the USB host, but the connection was unsuccessful. I checked a lot of data. It seems that I talked about the current signal. Now I record the problem I encountered, hoping to help more people
plug the module into the USB and use the dmesg command to view the cache information:

[  406.785107] usb 5-1: new high-speed USB device number 2 using xhci-hcd
[  406.908835] usb 5-1: device descriptor read/64, error -71
[  407.142008] usb 5-1: device descriptor read/64, error -71
[  407.371775] usb 5-1: new high-speed USB device number 3 using xhci-hcd
[  407.495321] usb 5-1: device descriptor read/64, error -71
[  407.725472] usb 5-1: device descriptor read/64, error -71
[  407.832210] usb usb5-port1: attempt power cycle
[  408.235232] usb 5-1: new high-speed USB device number 4 using xhci-hcd
[  408.235581] usb 5-1: Device not responding to setup address.
[  408.442000] usb 5-1: Device not responding to setup address.
[  408.648596] usb 5-1: device not accepting address 4, error -71
[  408.771923] usb 5-1: new high-speed USB device number 5 using xhci-hcd
[  408.772241] usb 5-1: Device not responding to setup address.
[  408.978858] usb 5-1: Device not responding to setup address.
[  409.185336] usb 5-1: device not accepting address 5, error -71
[  409.185559] usb usb5-port1: unable to enumerate USB device

First of all, I tried many online solutions. The general methods are:

echo Y > /sys/module/usbcore/parameters/old_scheme_first

perhaps

echo -1 > /sys/module/usbcore/parameters/autosuspend

I tried these methods, but they didn’t work in the end. But I directly inserted a hub on the board to transfer it out, and then inserted the module into the hub. At this time, the kernel can normally recognize the rtl8723du module
cache information displayed by dmesg after normal recognition:

[ 1862.348148] usb 5-1: new high-speed USB device number 11 using xhci-hcd
[ 1862.365237] usb 5-1: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.11
[ 1862.365269] usb 5-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 1862.365281] usb 5-1: Product: USB 2.0 Hub
[ 1862.403229] hub 5-1:1.0: USB hub found
[ 1862.403327] hub 5-1:1.0: 4 ports detected
[ 1862.784974] usb 5-1.2: new high-speed USB device number 12 using xhci-hcd
[ 1862.803946] usb 5-1.2: New USB device found, idVendor=0bda, idProduct=d723, bcdDevice= 2.00
[ 1862.804023] usb 5-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1862.804055] usb 5-1.2: Product: 802.11n WLAN Adapter
[ 1862.804084] usb 5-1.2: Manufacturer: Realtek
[ 1862.804109] usb 5-1.2: SerialNumber: 00e04c000001
[ 1862.888575] RTW:
[ 1862.888575] usb_endpoint_descriptor(0):
[ 1862.888660] RTW: bLength=7
[ 1862.888684] RTW: bDescriptorType=5
[ 1862.888705] RTW: bEndpointAddress=84
[ 1862.888725] RTW: wMaxPacketSize=512
[ 1862.888744] RTW: bInterval=0
[ 1862.888764] RTW: RT_usb_endpoint_is_bulk_in = 4
[ 1862.888784] RTW:
[ 1862.888784] usb_endpoint_descriptor(1):
[ 1862.888807] RTW: bLength=7
[ 1862.888825] RTW: bDescriptorType=5
[ 1862.888876] RTW: bEndpointAddress=5
[ 1862.888901] RTW: wMaxPacketSize=512
[ 1862.888935] RTW: bInterval=0
[ 1862.888975] RTW: RT_usb_endpoint_is_bulk_out = 5
[ 1862.889009] RTW:
[ 1862.889009] usb_endpoint_descriptor(2):
[ 1862.889046] RTW: bLength=7
[ 1862.889066] RTW: bDescriptorType=5
[ 1862.889085] RTW: bEndpointAddress=6
[ 1862.889104] RTW: wMaxPacketSize=512
[ 1862.889135] RTW: bInterval=0
[ 1862.889172] RTW: RT_usb_endpoint_is_bulk_out = 6
[ 1862.889205] RTW:
[ 1862.889205] usb_endpoint_descriptor(3):
[ 1862.889241] RTW: bLength=7
[ 1862.889278] RTW: bDescriptorType=5
[ 1862.889311] RTW: bEndpointAddress=87
[ 1862.889344] RTW: wMaxPacketSize=64
[ 1862.889364] RTW: bInterval=3
[ 1862.889383] RTW: RT_usb_endpoint_is_int_in = 7, Interval = 3
[ 1862.889419] RTW:
[ 1862.889419] usb_endpoint_descriptor(4):
[ 1862.889455] RTW: bLength=7
[ 1862.889491] RTW: bDescriptorType=5
[ 1862.889525] RTW: bEndpointAddress=8
[ 1862.889559] RTW: wMaxPacketSize=512
[ 1862.889591] RTW: bInterval=0
[ 1862.889625] RTW: RT_usb_endpoint_is_bulk_out = 8
[ 1862.889646] RTW:
[ 1862.889646] usb_endpoint_descriptor(5):
[ 1862.889670] RTW: bLength=7
[ 1862.889701] RTW: bDescriptorType=5
[ 1862.889737] RTW: bEndpointAddress=9
[ 1862.889772] RTW: wMaxPacketSize=512
[ 1862.889806] RTW: bInterval=0
[ 1862.889839] RTW: RT_usb_endpoint_is_bulk_out = 9
[ 1862.889873] RTW: nr_endpoint=6, in_num=2, out_num=4
[ 1862.889873]
[ 1862.889910] RTW: USB_SPEED_HIGH
[ 1862.889937] RTW: CHIP TYPE: RTL8723DU
[ 1862.890090] RTW: loadparam, Select P2P interface: iface_id:1
[ 1862.890593] RTW: Chip Version Info: CHIP_8723D_T4_1T1R_RomVer(0)
[ 1862.890640] RTW: USB NumInPipe(2), NumOutPipe(4/4)
[ 1862.890809] RTW: EEPROM type is E-FUSE
[ 1862.891165] RTW: Boot from EFUSE, Autoload OK !
[ 1862.891663] RTW: hal_EfuseSwitchToBank: Efuse switch bank to 0
[ 1862.981769] RTW: hal_ReadEFuse_WiFi: data end at address=0x86
[ 1862.982020] RTW: HW EFUSE
......

Failed to read artifact descriptor for xxx:jar Missing

Background

I’ve been looking at HBase recently, introducing

        <dependency>
            <groupId>org.apache.hbase</groupId>
            <artifactId>hbase-client</artifactId>
            <version>2.1.3</version>
        </dependency>

Abnormal

Exception thrown: failed to read artifact descriptor for XXX: jar missing

Solution

Delete the org.apache.hbase related files under the local repository to solve the problem

reference resources

https://blog.csdn.net/weixin_ 42204641/article/details/80768905

openwrt ipv6 nat6 ip6tables [How to Solve]

Install packages
opkg update
opkg install kmod-ipt-nat6
Run ip6tables -t nat -L
Error: ip6tables v1.4.21: can’t initialize ip6tables table `nat’: Table does not exist (do you need to insmod?)
Perhaps ip6tables or your kernel needs to be upgraded.

Solutioin:
The original ipv6 nat6 requires a kernel version of 3.9.0 or higher and an iptables version of 1.4.8 or higher.
Upgrade the corresponding kernel and iptables packages to solve the problem.

Linux environment setup – Update https://apt.repos.intel.com report errors

Problem description and solution

Problem description

After sudo apt get update, the https://apt.repos.intel.com Error message

Hit https://mirrors.tuna.tsinghua.edu.cn focal-security/multiverse Translation-en
Hit https://mirrors.tuna.tsinghua.edu.cn focal-security/restricted Translation-en
Hit https://mirrors.tuna.tsinghua.edu.cn focal-security/universe Translation-en
Err https://apt.repos.intel.com all/main amd64 Packages
  gnutls_handshake() failed: Handshake failed
Err https://apt.repos.intel.com all/main i386 Packages
  gnutls_handshake() failed: Handshake failed
Ign https://apt.repos.intel.com all/main Translation-en_US
Ign https://apt.repos.intel.com all/main Translation-en
Err https://apt.repos.intel.com binary/ Packages
  gnutls_handshake() failed: Handshake failed
Ign https://apt.repos.intel.com binary/ Translation-en_US
Ign https://apt.repos.intel.com binary/ Translation-en
Err https://apt.repos.intel.com all/main amd64 Packages
  gnutls_handshake() failed: Handshake failed
Err https://apt.repos.intel.com all/main i386 Packages
  gnutls_handshake() failed: Handshake failed
Ign https://apt.repos.intel.com all/main Translation-en_US
Ign https://apt.repos.intel.com all/main Translation-en
Err https://apt.repos.intel.com all/main amd64 Packages
  gnutls_handshake() failed: Handshake failed
Err https://apt.repos.intel.com all/main i386 Packages
  gnutls_handshake() failed: Handshake failed
Ign https://apt.repos.intel.com all/main Translation-en_US
Ign https://apt.repos.intel.com all/main Translation-en
Err https://apt.repos.intel.com all/main amd64 Packages
  gnutls_handshake() failed: Handshake failed
Err https://apt.repos.intel.com all/main i386 Packages
  gnutls_handshake() failed: Handshake failed
Ign https://apt.repos.intel.com all/main Translation-en_US
Ign https://apt.repos.intel.com all/main Translation-en
Err https://apt.repos.intel.com all/main amd64 Packages
  gnutls_handshake() failed: Handshake failed
Err https://apt.repos.intel.com all/main i386 Packages
  gnutls_handshake() failed: Handshake failed
Ign https://apt.repos.intel.com all/main Translation-en_US
Ign https://apt.repos.intel.com all/main Translation-en
W: There is no public key available for the following key IDs:
871920D1991BC93C
W: There is no public key available for the following key IDs:
871920D1991BC93C
W: There is no public key available for the following key IDs:
871920D1991BC93C
W: There is no public key available for the following key IDs:
871920D1991BC93C
W: Failed to fetch https://apt.repos.intel.com/mkl/dists/all/main/binary-amd64/Packages  gnutls_handshake() failed: Handshake failed

W: Failed to fetch https://apt.repos.intel.com/mkl/dists/all/main/binary-i386/Packages  gnutls_handshake() failed: Handshake failed

W: Failed to fetch https://apt.repos.intel.com/intelpython/binary/Packages  gnutls_handshake() failed: Handshake failed

W: Failed to fetch https://apt.repos.intel.com/ipp/dists/all/main/binary-amd64/Packages  gnutls_handshake() failed: Handshake failed

W: Failed to fetch https://apt.repos.intel.com/ipp/dists/all/main/binary-i386/Packages  gnutls_handshake() failed: Handshake failed

W: Failed to fetch https://apt.repos.intel.com/tbb/dists/all/main/binary-amd64/Packages  gnutls_handshake() failed: Handshake failed

W: Failed to fetch https://apt.repos.intel.com/tbb/dists/all/main/binary-i386/Packages  gnutls_handshake() failed: Handshake failed

W: Failed to fetch https://apt.repos.intel.com/daal/dists/all/main/binary-amd64/Packages  gnutls_handshake() failed: Handshake failed

W: Failed to fetch https://apt.repos.intel.com/daal/dists/all/main/binary-i386/Packages  gnutls_handshake() failed: Handshake failed

W: Failed to fetch https://apt.repos.intel.com/mpi/dists/all/main/binary-amd64/Packages  gnutls_handshake() failed: Handshake failed

W: Failed to fetch https://apt.repos.intel.com/mpi/dists/all/main/binary-i386/Packages  gnutls_handshake() failed: Handshake failed

E: Some index files failed to download. They have been ignored, or old ones used instead.

Solution

sudo rm intelproducts.list -rf
sudo rm intel-mkl.list intel-mkl.list.save -rf

Aliyunshield occupies port 80 error: Error starting userland proxy: listen tcp 0.0.0.0:80: bind: address already in use

Error starting userland proxy: listen TCP 0.0.0.0:80: bind: address already in use
today, it was found that port 80 was occupied on Ali’s server. The advantages are inexplicable. An investigation found that the process aliyundun occupied the port

tcp          100.100.100.200:80      TIME_WAIT   -                   
tcp          100.100.30.25:80        ESTABLISHED 1472/AliYunDun      
tcp          100.100.100.200:80      TIME_WAIT   -

Displaying with kill is not allowed

[root@lingg ~]# kill 1472
-bash: kill: (1472) - Disallowed operations
[root@lingg ~]# kill -9 1472
-bash: kill: (1472) - Disallowed operations

Then I found the solution online as follows

sudo fuser -k 80/tcp

```bash
[root@lingg ~]# sudo fuser -k 80/tcp
80/tcp:               1267  1272  1273  1274

Done!

server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none

ubuntu
NPM Install errs as follows:
npm ERR! Error while executing:
npm ERR! /usr/bin/git ls-remote -h -t https://test.com/scm/saf/test.git
npm ERR!
NPM ERR! fatal: unable to access ‘https://test.com/scm/saf/test.git/’: server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
npm ERR!
NPM ERR! exited with error code: 128
npm ERR! A complete log of this run can be found in:
npm ERR!/home/test /. NPM/_logs/2020-05-08 T03_03_55_220Z – debug. Log

the reason is that the private certificate is used. After checking the data, the security authentication of the system is shut down.
git config –global http.sslverify “false”
or
export GIT_SSL_NO_VERIFY=1
Reference: https://blog.csdn.net/xunan003/article/details/82190419

ProgrammerAH

Programmer Guide, Tips and Tutorial