JP7110942B2 - Information processing device, error analysis support method, and error analysis support program - Google Patents

Description

The present invention relates to an information processing device, an error analysis support method, and an error analysis support program.

Conventionally, in an information processing apparatus such as an image forming apparatus, in order to acquire information necessary for failure analysis, a log for failure analysis and information (accumulated log) of the apparatus in the apparatus are written to another storage device for backup. There is a method to keep

Japanese Patent Application Laid-Open No. 2002-200000 discloses that, in an image processing apparatus capable of implementing the above technique, loss of log information is detected when the loss of the log information in the image processing apparatus is detected. A configuration for preventing loss of log history of jobs executed by the image processing device after the loss of the log history by acquiring log information generated in the image processing device after the event has occurred and recording it in a recording area. is disclosed.

By the way, an error may occur due to this process during the process of writing the accumulated log to another storage device for backup. At this time, in order to investigate the cause of the error, it would be effective if the log in the device when the error occurred could be obtained. However, with the method described in Patent Document 1, when an error occurs during backup of log information (accumulated log) to a storage device, a log (analysis log) for investigating the cause of the error cannot be obtained, and an error occurs. The problem remains that the work efficiency for resolving the problem is lowered.

An object of the present invention is to make it possible to acquire an analysis log for investigating the cause of an error that occurred during backup of an accumulated log.

In order to solve the above-described problems, an information processing apparatus according to one aspect of the present invention includes a first storage device that holds logs output by applications; and a log management unit for writing the accumulated log to a storage device different from the first storage device and the second storage device, wherein the log management The unit writes the log stored in the first storage device to the other storage device as an analysis log for error analysis when an error occurs during the process of writing the accumulated log to the other storage device.

If an error occurs while acquiring the log, the log can be acquired to investigate the cause.

1 is a hardware configuration diagram of an image forming apparatus according to an embodiment; FIG. 2 is a diagram showing the relationship between software and hardware of an image forming apparatus; FIG. 4 is a diagram for explaining a log accumulation procedure in an image forming apparatus; Diagram explaining the internal structure of shared memory Sequence diagram of log accumulation in image forming apparatus FIG. 4 is a diagram for explaining the procedure for backing up accumulated logs in an image forming apparatus; Sequence diagram of log backup in an image forming apparatus Sequence diagram when an error occurs during log backup processing Sequence diagram when creation of the image forming device application log folder fails during log backup processing Diagram showing an example of an analysis log management table Diagram explaining the procedure for copying the analysis log to the SD card Diagram explaining the relationship between shared memory logs and analysis logs Flowchart of processing to write to the analysis log when a log acquisition error occurs Flowchart of logic for writing to analysis log when shared memory loop count is greater than analysis log FIG. 4 is a diagram for explaining a schematic configuration of analysis log acquisition processing of the image forming apparatus according to the present embodiment;

Embodiments will be described below with reference to the accompanying drawings. In order to facilitate understanding of the description, the same constituent elements in each drawing are denoted by the same reference numerals as much as possible, and overlapping descriptions are omitted.

An image forming apparatus 1 will be described below as an example of an information processing apparatus according to the present embodiment.

FIG. 1 is a hardware configuration diagram of an image forming apparatus 1 according to the embodiment. The SOC (System On Chip) 2 is an integrated circuit equipped with a CPU (Central Processing Unit) 2a and functions for controlling peripheral devices. A memory 3 , an HDD (hard disk drive) 4 , an SD card socket 5 and an operation unit 6 are connected to the SOC 2 .

The memory 3 (first storage device) stores data to be held while power is supplied.

HDD4 (second storage device) stores permanent data.

An SD card 7 can be inserted into the SD card socket 5, and permanent data is stored in the inserted SD card 7 (another storage device).

The operation unit 6 is composed of a display unit and an input unit, and is a device for inputting and outputting operations to the image forming apparatus 1 by a user of the image forming apparatus 1 .

FIG. 2 is a diagram showing the relationship between software and hardware of the image forming apparatus 1. As shown in FIG.

As shown in FIG. 2, the software consists of an OS (Operating System) 11, an application 12, and a library 13. FIG. Hardware includes the above-described CPU 2a, memory 3, HDD 4, SD card 7, operation unit 6, and the like.

The OS 11 manages the hardware and provides functions so that the application 12 and the library 13 can use the hardware.

The application 12 provides the user with functions for using the image forming apparatus 1 . In this embodiment, as an example of the application 12, there are an image forming apparatus management application 14 and a log management application 15 (log management unit) that manages logs.

The library 13 is incorporated when the application 12 is created, and provides functions commonly used by a plurality of applications 12 as an API (Application Programming Interface). In this embodiment, a log output library 16 exists as an example of the library 13 .

The image forming apparatus 1 can hold the log information of each application 12 in the memory 3 by using the log management application 15 , write the log information to the HDD 4 , and store the accumulation log 41 in the HDD 4 . FIG. 3 is a diagram for explaining the log accumulation procedure in the image forming apparatus 1. As shown in FIG.

As shown in FIG. 3, the application 12 such as the image forming apparatus management application 14 and the log management application 15, and the OS 11 call the API of the log output library 16 with the log to be output as an argument ("10. API call" process). ).

The log output library 16 stores the log 17 passed as an argument in an empty area from the top of the shared memory 31 ("11. Write out" process). In the example of FIG. 3, the image forming apparatus management application 14, log management application 15, and OS 11 are configured to store logs 17A, 17B, and 17C in shared memories 31A, 31B, and 31C, respectively. Hereinafter, the shared memories 31A, 31B, and 31C may be collectively referred to as the shared memory 31, and the logs 17A, 17B, and 17C may be collectively referred to as the log 17.

When the size of the log 17 on the shared memory 31 exceeds half the size of the shared memory 31, the log output library 16 notifies the log management application 15 that the log 17 has been accumulated (“12. ).

Upon receiving the notification, the log management application 15 checks all the shared memories 31A, 31B, and 31C, and if the size of the logs 17A, 17B, and 17C exceeds half the size of the shared memory, the log is transferred to the shared memory. area 32 to another area 33 on the memory 3 ("13. Writing" process).

The reason for moving the log 17 to another area 33 is to prevent the log 17 from overflowing from the area 32 of the shared memory 31 as a result of an increase in the size of the shared memory 31 because the size of the shared memory 31 is limited. Also, the reason why it works when the size of the shared memory 31 exceeds half is that the log output library 16 cannot write to the shared memory 31 while the log 17 in the shared memory 31 is being moved to another area 33. This is to ensure that

When the size of the log 17 collected in the separate area 33 exceeds half the size of the separate area 33, the collected log 17 is moved to the HDD 4 ("14. Writing" process). This log 17 is stored as an accumulation log 41 in the HDD 4 .

FIG. 4 is a diagram for explaining the internal structure of the shared memory 31. As shown in FIG. As shown in FIG. 4, the shared memory 31 is composed of management information 34 and a log 17. FIG.

The management information 34 is information used to manage the shared memory 31 . The management information includes, for example, loop count and write position information. Log 17 is written in a predetermined area of shared memory 31 .

The size of the shared memory 31 is finite, and as the log 17 is written to the shared memory 31, the writing area becomes full. In that case, the write area is overwritten from the beginning. The "number of loops" in the management information 34 matches the number of overwrites from the beginning. The “write position” of the management information 34 is the position of the log 17 currently written to the shared memory 31 .

The log output library 16 shown in FIG. 3 refers to the management information 34 of the shared memory 31 when storing the log 17 received from the application 12 or OS 11 in the process of "10. API call" in FIG. to For example, the received log 17 is stored from the position next to the writing position. Also, after the log 17 is stored, the storage location of the management information 34 in the shared memory 31 and the value of the number of loops are updated to the latest information.

FIG. 5 is a sequence diagram of log accumulation in the image forming apparatus 1. As shown in FIG. FIG. 5 shows a sequence of exchanges between the log output library 16 and the log management application 15 for log accumulation processing.

The application 12 calls the API of the log output library 16 with the log as an argument (step 1).

