Category Archives: Error

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

[Solved] zabbix Error: Cannot perform request: error:141A318A:SSL routines:tls_process_ske_dhe:dh key too small

zabbix 6.0 (Ubuntu 20.04) reports an error when using https to monitor the server hardware (redfish protocol), Cannot perform request: error:141A318A:SSL routines:tls_process_ske_dhe:dh key too small.

I am using curl to test and also report the error

curl: (35) error:141A318A:SSL routines:tls_process_ske_dhe:dh key too small

After checking the resource online, it is because openssl disables the low security encryption method. Just change the openssl parameters, restart the zabbix related services or reboot the system after the change.

Solution:

Edit the OpenSSL.conf file:

sudo nano /etc/ssl/openssl.cnf

Add this line at the top:

openssl_conf = openssl_init

And add these lines at the end:

[openssl_init]
ssl_conf = ssl_sect

[ssl_sect]
system_default = system_default_sect

[system_default_sect]
CipherString = DEFAULT@SECLEVEL=1

Restart the server, it will be OK!

[Solved] runtime error: reference binding to null pointer of type ‘std::vector＜int, std::allocator＜int＞＞‘

How to Solve Error: runtime error: reference binding to null pointer of type ‘std::vector＜int, std::allocator＜int＞＞‘

For vector<vector >
When initializing it, you have to open up the appropriate storage space for it!

Solution:
when initializing, open up the required storage space:

//Suppose the size of the two-dimensional array space is m x n
vector<vector<int> > count(m);
for(int i=0;i<m;i++)
	count[i].resize(n);

MindSpore Error: [ERROR] MD:unexpected error.Not a valid index

ERROR:[MD]:unexpected error. Not a valid index


problem phenomenon: a single card does not report an error, and the training process can be correctly executed. However, when switching to distributed training, an error in the diagram is reported. After troubleshooting, the cause of the error is found to be the wrong use of distributed sampling
the error reporting method is as follows:

the order of distributed sampling and random sampling needs to be changed. The correct way is to perform random sampling first and then distributed sampling

The correct modification is as follows:

distributed training can be performed correctly after modification

[Solved] pyinstaller: error: unrecognized arguments: sklearn

How to Solve Error: pyinstaller: error: unrecognized arguments: sklearn

 

Solution:

Go to cmd
pyinstaller main.py  –hidden-import PySide2.QtXml –hidden-import sklearn –hidden-import sklearn.ensemble._forest –icon=”logo.ico”
Add the unrecognized sklearn to hidden import –hidden-import sklearn
The issue will be fixed.

 

Error: env [NODE_ENV] is not set (How to Solve)

Error: env [NODE_ENV] is not set

Encountered problem: running project reports error: env [node_env] is not set

Screenshot of the problem:

Solution idea, env in NODE_ENV is not set, resulting in process failure, so you can set the value of this NODE_ENV can be solved. Because it is someone else’s project, I took it over directly, so I searched NODE_ENV globally and found that NODE_ENV=development, so just set NODE_ENV to development.

Implementation method:

1. For Linux:

NODE_ENV=development node foo.js

2. For Windows

SET NODE_ENV=development
node foo.js

Write node foo according to the actual needs of the project JS, some projects can not be written

tips：

It is possible that in addition to the property NODE_ENV is not set, there are other values that are not set, for the same reason, you can set the corresponding value for this value

[Solved] Oracle 18C RAC Install Error: Error in invoking target ‘irman ioracle idrdactl idrdalsnr idrdaproc‘ of makefile

When installing 18C RAC, the GI installation is completed, and an error occurs when installing RDBMS:

Error in invoking target ‘irman ioracle idrdactl idrdalsnr idrdaproc’ of makefile ‘/u01/app/oracle/product/18.0.0.0/dbhome_1/rdbms/lib/ins_rdbms.mk’.

View the installation log:

18 -lctx18 -lzx18 -lgx18 -lctx18 -lzx18 -lgx18 -lordimt -lclscest18 -loevm -lclsra18 -ldbcfg18 -lhasgen18 -lskgxn2 -lnnzst18 -lzt18 -lxml18 -lgeneric18 -locr18 -locrb18 -locrutl18 -lhasgen18 -lskgxn2 -lnnzst18 -lzt18 -lxml18 -lgeneric18  -lgeneric18 -lorazip -loraz -llzopro5 -lorabz2 -lipp_z -lipp_bz2 -lippdcemerged -lippsemerged -lippdcmerged  -lippsmerged -lippcore  -lippcpemerged -lippcpmerged  -lsnls18 -lnls18  -lcore18 -lsnls18 -lnls18 -lcore18 -lsnls18 -lnls18 -lxml18 -lcore18 -lunls18 -lsnls18 -lnls1
INFO: 
8 -lcore18 -lnls18 -lsnls18 -lunls18  -lsnls18 -lnls18  -lcore18 -lsnls18 -lnls18 -lcore18 -lsnls18 -lnls18 -lxml18 -lcore18 -lunls18 -lsnls18 -lnls18 -lcore18 -lnls18 -lasmclnt18 -lcommon18 -lcore18  -ledtn18 -laio -lons  -lfthread18   `cat /u01/app/oracle/product/18.0.0.0/dbhome_1/lib/sysliblist` -Wl,-rpath,/u01/app/oracle/product/18.0.0.0/dbhome_1/lib -lm    `cat /u01/app/oracle/product/18.0.0.0/dbhome_1/lib/sysliblist` -ldl -lm   -L/u01/app/oracle/product/18.0.0.0/dbhome_1/lib `test -x /usr/bin/hugeedit
INFO: 
 -a -r /usr/lib64/libhugetlbfs.so && test -r /u01/app/oracle/product/18.0.0.0/dbhome_1/rdbms/lib/shugetlbfs.o && echo -Wl,-zcommon-page-size=2097152 -Wl,-zmax-page-size=2097152 -lhugetlbfs`


报错原因：
↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓
***INFO: 
/usr/bin/ld:/u01/app/oracle/product/18.0.0.0/dbhome_1/lib//libodm18.so: file format not recognized; treating as linker script
/usr/bin/ld:/u01/app/oracle/product/18.0.0.0/dbhome_1/lib//libodm18.so:1: syntax error***

INFO: 
make: *** [/u01/app/oracle/product/18.0.0.0/dbhome_1/rdbms/lib/oracle] Error 1

INFO: End output from spawned process.
INFO: ----------------------------------
INFO: Exception thrown from action: make
Exception Name: MakefileException
Exception String: Error in invoking target 'irman ioracle idrdactl idrdalsnr idrdaproc' of makefile '/u01/app/oracle/product/18.0.0.0/dbhome_1/rdbms/lib/ins_rdbms.mk'. See '/u01/app/oraInventory/logs/InstallActions2022-08-11_03-59-03PM/installActions2022-08-11_03-59-03PM.log' for details.
Exception Severity: 1

From the log file, we know that it is due to a problem with the /u01/app/oracle/product/18.0.0.0/dbhome_1/lib//libodm18.so file, which is usually caused by a problem with the installation package.
According to the file format not recognized; treating as linker script keyword, there are also related articles on mos.
19c Installation Fails with error “libclntsh.so: file format not recognized; treating as linker script” (Doc ID 2631283.1)

Grid Infrastructure Installation Fail in 12.2.0.1 For Standalone And RAC with libodm12.so: file format not recognized; treating as linker script (Doc ID 2373904.1)

Solution:
Redownload the installation media (to be sure, do MD5 verification of the installation media before installation)