Tag Archives: Operation and maintenance

[Solved] Jenkins error: Asynchronous execution failure

The job normally builds success, and then reports asynchronous execution failure, as shown below

[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 45.983 s
[INFO] Finished at: 2022-01-12T09:56:29+08:00
[INFO] ------------------------------------------------------------------------
ERROR: Asynchronous execution failure
java.util.concurrent.ExecutionException: java.lang.NullPointerException
	at hudson.remoting.Channel$2.adapt(Channel.java:1037)
	at hudson.remoting.Channel$2.adapt(Channel.java:1031)
	at hudson.remoting.FutureAdapter.get(FutureAdapter.java:60)
	at hudson.maven.AbstractMavenBuilder.waitForAsynchronousExecutions(AbstractMavenBuilder.java:186)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:144)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:70)
	at hudson.remoting.UserRequest.perform(UserRequest.java:211)
	at hudson.remoting.UserRequest.perform(UserRequest.java:54)
	at hudson.remoting.Request$2.run(Request.java:376)
	at hudson.remoting.InterceptingExecutorService.lambda$wrap$0(InterceptingExecutorService.java:78)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NullPointerException
ERROR: Asynchronous execution failure
java.util.concurrent.ExecutionException: java.lang.NullPointerException
	at hudson.remoting.Channel$2.adapt(Channel.java:1037)
	at hudson.remoting.Channel$2.adapt(Channel.java:1031)
	at hudson.remoting.FutureAdapter.get(FutureAdapter.java:60)
	at hudson.maven.AbstractMavenBuilder.waitForAsynchronousExecutions(AbstractMavenBuilder.java:186)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:144)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:70)
	at hudson.remoting.UserRequest.perform(UserRequest.java:211)
	at hudson.remoting.UserRequest.perform(UserRequest.java:54)
	at hudson.remoting.Request$2.run(Request.java:376)
	at hudson.remoting.InterceptingExecutorService.lambda$wrap$0(InterceptingExecutorService.java:78)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

Solution: find the fingerprints folder in Jenkins’s home directory, delete the contents, and then build without reporting an error.

How to Solve “RIP Address Out Of Range” Error

When restarting Windows Server 2008 R2, you see this error on the HP ProLiant} dl388 Gen 9 server. The error may display several messages that do not mean much to you, such as:

X64 exception type 0d – General protection exception

Rip address out of range

RIP Address Out Of Range

This error was seen when Windows Server 2008 R2 was restarted

To resolve this error, disable the following settings in the BIOS:

UEFI optimization startup

[Solved] nvidia-docker runtime Error: (Unknown runtime specified nvidia)

1. An error is reported when running the docker command

[email protected]:~# docker run --runtime=nvidia -ti  -v $(pwd):/workspace -w /workspace -v /nfs:/nfs [email protected] --privileged -v /var/run/docker.sock:/var/run/docker.sock registry.test.cn/mla/cxx_toolchains:latest
docker: Error response from daemon: Unknown runtime specified nvidia.
See 'docker run --help'.

According to the error prompt, check whether NVIDIA-docker is installed

[email protected]:~# nvidia-docker
nvidia-docker: command not found
[email protected]:~# 

Obviously, it is not installed

2 execute the script and install NVIDIA-docker

[email protected]:~# cat install-nvidia-docker.sh
sudo curl -s -L https://nvidia.github.io/nvidia-docker/gpgkey | sudo apt-key add -
distribution=$(. /etc/os-release;echo $ID$VERSION_ID)
sudo curl -s -L https://nvidia.github.io/nvidia-docker/$distribution/nvidia-docker.list | sudo tee /etc/apt/sources.list.d/nvidia-docker.list
sudo apt-get update
sudo apt-get install -y nvidia-docker2
sudo pkill -SIGHUP dockerd
[email protected]:~#

Check that NVIDIA-docker and NVIDIA-container-Runtim are installed successfully

