Category Archives: Error

K8S Master Initialize Error: [ERROR CRI]: container runtime is not running: output: E0812

[[email protected] ~]# kubeadm init   --kubernetes-version 1.24.3   --apiserver-advertise-address=   --service-cidr=   --pod-network-cidr=   --image-repository 
[init] Using Kubernetes version: v1.24.3
[preflight] Running pre-flight checks
error execution phase preflight: [preflight] Some fatal errors occurred:
        [ERROR CRI]: container runtime is not running: output: E0812 15:41:43.145278   29697 remote_runtime.go:925] "Status from runtime service failed" err="rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService"
time="2022-08-12T15:41:43+08:00" level=fatal msg="getting status of runtime: rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService"
, error: exit status 1
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
To see the stack trace of this error execute with --v=5 or higher
# Solution
[[email protected] ~]# rm -rf /etc/containerd/config.toml
[[email protected] ~]# systemctl restart containerd

[Solved] HALCON error #5190: Invalid window parameter

There are two types of window operations in Halcon:

1. dev_open_window opens the entity’s form and displays the image

2. open_window opens a virtual form, which is actually an image into the cache

  1. * See the official routine advanced_visualization_settings.hdev
  2. dev_close_window()
  3.  dev_open_window ( 0, 0, 512, 512, ‘black’, WindowHandle)
  4.  set_window_param (WindowHandle, ‘graphics_stack’, ‘true’) //default value: ‘false’
  5.  set_window_param(WindowHandle, ‘flush’, ‘false’) //default value: ‘true’

In my C++ project, I encountered this problem. When the SetWindowParam function is executed, an exception is always reported:

HALCON error #5190: Invalid window parameter

The solution is as follows:
The SetWindowParam function needs to rely on the dynamic library file hcanvas.dll, and copy the library from
C:\Program Files\MVTec\HALCON-xxx\bin\x64-win64
to your own project path.

[Solved] Error: ENOSPC: System limit for number of file watchers rea


Apache Superset is an open source data visualization platform.

To reproduce:

[email protected]:~/Desktop/superset$ sudo docker-compose up

The error is reported during the startup process of superset with docker as follows

Error from chokidar (/app/superset-frontend/images/viz_thumbnails): Error: ENOSPC: System limit for number of file watchers reached, watch

** **


[email protected]:~/Desktop/superset$ echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p 
 sudo] password for kali: 
 = 524288 

Re-docker run superset, green shows no errors

Problem reference:

[Solved] Springboot Reflection calls ServiceImpl Error: java.lang.NullPointerException, mapper is null

Springboot uses reflection to call serviceimpl and reports an error: java.lang.nullpointerexception

Because the mapper of ServiceImpl is null, the following is the original implementation code:

           // package name and class name
           Class classzz = Class.forName("com.XXX.XXX.service.impl.SenDataServiceImpl");

           // Get the constructor object
           Constructor constructor = null;
           try {
               constructor = classzz.getConstructor();
           } catch (NoSuchMethodException e) {
           // Create an object using the constructor object
           Object o = constructor.newInstance();
           // Pass the method to be executed Pass the parameter type, if not, you can leave it out
           Method method = classzz.getMethod("method name", long.class,String.class,String.class );
// invoke method, and pass parameters, if there are no parameters, you can leave them out
           Object obj =method.invoke(o,  5,

In the post query mode, you need to ContextLoader.getCurrentWebApplicationContext() firstly, but you haven’t gone to invoke, so the ContextLoader.getCurrentWebApplicationContext() is null.

The final solution is as follows:

1. Create a new class SpringBootBeanUtil


import org.springframework.beans.BeansException;
import org.springframework.context.ApplicationContext;
import org.springframework.context.ApplicationContextAware;
import org.springframework.stereotype.Component;

 * SpringBoot Common class to get the bean tool class in the Spring container
public class SpringBootBeanUtil implements ApplicationContextAware {

    private static ApplicationContext applicationContext;

    public void setApplicationContext(ApplicationContext applicationContext) throws BeansException {
        if (SpringBootBeanUtil.applicationContext == null) {
            SpringBootBeanUtil.applicationContext = applicationContext;
//        System.out.println("========In the general class you can get the applicationContext object by calling SpringBootBeanUtil.getApplicationContext()========");
        System.out.println("========applicationContext="+ SpringBootBeanUtil.applicationContext +"========");

     * get applicationContext
     * @return
    public static ApplicationContext getApplicationContext() {
        return applicationContext;

     * Get Bean by name.
     * @param name
     * @return
    public static Object getBean(String name) {
        return getApplicationContext().getBean(name);

     * Get Bean by class.
     * @param clazz
     * @return
    public static <T> T getBean(Class<T> clazz) {
        return getApplicationContext().getBean(clazz);

     * Return the specified bean by name, and Clazz
     * @param name
     * @param clazz
     * @return
    public static <T> T getBean(String name, Class<T> clazz) {
        return getApplicationContext().getBean(name, clazz);


2. Call SpringBootBeanUtil.getApplicationContext(). When invoking, the first parameter is applicationContext.getBean(ServiceImplType). Refer to the following code for specific implementation.

try {
               //Retrieve the created object from the ApplicationContext
               // Do not create the serviceimpi object directly by reflection, because the object created by reflection cannot instantiate the dao interface
               ApplicationContext applicationContext = SpringBootBeanUtil.getApplicationContext();
               //reflection creates the serviceimpi entity object, and the entity class
               Class<? > ServiceImplType = Class.forName("com.XXX.XXX.service.impl.SenDataServiceImpl");
              // Class<? > entityType = Class.forName("com.XXX.XXX.service.impl.SenDataServiceImpl");
               //reflection set method parameters.
               Method method = ServiceImplType.getDeclaredMethod("methodName",long.class,String.class,String.class );
               // get the instantiated bean in the ApplicationContext according to class
               method.invoke(applicationContext.getBean(ServiceImplType), 5,

           } catch (ClassNotFoundException | IllegalAccessException | InvocationTargetException | NoSuchMethodException e) {
               LOGGER.error("\n onMessage Receive Processing Message Failed - {}", "methodName");

This solves the problem that the reflection calls ServiceImpland the mapper reports an error when it is null.

[Solved] SyntaxError: Unexpected end of JSON input

Note: When doing a project, I encountered the need to transfer a line of data objects to another page, using JSON.stringify => JSON.parse and then transferring it by url:

Then the error is reported as follows:

Later, after reviewing the relevant information, we found that we need to add a coding and decoding process, as follows:

After printing, the object appears:

Cause analysis:

Reason: If an address is encountered in the parameters of the object or the elements of the array, and the address includes ? and & these special symbols, the object/array must first be converted to a string by JSON.stringify and then encoded by encodeURIComponent, when received, first decoded by decodeURIComponent and then converted to JSON format object/array by JSON.parse

[Solved] uview u-sticky Error: Cannot read property ‘bottom‘ of null

The causes are:

The component u-sticky and the bottom navigation bar tabbar conflict when switching pages, the sticky component creates an Observer listener, and when the page is switched and not destroyed, it causes the component to remain listening, so the error Cannot read property ‘bottom’ of null appears. So we need to disconnect the Observer listener manually to solve this error problem

Source code:

<u-sticky offset-top="200" >




		<u-sticky offset-top="200" :enable="enable">

	export default {
		data() {
			return {
				// @property {Boolean} enable Whether to open the ceiling function(default is true)
		// Turn on or off listeners in the corresponding show and hide page lifecycle
		onShow() {
			this.enable= true
		onHide() {
			this.enable= false


[Solved] DatePicker Error: Prop being mutated: “placement“

1. Reason for error reporting

element-ui version: 2.15.9

Screenshot is as follows:

2. Cause analysis

After element-ui was upgraded to version 2.15.6 or higher, a line of code was added inside the date-picker component to directly modify the placement (you can check it out)
A screenshot of the viewing address is as follows.

3. Solution

  1. Go to the project package.json file to check the element-ui version, if it is higher than 2.15.6, uninstall the current version directly
  2. Type npm install [email protected] -S to install version 2.15.6, and then remove the ^ sign in front of the version (if you don’t know the version symbol in front of it, you can look at it on Google)
  3. Remove the node_modules package
  4. Type npm install to install the dependencies


4. Screenshot of element-ui version

[Solved] Neo4j error: Cannot merge the following node because of null property value for ‘casualty’

Execute the following command in neo4j:

LOAD CSV WITH HEADERS  FROM "file:///accident.csv" AS line
MERGE (p:accident{,name:line.code,casualty:line.casualty})


Report an error:

Cannot merge the following node because of null property value for 'casualty': (:accident {casualty: null}) (Failure when processing file '/E:/Program/...../neo4j-community-4.4.8/import/accident.csv' on line 2.)

Cause: In the first time the entity is created and the casualty value in the file is empty.
Solution: Change merge to create

Source: Explanation of error “Cannot merge node using null property value for” – Knowledge Base

Zookper Error: [org.apache.zookeeper. ClientCnxn]-[WARN] Session 0x0 for server, unexpected error…(SSM integration)

Problem: an error is reported after a project in multiple projects is started:

[org.apache.zookeeper. ClientCnxn]-[WARN] Session 0x0 for server, unexpected error


Reason 1: because there are not enough links in zookper, the maximum number of links needs to be modified


Modify the zoo.cfg in the conf directory of zookper. add maxClientCnxns = 500 at the end.


Kotlin: How to Solve kapt import error

The first problem encountered was that the BR file could not be found

Log: unresolved reference: BR

Reason: the plug-in developed by kotlin does not support cross module, so the reference of databinding when using APT Technology br file does not determine the directory, so the error (unresolved reference: be) is caused, so it needs to be completed by kapt


apply plugin: 'kotlin-kapt'
kapt {
    generateStubs = true

dependencies {
    implementation fileTree(dir: 'libs', include: ['*.jar'])
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
    //The version should be the same as the gradle version
    kapt  ""

New problem: Class not found Custom generated class can not be generated.

Reason: If you already have kapt, you need to replace it with kapt

Solution: In Kotlin, you need to add the kotlin-kapt plugin to activate kapt and replace the annotationProcessor with kapt.

[Solved] Qt Error: undefined reference to xxxxx

Error reporting information:

first of all, it is necessary to distinguish the two types of error : undefined reference to xxxxx and "XXXX was not declared in this scope". The former is because the compiler can find the declaration of the function, but cannot find the definition of the function, so it reports an error; The latter is not found at all. You should first check whether the header file is missing.

For undefined reference to xxxxx, there are two situations at present

1. The path to ffmpeg in the pro file is not correct
2. The header file is written in C, but without extern "C" {}