CN107545186B - Method, device and system for rapidly solving problem of engine non-work - Google Patents
Method, device and system for rapidly solving problem of engine non-work Download PDFInfo
- Publication number
- CN107545186B CN107545186B CN201710794717.1A CN201710794717A CN107545186B CN 107545186 B CN107545186 B CN 107545186B CN 201710794717 A CN201710794717 A CN 201710794717A CN 107545186 B CN107545186 B CN 107545186B
- Authority
- CN
- China
- Prior art keywords
- target
- monitoring
- monitoring parameter
- engine
- parameter
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Landscapes
- Combined Controls Of Internal Combustion Engines (AREA)
Abstract
The invention provides a method, a device and a system for rapidly solving the problem of engine non-work, which relate to the technical field of information security, and the method comprises the following steps: monitoring the state parameters of the target engine at the current moment through a monitoring program, wherein the monitoring program is a program pre-installed in the target engine, and the state parameters comprise: a process name and/or process number of the target engine; analyzing the state parameters to determine monitoring parameters of the target engine, wherein the monitoring parameters are used for determining the running state of the target engine at the current moment; calling the target script based on the monitoring parameters to execute target operation, wherein the target operation comprises the following steps: the starting operation or the restarting operation relieves the technical problem that the operation is passive and complicated when the problem that the engine does not work is solved by the existing mode.
Description
Technical Field
The invention relates to the technical field of information security, in particular to a method, a device and a system for rapidly solving the problem that an engine does not work.
Background
With the rapid development of network technology, how to discover security vulnerabilities in a network before hackers and repair the security vulnerabilities in advance is frequent in the current network security events, and a vulnerability scanning engine plays a critical role in the discovery. The scanning engine can find various vulnerability risks in software and hardware through uninterrupted scanning, can provide safety guarantee for data users, provides a solution for early processing, and prevents information leakage. In the current state of the art, once any event occurs, the engine can: if the engine is abnormally stopped in a false dead state, the whole system cannot normally operate. Such a situation usually occurs, and the system will report an error or no response directly, and the engine itself has no function of restarting, etc. If need solve the problem, then need the manual work to go to judge corresponding problem and carry out corresponding execution, this is quite passive, and is also very loaded down with trivial details, simultaneously also greatly reduced work efficiency. The prior art only has a monitoring program, but does not have an actual execution program, and a series of operations can be completed through the technical program.
In view of the above problems, no effective solution has been proposed in the prior art.
Disclosure of Invention
In view of the above, an object of the present invention is to provide a method, an apparatus and a system for quickly solving the problem of engine inoperability, so as to alleviate the technical problem of passive and tedious operation when solving the problem of engine inoperability in the existing manner.
In a first aspect, an embodiment of the present invention provides a method for quickly resolving engine inoperability, including: monitoring the state parameters of a target engine at the current moment through a monitoring program, wherein the monitoring program is a program pre-installed in the target engine, and the state parameters comprise: a process name and/or a process number of the target engine; analyzing the state parameters to determine monitoring parameters of the target engine, wherein the monitoring parameters are used for determining the running state of the target engine at the current moment; calling a target script based on the monitoring parameters to execute a target operation, wherein the target operation comprises: a start-up operation or a restart operation.
Further, analyzing the state parameter to determine a monitoring parameter of the target engine comprises: when the state parameter does not include the process name of the target engine, determining that the monitoring parameter is a first monitoring parameter; when the state parameter comprises the process name of the target engine and does not comprise the process number of the target engine, determining that the monitoring parameter is a second monitoring parameter; when the state parameters simultaneously comprise the process name and the process number of the target engine, determining the monitoring parameters as third monitoring parameters; and when the state parameters comprise the attached process of the target engine and the state of the attached process is an abnormal state, determining that the monitoring parameters are fourth monitoring parameters.
Further, invoking a target script based on the monitoring parameter to perform a target operation includes: judging whether the monitoring parameter at the current moment is the third monitoring parameter; under the condition that the monitoring parameter at the current moment is judged to be the third monitoring parameter, the target script is not called; and under the condition that the monitoring parameter at the current moment is judged not to be the third monitoring parameter, calling the target script to execute the target operation.
Further, when it is determined that the monitoring parameter at the current time is not the third monitoring parameter, invoking the target script to execute the target operation includes: and under the condition that the monitoring parameter is the first monitoring parameter, calling a first execution command in the target script to execute the starting operation through the first execution command, wherein the starting operation is the operation of starting the target engine.
Further, the restarting operation includes a first restarting operation, and if it is determined that the monitoring parameter at the current time is not the third monitoring parameter, the target script is called to execute the target operation, including: and under the condition that the monitoring parameter is the second monitoring parameter, calling a second execution command in the target script to execute a first restarting operation through the second execution command, wherein the first restarting operation is an operation of restarting the target engine.
Further, the restarting operation includes a second restarting operation, and if it is determined that the monitoring parameter at the current time is not the third monitoring parameter, the target script is called to execute the target operation, including: and under the condition that the monitoring parameter is the fourth monitoring parameter, calling a third execution command in the target script to execute a second restart operation through the third execution command, wherein the second restart operation is an operation of restarting an attached control program, and the control program is a program which causes the target engine to be in a locked state.
In a second aspect, an embodiment of the present invention further provides an apparatus for quickly resolving engine inactivity, including: the monitoring unit is used for monitoring the state parameters of the target engine at the current moment through a monitoring program, wherein the monitoring program is a program pre-installed in the target engine, and the state parameters comprise: a process name and/or a process number of the target engine; the analysis unit is used for analyzing the state parameters to determine monitoring parameters of the target engine, and the monitoring parameters are used for determining the running state of the target engine at the current moment; a calling unit, configured to call a target script based on the monitoring parameter to execute a target operation, where the target operation includes: a start-up operation or a restart operation.
Further, the analysis unit is configured to: when the state parameter does not include the process name of the target engine, determining that the monitoring parameter is a first monitoring parameter; when the state parameter comprises the process name of the target engine and does not comprise the process number of the target engine, determining that the monitoring parameter is a second monitoring parameter; when the state parameters simultaneously comprise the process name and the process number of the target engine, determining the monitoring parameters as third monitoring parameters; and when the state parameters comprise the attached process of the target engine and the state of the attached process is an abnormal state, determining that the monitoring parameters are fourth monitoring parameters.
Further, the calling unit is configured to: judging whether the monitoring parameter at the current moment is the third monitoring parameter; under the condition that the monitoring parameter at the current moment is judged to be the third monitoring parameter, the target script is not called; and under the condition that the monitoring parameter at the current moment is judged not to be the third monitoring parameter, calling the target script to execute the target operation.
In a second aspect, embodiments of the present invention also provide a computer-readable medium having non-volatile program code executable by a processor, the program code causing the processor to perform the method recited in the claims above.
In the embodiment of the invention, firstly, the state parameters of the target engine at the current moment are monitored through a monitoring program; then, the monitoring program analyzes the state parameters to determine monitoring parameters of the target engine, so that the monitoring program calls the target script based on the monitoring parameters to execute target operation, wherein the target operation comprises a starting operation or a restarting operation. In the embodiment of the invention, a monitoring program is arranged in the engine to regularly acquire the state parameters of the engine, and the target script is judged and called according to the current state parameters of the engine, so that the corresponding operation is executed by the target script under the condition that the current engine is unavailable or the engine is abnormal, thereby completing the running state of the current engine, further relieving the technical problem that the operation is more passive and more complicated when the problem that the engine does not work is solved by the existing mode, and further realizing the technical effect of improving the solving speed for solving the problem that the engine does not work.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
In order to make the aforementioned and other objects, features and advantages of the present invention comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.
FIG. 1 is a flow diagram of a method for rapidly resolving engine inactivity in accordance with an embodiment of the present invention;
FIG. 2 is a flow diagram of another method for rapidly resolving engine inactivity in accordance with an embodiment of the present invention;
FIG. 3 is a schematic diagram of an apparatus for rapidly resolving engine inactivity in accordance with an embodiment of the present invention;
FIG. 4 is a schematic diagram of a system for rapidly resolving engine inactivity in accordance with an embodiment of the present invention.
Detailed Description
To make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings, and it is apparent that the described embodiments are some, but not all embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The first embodiment is as follows:
in accordance with an embodiment of the present invention, there is provided an embodiment of a method for quickly resolving engine downtime, it being noted that the steps illustrated in the flowchart of the drawings may be performed in a computer system such as a set of computer-executable instructions and that, although a logical order is illustrated in the flowchart, in some cases the steps illustrated or described may be performed in an order different than that presented herein.
Fig. 1 is a flow chart of a method for rapidly resolving engine inactivity, according to an embodiment of the present invention, as shown in fig. 1, the method comprising the steps of:
step S102, monitoring the state parameters of the target engine at the current moment through a monitoring program, wherein the monitoring program is a program pre-installed in the target engine, and the state parameters comprise: a process name and/or process number of the target engine;
it should be noted that, in the embodiment of the present invention, the engine state of the target engine may be periodically checked by the monitoring program, that is, the state parameter of the target engine is periodically acquired, so that the engine state of the target engine is determined through analysis of the state parameter. Wherein the engine states include: the engine is not started, the engine is dead in a false mode, the engine is always restarted, the engine is unavailable, and the like.
Step S104, analyzing the state parameters to determine monitoring parameters of the target engine, wherein the monitoring parameters are used for determining the running state of the target engine at the current moment;
step S106, calling a target script based on the monitoring parameters to execute target operation, wherein the target operation comprises the following steps: a start-up operation or a restart operation.
In the embodiment of the present invention, when the monitoring program monitors that the target engine is unavailable or in an abnormal state, the target script preset inside the target engine may be called to execute a target operation according to the target script, that is, a start operation or a restart operation.
The target script includes an execution start engine script, a restart engine service, a restart control program that causes an engine lock-up, and the like.
In the embodiment of the invention, firstly, the state parameters of the target engine at the current moment are monitored through a monitoring program; then, the monitoring program analyzes the state parameters to determine monitoring parameters of the target engine, so that the monitoring program calls the target script based on the monitoring parameters to execute target operation, wherein the target operation comprises a starting operation or a restarting operation. In the embodiment of the invention, a monitoring program is arranged in the engine to regularly acquire the state parameters of the engine, and the target script is judged and called according to the current state parameters of the engine, so that the corresponding operation is executed by the target script under the condition that the current engine is unavailable or the engine is abnormal, thereby completing the running state of the current engine, further relieving the technical problem that the operation is more passive and more complicated when the problem that the engine does not work is solved by the existing mode, and further realizing the technical effect of improving the solving speed for solving the problem that the engine does not work.
In an optional embodiment, the step S104 of analyzing the state parameter to determine the monitoring parameter of the target engine includes the following steps:
step S1041, when the state parameter does not include the process name of the target engine, determining the monitoring parameter as a first monitoring parameter;
step S1042, when the state parameter includes the process name of the target engine and does not include the process number of the target engine, determining the monitoring parameter as a second monitoring parameter;
step S1043, when the state parameter includes the process name and the process number of the target engine at the same time, determining the monitoring parameter as a third monitoring parameter;
step S1044 is to determine that the monitoring parameter is the fourth monitoring parameter when the status parameter includes the attach process of the target engine and the status of the attach process is the abnormal status.
In the embodiment of the invention, a monitoring program is started firstly, then, the state parameters of the target engine are obtained periodically through the monitoring program, and the state parameters are analyzed to determine the monitoring parameters of the target engine, wherein the state parameters comprise a process name and a process number.
If the engine process does not exist in the state parameters, returning that the state is 1 (namely, the first monitoring parameter is 1); if the engine process exists in the state parameters but the process number does not exist, returning the state to be 2 (namely, the second monitoring parameter); if the engine process and the process number exist in the state parameters, the engine is normal, and the state 0 (namely, the third monitoring parameter) is returned at the same time; if the attached process state of the target engine is found to be abnormal, the state is returned to be 3 (namely, the fourth monitoring parameter).
In another alternative embodiment, invoking the target script based on the monitored parameters to perform the target operation comprises the steps of:
judging whether the monitoring parameter at the current moment is a third monitoring parameter;
under the condition that the current monitoring parameter is judged to be the third monitoring parameter, the target script is not called;
and under the condition that the monitoring parameter at the current moment is not the third monitoring parameter, calling the target script to execute the target operation.
In the embodiment of the invention, after the monitoring program acquires the monitoring parameters of the target engine, the monitoring parameters are returned to the target engine, so that the target engine executes the target operation based on the monitoring parameters.
Specifically, the target engine determines whether the monitoring parameter returned by the monitoring program at the current time is the third monitoring parameter, that is, the target engine determines whether the monitoring parameter returned by the monitoring program at the current time is 0. If the judgment result is 0, the target engine is in a normal state, and no processing is performed at this time. If the monitoring parameter is judged not to be 0, the target script is called to execute a corresponding command in the script, so that the target engine is controlled to execute a target operation, such as starting or restarting.
In another optional embodiment, in a case that it is determined that the current monitoring parameter is not the third monitoring parameter, invoking the target script to perform the target operation includes the following steps:
and under the condition that the monitoring parameter is the first monitoring parameter, calling a first execution command in the target script to execute a starting operation through the first execution command, wherein the starting operation is an operation of starting the target engine.
Specifically, if the current target engine is found to have no relevant process, returning to be the first monitoring parameter 1; and simultaneously calling the target script and calling a first execution command in the target script, for example, executing a first execution command enginestart.
In another optional embodiment, the restarting operation includes a first restarting operation, and in the case that it is determined that the monitoring parameter at the current time is not the third monitoring parameter, the calling the target script to execute the target operation includes the following steps:
and under the condition that the monitoring parameter is a second monitoring parameter, calling a second execution command in the target script to execute a first restarting operation through the second execution command, wherein the first restarting operation is an operation of restarting the target engine.
Specifically, if the current target engine is found to have a relevant process but no process number, the target engine is in a false death state, and then the second monitoring parameter 2 is returned; and simultaneously calling the target script to execute a second execution command in the target script, for example, executing a second execution command enginerestart.
In another optional embodiment, the restarting operation includes a second restarting operation, and in the case that it is determined that the monitoring parameter at the current time is not the third monitoring parameter, the invoking the target script to execute the target operation includes the following steps:
and under the condition that the monitoring parameter is a fourth monitoring parameter, calling a third execution command in the target script to execute a second restarting operation through the third execution command, wherein the second restarting operation is an operation of restarting the attached control program, and the control program is a program which causes the target engine to be in a locked state.
Specifically, if the attached process of the current target engine is found to be in a state exception, for example, a dongle exception or the like, the target script is called, and a third execution command of the target script program is executed, for example, a third execution command usbserver restart is executed, so as to restart the attached control program, where the control program is a program that causes the target engine to be in a lock-up state.
Compared with the prior art, the method for rapidly solving the problem that the engine does not work has the advantages that:
the invention can quickly and automatically discover the current state of the engine and carry out corresponding processing, and the method mainly carries out automatic starting and restarting under the condition that the engine state is unavailable so as to keep the engine in an available state. Therefore, more unnecessary participation can be reduced, and excessive manual participation of related technologies, users and the like can be reduced.
To sum up, the method for rapidly solving the engine failure provided by the embodiments is described by taking a schematic diagram of the method for rapidly solving the engine failure shown in fig. 2 as an example for intuitively understanding the above process, and the method mainly includes:
step A: starting a monitoring program, wherein the monitoring program is started along with the system starting, and the program runs immediately after the system starting;
and B: the monitoring program monitors and scans the current engine in real time to monitor whether the current engine is in a normal operation state, for example, the monitoring program may analyze the acquired state parameters, that is, analyze the current process and the process number of the current engine, so as to acquire one monitoring parameter, that is, the first monitoring parameter to the fourth monitoring parameter, (that is, the 0/1/2/3 monitoring parameters); if the current stealth is in a normal operation state, outputting information that the engine state is normal;
and C: returning the current monitoring parameters of the current engine obtained in the step B;
step D: and executing a corresponding command according to the returned monitoring parameters: for example, take an engine monitoring parameter returned in step C;
step E: execute the start engine command (i.e., the first execution command described above): specifically, the determination may be performed according to the returned monitoring parameter, and whether to execute the first command is determined according to the determination result: if the obtained monitoring parameter is 0, no processing is performed, and if the monitoring parameter is 1, a corresponding first execution command is executed, namely, a command for starting the current engine;
step F: executing the restart engine command: if the monitoring parameter is 2, executing a corresponding first execution command, namely, executing a restart engine and service (enginerestart.sh);
step H: executing a restart control program command: and if the monitoring parameter is 3, giving a corresponding command, and executing a third execution command to restart the control program service (usbserver restart). The specific implementation process is as above, and is not described herein again.
Example two:
the embodiment of the present invention further provides a device for rapidly solving the engine downtime, where the device is mainly used to execute the method for rapidly solving the engine downtime provided by the above-mentioned embodiment of the present invention, and the device for rapidly solving the engine downtime provided by the embodiment of the present invention is specifically described below.
Fig. 3 is a schematic diagram of an apparatus for rapidly resolving engine inactivity according to an embodiment of the present invention, as shown in fig. 3, the apparatus for rapidly resolving engine inactivity mainly includes: a monitoring unit 31, an analyzing unit 32 and a calling unit 33, wherein:
the monitoring unit 31 is configured to monitor a status parameter of the target engine at the current time through a monitoring program, where the monitoring program is a program pre-installed in the target engine, and the status parameter includes: a process name and/or process number of the target engine;
the analysis unit 32 is configured to analyze the state parameter to determine a monitoring parameter of the target engine, where the monitoring parameter is used to determine an operating state of the target engine at the current time;
a calling unit 33, configured to call the target script based on the monitoring parameter to perform a target operation, where the target operation includes: a start-up operation or a restart operation.
In the embodiment of the invention, firstly, the state parameters of the target engine at the current moment are monitored through a monitoring program; then, the monitoring program analyzes the state parameters to determine monitoring parameters of the target engine, so that the monitoring program calls the target script based on the monitoring parameters to execute target operation, wherein the target operation comprises a starting operation or a restarting operation. In the embodiment of the invention, a monitoring program is arranged in the engine to regularly acquire the state parameters of the engine, and the target script is judged and called according to the current state parameters of the engine, so that the corresponding operation is executed by the target script under the condition that the current engine is unavailable or the engine is abnormal, thereby completing the running state of the current engine, further relieving the technical problem that the operation is more passive and more complicated when the problem that the engine does not work is solved by the existing mode, and further realizing the technical effect of improving the solving speed for solving the problem that the engine does not work.
Optionally, the analysis unit is configured to: when the state parameter does not include the process name of the target engine, determining the monitoring parameter as a first monitoring parameter; when the state parameter comprises the process name of the target engine and does not comprise the process number of the target engine, determining the monitoring parameter as a second monitoring parameter; when the state parameters simultaneously comprise the process name and the process number of the target engine, determining the monitoring parameters as third monitoring parameters; and when the state parameters comprise the attached process of the target engine and the state of the attached process is an abnormal state, determining the monitoring parameters as fourth monitoring parameters.
Optionally, the invoking unit is configured to: judging whether the monitoring parameter at the current moment is a third monitoring parameter; under the condition that the current monitoring parameter is judged to be the third monitoring parameter, the target script is not called; and under the condition that the monitoring parameter at the current moment is not the third monitoring parameter, calling the target script to execute the target operation.
Optionally, the invoking unit is further configured to: and under the condition that the monitoring parameter is the first monitoring parameter, calling a first execution command in the target script to execute a starting operation through the first execution command, wherein the starting operation is an operation of starting the target engine.
Optionally, the invoking unit is further configured to: and under the condition that the monitoring parameter is a second monitoring parameter, calling a second execution command in the target script to execute a first restarting operation through the second execution command, wherein the first restarting operation is an operation of restarting the target engine.
Optionally, the invoking unit is further configured to: and under the condition that the monitoring parameter is a fourth monitoring parameter, calling a third execution command in the target script to execute a second restarting operation through the third execution command, wherein the second restarting operation is an operation of restarting the attached control program, and the control program is a program which causes the target engine to be in a locked state.
The device provided by the embodiment of the present invention has the same implementation principle and technical effect as the method embodiments, and for the sake of brief description, reference may be made to the corresponding contents in the method embodiments without reference to the device embodiments.
Example three:
referring to fig. 4, an embodiment of the present invention further provides a system 100 for rapidly resolving engine inactivity, including: a processor 400, a memory 401, a bus 402 and a communication interface 403, wherein the processor 400, the communication interface 403 and the memory 401 are connected through the bus 402; the processor 400 is used to execute executable modules, such as computer programs, stored in the memory 401.
The Memory 401 may include a high-speed Random Access Memory (RAM) and may also include a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. The communication connection between the network element of the system and at least one other network element is realized through at least one communication interface 403 (which may be wired or wireless), and the internet, a wide area network, a local network, a metropolitan area network, and the like can be used.
Bus 402 can be an ISA bus, PCI bus, EISA bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one double-headed arrow is shown in FIG. 4, but that does not indicate only one bus or one type of bus.
The memory 401 is configured to store a program, and the processor 400 executes the program after receiving an execution instruction, and the method executed by the apparatus defined by the flow process disclosed in any of the foregoing embodiments of the present invention may be applied to the processor 400, or implemented by the processor 400.
The processor 40 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 400. The Processor 400 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the device can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, or a discrete hardware component. The various methods, steps and logic blocks disclosed in the embodiments of the present invention may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 401, and the processor 400 reads the information in the memory 401 and completes the steps of the method in combination with the hardware.
In addition, in the description of the embodiments of the present invention, unless otherwise explicitly specified or limited, the terms "mounted," "connected," and "connected" are to be construed broadly, e.g., as meaning either a fixed connection, a removable connection, or an integral connection; can be mechanically or electrically connected; they may be connected directly or indirectly through intervening media, or they may be interconnected between two elements. The specific meanings of the above terms in the present invention can be understood in specific cases to those skilled in the art.
In the description of the present invention, it should be noted that the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer", etc., indicate orientations or positional relationships based on the orientations or positional relationships shown in the drawings, and are only for convenience of description and simplicity of description, but do not indicate or imply that the device or element being referred to must have a particular orientation, be constructed and operated in a particular orientation, and thus, should not be construed as limiting the present invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance.
The computer program product of the method, the apparatus, and the system for quickly solving the engine downtime provided by the embodiments of the present invention includes a computer-readable storage medium storing a non-volatile program code executable by a processor, where instructions included in the program code may be used to execute the method described in the foregoing method embodiments, and specific implementation may refer to the method embodiments, and will not be described herein again.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and there may be other divisions when actually implemented, and for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or units through some communication interfaces, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a non-volatile computer-readable storage medium executable by a processor. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
Finally, it should be noted that: the above-mentioned embodiments are only specific embodiments of the present invention, which are used for illustrating the technical solutions of the present invention and not for limiting the same, and the protection scope of the present invention is not limited thereto, although the present invention is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: any person skilled in the art can modify or easily conceive the technical solutions described in the foregoing embodiments or equivalent substitutes for some technical features within the technical scope of the present disclosure; such modifications, changes or substitutions do not depart from the spirit and scope of the embodiments of the present invention, and they should be construed as being included therein. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (4)
1. A method for quickly resolving engine inactivity, comprising:
monitoring the state parameters of a target engine at the current moment through a monitoring program, wherein the monitoring program is a program pre-installed in the target engine, and the state parameters comprise: a process name and/or a process number of the target engine;
analyzing the state parameters to determine monitoring parameters of the target engine, wherein the monitoring parameters are used for determining the running state of the target engine at the current moment;
calling a target script based on the monitoring parameters to execute a target operation, wherein the target operation comprises: a start operation or a restart operation;
analyzing the state parameters to determine monitoring parameters of the target engine comprises:
when the state parameter does not include the process name of the target engine, determining that the monitoring parameter is a first monitoring parameter;
when the state parameter comprises the process name of the target engine and does not comprise the process number of the target engine, determining that the monitoring parameter is a second monitoring parameter;
when the state parameters simultaneously comprise the process name and the process number of the target engine, determining the monitoring parameters as third monitoring parameters;
when the state parameter comprises an attached process of the target engine and the state of the attached process is an abnormal state, determining that the monitoring parameter is a fourth monitoring parameter;
calling a target script based on the monitoring parameters to execute target operation, wherein the target operation comprises the following steps:
judging whether the monitoring parameter at the current moment is the third monitoring parameter;
under the condition that the monitoring parameter at the current moment is judged to be the third monitoring parameter, the target script is not called;
calling the target script to execute the target operation under the condition that the monitoring parameter at the current moment is judged not to be the third monitoring parameter;
the restarting operation comprises a first restarting operation, and when the monitoring parameter at the current moment is judged not to be the third monitoring parameter, the target script is called to execute the target operation, wherein the target operation comprises the following steps:
calling a second execution command in the target script under the condition that the monitoring parameter is the second monitoring parameter so as to execute a first restarting operation through the second execution command, wherein the first restarting operation is an operation of restarting the target engine;
the restarting operation comprises a second restarting operation, and when the monitoring parameter at the current moment is judged not to be the third monitoring parameter, the target script is called to execute the target operation, wherein the target operation comprises the following steps:
and under the condition that the monitoring parameter is the fourth monitoring parameter, calling a third execution command in the target script to execute a second restart operation through the third execution command, wherein the second restart operation is an operation of restarting an attached control program, and the control program is a program which causes the target engine to be in a locked state.
2. The method of claim 1, wherein, in a case that it is determined that the monitoring parameter at the current time is not the third monitoring parameter, invoking the target script to perform the target operation comprises:
and under the condition that the monitoring parameter is the first monitoring parameter, calling a first execution command in the target script to execute the starting operation through the first execution command, wherein the starting operation is the operation of starting the target engine.
3. An apparatus for quickly resolving engine inactivity, comprising:
the monitoring unit is used for monitoring the state parameters of the target engine at the current moment through a monitoring program, wherein the monitoring program is a program pre-installed in the target engine, and the state parameters comprise: a process name and/or a process number of the target engine;
the analysis unit is used for analyzing the state parameters to determine monitoring parameters of the target engine, and the monitoring parameters are used for determining the running state of the target engine at the current moment;
a calling unit, configured to call a target script based on the monitoring parameter to execute a target operation, where the target operation includes: a start operation or a restart operation;
the analysis unit is configured to:
when the state parameter does not include the process name of the target engine, determining that the monitoring parameter is a first monitoring parameter;
when the state parameter comprises the process name of the target engine and does not comprise the process number of the target engine, determining that the monitoring parameter is a second monitoring parameter;
when the state parameters simultaneously comprise the process name and the process number of the target engine, determining the monitoring parameters as third monitoring parameters;
when the state parameter comprises an attached process of the target engine and the state of the attached process is an abnormal state, determining that the monitoring parameter is a fourth monitoring parameter;
the calling unit is used for:
judging whether the monitoring parameter at the current moment is the third monitoring parameter;
under the condition that the monitoring parameter at the current moment is judged to be the third monitoring parameter, the target script is not called;
calling the target script to execute the target operation under the condition that the monitoring parameter at the current moment is judged not to be the third monitoring parameter;
the restarting operation comprises a first restarting operation, and when the monitoring parameter at the current moment is judged not to be the third monitoring parameter, the target script is called to execute the target operation, wherein the target operation comprises the following steps:
calling a second execution command in the target script under the condition that the monitoring parameter is the second monitoring parameter so as to execute a first restarting operation through the second execution command, wherein the first restarting operation is an operation of restarting the target engine;
the restarting operation comprises a second restarting operation, and when the monitoring parameter at the current moment is judged not to be the third monitoring parameter, the target script is called to execute the target operation, wherein the target operation comprises the following steps:
and under the condition that the monitoring parameter is the fourth monitoring parameter, calling a third execution command in the target script to execute a second restart operation through the third execution command, wherein the second restart operation is an operation of restarting an attached control program, and the control program is a program which causes the target engine to be in a locked state.
4. A computer-readable medium having non-volatile program code executable by a processor, the program code causing the processor to perform the method of any of claims 1-2.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710794717.1A CN107545186B (en) | 2017-09-06 | 2017-09-06 | Method, device and system for rapidly solving problem of engine non-work |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710794717.1A CN107545186B (en) | 2017-09-06 | 2017-09-06 | Method, device and system for rapidly solving problem of engine non-work |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107545186A CN107545186A (en) | 2018-01-05 |
| CN107545186B true CN107545186B (en) | 2020-03-17 |
Family
ID=60959259
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710794717.1A Active CN107545186B (en) | 2017-09-06 | 2017-09-06 | Method, device and system for rapidly solving problem of engine non-work |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107545186B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111898158B (en) * | 2020-07-23 | 2023-09-26 | 百望股份有限公司 | Encryption method of OFD (optical frequency division) document |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101969391A (en) * | 2010-10-27 | 2011-02-09 | 北京邮电大学 | Cloud platform supporting fusion network service and operating method thereof |
| CN102521099A (en) * | 2011-11-24 | 2012-06-27 | 深圳市同洲视讯传媒有限公司 | Process monitoring method and process monitoring system |
| CN104022857A (en) * | 2014-06-23 | 2014-09-03 | 浪潮电子信息产业股份有限公司 | Server engine frame design method based on multiple working modes |
| CN104199772A (en) * | 2014-09-02 | 2014-12-10 | 浪潮(北京)电子信息产业有限公司 | Progress supervising method and device |
| CN104778042A (en) * | 2015-03-30 | 2015-07-15 | 江苏省邮电规划设计院有限责任公司 | Stream data processing method based on event stream processing and plug-in type development framework |
-
2017
- 2017-09-06 CN CN201710794717.1A patent/CN107545186B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101969391A (en) * | 2010-10-27 | 2011-02-09 | 北京邮电大学 | Cloud platform supporting fusion network service and operating method thereof |
| CN102521099A (en) * | 2011-11-24 | 2012-06-27 | 深圳市同洲视讯传媒有限公司 | Process monitoring method and process monitoring system |
| CN104022857A (en) * | 2014-06-23 | 2014-09-03 | 浪潮电子信息产业股份有限公司 | Server engine frame design method based on multiple working modes |
| CN104199772A (en) * | 2014-09-02 | 2014-12-10 | 浪潮(北京)电子信息产业有限公司 | Progress supervising method and device |
| CN104778042A (en) * | 2015-03-30 | 2015-07-15 | 江苏省邮电规划设计院有限责任公司 | Stream data processing method based on event stream processing and plug-in type development framework |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107545186A (en) | 2018-01-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20220201534A1 (en) | Method and device for determining terminal behavior analysis | |
| CN107704360B (en) | Monitoring data processing method, equipment, server and storage medium | |
| CN107948744B (en) | Interface detection method, interface detection device, and computer-readable storage medium | |
| CN108363653B (en) | Deployment method and device of monitoring system, computer equipment and storage medium | |
| CN111405006B (en) | Method and device for processing remote login failure and remote login system | |
| CN110119350B (en) | Software development kit testing method, device and equipment and computer storage medium | |
| EP3522449B1 (en) | Service state transition method and device | |
| CN107545186B (en) | Method, device and system for rapidly solving problem of engine non-work | |
| CN106506278B (en) | Service availability monitoring method and device | |
| CN111061448A (en) | Log information display method and device, electronic equipment and storage medium | |
| CN110618853A (en) | Detection method, device and equipment for zombie container | |
| CN111737060A (en) | Method and device for processing component exception and electronic equipment | |
| CN110413437B (en) | Network namespace exception handling method, device and equipment and readable storage medium | |
| US20230315620A1 (en) | System and Method for Diagnosing a Computing Device in Safe Mode | |
| CN111190761B (en) | Log output method and device, storage medium and electronic equipment | |
| CN104298924A (en) | Method and device for ensuring system safety and terminal | |
| CN113162815A (en) | Flow switching method, system, equipment and medium | |
| CN111723374A (en) | Vulnerability scanning method and device | |
| KR20210113595A (en) | Anomaly handling method, terminal device and storage medium | |
| CN107959595B (en) | Method, device and system for anomaly detection | |
| CN114528350A (en) | Cluster split brain processing method, device and equipment and readable storage medium | |
| CN114037539A (en) | Method and device for detecting single-link failure of insurance | |
| CN107623602B (en) | Automatic checking method and system | |
| CN110795321A (en) | Misoperation processing method and device and terminal equipment | |
| CN110752950A (en) | Update detection method and device for cloud resource pool and terminal equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: 310052 188 Lianhui street, Xixing street, Binjiang District, Hangzhou, Zhejiang Province Applicant after: Hangzhou Annan information technology Limited by Share Ltd Address before: Zhejiang Zhongcai Building No. 68 Binjiang District road Hangzhou City, Zhejiang Province, the 310051 and 15 layer Applicant before: Dbappsecurity Co.,ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |