Exception handling method, computing device and storage medium

Abstract

This application relates to an exception handling method, computing device, and storage medium. The method includes: an operating system kernel receiving a run command for running a pre-installed application in a container; in response to the run command, the kernel generates a kernel run record log corresponding to the run command by running a pre-installed logging module, and executes the pre-installed application by running a pre-installed program execution module. According to one embodiment of the application, the container's use of the operating system kernel can be monitored, thereby reducing the difficulty of troubleshooting exceptions.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to an exception handling method, a computing device, and a storage medium. Background Art

[0002] Docker is an open-source container engine. After installing Docker on a computing device, you can host multiple containers based on Docker. These containers share the operating system kernel, and each container can host and execute different applications, all isolated from each other.

[0003] In recent years, k8s (also known as kubernetes) has been increasingly used. k8s is an open source container-based cluster management platform, and its full name is kubernetes. Figure 1 As shown in the figure, a k8s system is usually called a k8s cluster. The cluster mainly includes a master node (also called a master node) and multiple computing nodes (also called computing nodes). Each computing node includes multiple pods. A pod encapsulates one or more closely related containers. The master node manages and controls the entire cluster, can realize automatic container deployment and scheduling, and provide load balancing between containers. Due to the complexity of the entire system architecture and the diversity of applications, it is difficult to troubleshoot when the system has an anomaly. On the other hand, because the containers share the operating system kernel, the containers and the operating system will affect each other, which further increases the difficulty of anomaly troubleshooting. In addition, the application of each container can configure the operating system kernel parameters, and usually acts on the operating system and other containers. In this way, the possibility of anomalies is high. Summary of the Invention

[0004] In order to solve or partially solve the problems existing in the related art, the present application provides an exception handling method, a computing device and a storage medium, which can monitor the use of the operating system kernel by the container, thereby reducing the difficulty of exception troubleshooting.

[0005] On one hand, the present application provides an exception handling method, including:

[0006] The kernel of the operating system receives a run command for running the pre-installed application in the container;

[0007] In response to the running command, the kernel generates a kernel running log corresponding to the running command by running a preset log recording module, and executes the preset application program by running a preset program execution module.

[0008] In some embodiments, generating a kernel operation record log corresponding to the operation command by running a preset log record module includes:

[0009] A dynamic link library usage record log corresponding to the running command is generated by calling a preset dynamic link library including a preset log record module.

[0010] In some embodiments, in response to the run command, the kernel generates a kernel run record log corresponding to the run command by running a preset log record module, and processes the run command by running a preset program execution module, including:

[0011] In response to the run command, the kernel sequentially calls a preset dynamic link library including a preset log recording module and a preset process replacement function, so as to generate a dynamic link library usage record log corresponding to the run command through the log recording module, and executes the application by calling the preset process replacement function;

[0012] The preset process replacement function is packaged in the preset dynamic link library.

[0013] In some embodiments, after generating the kernel operation record log corresponding to the operation command by running a preset log record module, the process includes:

[0014] The kernel operation record log is sent to the visualization platform module to perform a visualization display of the kernel operation record log.

[0015] In some embodiments, the present invention further comprises:

[0016] When kernel parameters need to be configured during the operation of the preset application, the kernel configures the kernel parameters to specified values and makes this configuration valid only for the container;

[0017] The kernel executes the preset application based on the specified value.

[0018] In some embodiments, configuring the kernel parameter to a specified value and making the configuration valid only for the container includes:

[0019] The kernel parameter is configured to a specified value through a control group mechanism, and the scope of the specified value is limited to be valid for the container.

[0020] In some embodiments, configuring the kernel parameter to a specified value through a control groups mechanism and limiting the scope of the specified value to be valid for the container includes:

[0021] The hook procedure BPF_PROG_TYPE_CGROUP_SYSCTL attached to the control group is called, and the bpf_sysctl_get_name() function and the bpf_sysctl_set_new_value() function are called to configure the kernel parameter to the specified value.

[0022] Another aspect of the present application provides an exception handling method, comprising:

[0023] When kernel parameters need to be configured during the operation of a pre-installed application in a container, the kernel of the operating system configures the kernel parameters to specified values and makes this configuration valid only for the container;

[0024] The kernel executes the preset application based on the specified value.

[0025] In another aspect, the present application provides a computing device, comprising:

[0026] processor; and

[0027] The memory stores executable codes thereon, and when the executable codes are executed by the processor, the processor is caused to execute the method described above.

[0028] Another aspect of the present application provides a computer-readable storage medium having executable codes stored thereon. When the executable codes are executed by a processor of an electronic device, the processor is caused to execute the method described above.

[0029] In one embodiment of the present application, the operating system kernel generates a kernel operation record log corresponding to the operation commands of the pre-installed application in the container by running a preset logging module. In this way, the container's use of the operating system kernel can be monitored, thereby reducing the difficulty of anomaly troubleshooting. It is understandable that the monitoring of the container's use of the operating system kernel in this application includes the monitoring of the container's use of some resources of the operating system kernel.

[0030] In one embodiment of the present application, when kernel parameters need to be configured during the operation of a container application, the operating system kernel configures the kernel parameters to specified values, and this configuration is only valid for that container. By limiting the scope of the specified value to only that container, the effect of the container's kernel parameter configuration can be limited to the container itself, isolating it from other containers and the operating system kernel. This can prevent mutual influence between containers and between the container and the operating system kernel, thereby optimizing operating system performance while reducing the possibility of anomalies caused by the container application's configuration of the operating system kernel parameters.

[0031] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] The above and other objects, features and advantages of the present application will become more apparent by describing in more detail exemplary embodiments of the present application in conjunction with the accompanying drawings, wherein the same reference numerals generally represent the same components in the exemplary embodiments of the present application.

[0033] Figure 1 Shows the architecture diagram of the k8s system;

[0034] Figure 2 This is a flowchart of an exception handling method according to an embodiment of the present application;

[0035] Figure 3 A specific example of the exception handling method of the present application is exemplarily shown;

[0036] Figure 4 is a flowchart of an exception handling method according to another embodiment of the present application;

[0037] Figure 5 It is a structural diagram of a computing device shown in an embodiment of the present application. DETAILED DESCRIPTION

[0038] The following describes embodiments of the present application in more detail with reference to the accompanying drawings. Although the accompanying drawings illustrate embodiments of the present application, it should be understood that the present application can be implemented in various forms and should not be limited by the embodiments described herein. Rather, these embodiments are provided to make the present application more thorough and complete, and to fully convey the scope of the present application to those skilled in the art.

[0039] The terms used in this application are for the purpose of describing specific embodiments only and are not intended to limit this application. As used in this application and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include the plural forms, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

[0040] It should be understood that although the terms "first", "second", "third", etc. may be used in this application to describe various information, this information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of this application, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of this application, the meaning of "plurality" is two or more, unless otherwise clearly and specifically defined.

[0041] One embodiment of the present invention provides a computing device comprising a processor and a memory storing a computer program. When the processor executes the stored computer program, it can implement the exception handling method described below. The computing device can be, but is not limited to, a cloud server. It is understood that the cloud server can be a physical server or a logical server virtualized from multiple physical servers. The cloud server can also be a server cluster consisting of multiple interconnected and communicative servers, and each functional module can be distributed on each server in the server cluster.

[0042] In some embodiments, the computing device is Figure 1 A Node node in the k8s cluster shown.

[0043] Figure 2 A flowchart of an exception handling method according to an embodiment of the present invention is shown. The method according to this embodiment can be used in the above-mentioned computing device. Figure 2 , the exception handling method of this embodiment includes:

[0044] In step S210 , the kernel of the operating system receives a run command for running the application pre-installed in the container.

[0045] The container is pre-installed with the application's executable program and its dependent files (such as configuration files and required dynamic libraries). Multiple containers are isolated from each other and share the operating system kernel, which provides the runtime environment for the containerized applications. Once a container is running, it essentially becomes a thread under the operating system, and the operating system kernel responds to run commands from the containerized applications.

[0046] In this embodiment, the operating system can be a Linux operating system, and the container can be a Docker container. It is understood that this application is not limited to this. For example, the operating system can also be a Windows system, and the container can also be a Linux container, OpenVZ, jail, zone, etc. The following description uses the Linux operating system and Docker container as an example.

[0047] In step S220 , the kernel of the operating system responds to the run command by running a preset log recording module to generate a kernel run record log corresponding to the run command, and runs a preset program execution module to execute the preset application program.

[0048] The kernel is the heart of the operating system and includes multiple modules that implement basic functions such as virtual memory, multitasking, shared libraries, on-demand loading, executable programs, and TCP / IP networking. The Linux kernel includes modules such as storage management, process management, file system, device management, drivers, and network calls.

[0049] After the kernel of the operating system receives a run command for running the pre-installed application in the container, in response to the run command, the kernel generates a kernel run record log corresponding to the run command by running the preset log record module, and executes the preset application by running the preset program execution module.

[0050] In the related art, the use of the operating system kernel by the container is usually not monitored. Thus, when an exception occurs due to the operating system kernel running an application in a container, it is difficult to troubleshoot the cause of the exception due to the lack of monitoring. In the embodiment of the present application, the operating system kernel generates a kernel operation record log corresponding to the running command of the pre-installed application in the container by running a preset logging module. In this way, the use of the operating system kernel by the container can be monitored, thereby reducing the difficulty of troubleshooting the exception. It is understandable that the monitoring of the use of the operating system kernel by the container described in the present application includes the situation of monitoring the use of some resources of the operating system kernel by the container.

[0051] In some embodiments, the operating system kernel, in response to a run command for running a pre-installed application in a container, generates a log recording dynamic link library usage corresponding to the run command by invoking a pre-installed dynamic link library program that includes a pre-installed logging module. When a container is running, in most cases, invoking the operating system kernel will also invoke the dynamic link library it provides. In this embodiment, by recording the container's use of the dynamic link library, the container's use of the operating system kernel can be more effectively monitored without consuming excessive resources.

[0052] In some embodiments, in response to a run command for running a pre-installed application in a container, the kernel of an operating system sequentially calls a pre-installed dynamic link library including a pre-installed logging module and a pre-installed process replacement function, generates a dynamic link library usage log corresponding to the run command through the logging module, and executes the application by calling the pre-installed process replacement function; wherein the pre-installed process replacement function is packaged within the pre-installed dynamic link library. In a Linux system, the pre-installed process replacement function may be a function in the exec function family, such as execv() and execve().

[0053] In a specific example, the functions in the exec function family in the Linux dynamic link library file system lib.so are packaged in a dynamic link library that can be named, for example, wrapper.so, and the dynamic link library also includes a logging module for generating a log of the use of the dynamic link library. It can be understood that the logging module can be a function encapsulated in wrapper.so, such as a log printing function, or it can be a code block in wrapper.so that can be directly executed without additional calls. It can be understood that the logging module can be an existing module provided by the Linux system, or it can be obtained through open source channels, or it can be implemented by the developer himself, which will not be repeated here. After wrapper.so is configured in the dynamic link library file system lib.so, the kernel of the Linux system responds to the running commands of applications of different containers as follows. Figure 3 As shown, bin / mount, dynamic link library wrapper.so, and exec family functions are automatically called in this order, a dynamic link library usage log corresponding to the run command is generated through the logging module contained in wrapper.so, and the application is executed by calling the exec family function.

[0054] The exec family of functions provides a method for launching another program within a process. It locates an executable file based on a specified filename or directory name and replaces the data, code, and stack segments of the calling process with it. In other words, it executes an executable file within the calling process. The executable file can be a binary file or any Linux executable script. After execution, the contents of the calling process, except for the process identifier, are replaced by the contents of the new program.

[0055] In this embodiment, by packaging the exec family functions in a dynamic link library, and the dynamic link library also includes a logging module for generating a dynamic link library usage log, after wrapper.so can be configured in the dynamic link library file system lib.so, when the Linux system kernel responds to the running commands of applications in different containers, as long as the application is configured to call the dynamic link library, it can automatically call the dynamic link library wrapper.so and the exec family functions, thereby recording the use of the dynamic link library by all containers. In this way, even if the container application runs for a very short time, corresponding records can be generated, thereby improving the effectiveness and reliability of monitoring.

[0056] In some embodiments, the generated dynamic link library usage record log may, for example, include preset information fields of the service process in the corresponding container called, such as part or all of the process ID, parent process ID, service name, specific command, command path, time, and other information.

[0057] In some embodiments, after generating a kernel operation related record log corresponding to an operation command by running a preset log record module, the kernel operation record log is sent to a visualization platform module for visual display of the kernel operation record log.

[0058] The visualization platform module is used to collect, manage, and display various logs during the operation of container applications, including the kernel operation logs mentioned above. Furthermore, it can provide management functions such as search and classification for various logs and display them accordingly through the user terminal.

[0059] Through visualization, personnel at different stages such as development, testing, and maintenance can intuitively understand the kernel operation records, which can significantly improve the efficiency of solving abnormal problems in systems using containers.

[0060] Figure 4 FIG. 1 is a flow chart of an exception handling method according to another embodiment of the present invention. Figure 4 , the method of this embodiment includes:

[0061] In step S410 , when kernel parameters need to be configured during the operation of the pre-installed application in the container, the kernel of the operating system configures the kernel parameters to specified values, and makes this configuration valid only for the container.

[0062] In step S420 , the kernel executes the preset application based on the specified value.

[0063] The operating system kernel has many customizable parameters, also known as kernel parameters. Kernel parameters cover all aspects of the kernel, including networking and file systems. By dynamically setting the values of kernel parameters, the performance of the operating system can be optimized.

[0064] The kernel of the operating system allows applications in the container to configure specified kernel parameters. In related technologies, each container's application can configure the operating system's kernel parameters, and usually acts on the operating system and other containers, so the possibility of anomalies is high. In this application, when the kernel parameters need to be configured during the operation of the container's application, the kernel of the operating system configures the kernel parameters to the specified value, and makes this configuration valid only for the container. By limiting the scope of the specified value to be valid for the container, the container's configuration effect on the kernel parameters can be limited to the container, isolated from other containers and the operating system kernel, and mutual influence between containers and between containers and the operating system kernel can be avoided, thereby optimizing the operating system performance while reducing the possibility of anomalies caused by the container's application configuring the operating system's kernel parameters.

[0065] In some embodiments, configuring the kernel parameter to a specified value and making the configuration valid only for the container includes:

[0066] The kernel parameter is configured to a specified value through the control groups mechanism, and the scope of the specified value is limited to the container.

[0067] The kernel of the Linux system exposes the access interface of its kernel parameters through the procfs pseudo file system (also known as proc file system), which is mounted under the / proc directory. Through this access interface, the parameter values of the kernel parameters can be configured. The sysctl command is built into the Linux system, and the parameter values of the kernel parameters can be specified by this command through the procfs interface configuration. When the parameter values of the kernel parameters are configured in this way, it takes effect on the entire kernel. In the present embodiment, when the kernel parameters need to be configured during the application program operation of the container, the kernel forbids mounting the proc file system, and the kernel parameters are configured to specified values by the control group control group mechanism, and the scope of the specified value is limited to the container.

[0068] Control group, abbreviated as cgroup, is a mechanism provided by the Linux system kernel to limit, record, and isolate the system resources (such as CPU, memory, IO, etc.) occupied by processes in containers; by controlling the system resources allocated to containers, it can avoid competition for system resources when multiple containers are running at the same time. When the container is started, Docker creates a control group set for the container in the background. The control group is divided into several subsystems, each of which represents a facility or resource controller used to schedule the use of a certain type of resource, such as CPU clock, memory, block device, etc. The subsystem must be attached to a level to work. After a subsystem is attached to a level, all control groups on this level are controlled by this subsystem.

[0069] In a specific implementation, when kernel parameters need to be set during the execution of a process in a control group within a container, the kernel prohibits mounting the proc file system and calls the hook procedure BPF_PROG_TYPE_CGROUP_SYSCTL attached to the control group to configure the kernel parameters to the specified values by calling the bpf_sysctl_get_name() function and the bpf_sysctl_set_new_value() function.

[0070] The BPF_PROG_TYPE_CGROUP_SYSCTL program provides a cgroup-BPF hook for the sysctl command. This hook must be attached to a cgroup and is called every time a process within that cgroup attempts to read or write the sysctl in the proc. The sysctl command is represented by a name and a value. If calling the BPF_PROG_TYPE_CGROUP_SYSCTL program returns a result that allows access to kernel parameters, the bpf_sysctl_get_name() and bpf_sysctl_set_new_value() functions can be called. Calling the bpf_sysctl_get_name() function obtains the sysctl name, and calling the bpf_sysctl_set_new_value() function overwrites the new string value currently written to the sysctl before the actual write occurs. It can be understood that in this embodiment, the hook can be attached to different control groups of the container so that it can take effect in different subsystems within the container. It will be called every time a process in each control group within the container attempts to read or write to the sysctl.

[0071] Understandably, Figure 4 The method of the illustrated embodiment can be independent of Figure 2 Alternatively, it can also be implemented with Figure 2 The embodiments are implemented in combination.

[0072] Figure 5 The computing devices mentioned above are shown. Figure 5 , a computing device 500 according to an embodiment of the present application includes a memory 510 and a processor 520 .

[0073] The processor 520 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.

[0074] The memory 510 may include various types of storage units, such as system memory, read-only memory (ROM), and permanent storage devices. ROM may store static data or operating commands required by the processor 520 or other modules of the computer. The permanent storage device may be a readable and writable storage device. The permanent storage device may be a non-volatile storage device that retains the stored operating commands and data even after the computer is powered off. In some embodiments, the permanent storage device uses a large-capacity storage device (such as a magnetic or optical disk, flash memory) as the permanent storage device. In other embodiments, the permanent storage device may be a removable storage device (such as a floppy disk, optical drive). The system memory may be a readable and writable storage device or a volatile readable and writable storage device, such as dynamic random access memory. The system memory may store some or all operating commands and data required by the processor during operation. In addition, the memory 510 may include any combination of computer-readable storage media, including various types of semiconductor memory chips (such as DRAM, SRAM, SDRAM, flash memory, programmable read-only memory), and magnetic disks and / or optical disks may also be used. In some embodiments, the memory 510 may include a readable and / or writable removable storage device, such as a compact disc (CD), a read-only digital versatile disc (e.g., DVD-ROM, dual-layer DVD-ROM), a read-only Blu-ray disc, an ultra-density optical disc, a flash memory card (e.g., SD card, mini SD card, Micro-SD card, etc.), a magnetic floppy disk, etc. Computer-readable storage media do not include carrier waves and transient electronic signals transmitted wirelessly or wired.

[0075] The memory 510 stores executable codes. When the executable codes are processed by the processor 520 , the processor 520 may execute part or all of the above-mentioned methods.

[0076] In addition, the method according to the present application can also be implemented as a computer program or computer program product, which includes computer program code execution commands for executing some or all of the steps in the above method of the present application.

[0077] Alternatively, the present application can also be implemented as a computer-readable storage medium (or non-transitory machine-readable storage medium or machine-readable storage medium) on which executable code (or computer program or computer running command code) is stored. When the executable code (or computer program or computer running command code) is executed by a processor of an electronic device (or server, etc.), the processor executes part or all of the steps of the above-mentioned method according to the present application.

[0078] The embodiments of the present application have been described above. The above description is exemplary, not exhaustive, and is not limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is selected to best explain the principles of the embodiments, their practical applications, or improvements to the technology in the market, or to enable other persons skilled in the art to understand the embodiments disclosed herein.