[email protected]:~# which nvidia-docker
/usr/bin/nvidia-docker
[email protected]:~# which nvidia-container-runtime
/usr/bin/nvidia-container-runtime
[email protected]:~#

3 edit /etc/docker/daemon.JSON is as follows

[email protected]:~# cat /etc/docker/daemon.json
{
  "insecure-registries": ["registry.test.cn"],
  "max-concurrent-downloads": 10,
  "log-driver": "json-file",
  "log-level": "warn",
  "log-opts": {
    "max-size": "10m",
    "max-file": "3"
  },
  "live-restore": true,
  "metrics-addr": "0.0.0.0:9323",
  "default-runtime": "nvidia",
  "experimental": true,
    "runtimes": {
        "nvidia": {
            "path": "/usr/bin/nvidia-container-runtime",
            "runtimeArgs": []
        }
    }
}
[email protected]:~#

4 restart docker

[email protected]:~# systemctl daemon-reload
[email protected]:~# systemctl restart docker

5 verification

[email protected]:~# docker run --runtime=nvidia -ti  -v $(pwd):/workspace -w /workspace -v /nfs:/nfs [email protected] --privileged -v /var/run/docker.sock:/var/run/docker.sock registry.test.cn/mla/cxx_toolchains:latest
[email protected]:/workspace#
[email protected]:/workspace# ls
[email protected]:/workspace# pwd
/workspace
[email protected]:/workspace#

[Solved] VMware Create a Virtual Machine Error: unsuccessful

VMware encountered a classic error when creating a virtual machine:

Attempting to start up from:
EFI VMware Virtual SCSI Hard Drive (0.0) … unsuccessful.
EFI VMware Virtual SATA CDROM Drive (1.0) … unsuccessful.
EFI Network…

Solution:
1 Find the VMX file in the installation directory of the virtual machine
2 Delete firmware = “EFI”
3 Save and restart the virtual machine to install normally

[Solved] ××: error while loading shared libraries: ××.so.19: cannot open shared object file: No such file or directory

××: error while loading shared libraries: ××. so. 19: cannot open shared object file: No such file or directory

When starting some programs, the corresponding link library could not find a solution

[[email protected] build]# ttyd --help
ttyd: error while loading shared libraries: libwebsockets.so.19: cannot open shared object file: No such file or directory
[[email protected] build]# ttyd --help
ttyd: error while loading shared libraries: libjson-c.so.5: cannot open shared object file: No such file or directory

This means that the program needs libwebsockets.so.19 and libjson-c.so.5 the functions in the two dynamic link libraries can not be found in the corresponding directory. The dynamic link library under Linux is composed of LD So is responsible for loading, and his configuration file is in etc/LD.so.conf , it is found that there is really no ××.So file under/usr/local/lib configured, we can manually add the specified path to solve the error problem

/environment/libwebsockets/build/lib		## libwebsockets.so.19
/cpack/json-c/build					## libjson-c.so.5

Then refresh the cache and run it again

[[email protected] build]# sudo ldconfig		

[[email protected] build]# ttyd --help
ttyd is a tool for sharing terminal over the web

USAGE:
    ttyd [options] <command> [<arguments...>]

VERSION:
    1.6.3-3e37e33

