Category Archives: Error

NVM use error: exit status [How to Solve]

Solution:

1. First, the installation directory should be free of spaces and Chinese

2. Check whether the administrator permission is turned on and check the steps

3. Change environment variables

NVM_HOME should be the installation directory of nvm, such as C:\development\nvm
NVM_SYMLINK should be the directory of nodejs, as follows

should be C:\development\NVM\v16.13.0
note that both user variables and system variables need to be changed, and then OK OK
4. Close the terminal, reopen it, and then use NVM use.

[Solved] Docker failed to start daemon: error initializing graphdriver: driver not supported

When the kubelet node joins, an error VFS not support is reported

[ERROR SystemVerification]: unsupported graph driver: vfs

/etc/docker/daemon.json

{
        "registry-mirrors":["https://registry.docker-cn.com"],
        "bridge":"nufront-br",
        "storage-driver":"devicemapper",   ####
        "exec-opts": ["native.cgroupdriver=systemd"],
        "insecure-registries": ["hadoop03:5000"]
}

###
systemctl daemon-reload
service docker start #Note error initializing graphdriver: driver not supported

reference resources: https://github.com/moby/moby/issues/15651, it is found that the current node downloads the docker CE decompression package and directly configures the service, not through Yum (offline environment…)

#### 

[root@nufront-worker-02 bin]# cd /opt/module/docker/
[root@nufront-worker-02 docker]# ll

-rwxr-xr-x 1 root root 39593864 Nov 23 11:12 containerd
-rwxr-xr-x 1 root root 21508168 Nov 23 11:12 ctr
-rwxr-xr-x 1 root root 60073904 Nov 23 11:12 docker
-rwxr-xr-x 1 root root 78951368 Nov 23 11:12 dockerd
-rwxr-xr-x 1 root root   708616 Nov 23 11:12 docker-init
-rwxr-xr-x 1 root root  2933646 Nov 23 11:12 docker-proxy


Try RPM installation

