CN116244113B - System downtime obstacle avoidance and restoration method and device - Google Patents
System downtime obstacle avoidance and restoration method and device Download PDFInfo
- Publication number
- CN116244113B CN116244113B CN202310150973.2A CN202310150973A CN116244113B CN 116244113 B CN116244113 B CN 116244113B CN 202310150973 A CN202310150973 A CN 202310150973A CN 116244113 B CN116244113 B CN 116244113B
- Authority
- CN
- China
- Prior art keywords
- downtime
- client
- server
- startup
- restarting
- 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
- 238000000034 method Methods 0.000 title claims abstract description 42
- 238000011084 recovery Methods 0.000 claims abstract description 60
- 238000012544 monitoring process Methods 0.000 claims abstract description 11
- 230000002159 abnormal effect Effects 0.000 claims description 7
- 230000004888 barrier function Effects 0.000 claims 2
- 230000008569 process Effects 0.000 abstract description 7
- 230000004044 response Effects 0.000 abstract description 6
- 230000006870 function Effects 0.000 description 16
- 238000004590 computer program Methods 0.000 description 7
- 238000012545 processing Methods 0.000 description 6
- 238000004891 communication Methods 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000011835 investigation Methods 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 238000013024 troubleshooting Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1438—Restarting or rejuvenating
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The embodiment of the invention relates to a method and a device for avoiding and recovering a system downtime, wherein the method comprises the following steps: 1, adding 1 to the count of a preset starting counting file in response to any starting instruction of the system; judging whether the count of the startup counting file exceeds a first threshold value or not in a preset first monitoring time; if the fault is exceeded, triggering downtime to avoid the obstacle and notifying a server; receiving a recovery instruction of a server, executing the recovery instruction and deleting a startup counting file; and executing a restarting program, and sending a restarting normal recovery notification to the server after restarting normal recovery. According to the technical scheme provided by the embodiment of the invention, when the client host is continuously down and restarted due to unknown reasons, the self-loading drive and process can be effectively identified and suspended, and the continuous down of the host caused by the failure of the safety software is avoided. After the host downtime reasons are checked through the server, the client software can be controlled to resume operation again through the server issuing instructions.
Description
Technical Field
The embodiment of the invention relates to the technical field of internet computers, in particular to a method and a device for avoiding and recovering a system downtime.
Background
The host security software is a software service deployed in the client host, has higher authority, and has risk of causing system downtime when the host is protected from malicious attack (other software deployed in the host such as resource monitoring, asset management and the like also have such risk). Therefore, direct recovery after downtime is easy to cause continuous downtime, so that the service is frequently interrupted, and huge loss is caused. In the prior art, obstacle avoidance measures for the host software are lacked.
Disclosure of Invention
Based on the above situation in the prior art, an object of the embodiments of the present invention is to provide a method and an apparatus for avoiding and recovering a downtime of a system, which can timely judge a continuous abnormal downtime scene of the system, trigger a downtime obstacle avoidance response, and realize rapid downtime recovery through a server after troubleshooting reasons.
In order to achieve the above object, according to a first aspect of the present invention, there is provided a system downtime obstacle avoidance and restoration method, applied to a client, including:
1, adding 1 to the count of a preset starting counting file in response to any starting instruction of the system;
judging whether the count of the startup counting file exceeds a first threshold value or not in a preset first monitoring time;
if the fault is exceeded, triggering downtime to avoid the obstacle and notifying a server; if the current value is not exceeded, the control system operates normally;
receiving a recovery instruction of a server, executing the recovery instruction and deleting a startup counting file;
and executing a restarting program, and sending a restarting normal recovery notification to the server after restarting normal recovery.
Further, the method further comprises:
responding to any one starting instruction of the system, and judging whether a starting counting file exists or not;
if yes, adding 1 to the count of the starting counting file; if not, a startup counting file is created.
Further, the method further comprises:
registering a first function in a system shutdown function;
and when the system normally executes the shutdown/restart operation, callback and execution of the first function are performed to delete the startup counting file.
Further, triggering downtime to avoid the obstacle, and not loading a driving program; and the control system normally operates, loads and operates the driving program.
Further, the method further comprises:
and after the restarting program is executed, judging whether the startup counting file exists, and restarting to be normal if the startup counting file does not exist.
The second aspect of the invention provides a system downtime obstacle avoidance and restoration method, which is applied to a server and comprises the following steps:
receiving a downtime obstacle avoidance notification sent by a client, and removing faults according to the notification;
sending a recovery instruction to the client so that the client restarts the client main program and deletes the startup counting file according to the instruction;
and receiving a restarting normal recovery notification sent by the client, and updating the downtime obstacle avoidance state of the client according to the notification.
In a third aspect of the present invention, a system downtime obstacle avoidance and restoration device is provided, applied to a client, including:
the counting module is used for responding to any one starting instruction of the system and performing 1-adding operation on the count of the preset starting counting file;
the judging module is used for judging whether the count of the startup counting file exceeds a first threshold value in a preset first monitoring time; if the fault is exceeded, triggering downtime to avoid the obstacle and notifying a server; if the current value is not exceeded, the control system operates normally;
the recovery module is used for receiving the recovery instruction of the server, executing the recovery instruction and deleting the startup counting file;
and the restarting module is used for executing the restarting program and sending a restarting recovery normal notification to the server after the restarting recovery normal.
Further, the device further comprises:
the counting module is also used for responding to any one starting instruction of the system and judging whether a starting counting file exists or not; if yes, adding 1 to the count of the starting counting file; if not, a startup counting file is created.
Further, the judging module is further configured to register a first function in a system shutdown function; and when the system normally executes the shutdown/restart operation, callback and execution of the first function are performed to delete the startup counting file.
The fourth aspect of the present invention provides a system downtime obstacle avoidance and restoration device, which is characterized in that the device is applied to a server, and comprises:
the fault removal module is used for receiving the downtime obstacle avoidance notification sent by the client and removing faults according to the notification;
the recovery instruction module is used for sending a recovery instruction to the client so that the client restarts the client main program according to the instruction and deletes the startup counting file;
and the state updating module is used for receiving a restarting normal recovery notification sent by the client and updating the downtime obstacle avoidance state of the client according to the notification.
In summary, the embodiment of the invention provides a method and a device for avoiding and recovering a system downtime, wherein the method comprises the following steps: 1, adding 1 to the count of a preset starting counting file in response to any starting instruction of the system; judging whether the count of the startup counting file exceeds a first threshold value or not in a preset first monitoring time; if the fault is exceeded, triggering downtime to avoid the obstacle and notifying a server; if the current value is not exceeded, the control system operates normally; receiving a recovery instruction of a server, executing the recovery instruction and deleting a startup counting file; and executing a restarting program, and sending a restarting normal recovery notification to the server after restarting normal recovery. According to the technical scheme provided by the embodiment of the invention, when the client host is continuously down and restarted due to unknown reasons, the self-loading drive and process can be effectively identified and suspended, and the continuous down of the host caused by the failure of the safety software is avoided. After the host downtime reasons are checked through the server, the security software can control the client software to resume operation again through the server issuing instructions. By the aid of the technical scheme, downtime obstacle avoidance of host safety software and quick recovery without redeployment are achieved through the design of the mechanism.
Drawings
FIG. 1 is a flow chart of a system downtime obstacle avoidance and restoration method provided by an embodiment of the present invention;
FIG. 2 is a flow chart of a method for downtime obstacle avoidance and restoration of a system according to another embodiment of the present invention;
FIG. 3 is a schematic flow chart of interaction between a server and a client according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
The objects, technical solutions and advantages of the present invention will become more apparent by the following detailed description of the present invention with reference to the accompanying drawings. It should be understood that the description is only illustrative and is not intended to limit the scope of the invention. In addition, in the following description, descriptions of well-known structures and techniques are omitted so as not to unnecessarily obscure the present invention.
It is noted that unless otherwise defined, technical or scientific terms used in one or more embodiments of the present invention should be given the ordinary meaning as understood by one of ordinary skill in the art to which this disclosure belongs. The use of the terms "first," "second," and the like in one or more embodiments of the present invention does not denote any order, quantity, or importance, but rather the terms "first," "second," and the like are used to distinguish one element from another. The word "comprising" or "comprises", and the like, means that elements or items preceding the word are included in the element or item listed after the word and equivalents thereof, but does not exclude other elements or items. The terms "connected" or "connected," and the like, are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect.
The technical scheme of the invention is described in detail below with reference to the accompanying drawings. The host security software system is generally divided into a client and a server, the client is deployed on a service host to protect the security of the service host, and the server is independently deployed to realize remote alarm management, policy distribution, system disposal and the like by collecting and processing data feedback of the client.
The embodiment of the invention provides a system downtime obstacle avoidance and restoration method, which is applied to a client, and a flow chart of the method is shown in fig. 1, and comprises the following steps:
s11, responding to any one starting instruction of the system, and adding 1 to the count of the preset starting counting file. According to the technical scheme of the embodiment of the invention, a startup counting file is set at the client of host security software, the number and time of abnormal restarting are recorded through the startup counting file, and the system can record the startup time and check the startup counting file when starting each time. If the startup counting file exists, the counting times of the startup counting file is increased by 1, the startup time of the subsystem is recorded, and if the startup time does not exist, the startup counting file is created. That is, in this step, in response to an arbitrary one-time startup instruction of the system, it is first determined whether a startup count file exists; if yes, adding 1 to the count of the starting counting file; if not, a startup counting file is created. If the system is restarted normally, the shutdown process is triggered, and the system function is called to delete the counting file. Specifically, the first function stop () function may be registered in the system shutdown () function; when the system normally executes the shutdown/restarting operation, callback and execution of the stop () function are carried out, and the startup counting file is deleted; when the system is restarted, the program executes a start () function to judge whether a startup counting file exists in the corresponding path, and if the startup counting file does not exist in the corresponding path, the shutdown before restarting is a normal shutdown.
S12, starting from the first starting time of the system, judging whether the count of the starting counting file exceeds a first threshold value in a preset first monitoring time; if the fault is exceeded, triggering downtime to avoid the obstacle and notifying a server; if not, the control system operates normally. Under the condition of triggering downtime and obstacle avoidance, a driving program is not loaded; and under the normal operation condition of the control system, loading and operating the driving program. When the client triggers the downtime to avoid the obstacle, the power supply system is cut off, and the normal shutdown process is not executed by the system in the process, so that the set stop () function can be skipped, and when the system is restarted again, a startup counting file still exists in a system disk, so that the shutdown before the restarting is prompted to be abnormal shutdown. The step is used for judging whether frequent abnormal shutdown restarting occurs or not, when the system frequently triggers shutdown restarting in a short time, for example, the first monitoring time is 10 minutes, the first threshold value is 3 times, the system is shutdown restarting for 3 times in 10 minutes, after the 3 rd restarting of the system, the count in the startup counting file is 3, the control client side does not load a driving program any more, and because the driving is not allowed, the application program does not carry out Hook (Hook) action on the system, at the moment, the safety protection capability is closed, the application program runs in a lightweight mode, and still can be communicated with the server side. After triggering downtime to avoid the obstacle, information is sent to the server to inform the server.
S13, receiving a recovery instruction of the server, executing the recovery instruction and deleting the startup counting file. In general, after receiving the downtime obstacle avoidance notification, a security operation and maintenance person at the server end performs fault investigation on the abnormally restarted client-side server, and determines that the downtime caused by the loading of the security drive is not caused, and then the command for downtime obstacle avoidance recovery can be directly issued through the server end. After the client confirms the instruction of the server, the current startup counting file is deleted, the client is restarted, and the driving program is normally loaded after the startup counting file is judged at the moment, so that quick obstacle avoidance recovery is realized.
S14, executing a restarting program, and sending a restarting restoration normal notification to the server after restarting restoration normal. After executing the restarting program, judging whether the startup counting file exists, and if not, restarting to restore to normal.
The embodiment of the invention also provides a system downtime obstacle avoidance and restoration method, wherein a flow chart of the method is shown in fig. 2 and applied to a server, a flow chart of interaction between the server and a client is shown in fig. 3, and the method comprises the following steps of:
s21, receiving a downtime obstacle avoidance notification sent by the client, and removing faults according to the notification. After the safe operation and maintenance personnel receive the downtime obstacle avoidance notification, the abnormal restarting client server is subjected to fault investigation, and after the downtime caused by safe driving loading is determined, a command for downtime obstacle avoidance recovery can be directly issued through the server.
S22, sending a recovery instruction to the client so that the client restarts the client main program according to the instruction and deletes the startup counting file. The server judges that the client can keep normal communication (online state), and can send a recovery instruction to the client. After verifying the signature, the client confirms that the command is issued by the server, analyzes the command issued by the server, executes the corresponding command, and deletes the startup counting file. And then, restarting the client main program, continuing the startup procedure after restarting, judging whether to avoid the obstacle, and if the startup counting file does not exist at the moment, recovering to be normal.
S23, receiving a restarting normal recovery notification sent by the client, and updating the downtime obstacle avoidance state of the client according to the notification.
The embodiment of the invention also provides a system downtime obstacle avoidance and restoration device, which is applied to a client and comprises the following components:
the counting module is used for responding to any one starting instruction of the system and performing 1-adding operation on the count of the preset starting counting file;
the judging module is used for judging whether the count of the startup counting file exceeds a first threshold value in a preset first monitoring time; if the fault is exceeded, triggering downtime to avoid the obstacle and notifying a server; if the current value is not exceeded, the control system operates normally;
the recovery module is used for receiving the recovery instruction of the server, executing the recovery instruction and deleting the startup counting file;
and the restarting module is used for executing the restarting program and sending a restarting recovery normal notification to the server after the restarting recovery normal.
The embodiment of the invention also provides a system downtime obstacle avoidance and restoration device, which is applied to a server and comprises the following components:
the fault removal module is used for receiving the downtime obstacle avoidance notification sent by the client and removing faults according to the notification;
the recovery instruction module is used for sending a recovery instruction to the client so that the client restarts the client main program according to the instruction and deletes the startup counting file;
the state updating module is used for receiving a restarting normal recovery notification sent by the client and updating the downtime obstacle avoidance state of the client according to the notification
The specific process of each module in the system downtime obstacle avoidance and restoration device provided by the embodiment of the invention to realize the functions is the same as each step of the system downtime obstacle avoidance and restoration method provided by the embodiment of the invention, so that repeated description thereof will be omitted here.
The embodiment of the invention also provides electronic equipment, and fig. 4 is a schematic structural diagram of the electronic equipment according to the embodiment of the invention. As shown in fig. 4, the electronic device includes: one or more processors 401 and a memory 402; and computer program instructions stored in the memory 402 that, when executed by the processor 401, cause the processor 401 to perform the system downtime obstacle avoidance and restoration method of any of the embodiments described above. The processor 401 may be a Central Processing Unit (CPU) or other form of processing unit having data processing capabilities and/or instruction execution capabilities and may control other components in the electronic device to perform desired functions.
Memory 402 may include one or more computer program products, which may include various forms of computer-readable storage media, such as volatile memory and/or non-volatile memory. Volatile memory can include, for example, random Access Memory (RAM) and/or cache memory (cache) and the like. The non-volatile memory may include, for example, read Only Memory (ROM), hard disk, flash memory, and the like. One or more computer program instructions may be stored on a computer readable storage medium and the processor 401 may run the program instructions to implement the steps in the system downtime obstacle avoidance and restoration method of the various embodiments of the invention above, and/or other desired functions.
In some embodiments, the electronic device may further include: an input device 403 and an output device 404, which are interconnected by a bus system and/or other forms of connection mechanisms (not shown in fig. 4). For example, when the electronic device is a stand-alone device, the input means 403 may be a communication network connector for receiving the acquired input signal from an external removable device. In addition, the input device 403 may also include, for example, a keyboard, a mouse, a microphone, and the like. The output device 404 may output various information to the outside, and may include, for example, a display, a speaker, a printer, a communication network, a remote output apparatus connected thereto, and the like.
In addition to the methods and apparatus described above, embodiments of the invention may also be a computer program product comprising computer program instructions which, when executed by a processor, cause the processor to perform the steps of the system downtime obstacle avoidance and restoration method of any of the embodiments described above.
The computer program product may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device, partly on a remote computing device, or entirely on the remote computing device or server.
Furthermore, embodiments of the present invention may also be a computer-readable storage medium having stored thereon computer program instructions that, when executed by a processor, cause the processor to perform the steps in the system downtime obstacle avoidance and restoration method of the various embodiments of the present invention.
A computer readable storage medium may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may include, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium would include the following: an electrical connection having one or more wires, a portable disk, a hard disk, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
It should be appreciated that the processor in embodiments of the present invention may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), off-the-shelf programmable gate arrays (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
In summary, the embodiment of the invention relates to a method and a device for avoiding and recovering a fault of a system downtime, wherein the method comprises the following steps: 1, adding 1 to the count of a preset starting counting file in response to any starting instruction of the system; judging whether the count of the startup counting file exceeds a first threshold value or not in a preset first monitoring time; if the fault is exceeded, triggering downtime to avoid the obstacle and notifying a server; if the current value is not exceeded, the control system operates normally; receiving a recovery instruction of a server, executing the recovery instruction and deleting a startup counting file; and executing a restarting program, and sending a restarting normal recovery notification to the server after restarting normal recovery. According to the technical scheme provided by the embodiment of the invention, when the client host is continuously down and restarted due to unknown reasons, the self-loading drive and process can be effectively identified and suspended, and the continuous down of the host caused by the failure of the safety software is avoided. After the host downtime reasons are checked through the server, the security software can control the client software to resume operation again through the server issuing instructions. The technical scheme of the embodiment of the invention focuses on solving the problem of obstacle avoidance and recovery after frequent downtime restarting caused by unknown reasons of the system, judges the frequent downtime restarting of the system by setting the downtime obstacle avoidance counting file, and after triggering the downtime restarting, the safety software stops loading the driving program and minimizes the operation, thereby reducing the possible negative influence on the service system. Meanwhile, after the reasons of the safety software are eliminated, a method for quickly recovering the safety software through the server side is provided. The mechanism can be further applied to other software of the system to maximally avoid the negative influence of security, operation and maintenance and management software on the service, thereby ensuring the service continuity.
It should be understood that the above discussion of any of the embodiments is exemplary only and is not intended to suggest that the scope of the invention (including the claims) is limited to these examples; combinations of features of the above embodiments or in different embodiments are also possible within the spirit of the invention, steps may be implemented in any order and there are many other variations of the different aspects of one or more embodiments of the invention described above which are not provided in detail for the sake of brevity. The above detailed description of the present invention is merely illustrative or explanatory of the principles of the invention and is not necessarily intended to limit the invention. Accordingly, any modification, equivalent replacement, improvement, etc. made without departing from the spirit and scope of the present invention should be included in the scope of the present invention. Furthermore, the appended claims are intended to cover all such changes and modifications that fall within the scope and boundary of the appended claims, or equivalents of such scope and boundary.
Claims (5)
1. The system downtime obstacle avoidance and restoration method is characterized by being applied to a client and comprising the following steps:
registering a first function in a system shutdown function;
responding to any one starting instruction of the system, and judging whether a starting counting file exists or not;
if the startup count file exists, performing 1-adding operation on the count of the preset startup count file, and prompting that shutdown before startup is abnormal shutdown;
if the power-on state does not exist, a power-on counting file is created, and the power-off before the power-on is prompted to be normal;
judging whether the count of the startup counting file exceeds a first threshold value or not in a preset first monitoring time;
if yes, triggering downtime to avoid the obstacle and informing the server, cutting off a power supply system, and skipping the first function;
if the current value is not exceeded, the control system operates normally;
receiving a recovery instruction of a server, executing the recovery instruction and deleting a startup counting file;
executing a restarting program, and sending a restarting recovering normal notification to the server after the restarting is recovered to be normal;
when the system normally executes the shutdown/restart operation, the first function is called back and executed to delete the startup counting file.
2. The method of claim 1, wherein the triggering downtime to avoid an obstacle does not load a driver; and the control system normally operates, loads and operates the driving program.
3. A method for avoiding and recovering a system downtime is characterized by being applied to a server and comprising the following steps:
receiving a downtime obstacle avoidance notification sent by a client, and removing faults according to the downtime obstacle avoidance notification; the client sends out a downtime obstacle avoidance notification according to the method of claim 1 or 2;
sending a recovery instruction to the client so that the client restarts the main program of the client and deletes the startup counting file according to the recovery instruction;
and receiving a restart normal recovery notification sent by the client, and updating the downtime obstacle avoidance state of the client according to the restart normal recovery notification.
4. The utility model provides a barrier and recovery unit are kept away to system downtime which characterized in that is applied to the customer end includes:
the counting module is used for responding to any one starting instruction of the system and judging whether a starting counting file exists or not; if the startup count file exists, performing 1-adding operation on the count of the preset startup count file, and prompting that shutdown before startup is abnormal shutdown; if the power-on state does not exist, a power-on counting file is created, and the power-off before the power-on is prompted to be normal;
the judging module is used for registering a first function in the system shutdown function and judging whether the count of the startup counting file exceeds a first threshold value in a preset first monitoring time; if yes, triggering downtime to avoid the obstacle and informing the server, cutting off a power supply system, and skipping the first function; if the current value is not exceeded, the control system operates normally;
the recovery module is used for receiving the recovery instruction of the server, executing the recovery instruction and deleting the startup counting file;
the restarting module is used for executing the restarting program and sending a restarting restoration normal notification to the server after the restarting restoration normal; and when the system normally executes the shutdown/restart operation, callback and execution of the first function are performed to delete the startup counting file.
5. The utility model provides a barrier and recovery unit are kept away to system downtime which characterized in that is applied to the server, includes:
the fault removal module is used for receiving the downtime obstacle avoidance notification sent by the client and removing faults according to the downtime obstacle avoidance notification; the client sends out a downtime obstacle avoidance notification through the device of claim 4;
the recovery instruction module is used for sending a recovery instruction to the client so that the client restarts the client main program according to the recovery instruction and deletes the startup counting file;
and the state updating module is used for receiving a restart normal restoration notification sent by the client and updating the downtime obstacle avoidance state of the client according to the restart normal restoration notification.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310150973.2A CN116244113B (en) | 2023-02-22 | 2023-02-22 | System downtime obstacle avoidance and restoration method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310150973.2A CN116244113B (en) | 2023-02-22 | 2023-02-22 | System downtime obstacle avoidance and restoration method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116244113A CN116244113A (en) | 2023-06-09 |
| CN116244113B true CN116244113B (en) | 2023-12-19 |
Family
ID=86623753
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310150973.2A Active CN116244113B (en) | 2023-02-22 | 2023-02-22 | System downtime obstacle avoidance and restoration method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116244113B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103902338A (en) * | 2014-03-21 | 2014-07-02 | 珠海市君天电子科技有限公司 | Drive loading method, drive processing method, client side, server and system |
| CN105912431A (en) * | 2016-04-01 | 2016-08-31 | 浪潮电子信息产业股份有限公司 | Reboot testing method of server, server, control device and system |
| CN111459692A (en) * | 2019-01-18 | 2020-07-28 | 伊姆西Ip控股有限责任公司 | Method, apparatus and computer program product for predicting drive failure |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7028225B2 (en) * | 2001-09-25 | 2006-04-11 | Path Communications, Inc. | Application manager for monitoring and recovery of software based application processes |
-
2023
- 2023-02-22 CN CN202310150973.2A patent/CN116244113B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103902338A (en) * | 2014-03-21 | 2014-07-02 | 珠海市君天电子科技有限公司 | Drive loading method, drive processing method, client side, server and system |
| CN105912431A (en) * | 2016-04-01 | 2016-08-31 | 浪潮电子信息产业股份有限公司 | Reboot testing method of server, server, control device and system |
| CN111459692A (en) * | 2019-01-18 | 2020-07-28 | 伊姆西Ip控股有限责任公司 | Method, apparatus and computer program product for predicting drive failure |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116244113A (en) | 2023-06-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107179957B (en) | Physical machine fault classification processing method and device and virtual machine recovery method and system | |
| CN107515796B (en) | Equipment abnormity monitoring processing method and device | |
| US8645757B2 (en) | Administering incident pools for event and alert analysis | |
| US9086968B2 (en) | Checkpointing for delayed alert creation | |
| CN108845875B (en) | Resident process keep-alive system and method | |
| TW201901514A (en) | Program change monitoring and strain system and method | |
| CN102867146A (en) | Method and system for preventing computer virus from frequently infecting systems | |
| CN111581021B (en) | Application program starting abnormality repairing method, device, equipment and storage medium | |
| KR101974989B1 (en) | Method and apparatus for determining behavior information corresponding to a dangerous file | |
| WO2019140738A1 (en) | Method for avoiding excess return visits, and electronic apparatus and computer-readable storage medium | |
| CN111124761B (en) | Equipment restarting method, device, equipment and medium | |
| CN112732674A (en) | Cloud platform service management method, device, equipment and readable storage medium | |
| CN111625386A (en) | Monitoring method and device for power-on overtime of system equipment | |
| CN105426263A (en) | Implementation method and system for secure operation of cashbox system | |
| CN116244113B (en) | System downtime obstacle avoidance and restoration method and device | |
| CN114020509A (en) | Method, device and equipment for repairing work load cluster and readable storage medium | |
| KR20140134987A (en) | Device and method for securing computer | |
| CN103679024A (en) | Virus treating method and device | |
| CN113127245B (en) | Method, system and device for processing system management interrupt | |
| JP6222759B2 (en) | Failure notification device, failure notification method and program | |
| CN115080132A (en) | Information processing method, information processing apparatus, server, and storage medium | |
| EP3819799A1 (en) | Method of threat detection | |
| KR101310070B1 (en) | Method for preventing collision between each programs and recording-medium recorded program thereof | |
| CN105391575A (en) | Treasury control method and system | |
| CN110851300A (en) | Program process monitoring method and device, computer equipment and readable storage medium |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |