Author Archives: Robins

[Solved] Rancher Add User Error: x509: certificate has expired Internal error occurred: failed calling webhook “rancherauth.cattle.io”:

Leave a reply

Error message:

Internal error occurred: failed calling webhook " rancherauth.cattle.io " :
Post https: // rancher-webhook.cattle-system.svc:443/v1/webhook/validation?timeout=10s: x509: certificate has expired or is not yet valid

Check the validity period of the certificate, it has expired 24 days

Solution:
0. Backup the yaml file of the cattle-webhook-tls certificate (the yaml file contains tls.crt and tls.key information)
1. Delete the expired cattle-webhook-tls certificate
2. Restart rancher-webhook pod
3. Check the validity period of the certificate again, it is already 1 year

[Solved] ERROR–Unable to process Jar entry [module-info.class] from Jar

Leave a reply

Unable to process Jar entry [module-info.class] from Jar

Cause Analysis Unable to process jar entry [module-info.class] from Jar package
Scenes Serious red error when starting Idea projectimageimage

Step 1: Go to the Maven repository to find the jar. (I am running the jar reporting an error)
image

Step 2: Right-click the jar and open it with a compression tool, (not unzip it, but open it with WinRar) image

Step 3: Delete the module-info.class folder in the open file (mine has been deleted, you can delete it directly, and then re-run the project.)

1. Generally, this kind of error will not affect the normal operation of the program.

2. The lombok warning in the second picture can be solved by adding the permission <scope>provided</scope> to the location where lombok depends on the import in pom.xml

[Solved] IDEA Error: Unable to resolve column XXXX

Leave a reply

IDEA reported an error Unable to resolve column XXXX solution.

Cause Analysis IDEA cannot fully identify the information of the database
Scenes When Mybatis in IDEA needs to write SQL statements, the compilation process will report a warninginsert image description here

In idea, file>setting–>languages&Frameworks–>SQL Resolution Scopes–>Project mapping select the library table of your own project–>click the plus sign to add your own project address–>Select your own library table as under Resolution Scope ——>Apply——>OK is solved.
image

[Solved] qt5.9 + vs2015 32bit Error: “-1: error: LNK1158: Can not Run “rc.exe”

Leave a reply

The development platform qt5.9.0+vs2015 32bit…. After preparing to run vs2015 and installing vs2019, an error occurred when running the original program that could run

“-1: error: LNK1158: cannot run “rc.exe”

Copied the two files “rc.exe rcdll.dll” in the “C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\x86” directory to “C:\Program Files (x86) \Microsoft Visual Studio 12.0\VC\bin”. 

(Pay attention to the version number, because I am 32-bit so I choose X86, the reason why I choose “Microsoft Visual Studio 12.0” instead of “Microsoft Visual Studio 14.0” is that it should be in my “C:\Program Files (x86)” directory The best is “Microsoft Visual Studio 12.0”). 

Add the path C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\x86 to the system environment variable Path, as shown in the following figure:

 After following the above steps, the problem is solved.

[Solved] docker: Error response from daemon: driver failed programming external connectivity on endpoint mysql-test …

Leave a reply

1. The problem is as follows

[root@echohye app]# docker run -itd --name mysql-test -p 3306:3306 -e MYSQL_ROOT_PASSWORD=123456 mysql:5.7
5ae9dc1c7bf16762e7064a5f3ab0396b1f5ba3a23e64997939730f27aa11eebb
docker: Error response from daemon: driver failed programming external connectivity on endpoint mysql-test (b428e451446b6b6bd1be1ea58ca6f66b632680b0756d6fe9c9411099c03dff5b):  (iptables failed: iptables --wait -t nat -A DOCKER -p tcp -d 0/0 --dport 3306 -j DNAT --to-destination 172.17.0.2:3306 ! -i docker0: iptables: No chain/target/match by that name.

2. Solution

After consulting the information, it is known that it is the cause of the docker0 bridge. To solve the above error problem, the following steps are required.

1. Kill all docker processes

pkill docker

2. Clear all chains of the nat table

iptables -t nat -F

3. Stop docker default bridge docker0

ifconfig docker0 down

4. Delete the docker0 bridge

brctl delbr docker0

5. Restart the docker service

systemctl restart docker

6. Rerun the original command

[root@echohye /]# docker run -itd --name mysql-test -p 3306:3306 -e MYSQL_ROOT_PASSWORD=123456 mysql:5.7
7097016ef0b1c57b6db110dff96b179f8989427c55b1501c36c1c1fb425ba5ce

[root@echohye /]# docker ps
CONTAINER ID   IMAGE       COMMAND                  CREATED         STATUS         PORTS       NAMES
7097016ef0b1   mysql:5.7   "docker-entrypoint.s…"   4 minutes ago   Up 4 minutes   0.0.0.0:3306->3306/tcp, :::3306->3306/tcp, 33060/tcp   mysql-test

[Solved] “errmsg” : “Got invalid BSON from external server while reading from cursor

Leave a reply

db.copyDatabase Error:

"errmsg" : "Got invalid BSON from external server while reading from cursor
:: caused by :: InvalidBSON: Cannot use decimal BSON type when the featureCompatibilityVersion is 3.2.
See http://dochub.mongodb.org/core/3.4-feature-compatibility."

This is because the featureCompatibilityVersion version is not correct
1. Check the current featureCompatibilityVersion version and
execute the command line db.adminCommand({getParameter:1,featureCompatibilityVersion:1})
to return { “featureCompatibilityVersion” : “3.2”, “ok ” : 1 }
2. Modify the featureCompatibilityVersion version
Execute the command line db.adminCommand ({setFeatureCompatibilityVersion: “3.4”})
to return { “featureCompatibilityVersion” : “3.4”, “ok” :1 } , after the modification is successful,
execute db.copyDatabase and it will be ok

[Solved] pycallgraph Install Error: subprocess-exited-with-error

In the win7 system, under the command terminal, the two methods of installing pycallgraph report the exception of subprocess exited with error


Solution: downgrade setuptools

1. First check the current version of setuptools.

pip show setuptools

2. The version of setuptools has been downgraded. Here, I downgraded it to 57.5.0

pip install --upgrade setuptools==57.5.0

3. Try installing pycallgraph again

pip install pycallgraph

[Solved] JAVA Connect rabbitMQ Error: An unexpected connection driver error occured

Rabbitmq cannot be connected in the Java project. The error content is as follows:

ERROR com.rabbitmq.client.impl.ForgivingExceptionHandler.log(ForgivingExceptionHandler.java:119) - An unexpected connection driver error occured

An unexpected connection driver error occurred

Most likely, the newly created user is not authorized

1. You need to confirm that the default port 15672 is the port browsed by the browser after MQ is installed on the server, it needs to be configured as 5672 in the project.

2. Creating a new user requires authorization.
adding a user

Or

After the creation is successful, click the newly created user

User authorization

Then you can connect with the newly created user

The yellow No access will change to /, which indicates that the authorization is successful.

[Solved] Vue Error: Parsing error:No Babel config file detected for xxx

In the Vue project, the following error is reported at the beginning of each file.
Prompt: Parsing error: No Babel config file detected for xxx. Either disable config file checking with requireConfigFile: false, or configure Babel so that it can find the config files.eslint
Solution:
Add “requireConfigFile”: false in “parserOptions” of the package.json file as below:

[Solved] Error running tomcat8: Address localhost:80 is already in use

Error running tomcat8: Address localhost:80 is already in use

1. Problems

Tomcat startup error: Error running tomcat8: Address localhost:80 is already in use

2. Solution

2.1 port 8080 is modified

Modify the server.xml file in E:\software\apache-tomcat-8.5.81\conf back.

npm run dev Error: opensslErrorStack: [ ‘error:03000086:digital envelope routines::initialization error‘ ]

npm run dev Error: opensslErrorStack: [ ‘error:03000086:digital envelope routines::initialization error‘ ]

report errors:

Solution:

Method 1: Replace the scripts part in package.json:

 "scripts": {
    "dev": "SET NODE_OPTIONS=--openssl-legacy-provider && vue-cli-service serve",
    "serve": "SET NODE_OPTIONS=--openssl-legacy-provider && vue-cli-service serve",
    "lint": "eslint --ext .js,.vue src",
    "build:prod": "SET NODE_OPTIONS=--openssl-legacy-provider && vue-cli-service build",
    "build:stage": "vue-cli-service build --mode staging",
    "preview": "node build/index.js --preview",
    "new": "plop",
    "svgo": "svgo -f src/icons/svg --config=src/icons/svgo.yml",
    "test:unit": "jest --clearCache && vue-cli-service test:unit",
    "test:ci": "npm run lint && npm run test:unit"
  }

Method 2: reduce the node version

[Solved] “npm WARN logfile could not be created: Error: EPERM: operation not permitted,…”

Error: “npm WARN logfile could not be created: Error: EPERM: operation not permitted,…”

npm WARN logfile could not be created: Error: EPERM: operation not permitted, open 'D:\nodejs\node_cache\_logs\2022-08-09T03_07_24_221Z-debug-0.log'
npm WARN logfile could not be created: Error: EPERM: operation not permitted, open 'D:\nodejs\node_cache\_logs\2022-08-09T03_07_24_798Z-debug-0.log'
npm ERR! code EPERM
npm ERR! syscall open
npm ERR! path D:\nodejs\node_cache\_cacache\tmp\299683ad
npm ERR! errno -4048
npm ERR! Error: EPERM: operation not permitted, open 'D:\nodejs\node_cache\_cacache\tmp\299683ad'
npm ERR!  [Error: EPERM: operation not permitted, open 'D:\nodejs\node_cache\_cacache\tmp\299683ad'] {
npm ERR!   errno: -4048,
npm ERR!   code: 'EPERM',
npm ERR!   syscall: 'open',
npm ERR!   path: 'D:\\nodejs\\node_cache\\_cacache\\tmp\\299683ad'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It's possible that the file was already in use (by a text editor or antivirus),
npm ERR! or that you lack permissions to access it.
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.

npm ERR! Log files were not written due to an error writing to the directory: D:\nodejs\node_cache\_logs
npm ERR! You can rerun the command with `--loglevel=verbose` to see the logs in your terminal

Solution:

  2. window + r –> cmd –> where node –> find the path where nodejs is located
  3. nodejs file –> right click –> properties

3. Security -> Select Users -> Edit -> Check Full Control -> Click Confirm

    why is this problem reported? Because I don’t have permission