Author Archives: Robins

Nginx Failed to Starup Error: [emerg] mkdir() “/var/tmp/nginx/client” failed (2: No such file or directory)

Nginx Failed to startup Error: [emerg] mkdir() “/var/tmp/nginx/client” failed (2: No such file or directory)

Commands:
mkdir -pv /var/tmp/nginx/client
Type nginx -t again to display: the configuration file /etc/nginx/nginx.conf syntax is ok
After starting Nginx, you can now. service nginx start

Execute the Jmeter Script Error: .org.apache.http.conn.httphostconnectexception: XXXX failed: unable to specify the solution of the requested address (Connect failed)

Problem Description: While executing a single transaction load script, I found that running the script locally, the exception rate was 0%, and when the same script was executed on the hair press, there were large error reports.

Reason: Linux allocate to the client connection port exhausted, can not establish a socket connection caused by, although the socket closed, but the port default wait for 60s to be released, so as long as we give more available ports will be fine.

Solution steps.

1. Check the range of client connection ports supported by Linux: cat /proc/sys/net/ipv4/ip_local_port_range

2. Tune down the waiting time after port release, the default is 60s, modify it to 15~30s: echo 30 > /proc/sys/net/ipv4/tcp_fin_timeout

3. Modify the tcp/ip protocol configuration by configuring /proc/sys/net/ipv4/tcp_tw_reuse, the default is 0, modify it to 1 to release the TIME_WAIT port for new connections: echo 1 > /proc/sys/net/ipv4/tcp_tw_resue

4. Modify the tcp/ip protocol configuration to quickly recycle socket resources, the default is 0, modify it to 1: echo 1 > /proc/sys/net/ipv4/tcp_tw_recycle

After the modification, execute the single transaction load script on the issuing press again, and the exception rate is normal.

[Solved] for user ‘root’ using method ‘mysql_native_password’ failed with message: Reading from the stream has failed

Add to the connection string:SslMode=None;

Example:

[Solved] frp Error: login to server failed: EOF

Error:

frp Error: login to server failed: EOF

Solution:

Add tls_enable = true in the common of Client

[common]
tls_enable = true

Uncaught InvalidStateError: Failed to execute ‘stop’ on ‘MediaRecorder’: The MediaRecorder’s state is ‘inactive’

      
The state is already inactive, add a state determination
　　　　　　　　　　　　  console.log(mediaRecorder.state);
                        if(mediaRecorder.state!="inactive"){
                            mediaRecorder.stop();
                        }

[Solved] Archlinux Upgrade Error: failed to update core (unable to lock database)

Unable to upgrade database

This is because the Pacman database was locked due to previous operation exceptions, so you can unlock it manually.

The command is as follows:

rm -f /var/lib/pacman/db.lck

Re-execute pacman -Syu

import torchvision Error: UserWarning: Failed to load image Python extension: Could not find module

My version of torch and torchvision do not correspond, this chart is the current version of torch, torchvision, python adaptation, according to the version of this chart to start a new torch and torchvision

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.