CN106682162B - Log management method and device - Google Patents
Log management method and device Download PDFInfo
- Publication number
- CN106682162B CN106682162B CN201611218562.9A CN201611218562A CN106682162B CN 106682162 B CN106682162 B CN 106682162B CN 201611218562 A CN201611218562 A CN 201611218562A CN 106682162 B CN106682162 B CN 106682162B
- Authority
- CN
- China
- Prior art keywords
- log information
- embedded system
- file system
- writing
- embedded
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/174—Redundancy elimination performed by the file system
- G06F16/1744—Redundancy elimination performed by the file system using compression, e.g. sparse files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/1805—Append-only file systems, e.g. using logs or journals to store data
- G06F16/1815—Journaling file systems
Abstract
The application provides a log management method and a device, wherein the method is applied to a terminal with an embedded system, the embedded system is mounted with a memory file system and a Flash file system, and the method comprises the following steps: acquiring log information of the embedded system; acquiring the working state of the embedded system; if the working state indicates that the embedded system normally operates, the log information is written into the memory file system; and if the working state indicates that the embedded system is abnormal, writing the log information into the Flash file system. By applying the method, the log information recorded with the abnormal information occurring in the running process of the embedded device can be effectively saved, so that a user can conveniently locate faults, analyze abnormal reasons and the like according to the log information, and the influence on the service life of the Flash file system is avoided.
Description
Technical Field
The present application relates to the field of embedded technologies, and in particular, to a log management method and apparatus.
Background
With the development of computer technology, embedded systems have become an important component of the computer field. For the embedded system, the log information recorded in the running process plays a very important role in positioning the fault by the user.
In the prior art, the embedded device may write log information generated in the operation process into the memory file system, and then compress the log information in the memory file system and write the compressed log information into the Flash file system, so as to avoid the log information recorded in the memory file system from being lost due to the power failure of the embedded device.
However, in the prior art, if the embedded device is powered off before the log information in the memory file system is compressed and written into the Flash file system, the log information in the memory file system is still lost; meanwhile, if the generated log information is more, the embedded device still needs to write the log information into the Flash file system for many times, so that the service life of the Flash file system is shortened.
Disclosure of Invention
In view of this, the present application provides a log management method and apparatus, so as to effectively store log information recorded with abnormal information occurring during the operation of an embedded device, so that a user can locate a fault and analyze the reason of the abnormal information according to the log information, and meanwhile, the service life of a Flash file system is prevented from being affected.
Specifically, the method is realized through the following technical scheme:
according to a first aspect of an embodiment of the present application, a log management method is provided, where the method is applied to a terminal having an embedded system, and the embedded system is mounted with a memory file system and a Flash file system, and the method includes:
acquiring log information of the embedded system;
acquiring the working state of the embedded system;
if the working state indicates that the embedded system normally operates, the log information is written into the memory file system; and if the working state indicates that the embedded system is abnormal, writing the log information into the Flash file system.
Optionally, the method further includes:
determining an event identified by the log information;
and if the event belongs to a preset key event, writing the log information into the Flash file system.
Optionally, the occurrence of an exception in the embedded system includes: the kernel of the embedded system is abnormal, and the business process in the embedded system is abnormal.
Optionally, when the working state indicates that the kernel of the embedded system is abnormal, the writing the log information into the Flash file system includes:
writing the log information into a preset memory space based on a preset Pstore mechanism;
after the embedded system is restarted, compressing the log information in the memory space;
and writing the compressed log information into the Flash file system.
Optionally, when the working state indicates that a service process in the embedded system is abnormal, the writing the log information into the Flash file system includes:
compressing the log information in the memory file system;
and writing the compressed log information into the Flash file system.
According to a second aspect of the embodiments of the present application, there is provided a log management apparatus, where the apparatus is applied to a terminal having an embedded system, and the embedded system is mounted with a memory file system and a Flash file system, and the apparatus includes:
the information acquisition module is used for acquiring the log information of the embedded system;
the state acquisition module is used for acquiring the working state of the embedded system;
the storage processing module is used for writing the log information into the memory file system if the working state indicates that the embedded system normally operates; and if the working state indicates that the embedded system is abnormal, writing the log information into the Flash file system.
Optionally, the apparatus further comprises:
an event determination module, configured to determine an event identified by the log information;
the storage processing module is further configured to: and if the event belongs to a preset key event, writing the log information into the Flash file system.
Optionally, the occurrence of an exception in the embedded system includes: the kernel of the embedded system is abnormal, and the business process in the embedded system is abnormal.
Optionally, when the working state indicates that the kernel of the embedded system is abnormal, the storage processing module includes:
the first storage submodule is used for writing the log information into a preset memory space based on a preset Pstore mechanism;
the first compression submodule is used for compressing the log information in the memory space after the embedded system is restarted;
and the second storage submodule is used for writing the compressed log information into the Flash file system.
Optionally, when the working state indicates that the service process in the embedded system is abnormal, the storage processing module includes:
the second compression submodule is used for compressing the log information in the memory file system;
and the third storage sub-module is used for writing the compressed log information into the Flash file system.
According to the embodiment, the obtained log information is written into the memory file system when the embedded system works normally, and the obtained log information is written into the Flash file system when the embedded system is abnormal, so that the frequency of writing the log information into the Flash file system is greatly reduced, and the service life of the Flash file system is prevented from being shortened due to frequent writing of the log information into the Flash file system; in addition, the log information recorded with abnormal information occurring in the running process of the embedded device can be effectively stored, so that a user can locate faults, analyze abnormal reasons and the like according to the log information.
Drawings
FIG. 1 is a flowchart of an embodiment of a log management method of the present application;
fig. 2 is a hardware structure diagram of a terminal where the log management device of the present application is located;
fig. 3 is a block diagram of an embodiment of a log management apparatus according to the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
In the operation process of the embedded system, various error information, warning information or other prompt information can be generated by a system kernel and a plurality of business processes, and the information plays an important role in knowing the operation state of the embedded system and positioning faults for users, so that log information can be generated by the information generated in the operation process of the embedded system on the embedded device, and the log information can be recorded.
In the embedded device, if the log information acquired by the embedded system in the running process is written into the Flash file system, the log information is frequently written into the Flash file system, so that the service life of the Flash file system is shortened; if the log information acquired by the embedded system in the running process is written into the memory file system, the log information in the memory file system is lost after the embedded device is powered off and restarted, so that a user cannot perform work such as fault location, abnormal reason analysis and the like according to the log information.
Based on the above description, in order to effectively store log information acquired by the embedded device in the running process, especially log information recorded with abnormal information occurring in the running process of the embedded device, and avoid influencing the service life of the Flash file system, the application provides a log management method and device.
As follows, the log management method provided by the present application is described by referring to the following examples.
Referring to fig. 1, a flowchart of an embodiment of a log management method according to the present application is shown, where the method may be applied to a terminal having an embedded system, where the embedded system is mounted with a memory file system, such as a tmpfs file system and a Flash file system, such as a JFFS2 file system, and the method may include the following steps:
step S101: and acquiring the log information of the embedded system.
In the running process of the embedded system, information such as the occurrence event, the running state of the system, the running state of each service process in the system and the like can be recorded, and the log information of the embedded system can be obtained according to the recorded information.
The log information may have various levels, for example, emerg (emergency), error (general error message), warning (warning information), info (general information), debug (debug information), and the like, depending on the recorded information. The user can customize the level of log information that needs to be saved.
Step S102: acquiring the working state of the embedded system, and executing the step S103 if the working state indicates that the embedded system normally runs; if the operating status indicates that an abnormality occurs in the embedded system, step S104 is executed.
In the application, the terminal with the embedded system may have a monitoring process, where the monitoring process is used to monitor a working state of the embedded system on the terminal, and specifically may include a working state of an embedded system kernel and a working state of a service process in the embedded system.
As follows, how the monitoring process monitors the working state of the business process in the embedded system is specifically described:
in the application, the terminal may obtain the duration of the suspended service process in the embedded system based on a preset watchdog mechanism, and if the duration of the suspended service process reaches a preset duration threshold, for example, 1 minute, it may be determined that the service process is abnormal.
Specifically, in the present application, the terminal with the embedded system may have a watchdog mechanism, that is, the hardware of the terminal may include a timer circuit, which has an input terminal and an output terminal, and is preset with a timeout time, for example, 2 minutes. Based on a watchdog mechanism, if the input end of the timing circuit has no input within 2 minutes, the output end of the timing circuit can output a reset signal, so that the CPU of the terminal is powered off and restarted.
After the start of the service process, a signal may be input to the input of the timer circuit at a fixed time interval, for example 5 seconds (commonly referred to as a dog feeding operation), and a temporary file may be created in the memory file system to identify the dog feeding operation each time the signal is input.
The monitoring process can check whether a temporary file for identifying the dog feeding operation exists in the memory file system every interval of the fixed time, and if the temporary file exists in the memory file system, the monitoring process can delete the temporary file from the memory file system; if the temporary file does not exist, the monitoring process may add 1 to a preset counter, where an initial value of the preset counter is 0.
Subsequently, if it is determined that the traffic process has continued for the preset duration threshold value by the value of the counter, no signal is input to the input terminal of the timer circuit, for example, when it is determined that the value of the counter reaches 12, the traffic process is considered to have continued for the preset duration threshold value, for example, 1 minute (12 × 5 seconds — 1 minute) no signal is input to the input terminal of the timer circuit, and at this time, the traffic process may be considered to be abnormal.
It should be noted that the preset time threshold described above is smaller than the timeout period in the watchdog mechanism.
In the present application, if it is monitored that the embedded system is working normally, step S103 is executed; if the embedded system is monitored to be abnormal, including the kernel of the embedded system being abnormal and the business process in the embedded system being abnormal, step S104 is executed.
Step S103: and writing the log information into a memory file system, and ending the process.
In the memory file system, in order to avoid the capacity overflow of the memory file system caused by the continuous increase of the log information, two log files, for example, log file 1 and log file 2, may be maintained in the memory file system. When the embedded device writes log information into the memory file system, firstly determining whether the size of the log file 1 exceeds a preset file size threshold, and if the size of the log file 1 does not exceed the preset file size threshold, writing the log information into the log file 1; if the size of the log file 1 reaches the preset file size threshold, the current log file 1 can be renamed to be the log file 2, a log file is newly built, the log file is named to be the log file 1, and the log information is written into the log file 1.
Step S104: and writing the log information into a Flash file system.
First, a case where an abnormality occurs in the kernel of the embedded system is described as follows:
in the application, a Pstore (persistent storage) mechanism may be preset in the embedded device, and the Pstore mechanism may provide a set of general interfaces to store exception information. In the process of presetting a Pstore mechanism in an embedded device, firstly, a structure variable of a Pstore _ info type is initialized, then, int Pstore _ register (struct Pstore _ info) is called for registration, and then, a platform _ device structure named ramoops is registered, wherein in the structure, the platform _ data points to a variable address of the type ramoops _ platform _ data and is used for indicating a memory address and size for storing exception information.
When the working state acquired by the monitoring process indicates that the kernel of the embedded system is abnormal, the embedded device can write the acquired log information into a memory space pointed by a Pstore mechanism, then after the embedded system is restarted due to the abnormal kernel, the log information in the memory space is compressed, and the compressed log information is written into a Flash file system.
Next, a description is given of a case where an exception occurs in a business process in an embedded system:
when the working state obtained by the monitoring process indicates that the service process in the embedded system is abnormal, the embedded device can compress the log information in the memory file system and write the compressed log information into the Flash file system.
As can be seen from the above description, in the process of acquiring, by the monitoring process, that the service process in the embedded system is abnormal, the used time threshold is smaller than the timeout time in the watchdog mechanism, so that the log information in the memory file system can be written into the Flash file system before the CPU is restarted due to power failure, and the log information in the memory file system is prevented from being lost due to the CPU is restarted due to power failure.
In addition, in the present application, if the event identified by the log information belongs to a preset key event, the log information may be written into a Flash file system to persistently store the log information, where the key event generally may include events that seriously affect the service, such as system restart and network outage.
According to the embodiment, the obtained log information is written into the memory file system when the embedded system works normally, and the obtained log information is written into the Flash file system when the embedded system is abnormal, so that the frequency of writing the log information into the Flash file system is greatly reduced, and the service life of the Flash file system is prevented from being shortened due to frequent writing of the log information into the Flash file system; in addition, the log information recorded with abnormal information occurring in the running process of the embedded device can be effectively stored, so that a user can locate faults, analyze abnormal reasons and the like according to the log information.
Corresponding to the embodiment of the log management method, the application also provides an embodiment of a log management device.
The embodiment of the log management device can be applied to a terminal with an embedded system. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. The software implementation is taken as an example, and as a logical device, the device is formed by reading corresponding computer program instructions in the nonvolatile memory into the memory for operation through the processor of the terminal where the device is located. From a hardware aspect, as shown in fig. 2, the present application is a hardware structure diagram of a terminal where the log management device is located, except for the processor 21, the memory 22, the network interface 23, and the nonvolatile memory 24 shown in fig. 2, the terminal where the device is located in the embodiment may also include other hardware according to the actual function of the terminal, which is not described again.
Referring to fig. 3, a block diagram of an embodiment of a log management apparatus according to the present application, which may be applied to a terminal having an embedded system, the embedded system being mounted with a memory file system, such as a tmpfs file system, and a Flash file system, such as a JFFS2 file system, and the apparatus may include: an information acquisition module 31, a state acquisition module 32, and a storage processing module 33.
The information obtaining module 31 may be configured to obtain log information of the embedded system;
the state obtaining module 32 may be configured to obtain a working state of the embedded system;
the storage processing module 33 may be configured to write the log information into the memory file system if the working state indicates that the embedded system is operating normally; and if the working state indicates that the embedded system is abnormal, writing the log information into the Flash file system.
In an embodiment, the apparatus may further comprise (not shown in fig. 3):
an event determination module operable to determine an event identified by the log information;
the storage processing module may be further operable to: and if the event belongs to a preset key event, writing the log information into the Flash file system.
In one embodiment, the occurrence of an exception in the embedded system may include: the kernel of the embedded system is abnormal, and the business process in the embedded system is abnormal.
In an embodiment, when the working status indicates that an exception occurs in the kernel of the embedded system, the storage processing module may include (not shown in fig. 3):
the first storage submodule can be used for writing the log information into a preset memory space based on a preset Pstore mechanism;
the first compression submodule can be used for compressing the log information in the memory space after the embedded system is restarted;
and the second storage submodule can be used for writing the compressed log information into the Flash file system.
In an embodiment, when the working status indicates that an exception occurs in a business process in the embedded system, the storage processing module 33 may include (not shown in fig. 3):
the second compression submodule can be used for compressing the log information in the memory file system;
and the third storage submodule can be used for writing the compressed log information into the Flash file system.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and 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 modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Claims (10)
1. A log management method is characterized in that the method is applied to a terminal with an embedded system, the embedded system is mounted with a memory file system and a Flash file system, and the method comprises the following steps:
acquiring log information of the embedded system in the running process of the embedded system;
acquiring the working state of the embedded system according to fixed time;
if the working state indicates that the embedded system normally operates, the log information is written into the memory file system; and if the working state indicates that the embedded system is abnormal, writing the log information into the Flash file system.
2. The method of claim 1, further comprising:
determining an event identified by the log information;
and if the event belongs to a preset key event, writing the log information into the Flash file system.
3. The method of claim 1, wherein the occurrence of an exception in the embedded system comprises: the kernel of the embedded system is abnormal, and the business process in the embedded system is abnormal.
4. The method according to claim 3, wherein when the working status indicates that the kernel of the embedded system is abnormal, the writing the log information into the Flash file system comprises:
writing the log information into a preset memory space based on a preset persistent storage Pstore mechanism;
after the embedded system is restarted, compressing the log information in the memory space;
and writing the compressed log information into the Flash file system.
5. The method according to claim 3, wherein when the working status indicates that the business process in the embedded system is abnormal, the writing the log information into the Flash file system comprises:
compressing the log information in the memory file system;
and writing the compressed log information into the Flash file system.
6. A log management device is characterized in that the device is applied to a terminal with an embedded system, the embedded system is mounted with a memory file system and a Flash file system, and the device comprises:
the information acquisition module is used for acquiring the log information of the embedded system in the running process of the embedded system;
the state acquisition module is used for acquiring the working state of the embedded system according to fixed time;
the storage processing module is used for writing the log information into the memory file system if the working state indicates that the embedded system normally operates; and if the working state indicates that the embedded system is abnormal, writing the log information into the Flash file system.
7. The apparatus of claim 6, further comprising:
an event determination module, configured to determine an event identified by the log information;
the storage processing module is further configured to: and if the event belongs to a preset key event, writing the log information into the Flash file system.
8. The apparatus of claim 6, wherein the occurrence of an exception in the embedded system comprises: the kernel of the embedded system is abnormal, and the business process in the embedded system is abnormal.
9. The apparatus of claim 8, wherein when the operating state indicates an exception occurs in a core of the embedded system, the storage processing module comprises:
the first storage submodule is used for writing the log information into a preset memory space based on a preset Pstore mechanism;
the first compression submodule is used for compressing the log information in the memory space after the embedded system is restarted;
and the second storage submodule is used for writing the compressed log information into the Flash file system.
10. The apparatus according to claim 8, wherein when the working status indicates that an exception occurs in a business process in the embedded system, the storage processing module comprises:
the second compression submodule is used for compressing the log information in the memory file system;
and the third storage sub-module is used for writing the compressed log information into the Flash file system.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611218562.9A CN106682162B (en) | 2016-12-26 | 2016-12-26 | Log management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611218562.9A CN106682162B (en) | 2016-12-26 | 2016-12-26 | Log management method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106682162A CN106682162A (en) | 2017-05-17 |
| CN106682162B true CN106682162B (en) | 2021-03-09 |
Family
ID=58870648
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611218562.9A Active CN106682162B (en) | 2016-12-26 | 2016-12-26 | Log management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106682162B (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107396389B (en) * | 2017-06-01 | 2020-12-15 | 台州市吉吉知识产权运营有限公司 | Method and system for diagnosing abnormal restart time of wireless access equipment |
| CN108563582B (en) * | 2018-04-28 | 2022-11-29 | 深圳市卓鸿威科技有限公司 | Restart positioning method based on power management, mobile terminal and readable storage medium |
| CN108762965A (en) * | 2018-05-22 | 2018-11-06 | 东旭集团有限公司 | Daily record lookup method, system and production equipment |
| CN109614042B (en) * | 2018-11-30 | 2022-09-02 | 维沃移动通信有限公司 | Method for storing log information and terminal equipment |
| CN110750375B (en) * | 2019-07-16 | 2023-07-21 | 许昌许继软件技术有限公司 | Embedded equipment and abnormal information processing method thereof |
| CN110716845B (en) * | 2019-09-29 | 2024-03-12 | 上海龙旗科技股份有限公司 | Log information reading method of Android system |
| CN111881012A (en) * | 2020-08-10 | 2020-11-03 | 深圳大势智能科技有限公司 | Log recording method, device, equipment and storage medium |
| CN114679397B (en) * | 2022-05-06 | 2023-12-12 | 苏州德姆斯信息技术有限公司 | Fault analysis system and method for embedded equipment |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20070015704A (en) * | 2005-08-01 | 2007-02-06 | 양재우 | Method for upgrading software mcu |
| CN101320348A (en) * | 2008-06-25 | 2008-12-10 | 中兴通讯股份有限公司 | Log function implementing method of embedded system |
| CN101706822A (en) * | 2009-12-18 | 2010-05-12 | 杭州迪普科技有限公司 | Method and device for improving speed of mounting journal file system |
| US7885122B2 (en) * | 2006-08-10 | 2011-02-08 | Actel Corporation | Flash-based FPGA with secure reprogramming |
| CN102290866A (en) * | 2011-08-26 | 2011-12-21 | Tcl集团股份有限公司 | Control method and control system of intelligent releaser |
| CN103514260A (en) * | 2013-08-13 | 2014-01-15 | 中国科学技术大学苏州研究院 | Internal storage log file system and achieving method thereof |
| CN104699589A (en) * | 2013-12-09 | 2015-06-10 | 鸿富锦精密工业（深圳）有限公司 | Fan error detection system and method |
| CN105426293A (en) * | 2015-10-29 | 2016-03-23 | 汉柏科技有限公司 | Method and system for recording kernel exception stack and vmcore file |
| US9329994B2 (en) * | 2014-02-20 | 2016-05-03 | Kabushiki Kaisha Toshiba | Memory system |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102508621B (en) * | 2011-10-20 | 2015-07-08 | 珠海全志科技股份有限公司 | Debugging printing method and device independent of serial port on embedded system |
| CN103186461B (en) * | 2011-12-30 | 2016-07-06 | 重庆重邮信科通信技术有限公司 | The store method of a kind of field data and restoration methods and relevant apparatus |
| CN102662785B (en) * | 2012-04-12 | 2020-09-25 | 青岛海信移动通信技术股份有限公司 | Method and device for acquiring kernel error information of Android system |
| CN102779047B (en) * | 2012-07-09 | 2016-07-06 | 哈尔滨工程大学 | A kind of embedded software supports platform |
| CN104951395A (en) * | 2014-03-27 | 2015-09-30 | 浙江大华技术股份有限公司 | Debugging information processing method and device for embedded system |
| JP6417742B2 (en) * | 2014-06-18 | 2018-11-07 | 富士通株式会社 | Data management program, data management apparatus and data management method |
| CN105183576B (en) * | 2015-09-21 | 2018-02-13 | 上海斐讯数据通信技术有限公司 | The method and system of abnormal information is collected after a kind of collapse for embedded OLT |
-
2016
- 2016-12-26 CN CN201611218562.9A patent/CN106682162B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20070015704A (en) * | 2005-08-01 | 2007-02-06 | 양재우 | Method for upgrading software mcu |
| US7885122B2 (en) * | 2006-08-10 | 2011-02-08 | Actel Corporation | Flash-based FPGA with secure reprogramming |
| CN101320348A (en) * | 2008-06-25 | 2008-12-10 | 中兴通讯股份有限公司 | Log function implementing method of embedded system |
| CN101706822A (en) * | 2009-12-18 | 2010-05-12 | 杭州迪普科技有限公司 | Method and device for improving speed of mounting journal file system |
| CN102290866A (en) * | 2011-08-26 | 2011-12-21 | Tcl集团股份有限公司 | Control method and control system of intelligent releaser |
| CN103514260A (en) * | 2013-08-13 | 2014-01-15 | 中国科学技术大学苏州研究院 | Internal storage log file system and achieving method thereof |
| CN104699589A (en) * | 2013-12-09 | 2015-06-10 | 鸿富锦精密工业（深圳）有限公司 | Fan error detection system and method |
| US9329994B2 (en) * | 2014-02-20 | 2016-05-03 | Kabushiki Kaisha Toshiba | Memory system |
| CN105426293A (en) * | 2015-10-29 | 2016-03-23 | 汉柏科技有限公司 | Method and system for recording kernel exception stack and vmcore file |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106682162A (en) | 2017-05-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106682162B (en) | Log management method and device | |
| CN109783262B (en) | Fault data processing method, device, server and computer readable storage medium | |
| EP3121726B1 (en) | Fault processing method, related device and computer | |
| US8984335B2 (en) | Core diagnostics and repair | |
| CN107590016B (en) | Power-down restarting identification method and device | |
| CN105607973B (en) | Method, device and system for processing equipment fault in virtual machine system | |
| CN114116280B (en) | Interactive BMC self-recovery method, system, terminal and storage medium | |
| Koutras | Two-level software rejuvenation model with increasing failure rate degradation | |
| CN108958965B (en) | Method, device and equipment for monitoring recoverable ECC errors by BMC | |
| CN110674149B (en) | Service data processing method and device, computer equipment and storage medium | |
| CN112231140A (en) | Method, system, terminal and storage medium for fault recovery of BMC (baseboard management controller) of storage device | |
| CN109710443B (en) | Data processing method, device, equipment and storage medium | |
| JP6880961B2 (en) | Information processing device and log recording method | |
| CN111159051B (en) | Deadlock detection method, deadlock detection device, electronic equipment and readable storage medium | |
| CN109086162B (en) | Memory diagnosis method and device | |
| CN111400153A (en) | Serial port log starting method and device and computer readable storage medium | |
| CN107273291B (en) | Processor debugging method and system | |
| CN115391110A (en) | Test method of storage device, terminal device and computer readable storage medium | |
| CN107025148B (en) | Mass data processing method and device | |
| CN109062718B (en) | Server and data processing method | |
| CN112650613A (en) | Error information processing method and device, electronic equipment and storage medium | |
| CN110851300A (en) | Program process monitoring method and device, computer equipment and readable storage medium | |
| CN111475335A (en) | Method, system, terminal and storage medium for fast recovery of database | |
| US10108499B2 (en) | Information processing device with watchdog timer | |
| US20060230196A1 (en) | Monitoring system and method using system management interrupt |
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 | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20221110 Address after: 250101 4th floor, building 5, zone A2, Hanyu Jingu, Shunhua South Road, high tech Zone, Jinan City, Shandong Province Patentee after: Jinan Yushi Intelligent Technology Co.,Ltd. Address before: 310051 Zhejiang Jiangling Hangzhou Road, Binjiang District, Jiangling, 88, No. 10 South Block 1-11. Patentee before: ZHEJIANG UNIVIEW TECHNOLOGIES Co.,Ltd. |