Category Archives: Error

Could not transfer artifact org.glassfish:javax.el:pom:3.0.1-b06-SNAPSHOT from/to jvnet-nexus-snapshots (https://maven.java.net/content/repositories/snapshots)

Error Messages:

[ERROR] Failed to execute goal on project cds-think-tanks-impl: Could not resolve 
dependencies for project com.orangecds:cds-think-tanks-impl:jar:0.0.1-SNAPSHOT: 
Failed to collect dependencies at org.apache.phoenix:phoenix-core:jar:5.0.0-HBase-2.0 
-> org.apache.hbase:hbase-mapreduce:jar:2.0.0 -> org.apache.hbase:hbase-server:jar:2.0.0
 -> org.glassfish.web:javax.servlet.jsp:jar:2.3.2 -> org.glassfish:javax.el:jar
:3.0.1-b06-SNAPSHOT: Failed to read artifact descriptor for org.glassfish:javax.el:jar
:3.0.1-b06-SNAPSHOT: Could not transfer artifact org.glassfish:javax.el:pom:3.0.1-b06-SNAPSHOT 
from/to jvnet-nexus-snapshots (https://maven.java.net/content/repositories/snapshots): 
maven.java.net: Unknown host maven.java.net -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException

Solution:

1. Re-compile

2. pom:

< dependency>
< groupId> org. Apache. hive
< artifactId> hive-jdbc
< exclusions>
< exclusion>
< groupId> org. glassfish
< artifactId> javax. el

< exclusion>
< groupId> org. eclipse. jetty
< artifactId> jetty-runner

< version> 3.1.2

Note:

exclusions is a sub-tag of dependence. To exclude jars

-maven import packages, jar packages import the necessary jar packages as well. For example, importing the springmvc package.

springcore and springbean and other packages will also come in together. If you take the initiative to add other versions of springcore package. There may be a jar conflict problem

[Solved] CentOS yum Install Error: BDB1507 Thread died in Berkeley DB library

1. Error message during Yum installation

#yum install net-tools
error: rpmdb: BDB0113 Thread/process 31403/139827795044416 failed: BDB1507 Thread died in Berkeley DB library
error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Packages index using db5 -  (-30973)
error: cannot open Packages database in /var/lib/rpm
CRITICAL:yum.main:

Error: rpmdb open failed

2. Solution

2.1 view the/var/lib/RPM directory

2.2 Delete the rpmdb files starting with __db in the /var/lib/rpm directory

rm -f /var/lib/rpm/__db*

2.3 RPM Database Reconstruction

rpm --rebuilddb

2.4 clean up all Yum caches

yum clean all

2.5 regenerate Yum cache

yum makecache

Git Error: Unable to create ‘D:/xxx/.git/index.lock’: File exists. Another git process seems to be running in this repository, e.g.an editor opened by ‘git commit’. Please make sure all p

Unable to create ‘D:/xxx/. git/index. lock’: File exists.
Another git process seems to be running in this repository, e.g.an editor opened by ‘git commit’.
Please make sure all processes are terminated then try again. If it still fails, a git process may have crashed in this repository earlier:
remove the file manually to continue.
Pull operation failed.

 

Cause analysis:

The index.lock file under .git is automatically generated when some time-consuming git operations are performed, and is automatically deleted when the operation is finished. Sometimes when you force a git operation in progress to close, the file is not automatically deleted, so you can’t do other git operations afterwards and must delete it manually.

 

Solution:

Method 1: find git/index.lock file and delete it directly
If Linux, execute the RM delete command: rm -f .git/index.lock

Method 2: execute git command: git clean -f .git/index.lock

React Native Project Run Error [How to Solve]

React native version: 0.67

Initialize and run the project according to the official document

$ npx react-native init AwesomeProject
$ yarn ios

The error message is as follows

The following build commands failed: 
	PhaseScriptExecution [CP-User]\ Generate\ Specs /Users/zh/Library/Developer/Xcode/DerivedData/AwesomeProject-cvxgkvyxvvajjvaydcivldmzlgxr/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/FBReactNativeSpec.build/Script-5F4C70EF7D90A5A5BDAEB404279F232A.sh (in target 'FBReactNativeSpec' from project 'Pods') (1 failure)

Possible causes

  1. The project path contains white space characters
  2. NVM is used for node installation

I’m because of reason 2. The solution is to go to node_modules/react-native/scripts/find-node. SH, comment out this part of the file

if [[ -s "$HOME/.nvm/nvm.sh" ]]; then
   # shellcheck source=/dev/null
   . "$HOME/.nvm/nvm.sh"
 elif [[ -x "$(command -v brew)" && -s "$(brew --prefix nvm)/nvm.sh" ]]; then
   # shellcheck source=/dev/null
   . "$(brew --prefix nvm)/nvm.sh"
 fi

Then execute yarn IOS , and the execution will be successful

[Solved] Homebrew curl: (60) SSL certificate problem: certificate has expired

1. Problem description

Homebrew has a problem installing GIT

curl: (60) SSL certificate problem: certificate has expired More details here: https://curl.haxx.se/docs/sslcerts.html
If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. 
HTTPS-proxy has similar options --proxy-cacert and --proxy-insecure.
Error: Failed to download resource "pcre2"

Probably because homebrew has not been updated for a long time, the local certificate has expired.

2. Solution

echo insecure >> ~/.curlrc
HOMEBREW_CURLRC=1
export HOMEBREW_CURLRC
#brew install git

 

WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! [How to Fix]

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
SHA256:36vsuYywBZkJ0W04SmMFKgSPvJk/FoUTCOkIytwSS1I.
Please contact your system administrator.
Add correct host key in /c/Users/86131/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /c/Users/86131/.ssh/known_hosts:21
ECDSA host key for 106.52.223.232 has changed and you have requested strict checking.
Host key verification failed.

If you encounter this problem, you only need to execute

vi ~/.ssh/known_hosts

Then delete the connection IP information. For example, if I connect to 106.52.223.232, I will delete the IP information

[Solved] oracle Execute netca Error: UnsatisfiedLinkError exception loading native library: njni11

@Write at the beginning: after testing, this kind of problem occurs when centos8 installs Oracle 11g R2

@There will also be no response after lsnrctl start. After checking the lsnrctl file, it is found that the file is also 0kb

@It may be a compatibility problem. It is recommended to install Oracle help center with the system recommended by Oracle

1. Execute netca/silent/responsefile/data/Oracle/response/netca RSP error unsatisfiedlinkerror exception loading native library: njni11

[oracle@oracle ~]$ netca /silent /responsefile /datas/oracle/response/netca.rsp
UnsatisfiedLinkError exception loading native library: njni11
java.lang.UnsatisfiedLinkError: /datas/oracle/product/11.2.0/db_1/lib/libnjni11.so: /datas/oracle/product/11.2.0/db_1/lib/libclntsh.so.11.1: file too short
java.lang.UnsatisfiedLinkError: jniGetOracleHome
	at oracle.net.common.NetGetEnv.jniGetOracleHome(Native Method)
	at oracle.net.common.NetGetEnv.getOracleHome(Unknown Source)
	at oracle.net.ca.NetCALogger.getOracleHome(NetCALogger.java:230)
	at oracle.net.ca.NetCALogger.initOracleParameters(NetCALogger.java:215)
	at oracle.net.ca.NetCALogger.initLogger(NetCALogger.java:130)
	at oracle.net.ca.NetCA.main(NetCA.java:404)

Error: jniGetOracleHome
Oracle Net Services configuration failed.  The exit code is 1

2. View/data/Oracle/product/11.2.0/db_1/lib/libclntsh.so.11.1 documents found 0kb

3. Find libclntsh.so.11.1 fileĀ In the system (the installation information directory orainventory happens to exist)

find/-name libclntsh.so.11.1

4. Cover the damaged libclntsh.so.11.1 documents

cp /datas/oracle/product/11.2.0/db_1/inventory/backup/2021-04-27_02-37-24PM/Scripts/ext/lib/libclntsh.so.11.1 /datas/oracle/product/11.2.0/db_1/lib/libclntsh.so.11.1

5. Execute the netca command again and solve the problem successfully

[Solved] No qualifying bean of type ‘org.springframework.boot.orm.jpa.EntityManagerFactoryBuilder’ available:

DEBUG o.s.b.diagnostics.LoggingFailureAnalysisReporter – Application failed to start due to an exception

org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'org.springframework.boot.orm.jpa.EntityManagerFactoryBuilder' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {}
        at org.springframework.beans.factory.support.DefaultListableBeanFactory.raiseNoMatchingBeanFound(DefaultListableBeanFactory.java:1493)
        at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1104)
        at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1066)
        at org.springframework.beans.factory.support.ConstructorResolver.resolveAutowiredArgument(ConstructorResolver.java:835)
        at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:741)
        at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:467)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1173)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1067)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:513)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:483)
        at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
        at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
        at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
        at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1080)
        at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:857)
        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:543)
        at org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.refresh(EmbeddedWebApplicationContext.java:122)
        at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:693)
        at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:360)
        at org.springframework.boot.SpringApplication.run(SpringApplication.java:303)
        at org.springframework.boot.SpringApplication.run(SpringApplication.java:1118)
        at org.springframework.boot.SpringApplication.run(SpringApplication.java:1107)

Solution:

Add the following jar pack”

		<dependency>
   			<groupId>org.springframework.boot</groupId>
   			<artifactId>spring-boot-starter-data-jpa</artifactId>
   			<version>${springboot.version}</version>
		</dependency>

Version can be the springboot version of your own project. The problem is solved!

How to Solve DbVisualizer Error: Could not read XML file

Database connection tool is a daily tool for our software test engineers. Once we report some inexplicable errors at the critical moment, I believe we are very distressed
of course, companies have different database connection tools, such as dbvisualizer, PLSQL, sqldeveloper, toad for SQL Server/MySQL and so on
now I’d like to introduce an annoying and inexplicable error reporting and solution of my dbvisualizer.

The following error occurred while opening dbvisualizer:

Error message: Could not read XML file: C:\Users\lxw\.dbvis\config70\dbvis.xml Error is: Error on line 1: no content is allowed in the preface

Solution:

1. Follow the above path to find dbvis.xml

2. After opening, you will find two files:
First File: dbvis.xml
Second File: dbvis.xml.bak

3. Back up dbvis.xml.bak file and rename dbvis.xml.bak to dbvis.xml is OK