Claims

1. An exception handling method, characterized in that: include: The kernel of the operating system receives a run command for running the pre-installed application in the container; In response to the running command, the kernel generates a kernel running record log corresponding to the running command by running a preset log recording module, and executes the preset application program by running a preset program execution module; The step of generating a kernel operation record log corresponding to the operation command by running a preset log record module includes: Generate a dynamic link library usage record log corresponding to the run command by calling a preset dynamic link library including a preset log record module; The kernel generates a kernel operation record log corresponding to the operation command by running a preset log record module in response to the operation command, and processes the operation command by running a preset program execution module, including: In response to the run command, the kernel sequentially calls a preset dynamic link library including a preset log recording module and a preset process replacement function, so as to generate a dynamic link library usage record log corresponding to the run command through the log recording module, and executes the application by calling the preset process replacement function; Wherein, the preset process replacement function is packaged in the preset dynamic link library; The preset process replacement function is a function in the exec function family; the functions in the exec function family in the dynamic link library file system are packaged in the dynamic link library, and the dynamic link library also includes a log recording module for generating a dynamic link library usage record log.

2. The method according to claim 1, characterized in that After generating the kernel operation record log corresponding to the operation command by running the preset log record module, the method further includes: The kernel operation record log is sent to the visualization platform module to perform a visualization display of the kernel operation record log.

3. The method according to claim 1, characterized in that Also includes: When kernel parameters need to be configured during the operation of the preset application, the kernel configures the kernel parameters to specified values and makes this configuration valid only for the container; The kernel executes the preset application based on the specified value.

4. The method according to claim 3, characterized in that Configuring the kernel parameter to a specified value and making the configuration valid only for the container includes: The kernel parameter is configured to a specified value through a control group mechanism, and the scope of the specified value is limited to be valid for the container.

5. The method according to claim 4, characterized in that Configuring the kernel parameter to a specified value through a control group controlgroups mechanism and limiting the scope of the specified value to be valid for the container includes: The hook procedure BPF_PROG_TYPE_CGROUP_SYSCTL attached to the control group is called, and the bpf_sysctl_get_name() function and the bpf_sysctl_set_new_value() function are called to configure the kernel parameter to the specified value.

6. An exception handling method, characterized in that: include: When kernel parameters need to be configured during the operation of a pre-installed application in a container, the kernel of the operating system configures the kernel parameters to specified values and makes this configuration valid only for the container; The kernel executes the preset application based on the specified value; Configuring the kernel parameter to a specified value and making the configuration valid only for the container includes: The kernel parameter is configured to a specified value through a control group mechanism, and the scope of the specified value is limited to be valid for the container; When kernel parameters need to be set during the operation of a process in a control group within a container, the kernel prohibits mounting the proc file system and calls the hook program BPF_PROG_TYPE_CGROUP_SYSCTL attached to the control group to configure the kernel parameters to the specified values by calling the bpf_sysctl_get_name() function and the bpf_sysctl_set_new_value() function; the BPF_PROG_TYPE_CGROUP_SYSCTL program provides a cgroup-bpf hook for the sysctl command, which is attached to a cgroup and is called every time a process in the cgroup attempts to read or write the sysctl in the proc; the sysctl command is represented by a name and a value; if calling the BPF_PROG_TYPE_CGROUP_SYSCTL program returns a result that allows access to kernel parameters, you can continue to call the bpf_sysctl_get_name() and bpf_sysctl_set_new_value() functions; calling bpf_sysctl_get_name( ) function to get the sysctl name and call the bpf_sysctl_set_new_value() function to overwrite the new string value currently written to the sysctl before the write occurs.

7. A computing device, characterized in that include: processor; as well as A memory having executable codes stored thereon, which, when executed by the processor, causes the processor to perform the method according to any one of claims 1 to 6. 8 . A computer-readable storage medium having executable codes stored thereon, wherein when the executable codes are executed by a processor of an electronic device, the processor is caused to execute the method according to claim 1 .

Images