The log output library 16 stores the log 17 in an empty area toward the top of the shared memory 31 (step 1.1: holding step).

When the size of the log 17 on the shared memory 31 exceeds half the size of the shared memory 31, the log output library 16 notifies the log management application 15 that the log 17 has been accumulated (step 2).

When the log management application 15 receives the notification, it checks all the shared memories 31A, 31B, and 31C. The log 17 is moved to another area 33 on the memory 3 (step 2.1).

When the size of the logs 17 collected in the separate area 33 exceeds half the size of the separate area 33, the log management application 15 moves the collected logs 17 to the HDD 4 (step 2.2: storage step).

Further, the image forming apparatus 1 can copy the accumulation log 41 stored in the HDD 4 to the SD card 7 to back it up by using the log management application 15 . FIG. 6 is a diagram for explaining the procedure for backing up the accumulation log 41 in the image forming apparatus 1. As shown in FIG.

When the user inserts the SD card 7 into the SD card socket 5 and operates the operation unit 6 to start log acquisition, the log management application 15 stores an output destination folder ( A storage log folder 71) is created, and the storage logs 41 (“log 1” and “log 2” in FIG. 6) stored in the HDD 4 are copied to the folder 71 (“21. copy” process).

Further, the image forming apparatus management application 14 creates a log 17A ("log a1" in FIG. 6) based on the internal information of the application, and stores the log 17A in the folder created by the log management application 15 (image forming apparatus management application log folder 72). ) (“22. Generate” process).

FIG. 7 is a sequence diagram of log backup in the image forming apparatus 1. FIG.

When the user inserts the SD card 7 into the SD card socket 5 of the image forming apparatus 1 and operates the operation unit 6 to start log acquisition (step 1), the image forming apparatus management application 14 starts the log management application 15. is requested to acquire the accumulation log 41 (step 1.1).

The log management application 15 creates an output destination folder (accumulation log folder 71) in the SD card 7, and copies the accumulation log 41 (“log 1” and “log 2” in FIG. 6) accumulated in the HDD 4 to the folder 71. (step 1.1.1: accumulation log writing step).

The log management application 15 creates the folder 72 of the image forming apparatus management application log in the SD card 7 (step 1.1.2), and requests the image forming apparatus management application 14 to acquire the log 17A (step 1.1.2). 1.3).

The image forming apparatus management application 14 creates a log 17A (“log a1” in FIG. 6) based on the internal information of the application and stores it in the image forming apparatus management application log folder 72 (step 1.2).

When the image forming apparatus management application 14 notifies the log management application 15 of the completion of log acquisition (step S1.3), the log management application 15 notifies the image forming apparatus management application 14 of the completion of log acquisition (step S1.3). ).

The image forming apparatus management application 14 displays completion of log acquisition on the operation unit 6 to notify the user of the log acquisition completion (step 2.1).

The user collects the SD card 7 and uses the log 17 for failure analysis.

The above FIGS. 6 and 7 explained the normal procedure of log backup. In contrast, this embodiment has a function of writing an analysis log 74 (see FIG. 11) corresponding to the error type from the memory 3 to the SD card 7 when an error occurs during log backup processing. The analysis log 74 is a log that is stored in an external storage device such as the SD card 7 in order to analyze an error that has occurred during log acquisition of the image forming apparatus 1 . This analysis log writing process (error analysis support method) will be described below.

FIG. 8 is a sequence diagram when an error occurs during log backup processing. The basic sequence in FIG. 8 is the same as the sequence diagram of log backup in the image forming apparatus 1 in FIG. 7, but differs in the following points.

(1) If an error occurs in step 1.1.1 "Create an output destination folder on the SD card and copy the logs accumulated in the HDD to that folder", for example, the accumulation log 41 cannot be read from the HDD4. If so, step 1.1.2 “Copy analysis log to SD” is executed (analysis log writing step).

(2) If an error occurs in step 1.2 "Create a log based on the internal information of the application and store it in the folder of the image forming apparatus management application log", the image forming apparatus management application 14 performs step 1. 3. Notify the log management application 15 of the error with 3 "notification of completion of log acquisition". Upon receiving the error notification, the log management application 15 executes step 2 "copy analysis log to SD" (analysis log writing step).