OPTIONS:
    -p, --port              Port to listen (default: 7681, use `0` for random port)
    -i, --interface         Network interface to bind (eg: eth0), or UNIX domain socket path (eg: /var/run/ttyd.sock)
    -c, --credential        Credential for basic authentication (format: username:password)
    -H, --auth-header       HTTP Header name for auth proxy, this will configure ttyd to let a HTTP reverse proxy handle authentication
    -u, --uid               User id to run with
    -g, --gid               Group id to run with
    -s, --signal            Signal to send to the command when exit it (default: 1, SIGHUP)
    -w, --cwd               Working directory to be set for the child program
    -a, --url-arg           Allow client to send command line arguments in URL (eg: http://localhost:7681?arg=foo&arg=bar)
    -R, --readonly          Do not allow clients to write to the TTY
    -t, --client-option     Send option to client (format: key=value), repeat to add more options
    -T, --terminal-type     Terminal type to report, default: xterm-256color
    -O, --check-origin      Do not allow websocket connection from different origin
    -m, --max-clients       Maximum clients to support (default: 0, no limit)
    -o, --once              Accept only one client and exit on disconnection
    -B, --browser           Open terminal with the default system browser
    -I, --index             Custom index.html path
    -b, --base-path         Expected base path for requests coming from a reverse proxy (eg: /mounted/here, max length: 128)
    -P, --ping-interval     Websocket ping interval(sec) (default: 5)
    -S, --ssl               Enable SSL
    -C, --ssl-cert          SSL certificate file path
    -K, --ssl-key           SSL key file path
    -A, --ssl-ca            SSL CA file path for client certificate verification
    -d, --debug             Set log level (default: 7)
    -v, --version           Print the version and exit
    -h, --help              Print this text and exit

Visit https://github.com/tsl0922/ttyd to get more information and report bugs.
[[email protected] build]#

[Solved] ERROR A malformed block was encountered while loading a block

ERROR! A malformed block was encountered while loading a block
[[email protected] test]# ansible-playbook -C roles_redis.yml -i hosts
ERROR! A malformed block was encountered while loading a block

Reason:
You don’t add the follow code after include when you are write main file:

- include add_group.yml

Solution:

We must pay attention to the problem of space format. The specification is very strict

- include: add_group.yml

[Solved] jumpserver nginx Error: Connect websocket server error

After installation, the jumpserver selects a custom port, and the HTTP port 80 is changed to 88. After forwarding through nginx, remember to set the upgrade of nginx, otherwise it will prompt: connect websocket server error

Nginx is configured as follows:

##Jump
server {
listen 80;
server_name jump.xxxxxx.cn;

location/{
proxy_pass   http://127.0.0.1:88;
        proxy_http_version      1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
}
}

This will not prompt an error

[Solved] pxp_lib.h:19:10: fatal error: linux/pxp_device.h: No such file or directory


ERROR: imx-lib-1_5.8+AUTOINC+3f777974c0-r0 do_compile: oe_runmake failed
ERROR: imx-lib-1_5.8+AUTOINC+3f777974c0-r0 do_compile: Execution of '/sd1/jarvis-workspace/build-x11/tmp/work/cortexa7t2hf-neon-mx6ul-fsl-linux-gnueabi/imx-lib/1_5.8+AUTOINC+3f777974c0-r0/temp/run.do_compile.612337' failed with exit code 1
ERROR: Logfile of failure stored in: /sd1/jarvis-workspace/build-x11/tmp/work/cortexa7t2hf-neon-mx6ul-fsl-linux-gnueabi/imx-lib/1_5.8+AUTOINC+3f777974c0-r0/temp/log.do_compile.612337
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 1 CROSS_COMPILE=arm-fsl-linux-gnueabi- PLATFORM= INCLUDE=-I/sd1/jarvis-workspace/build-x11/tmp/work/cortexa7t2hf-neon-mx6ul-fsl-linux-gnueabi/imx-lib/1_5.8+AUTOINC+3f777974c0-r0/recipe-sysroot/usr/include/imx all
| make -C pxp all
| make[1]: Entering directory '/sd1/jarvis-workspace/build-x11/tmp/work/cortexa7t2hf-neon-mx6ul-fsl-linux-gnueabi/imx-lib/1_5.8+AUTOINC+3f777974c0-r0/git/pxp'
| arm-fsl-linux-gnueabi-gcc  -mthumb -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a7 -fstack-protector-strong  -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=/sd1/jarvis-workspace/build-x11/tmp/work/cortexa7t2hf-neon-mx6ul-fsl-linux-gnueabi/imx-lib/1_5.8+AUTOINC+3f777974c0-r0/recipe-sysroot -D -I/sd1/jarvis-workspace/build-x11/tmp/work/cortexa7t2hf-neon-mx6ul-fsl-linux-gnueabi/imx-lib/1_5.8+AUTOINC+3f777974c0-r0/recipe-sysroot/usr/include/imx -Wall -fPIC  -O2 -pipe -g -feliminate-unused-debug-types -fmacro-prefix-map=/sd1/jarvis-workspace/build-x11/tmp/work/cortexa7t2hf-neon-mx6ul-fsl-linux-gnueabi/imx-lib/1_5.8+AUTOINC+3f777974c0-r0=/usr/src/debug/imx-lib/1_5.8+AUTOINC+3f777974c0-r0                      -fdebug-prefix-map=/sd1/jarvis-workspace/build-x11/tmp/work/cortexa7t2hf-neon-mx6ul-fsl-linux-gnueabi/imx-lib/1_5.8+AUTOINC+3f777974c0-r0=/usr/src/debug/imx-lib/1_5.8+AUTOINC+3f777974c0-r0                      -fdebug-prefix-map=/sd1/jarvis-workspace/build-x11/tmp/work/cortexa7t2hf-neon-mx6ul-fsl-linux-gnueabi/imx-lib/1_5.8+AUTOINC+3f777974c0-r0/recipe-sysroot=                      -fdebug-prefix-map=/sd1/jarvis-workspace/build-x11/tmp/work/cortexa7t2hf-neon-mx6ul-fsl-linux-gnueabi/imx-lib/1_5.8+AUTOINC+3f777974c0-r0/recipe-sysroot-native=  -c pxp_lib.c -o pxp_lib.o
| <command-line>: error: macro names must be identifiers
| In file included from pxp_lib.c:26:
| pxp_lib.h:19:10: fatal error: linux/pxp_device.h: No such file or directory
|    19 | #include <linux/pxp_device.h>
|       |          ^~~~~~~~~~~~~~~~~~~~
| compilation terminated.
| make[1]: *** [Makefile:30: pxp_lib.o] Error 1
| make[1]: Leaving directory '/sd1/jarvis-workspace/build-x11/tmp/work/cortexa7t2hf-neon-mx6ul-fsl-linux-gnueabi/imx-lib/1_5.8+AUTOINC+3f777974c0-r0/git/pxp'
| make: *** [Makefile:17: pxp] Error 2
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Execution of '/sd1/jarvis-workspace/build-x11/tmp/work/cortexa7t2hf-neon-mx6ul-fsl-linux-gnueabi/imx-lib/1_5.8+AUTOINC+3f777974c0-r0/temp/run.do_compile.612337' failed with exit code 1

Error resolution:

meta-jarvis/recipes-bsp/imx-lib/imx-lib_git.bbappend



ADD:


PLATFORM_mx6ull = "IMX6UL"

[Solved] Error: ER_ACCESS_DENIED_ERROR: Access denied for user ‘root’@‘localhost’ (using password: YES)

Add the port number when configuring the server file

// Create the connection of database
const mysql=require('mysql')
const db=mysql.createPool({
  host:'127.0.0.1',
  port:'3307',
  user:'root',
  password:'admin123',
  database:'my_db'
})
module.exports=db

When creating a table, check the ID and increment options

[Solved] Linux program error: dpkg is interrupted. You must manually run ‘sudo dpkg — configure – a’

The Linux program reports an error: dpkg is interrupted. You must manually run ‘sudo dpkg — configure – a’ to solve this problem.

Run the following command to resolve the error

sudo rm /var/lib/dpkg/updates/*
sudo apt-get update
sudo apt-get upgrade

The main reason should be that there are errors in the data in the/var/lib/dpkg/updates folder, resulting in errors in the software update program, so they have to be completely deleted. The sudo apt get update command will re-establish these data, use sudo apt get upgrade to update the details of the software installed in your computer, and update the software to the latest version according to the details of the software.