#######
[root@nufront-worker-02 docker]# ll
total 350072
-rw-r--r-- 1 root root   104408 Nov 23 11:12 audit-libs-2.8.5-4.el7.x86_64.rpm
-rw-r--r-- 1 root root    78256 Nov 23 11:12 audit-libs-python-2.8.5-4.el7.x86_64.rpm
-rwxr-xr-x 1 root root 39593864 Nov 23 11:12 containerd
-rw-r--r-- 1 root root 35130608 Nov 23 11:12 containerd.io-1.4.6-3.1.el7.x86_64.rpm
-rwxr-xr-x 1 root root  7270400 Nov 23 11:12 containerd-shim
-rwxr-xr-x 1 root root  9953280 Nov 23 11:12 containerd-shim-runc-v2
-rw-r--r-- 1 root root    40816 Nov 23 11:12 container-selinux-2.119.2-1.911c772.el7_8.noarch.rpm
-rwxr-xr-x 1 root root 21508168 Nov 23 11:12 ctr
-rwxr-xr-x 1 root root 60073904 Nov 23 11:12 docker
-rw-r--r-- 1 root root 27902344 Nov 23 11:12 docker-ce-20.10.7-3.el7.x86_64 (1).rpm
-rw-r--r-- 1 root root 34717572 Nov 23 11:12 docker-ce-cli-20.10.7-3.el7.x86_64.rpm
-rw-r--r-- 1 root root  9659320 Nov 23 11:12 docker-ce-rootless-extras-20.10.7-3.el7.x86_64.rpm
-rwxr-xr-x 1 root root 78951368 Nov 23 11:12 dockerd
-rwxr-xr-x 1 root root   708616 Nov 23 11:12 docker-init
-rwxr-xr-x 1 root root  2933646 Nov 23 11:12 docker-proxy
-rw-r--r-- 1 root root  4373740 Nov 23 11:12 docker-scan-plugin-0.8.0-3.el7.x86_64.rpm
-rwxr-xr-x 1 root root     1200 Nov 23 11:12 docker.service
-rw-r--r-- 1 root root    83764 Nov 23 11:12 fuse3-libs-3.6.1-4.el7.x86_64.rpm
-rw-r--r-- 1 root root    95424 Nov 23 11:12 fuse-libs-2.9.2-11.el7.x86_64.rpm
-rw-r--r-- 1 root root    55796 Nov 23 11:12 fuse-overlayfs-0.7.2-6.el7_8.x86_64.rpm
-rw-r--r-- 1 root root    67720 Nov 23 11:12 libcgroup-0.41-21.el7.x86_64.rpm
-rw-r--r-- 1 root root   101800 Nov 23 11:12 libcgroup-tools-0.41-21.el7.x86_64.rpm
-rw-r--r-- 1 root root    56824 Nov 23 11:12 libnetfilter_conntrack-1.0.6-1.el7_3.x86_64.rpm
-rw-r--r-- 1 root root    57460 Nov 23 11:12 libseccomp-2.3.1-4.el7.x86_64.rpm
-rw-r--r-- 1 root root   166012 Nov 23 11:12 libselinux-2.5-15.el7.x86_64.rpm
-rw-r--r-- 1 root root   154876 Nov 23 11:12 libselinux-utils-2.5-15.el7.x86_64.rpm
-rw-r--r-- 1 root root   154244 Nov 23 11:12 libsemanage-2.5-14.el7.x86_64.rpm
-rw-r--r-- 1 root root   115284 Nov 23 11:12 libsemanage-python-2.5-14.el7.x86_64.rpm
-rw-r--r-- 1 root root   304196 Nov 23 11:12 libsepol-2.5-10.el7.x86_64.rpm
-rw-r--r-- 1 root root    78740 Nov 23 11:12 libsepol-devel-2.5-10.el7.x86_64 (1).rpm
-rw-r--r-- 1 root root    78740 Nov 23 11:12 libsepol-devel-2.5-10.el7.x86_64.rpm
-rw-r--r-- 1 root root   938736 Nov 23 11:12 policycoreutils-2.5-34.el7.x86_64.rpm
-rw-r--r-- 1 root root   468316 Nov 23 11:12 policycoreutils-python-2.5-34.el7.x86_64.rpm
-rwxr-xr-x 1 root root 14485560 Nov 23 11:12 runc
-rw-r--r-- 1 root root   509568 Nov 23 11:12 selinux-policy-3.13.1-268.el7_9.2.noarch.rpm
-rw-r--r-- 1 root root  7335504 Nov 23 11:12 selinux-policy-targeted-3.13.1-268.el7_9.2.noarch.rpm
-rw-r--r-- 1 root root    83452 Nov 23 11:12 slirp4netns-0.4.3-4.el7_8.x86_64.rpm

[root@nufront-worker-02 docker]# rpm -ivh *.rpm  --nodeps --force 


[root@nufront-worker-02 docker]# yum list installed | grep docker
docker-ce.x86_64                        3:20.10.7-3.el7                installed
docker-ce-cli.x86_64                    1:20.10.7-3.el7                installed
docker-ce-rootless-extras.x86_64        20.10.7-3.el7                  installed
docker-scan-plugin.x86_64               0.8.0-3.el7                    installed

Docker can be started again…

[root@nufront-worker-02 docker]# docker info
Client:
 Context:    default
 Debug Mode: false
 Plugins:
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Build with BuildKit (Docker Inc., v0.5.1-docker)
  scan: Docker Scan (Docker Inc., v0.8.0)