(3) When the log management application 15 detects that an error has occurred even once, it notifies the image forming apparatus management application 14 of the occurrence of the error in step 3 "log acquisition completion notification". When the image forming apparatus management application 14 receives the fact that the error has occurred, it displays on the operation unit 6 that the log acquisition has failed in step 3.1 "Display completion of log acquisition on operation unit".

FIG. 9 is a sequence diagram when creation of the image forming apparatus application log folder 72 fails during log backup processing. The basic sequence in FIG. 9 is the same as the sequence diagram of log backup in the image forming apparatus 1 in FIG. 7, as in FIG. 8, except for the following points.

(1) If an error occurs in step 1.1.2 "create folder for image forming apparatus management application log in SD card", for example, if folder 72 cannot be created in SD card 7, step 1.1. 2 Execute "copy analysis log to SD" (analysis log writing step).

(2) The log management application 15 notifies the image forming apparatus management application 14 of the occurrence of an error in step 2 "log acquisition completion notification". When the image forming apparatus management application 14 receives the fact that the error has occurred, it displays on the operation unit 6 that the log acquisition has failed in step 2.1 "Display completion of log acquisition on operation unit".

The sequence in FIG. 9 is different from the sequence in FIG. 8 in that the log management application 15 does not "request log acquisition" to the image forming apparatus management application 14 . This is because the creation of a location for storing the log created by the image forming apparatus management application 14 has failed, so there is no place to store the log, and the processing is skipped.

Further, in this embodiment, the log management application 15 can appropriately select the analysis log 74 required for analysis according to the type of error and write it to the SD card 7 when an error occurs. The log management application 15 has, for example, a management table 15A of the analysis log 74 as shown in FIG.

FIG. 10 is a diagram showing an example of the management table 15A of the analysis log 74. As shown in FIG. The management table 15A of the analysis log 74 associates the timing at which an error occurred during log acquisition with the type of log 17 required to analyze the error. In the example of FIG. 10, items are provided for (1) and (2) in the sequence diagram of FIG. 8 and (1) in the sequence diagram of FIG. For example, when an error occurs in the step of "creating a folder for the image forming apparatus management application log in the SD card", it is possible to analyze the logs 17C and 17B of the OS 11 and the log management application 15. FIG.

This management table 15A is built into the log management application 15 as fixed values and cannot be dynamically changed.

"Copying the analysis log to the SD" listed as a process when an error occurs in the error sequences of FIGS. 8 and 9 will be described with reference to FIG. FIG. 11 is a diagram for explaining the procedure for copying the analysis log 74 to the SD card 7. As shown in FIG.

In the process of copying the analysis log 74 to the SD card 7, the log management application 15 mainly performs the following processes.

(1) If the SD card 7 does not have an analysis log folder 73, create a folder. A unique number is added to the analysis log folder 73 for each log acquisition. In other words, the name of the folder created when the user executed log acquisition using the operation unit 6 last time and an error occurred differs from the name of the folder created when the error occurred this time.

The "unique number" is a value obtained by converting the time when the log management application 15 received log acquisition into the YYYY_MM_DD_HH_MM_SS format. YYYY is the year, MM is the month, DD is the day, HH is the hour, MM is the minute, and SS is the second. For example, if a request is received at 18:50:20 on October 1, 2018, the number 2018_10_01_18_50_20 is added.

(2) Based on the management table 15A of the analysis log 74 in FIG. 10, the type of log 17 to be acquired is determined from the timing at which the error occurred. In the example of FIG. 11, the log 17B of the log management application 15 and the log 17C of the OS 11 are selected.

(3) The logs 17B and 17C stored in the shared memories 31B and 31C are stored in the analysis log folder 73 of the SD card 7 from the shared memories 31B and 31C corresponding to the types of the logs 17B and 17C determined in (2) above, respectively. write out. Since which shared memory 31 is used by each application 12 is set in advance, the log management application 15 can search for the shared memory 31 for the log 17 required for analysis.

