Category Archives: Error

[Solved] Arcgis Pro2.8 Error: kernel error, failed open to kernel

This is the most depressing thing I encountered in learning ArcGIS pro. The error is reported as follows. This is the most depressing thing I encountered in learning ArcGIS pro. The error is reported as follows

This error occurs when using jupyter notbook because “Due to repeated uninstallation of anaconda or too many python versions installed, the path of the notbook kernel startup is confused and needs to be manually adjusted by yourself”. The solution is simple, open Python Prompt and type python -m ipykernel install -user, reinstall the kernel and restart.

I changed the version, I reinstalled Arcgis Pro2.5, and the above problem was solved wonderfully

[Solved] kubelet Startup Error: cannot find network namespace for the terminated container

1. Error reporting:

Use the journalctl – xefu kubelet command to view the kubelet log. The following errors are found:

cannot find network namespace for the terminated container

2. Solution:

# docker system prune

# systemctl restart kubelet

Instructions for using docker system:

# docker system -h

Flag shorthand -h has been deprecated, please use –help

Usage: docker system COMMAND

Manage Docker

Commands:

df             Show docker disk usage

Check the usage of docker space.

events     Get real time events from the server

View live events.

info         Display system-wide information

View system information.

prune     Remove unused data

Docker cleans the stopped container, and there is no network, image and cache used by the container.

[Solved] Android Studio Compile Error: Could not determine java version from ‘11.0.8‘.

There are two solutions to solve Error: Could not determine java version from '11.0.8'.

Method 1: downgrade Android Studio and use the historical version of Android Studio environment;

Method 2: upgrade Gradle version;

1. Error reporting information

 

Open an old project and report the following error:

Could not determine java version from '11.0.8'.

The project uses Gradle version which is incompatible with Studio running on Java 10 or newer.
See details at https://github.com/gradle/gradle/issues/8431
Possible solution:
 - Upgrade Gradle wrapper to 4.8.1 version and re-import the project

Select the “menu bar/file/Project Structure” option,

Check that the Android Gradle plug-in version of the Android project is 3.2.0 and the Gradle version is 4.6. This is the version used a few years ago. At present, the project cannot be compiled using the latest Android studio;

 

 

 

 

2. Solution

Select the menu bar/file/project structure option,

In the pop-up project structure dialog box, update the Android gradle plug-in version to 4.2.1 and the gradle plug-in version to 6.7.1;

[Solved] Failed to find glog – Could not find glog include directory, set…

catkin_make Compile Error:

– Found OpenCV: /opt/ros/kinetic (found version “3.3.1”)
CMake Error at cmake/FindGlog.cmake:77 (MESSAGE):
Failed to find glog - Could not find glog include directory, set
GLOG_INCLUDE_DIR to directory containing glog/logging.h
Call Stack (most recent call first):
cmake/FindGlog.cmake:103 (GLOG_REPORT_NOT_FOUND)
CMakeLists.txt:147 (find_package)

 

Solution:
$ sudo apt-get install libgoogle-glog-dev

Android Error: Failure [INSTALL_FAILED_USER_RESTRICTED: Invalid apk] in android

When debugging with Xiaomi mobile phone (MI Max 2), the application cannot be installed

Settings -> Additional settings -> Developer options ->

1. Close “MIUI optimization” and restart
2 Open “USB debugging”
3 Open “install via USB”
4 Set USB configuration to charging
5 Open “install via USB”**

next step

At this step, the problem of mismatch of SDK version has been fixed. Modify the SDK version

[Solved] Failed to get convolution algorithm. This is probably because cuDNN failed to initialize

Problem description

Failed to get convolution algorithm. This is probably because cuDNN failed to initialize

Cause analysis:

Insufficient GPU memory

Solution:

1.kill -9 PID_*
2. Dynamically allocate GPU memory:

from tensorflow.compat.v1 import ConfigProto
from tensorflow.compat.v1 import InteractiveSession

config = ConfigProto()
config.gpu_options.allow_growth = True
session = InteractiveSession(config=config)

failed to obtain in-memory shard lock [How to Solve]

Cause of problem:

1. The reason for this problem is that the original slice was not properly closed and cleaned up, so there is no way to get a slice lock when the slice has to be reallocated back to the problem node.
2. This does not cause the slice data to be lost, it just needs to retrigger the allocation

Recovery instruction

curl -XPOST http://localhost:9200/_cluster/reroute?retry_failed

View details

curl -XGET http://localhost:9200/_cluster/allocation/explain

[Solved] “Failed to run kubelet“ err=“failed to run Kubelet: misconfiguration: kubelet cgroup driver: \“cgrou

kubelet Startup Error:

"Failed to run kubelet" err="failed to run Kubelet: misconfiguration: kubelet cgroup driver: \"cgrou...: \"systemd\""
systemctl status kubelet
[root@k8s-node1 kubernetes]# systemctl status kubelet
● kubelet.service - Kubernetes Kubelet
   Loaded: loaded (/usr/lib/systemd/system/kubelet.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since 一 2022-03-21 15:29:19 CST; 23s ago
  Process: 30267 ExecStart=/usr/bin/kubelet (code=exited, status=1/FAILURE)
 Main PID: 30267 (code=exited, status=1/FAILURE)
3月 21 15:29:19 k8s-node1 kubelet[30267]: E0321 15:29:19.200485   30267 server.go:302] "Failed to run kubelet" err="failed to run Kubelet: misconfiguration: kubelet cgroup driver: \"cgrou...: \"systemd\""
3月 21 15:29:19 k8s-node1 systemd[1]: kubelet.service: main process exited, code=exited, status=1/FAILURE
3月 21 15:29:19 k8s-node1 systemd[1]: Unit kubelet.service entered failed state.
3月 21 15:29:19 k8s-node1 systemd[1]: kubelet.service failed.
3月 21 15:29:19 k8s-node1 systemd[1]: kubelet.service holdoff time over, scheduling restart.
3月 21 15:29:19 k8s-node1 systemd[1]: Stopped Kubernetes Kubelet.
3月 21 15:29:19 k8s-node1 systemd[1]: start request repeated too quickly for kubelet.service
3月 21 15:29:19 k8s-node1 systemd[1]: Failed to start Kubernetes Kubelet.
3月 21 15:29:19 k8s-node1 systemd[1]: Unit kubelet.service entered failed state.
3月 21 15:29:19 k8s-node1 systemd[1]: kubelet.service failed.
Hint: Some lines were ellipsized, use -l to show in full.

 

Solution:
Remove native.cgroupdriver=systemd from the docker configuration file or change systemd to cgroupfs

vim /etc/docker/daemon.json 
{
    "exec-opts": ["native.cgroupdriver=cgroupfs"]
}
systemctl daemon-reload
systemctl enable kubelet
systemctl restart kubelet
systemctl status kubelet

[Solved] element-plus Error: Failed to resolve component

vue3 & element-plus Project Error:

Failed to resolve component: el-form If this is a native custom element, make sure to exclude it
Failed to resolve component: el-form If this is a native custom element, make sure to exclude it
Failed to resolve component el-form-item
Failed to resolve component Descriptions
Component inside ＜Transition＞ renders non-element root node that cannot be animated.

Reason:
On-demand introduction of element

Solution:
1. Enter in the page script

import { ElForm } from "element-plus";

2. Add commonly used ones to element-plus files 

import {
    ElForm,
}

const components = [
    ElForm,
]

Done!

[Solved] Execution failed for task ‘:app:mergeDebugJavaResource‘.

Execution failed for task ‘:app:mergeDebugJavaResource’.

> A failure occurred while executing com.android.build.gradle.internal.tasks.MergeJavaResWorkAction
   > 2 files found with path 'META-INF/library_release.kotlin_module' from inputs:
      - C:\Users\pc5\.gradle\caches\transforms-2\files-2.1\ce2b46fc1c5f5af8ed7abfa332710f84\zoomlayout-1.9.0\jars\classes.jar
      - C:\Users\pc5\.gradle\caches\transforms-2\files-2.1\a562c978ea1815ba0e02c6c6a3c46b97\egloo-0.6.1\jars\classes.jar
     Adding a packagingOptions block may help, please refer to
     https://google.github.io/android-gradle-dsl/current/com.android.build.gradle.internal.dsl.PackagingOptions.html
     for more information

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

When Importing the zoomlayou third-party library, the installation reports an error, Clean Project, clearing the cache and restarting are also invalid

Solution:
Add the following code to the module’s build.gradle under the android tab

android {
	packagingOptions {
      	pickFirst "META-INF/library_release.kotlin_module"
	}
}
or
android {
	packagingOptions {
      	exclude "META-INF/library_release.kotlin_module"
	}
}

Reference:
https://stackoverflow.com/questions/60684730/error-execution-failed-for-task-appmergedebugjavaresource.

[Solved] Matlab Code generate error: failed to generate all binary outputs

When generating Matlab code, the following error is sometimes reported: Failed to generate all binary outputs

You can check if there are any problems as follows.

1. Check if the path of the executed model has spaces in it, if so, delete the spaces or replace them with underscores.
Reason: Sometimes the compiler will remove the space key from the path by default, resulting in incorrect path identification.
2. check whether the compiler path is executed with spaces, if so, reinstall it under the path without spaces
Cause: the same as above.
3. Modify the configuration: Configure–Code Generation–Templates–Generate an exanmple program (check), this option will generate the ert_main.c file after the check.
4. modify the configuration: Configure—Code Generation—Generate code only (check), this option will not execute the makefile when the code is generated.

If it still cannot be solved, please refer to:
https://www.mathworks.com/matlabcentral/answers/474572-failed-to-generate-all-binary-outputs-works-externally-but-will-not-deploy