Server:
 Containers: 0
  Running: 0
  Paused: 0
  Stopped: 0
 Images: 0
 Server Version: 20.10.7
 Storage Driver: devicemapper ###
  Pool Name: docker-253:0-812466384-pool
  Pool Blocksize: 65.54kB
  Base Device Size: 10.74GB
  Backing Filesystem: xfs
  Udev Sync Supported: true
  Data file: /dev/loop0
  Metadata file: /dev/loop1
  Data loop file: /var/lib/docker/devicemapper/devicemapper/data
  Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
  Data Space Used: 11.8MB
  Data Space Total: 107.4GB
  Data Space Available: 107.4GB
  Metadata Space Used: 581.6kB
  Metadata Space Total: 2.147GB
  Metadata Space Available: 2.147GB
  Thin Pool Minimum Free Space: 10.74GB
  Deferred Removal Enabled: true
  Deferred Deletion Enabled: true
  Deferred Deleted Device Count: 0
  Library Version: 1.02.107-RHEL7 (2015-10-14)
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 1
 Plugins:
...

[Solved] curl error while loading shared libraries libcrypto.so.1.0.0

Curl: error while loading shared libraries: libcrypto.So.1.0.0 solution

1 problem description

When executing curl command, the following error message is reported:

curl: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory

Error message:

Find various schemes on the Internet, mainly as follows:

1. Reinstall curl 2. Update libcrypto

All the methods have been tried, but they have not been solved.

Finally, the solution is as follows: in curl command, establish target soft link.

The specific scheme is as follows:

2 solution

Basic idea.
Looking in the development machine, inside libcrypto.so.1.0.0 is already installed. According to the error report, this is because the curl command cannot find the dependency libcrypto.so.1.0.0
1. check the dependencies of curl command.
2. Find the missing shared library on the machine
3. Create a soft connection

2.1 using the LDD command to view dependencies

The LDD command is used to view the shared library required for the command to run. It is often used to solve some problems that the command cannot run due to the lack of a library file.

# View the absolute path of the command
which curl
# ~/anaconda3/bin/curl

Find the corresponding dependency:

ldd ~/anaconda3/bin/curl
	linux-vdso.so.1 =>  (0x00007fff666dd000)
	libcurl.so.4 => /home/work/anaconda3/bin/../lib/libcurl.so.4 (0x00007fd47e181000)
	librt.so.1 => /lib64/librt.so.1 (0x00007fd47dde2000)
	libz.so.1 => /home/work/anaconda3/bin/../lib/libz.so.1 (0x00007fd47dbcb000)
	libc.so.6 => /lib64/libc.so.6 (0x00007fd47d80a000)
	libssh2.so.1 => /home/work/anaconda3/bin/../lib/./libssh2.so.1 (0x00007fd47d5db000)
	libssl.so.1.1 => /home/work/anaconda3/bin/../lib/./libssl.so.1.1 (0x00007fd47e0da000)
	libcrypto.so.1.1 => /home/work/anaconda3/bin/../lib/./libcrypto.so.1.1 (0x00007fd47d32d000)
	libgssapi_krb5.so.2 => /home/work/anaconda3/bin/../lib/./libgssapi_krb5.so.2 (0x00007fd47e08a000)
	libkrb5.so.3 => /home/work/anaconda3/bin/../lib/./libkrb5.so.3 (0x00007fd47d251000)
	libk5crypto.so.3 => /home/work/anaconda3/bin/../lib/./libk5crypto.so.3 (0x00007fd47e06b000)
	libcom_err.so.3 => /home/work/anaconda3/bin/../lib/./libcom_err.so.3 (0x00007fd47e064000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fd47d035000)
	/lib64/ld-linux-x86-64.so.2 (0x00007fd47dfea000)
	# See here that the message does not depend on
	libcrypto.so.1.0.0 (0x00007fd47cbf5000)
	libdl.so.2 => /lib64/libdl.so.2 (0x00007fd47c9f1000)
	libkrb5support.so.0 => /home/work/anaconda3/bin/../lib/././libkrb5support.so.0 (0x00007fd47e053000)
	libresolv.so.2 => /lib64/libresolv.so.2 (0x00007fd47c7d7000)

Then establish dependencies and soft links

2.2 find the missing shared library on the machine

Many shared libraries and other software may be installed automatically during installation, so you can directly find the shared libraries installed by other software and use them

# Find the missing shared library information
find ~ -name libcrypto.so.1.0.0

# The returned results are as follows.
# /home/work/anaconda3/libcrypto.so.1.0.0

2.3 establishing soft connection

Soft connect the found shared library to the Lib directory of the software installation:

# View the software installation path
which curl
# The result is as follows, the software was installed using anaconda
# ~/anaconda3/bin/curl

# Create a soft connection
ln -s /home/work/anaconda3/libcrypto.so.1.0.0 ~/anaconda3/bin/../lib/libcrypto.so.1.0.0

Note: the /home/work/anaconda3/libcrypto. So. 1.0.0 directory is the information found through Find ~ - name libcrypto. So. 1.0.0 .

The ~/anaconda3/bin /../lib/ directory is actually the bin directory under the curl directory.


Check whether the soft link is established successfully

ldd ~/anaconda3/bin/curl
	linux-vdso.so.1 =>  (0x00007fffa19e9000)
	libcurl.so.4 => /home/work/anaconda3/bin/../lib/libcurl.so.4 (0x00007fa7c5d37000)
	librt.so.1 => /lib64/librt.so.1 (0x00007fa7c5998000)
	libz.so.1 => /home/work/anaconda3/bin/../lib/libz.so.1 (0x00007fa7c5781000)
	libc.so.6 => /lib64/libc.so.6 (0x00007fa7c53c0000)
	libssh2.so.1 => /home/work/anaconda3/bin/../lib/./libssh2.so.1 (0x00007fa7c5191000)
	libssl.so.1.1 => /home/work/anaconda3/bin/../lib/./libssl.so.1.1 (0x00007fa7c5c90000)
	libcrypto.so.1.1 => /home/work/anaconda3/bin/../lib/./libcrypto.so.1.1 (0x00007fa7c4ee3000)
	libgssapi_krb5.so.2 => /home/work/anaconda3/bin/../lib/./libgssapi_krb5.so.2 (0x00007fa7c5c40000)
	libkrb5.so.3 => /home/work/anaconda3/bin/../lib/./libkrb5.so.3 (0x00007fa7c4e07000)
	libk5crypto.so.3 => /home/work/anaconda3/bin/../lib/./libk5crypto.so.3 (0x00007fa7c5c21000)
	libcom_err.so.3 => /home/work/anaconda3/bin/../lib/./libcom_err.so.3 (0x00007fa7c5c1a000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fa7c4beb000)
	/lib64/ld-linux-x86-64.so.2 (0x00007fa7c5ba0000)
	# Check for successful establishment
	libcrypto.so.1.0.0 => /home/work/anaconda3/bin/../lib/././libcrypto.so.1.0.0 (0x00007fa7c47ab000)
	libdl.so.2 => /lib64/libdl.so.2 (0x00007fa7c45a7000)
	libkrb5support.so.0 => /home/work/anaconda3/bin/../lib/././libkrb5support.so.0 (0x00007fa7c5c0a000)
	libresolv.so.2 => /lib64/libresolv.so.2 (0x00007fa7c438d000)

Spark Error: java.lang.StackOverflowError [How to Solve]

Spark broadcast class message java.lang.stackoverflowerror

Background: a 167m tree class needs to be broadcast, so the stack memory is not enough
solution: add in spark submit: (at present, due to the small data level, it runs in local mode)

spark-submit \$
--class bp_beauty_op.beauty_op \$
--master local[*] \$
--driver-java-options "-Xss256m" \$
test-1.0-SNAPSHOT.jar

Or add spark.Driver.Extrajavaoptions = “- xss256m”
in spark-defaults.conf to test the running.

[Solved] Mac Install homebrew Error: error: Not a valid ref: refs/remotes/origin/master

The MAC reports the following error after installing homeberw:

Press RETURN to continue or any other key to abort
==> /usr/bin/sudo /usr/sbin/chown -R aa:admin /opt/homebrew
==> Downloading and installing Homebrew...
HEAD is now at 8de10a05b Merge pull request #10472 from MikeMcQuaid/new-issue-templates
error: Not a valid ref: refs/remotes/origin/master
fatal: ambiguous argument 'refs/remotes/origin/master': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git [...] -- [...]'
fatal: the remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
Error: Fetching /opt/homebrew/Library/Taps/homebrew/homebrew-core failed!
fatal: invalid upstream 'origin/master'
Failed during: /opt/homebrew/bin/brew update --force --quiet

The solution is as follows:

Uninstall homebrew

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/uninstall.sh)"

Set git compression:

git config --global core.compression 0

Set git buffer size:

git config --global http.postBuffer 1048576000

Reinstall brew

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"

[Solved] Nginx Certificate Fill Path Error: SSL: error:0200107B:system library:fopen:Unknown error:fopen

When nginx configures the SSL certificate, it starts with an error. The certificate file cannot be found. The error log is as follows:

2021/11/24 15:52:19 [emerg] 4124#3800: cannot load certificate "E:
ginx-1.21.4\ssl\6667030_xxxx.pem": BIO_new_file() failed (SSL: error:0200107B:system library:fopen:Unknown error:fopen('E:
ginx-1.21.4\ssl\6667030_xxxxxx.pem','r') error:2006D002:BIO routines:BIO_new_file:system lib)
2021/11/24 15:53:33 [emerg] 1832#4972: cannot load certificate "E:
ginx-1.21.4\ssl\6667030_xxxx.pem": BIO_new_file() failed (SSL: error:0200107B:system library:fopen:Unknown error:fopen('E:
ginx-1.21.4\ssl\6667030_xxxx.pem','r') error:2006D002:BIO routines:BIO_new_file:system lib)

Solution:

Change the address path of disk e to “\\”, which was written as “ssl_certificate”       E: “\nginx-1.21.4\SSL\6667030_xxxx.PEM”, it keeps reporting errors

 server {
        listen       443 ssl;
        server_name  xxxx;

        ssl_certificate      E:\\nginx-1.21.4\ssl\6667030_xxxx.pem;
        ssl_certificate_key  E:\\nginx-1.21.4\ssl\6667030_xxxx.key;

        ssl_session_cache    shared:SSL:1m;
        ssl_session_timeout  5m;

        ssl_ciphers  HIGH:!aNULL:!MD5;
        ssl_prefer_server_ciphers  on;


		location /api/ {
			client_max_body_size 1000m;
			alias   E:\dev\Server\api/;
            index  index.html index.htm;
        }
		
    }

[Solved] HiveSQL Error: “Error while processing statement: FAILED: Execution Error, return code 2“

Project scenario:

tip: briefly describe the project background here:
when writing hivesql today, some codes are executed, and the same errors are reported after execution
 


Problem Description:

tip: problems encountered in the project are described here: </ font>

Error while processing statement: FAILED: Execution Error, return code 2 from org.apache.hadoop.hive

Solution:

tip: fill in the specific solution to the problem here:
later, it was found that this is an MR execution error. The reason is that the program here needs to go through Mr, and I manually turned on the local mode. Just turn it off now. Slow down and slow down

set hive.exec.mode.local.auto=false;

[Solved] Windows10 Start Linux Subsystem Error: WslRegisterDistribution failed with error: 0x80370102

Question

Error installing Carla simulator installation failed 0x80070005 – access denied
error setup failed 0x80070005 – access is denied

One or more problems caused the setup to fail. Please fix the problem and try setting again. For more information, see the log file
installation failed

0x80070005 - Access is denied.

Solution:

Scenario option 1: run the installation file as an administrator
right click the installation file and select run as administrator. You need to work with your IT team to do this
option 2: temporarily disable anti-virus software
work with your IT team to temporarily disable any anti-virus software or malware running on your computer, and then try installing the software again.

reason

Antivirus or antimalware software prevents the installation of Carla simulator
additional information