At this time, if the log 76A of the same type has already been created in the analysis log folder 73 of the SD card 7, only the difference 76B is added to the existing log without overwriting. FIG. 12 is a diagram for explaining the relationship between the log 17 of the shared memory 31 and the analysis log 74. As shown in FIG.

The analysis log 74 is a file composed of management information 75 and log 76 . The management information 75 has the loop count and write position. A log 76 is a copy of the log 17 in the shared memory 31 .

When an error occurs during log acquisition of the image forming apparatus 1 , an analysis log 74 is created, and the loop count and write position in the management information 34 of the shared memory 31 are written in the management information 75 area of the analysis log 74 . , log 76 is appended. After that, if an error occurs in log acquisition during the same operation, the management information 75 of the analysis log 74 is updated based on the management information 34 of the shared memory 31, and the log 17 of the shared memory 31 is saved to the file of the analysis log 74. It will be added. That is, only the difference 76B between the log 76A already recorded in the analysis log 74 and the current log 17 in the shared memory 31 is added to the analysis log 74, and the existing log 76A and the newly added difference 76B are added to the analysis log 74. It becomes the latest log 76 .

Note that if there are a plurality of shared memories 31, the analysis log 74 is created individually for each.

The logic for writing to the analysis log 74 when a log acquisition error occurs will be described with reference to FIG. FIG. 13 is a flow chart of writing processing to the analysis log 74 when a log acquisition error occurs.

Writing to the analysis log 74 is performed in the following order.

(1) If there is no analysis log folder 73 in the SD card 7, create it (steps S101, S102)

(2) Referring to the management table 15A of the analysis log 74 of FIG. 10, the log 17 necessary for analysis is determined from the timing of error occurrence (step S103).

(3) Perform subsequent processing for each log 17 required for analysis (steps S104 and S105).

(4) If the analysis log 74 corresponding to the log 17 required for analysis does not exist in the analysis log folder 73 (NO in step S106), a file for the analysis log 74 is created (S107), and the log 17 required for analysis The management information 34 of the corresponding shared memory 31 is written to the beginning of the analysis log 74 (S108), and the log 17 in the shared memory 31 is added to the analysis log 74 (S109). As the size of the log 17 of the shared memory 31 to be written in the analysis log 74, the value of the write position in the management information 34 of the shared memory 31 is used.

(5) On the other hand, if the analysis log 74 corresponding to the log 17 required for analysis exists in the analysis log folder 73 (YES in step S106), the management information 75 of the analysis log 74 and the management information 34 of the shared memory 31 are compared (S110) to determine whether there is a difference between the log 17 of the shared memory 31 and the log 76 of the analysis log 74. FIG.

Whether or not there is a difference is determined using the loop count and write position recorded in the management information 34 of the shared memory 31 and the management information 75 of the analysis log 74 . It can be considered that there is no difference between the analysis log 74 and the shared memory 31 because the number of loops and the write position match. If the number of loops in the shared memory 31 and the write position are larger than those in the analysis log 74 , it is considered that a difference has occurred, and only the difference 76B is added to the analysis log 74 .

(6) When the management information 75 of the analysis log 74 and the loop count of the management information 34 of the shared memory 31 match (YES in S111), and the write position of the shared memory 31 and the position of the analysis log 74 match ( NO in S112), that is, if there is no difference between the log 17 of the shared memory 31 and the log 76 of the analysis log 74, there is no need to copy the log 17 to the analysis log 74, so the processing of the log 17 is performed. is skipped and the process returns to step S104.

(7) On the other hand, when the management information 75 of the analysis log 74 and the loop count of the management information 34 of the shared memory 31 match (YES in S111) and the write position of the shared memory 31 is larger than the position of the analysis log 74; (YES in S112), that is, if there is a difference between the log 17 of the shared memory 31 and the log 76 of the analysis log 74, the number obtained by subtracting the writing position of the analysis log 74 from the writing position of the shared memory 31 (difference 76B) is copied from the log 17 of the shared memory 31 to the analysis log 74 (S113). Further, when the management information 75 of the analysis log 74 is updated with the management information 34 of the shared memory 31 (S114), the processing of the log 17 is completed and the process returns to step S104.