e000: Error 0x80070005: Failed to write run key value. 
e000: Error 0x80070005: Failed to update resume mode. 
e000: Error 0x80070005: Failed to begin registration session. 
e000: Error 0x80070005: Failed to begin registration session in per-machine process. 
e000: Error 0x80070005: Failed to register bundle. 
i399: Apply complete, result: 0x80070005, restart: None, ba requested restart: No 

Carla emulator running interface

#Reference:
https://kb.tableau.com/articles/issue/error-setup-failed-0x80070005-access-is-denied-after-upgrading

[Solved] win32diskimager Error: An error occured when attempting to XXX, Error 5: Access is Denied

Problem Description:

today, you need to format the SD card as FAT32, and then write an img file to it. Use the card reader to connect the SD card to the host, and then use win32discriminator software to write an error to the specified drive letter: an error occurred when attempting to XXX, error 5: access is denied.

Problem-solving:

1) Download SD memory card formatter (official website)
2) select overwirte format to format
3) use win32diskimager to write again. Success!

I think some people on the Internet say that the card reader is broken. Change a card reader. You can try this method first. If not, replace the card reader.

[Solved] azkaban Upload zip Error :Error Chunking during uploading files to db


The page reported an error when uploading
Installation Failed
Error Chunking during uploading files to db
View web-server log:

2021/11/26 11:20:38.253 +0800 INFO [ProjectManagerServlet] [Azkaban] Installation Failed.
azkaban.project.ProjectManagerException: Error Chunking during uploading files to db...
	at azkaban.project.JdbcProjectImpl.uploadFileInChunks(JdbcProjectImpl.java:383)
	at azkaban.project.JdbcProjectImpl.lambda$uploadProjectFile$1(JdbcProjectImpl.java:226)
	at azkaban.db.DatabaseOperator.transaction(DatabaseOperator.java:95)
	at azkaban.project.JdbcProjectImpl.uploadProjectFile(JdbcProjectImpl.java:234)
	at azkaban.storage.DatabaseStorage.putProject(DatabaseStorage.java:58)
	at azkaban.storage.ProjectStorageManager.uploadProject(ProjectStorageManager.java:106)
	at azkaban.project.AzkabanProjectLoader.persistProject(AzkabanProjectLoader.java:221)
	at azkaban.project.AzkabanProjectLoader.uploadProject(AzkabanProjectLoader.java:146)
	at azkaban.project.ProjectManager.uploadProject(ProjectManager.java:507)
	at azkaban.webapp.servlet.ProjectManagerServlet.ajaxHandleUpload(ProjectManagerServlet.java:1828)
	at azkaban.webapp.servlet.ProjectManagerServlet.handleUpload(ProjectManagerServlet.java:2001)
	at azkaban.webapp.servlet.ProjectManagerServlet.handleMultiformPost(ProjectManagerServlet.java:211)
	at azkaban.webapp.servlet.LoginAbstractAzkabanServlet.doPost(LoginAbstractAzkabanServlet.java:308)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:688)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:770)
	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401)
	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
	at org.mortbay.jetty.Server.handle(Server.java:326)
	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
	at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:945)
	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756)
	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
	at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
	at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)

Can’t see what the problem is, then go to the code:

good guy, give me the exception directly
you can only roughly see that an error is reported when executing SQL
although I don’t know what the specific error is, I guess it’s the problem of database settings, because Azkaban uploads in other environments are normal.

View official documents: https://azkaban.readthedocs.io/en/latest/getStarted.html#database-Setup

the database settings are indeed missing. In addition, this problem can be solved

Unknown SSL protocol error in connection to xxx:443 [How to Solve]

1. Unknown SSL protocol error in connection to XXX: 443

Unknown SSL protocol error in connection to XXX: 443 occurs when Git is used to download from a remote location..

Method 1:

(example):

Set up proxy server:

: Add in .gitconfig

http.proxy=127.0.0.1:8087

http.sslVerify=false

Method 2:

(example):

Type directly on the command line

git config --global http.proxy 127.0.0.1:8087

git config --global http.sslVerify false