(8) If the number of loops in the shared memory 31 is greater than that in the analysis log 74 (NO in step S111→YES in step S115), the log 17 in the shared memory 31 is added to the analysis log file. (S116). Further, when the management information 75 of the analysis log 74 is updated with the management information 34 of the shared memory 31 (S114), the processing of the log 17 is completed and the process returns to step S104.

If the number of loops in the shared memory 31 is smaller than that in the analysis log 74 (NO in step S111→NO in step S115), the processing of the log 17 is skipped and the process returns to step S104.

In the process of step S116, if the number of loops in the shared memory 31 is greater than that of the analysis log 74, the logs in the area after the write position in the shared memory 31 can be considered as valid logs or invalid logs. . Therefore, in step S116, it is first determined whether the log in the area after the write position in the shared memory 31 is valid or invalid. After adding to the subsequent analysis log 74, the log 17 of the write position in the shared memory 31 may be added. The logic is further described with reference to FIG.

FIG. 14 is a flow chart of logic for writing to the analysis log 74 when the number of loops in the shared memory 31 is greater than the analysis log 74 .

Whether or not the log 17 in the area after the write position of the shared memory 31 is valid is determined by comparing the number of loops and the write position of the shared memory 31 and the analysis log 74 .

If the loop count difference is greater than 1 (YES in S201), all areas of the shared memory 31 are considered valid. In this case, considering the order, the area after the write position in the shared memory 31 and the area before it are added to the analysis log 74 in this order (S202, S203).

On the other hand, if the difference in the number of loops is 1 (NO in S201), the writing positions of the shared memory 31 and the analysis log 74 are compared, and the area after the larger value is considered valid. If the write position of the analysis log 74 is larger than the shared memory 31 (YES in S204), considering the order, the area of the shared memory 31 after the write position of the analysis log 74 is added to the analysis log 74. The area before the write position of the shared memory is added to the analysis log 74 (S205, S206). If the write position in the shared memory 31 is larger than the analysis log 74 (NO in S204), steps S202 and S203 are processed.

If the difference in the number of loops is 0 (YES in S111) or negative (NO in S111→NO in S115), the determination is made in the flow of FIG.

Each function of the image forming apparatus management application 14, the log management application 15, the log output library 16, and the OS 11 described above causes predetermined computer software (error analysis support program) to be read into hardware such as the CPU 2a, SOC 2, and memory 3. As a result, the SOC 2 and the operation unit 6 are operated under the control of the CPU 2a, and data is read from and written to the memory 3 and the HDD 4. That is, the image forming apparatus 1 functions as the image forming apparatus management application 14, the log management application 15, the log output library 16, and the OS 11 shown in FIG. 2 by executing the error analysis support program of the present embodiment on a computer.

Effects of the image forming apparatus 1 according to the present embodiment will be described with reference to FIG. FIG. 15 is a diagram illustrating a schematic configuration of analysis log acquisition processing of the image forming apparatus 1 according to this embodiment. The image forming apparatus 1 of this embodiment includes a memory 3 that holds a log 17 output by an application 12, and an HDD 4 that stores an accumulation log 41 output from the memory 3 when the log 17 accumulates a predetermined amount or more. . The accumulated log 41 is written by the log management application 15 of the image forming apparatus 1 to the SD card 7 which is another storage device different from the memory 3 and the HDD 4 . Especially in this embodiment, as shown in FIG. 15, when an error occurs during the process of writing the accumulation log 41 to the SD card 7, the log management application 15 reads the log 17 stored in the memory 3. It is written to the SD card 7 as an analysis log 74 for error analysis.

With this configuration, it is possible to acquire the analysis log 74 for investigating the cause of an error that occurred during the backup of the accumulation log 41. Therefore, it is possible to suitably support the error analysis work by the user, and to eliminate the error. can improve work efficiency.

Further, in the image forming apparatus 1 of the present embodiment, when an error occurs, the log management application 15 identifies the type of error, and identifies the types of logs 17A, 17B, and 17C required for error analysis according to the type. Then, the specified type of log 17 is written from the memory 3 to the SD card 7 . With this configuration, the logs 17 necessary for analyzing various types of errors can be individually acquired, and since the logs 17 not required for analysis are not acquired, the analysis log 74 can be acquired without excess or deficiency. As a result, the capacity of the SD card 7 for writing the analysis log 74 can also be suppressed.

Further, in the image forming apparatus 1 of the present embodiment, when the log management application 15 writes the analysis log 74, if the same type of analysis log 74 already exists in the SD card 7, the written analysis log 76A and the current A difference 76 B from the log 17 held in the memory 3 is written to the SD card 7 . With this configuration, the content of the analysis log 74 stored in the SD card 7 can be prevented from being duplicated, so the capacity of the SD card 7 for writing the analysis log 74 can be further reduced.

The present embodiment has been described above with reference to specific examples. However, the present disclosure is not limited to these specific examples. Design modifications to these specific examples by those skilled in the art are also included in the scope of the present disclosure as long as they have the features of the present disclosure. Each element included in each specific example described above and its arrangement, conditions, shape, etc. are not limited to those illustrated and can be changed as appropriate. As long as there is no technical contradiction, the combination of the elements included in the specific examples described above can be changed as appropriate.

In the above embodiment, the image forming apparatus 1 is described as an example of the information processing apparatus according to the embodiment. Any device or system other than the image forming device 1 may be used.

In the above-described embodiment, the SD card 7 attached to the image forming apparatus 1 was exemplified as the "other storage device" for storing accumulated log backups and analysis logs. It may be an external storage medium or an external storage device other than the SD card 7 connected to, a storage device mounted on another computer device such as a server via a network, or the memory 3 in the image forming apparatus 1, Another storage device different from the HDD 4 may be used.

1 Image forming device (information processing device)
3 memory (first storage device)
4 HDD (second storage device)
7 SD card (other storage device)
15 Log management application 17 Log 41 Accumulation log 74 Analysis log

JP 2016-066214 A

Claims (6)

a first storage device that holds logs output by the application;
a second storage device for storing an accumulation log output from the first storage device when the log accumulates a predetermined amount or more;
a log management unit that writes the accumulation log to a storage device different from the first storage device and the second storage device;
with
The log management unit
If an error occurs during the process of writing the accumulated log to the other storage device, writing the log stored in the first storage device to the other storage device as an analysis log for error analysis;
Information processing equipment. The log management unit
when the error occurs, identifying the type of the error, identifying the type of log necessary for error analysis according to the type, and transferring the identified type of log from the first storage device to the other storage device write out to
The information processing device according to claim 1 . The log management unit
When writing the analysis log, if the other storage device already has the same type of analysis log, the difference between the written analysis log and the current log held in the first storage device is stored in the other storage device. write to the device,
The information processing apparatus according to claim 1 or 2. The other storage device is an external storage device connectable to the information processing device,
The information processing apparatus according to any one of claims 1 to 3. An error analysis support method executed by an information processing device comprising a first storage device and a second storage device,
a holding step of holding the log output by the application in the first storage device;
a storage step of storing an accumulated log output from the first storage device when the log accumulates a predetermined amount or more in the second storage device;
an accumulation log writing step of writing the accumulation log to another storage device different from the first storage device and the second storage device;
an analysis log writing step of writing the log stored in the first storage device to the other storage device as an analysis log for error analysis when an error occurs during the processing of the accumulated log writing step;
including,
Error analysis support method. An error analysis support program for an information processing device comprising a first storage device and a second storage device,
to the computer,
a holding function for holding a log output by an application in the first storage device;
a storage function for storing, in the second storage device, an accumulated log output from the first storage device when the log accumulates a predetermined amount or more;
an accumulation log writing function for writing the accumulation log to another storage device different from the first storage device and the second storage device;
an analysis log writing function for writing the log stored in the first storage device to the other storage device as an analysis log for error analysis when an error occurs during processing of the accumulation log writing function;
An error analysis support program for realizing

Images