JP6743546B2 - Information processing apparatus, information processing system, information processing method, and program - Google Patents

Description

The present invention relates to an information processing device, an information processing system, an information processing method, and a program.

For example, an information processing device such as a printer device or a fax communication device has an operating state in which it can operate in response to an operation request from the outside, such as a PC (Personal Computer) or a communication line, and suspends some functions. It operates by a complicated program, such as making a transition to the standby state waiting for an operation request. Therefore, in the unlikely event that an information processing device fails, the operation information, status information, and error information of the information processing device are saved and collected as a log inside the information processing device in order to quickly find the location of the cause. The technology to do is known.

Here, in the log storage/collection technology for a plurality of information processing devices (for example, MFPs), the log collection amount increases when the amount of log data or the number of MFPs increases, and the log collection/collection technique increases. There is a problem that it takes a long time. In order to solve such a problem, for example, Patent Document 1 discloses a configuration in which the log recording frequency is dynamically changed for each terminal to reduce the log collection amount as a whole.

However, in the technique disclosed in Patent Document 1, when a problem occurs in a terminal that is set to “do not record logs” because the log recording amount is too small to reduce the log collection amount, the problem is solved. There is a problem that it is not possible to record the log for, and it becomes impossible to solve the problem.

The present invention has been made in view of the above, and an information processing apparatus, an information processing system, an information processing method, and an information processing method capable of obtaining sufficient information for solving a problem while suppressing the amount of logs collected The purpose is to provide the program.

In order to solve the above-mentioned problems and to achieve the object, the present invention provides a self-device or one or more other information processing devices when a failure occurs in the self-device or one or more other information processing devices. The device identification information for identifying, the fault identifier for identifying the fault that has occurred, and the log management information for identifying the log relating to the fault are acquired by the acquisition unit that acquires the fault management information, and the acquisition unit that acquires the fault management information. A storage unit that stores the failure management information, and a collection unit that collects the logs identified by the log identification information for all the log identification information associated with the failure identifier that identifies a designated failure Is an information processing apparatus including.

According to the present invention, it is possible to provide an information processing apparatus, an information processing system, an information processing method, and a program that can obtain sufficient information for solving a problem while suppressing the amount of logs collected.

FIG. 1 is a diagram illustrating an example of the configuration of an information processing system. FIG. 2 is a diagram illustrating an example of the hardware configuration of the MFP. FIG. 3 is a diagram showing an example of a program configuration of the MFP. FIG. 4 is a diagram for explaining respective configurations of Master and Slave. FIG. 5 is a diagram showing an example of the MFP log management information. FIG. 6 is a diagram showing an example of individual information. FIG. 7 is a diagram showing an example of failure information. FIG. 8 is a diagram for explaining an event of the notification program included in Slave. FIG. 9 is a diagram showing a list of requests. FIG. 10 is a diagram for explaining the function of the management data display program. FIG. 11 is a diagram illustrating an example of functions of each of Master and Slave. FIG. 12 is a flowchart showing an operation example of the information processing system. FIG. 13 is a flowchart showing an operation example of the information processing system. FIG. 14 is a flowchart showing an operation example of Master.

Hereinafter, embodiments of an information processing apparatus, an information processing system, an information processing method, and a program according to the present invention will be described in detail with reference to the accompanying drawings. Hereinafter, as an example of the information processing apparatus according to the present invention, a multifunction peripheral (MFP), which is one aspect of the image forming apparatus, will be described as an example, but the present invention is not limited to this. The multifunction device is a device having a plurality of different functions such as a copy function, a scanner function, a print function, and a fax function.

FIG. 1 is a diagram showing an example of the configuration of the information processing system 100 of this embodiment. As shown in FIG. 1, the information processing system 100 includes a plurality of MFPs 1, which are mutually connected via a network 2 such as the Internet. For convenience of explanation, only two MFPs 1 are illustrated in the example of FIG. 1, but the number of MFPs 1 included in the information processing system 100 is not limited to this and is arbitrary. The two MFPs 1 illustrated in FIG. 1 have a master/slave relationship, and the MFP 1 functioning as a master (Master) functions as a “first information processing device” and the MFP 1 functioning as a slave (Slave) is “ It functions as a "second information processing device".

FIG. 2 is a diagram illustrating an example of the hardware configuration of the MFP 1. As shown in FIG. 2, the MFP 1 includes a CPU 11, a ROM 12, a RAM 13, an HDD (hard disk drive) 14, an SD memory card 15, a communication I/F (interface) 16, an operation panel 17, and an engine section. 18 and 18 are connected to each other via a system bus 19.

The CPU 11 centrally controls the operation of the MFP 1. The CPU 11 controls the overall operation of the MFP 1 by executing a program stored in the ROM 12 or the like by using the RAM 13 as a work area (work area), and performs various functions such as the copy function, the scanner function, the fax function, and the printer function described above. To realize.

The communication I/F 16 is an interface for connecting to the network 2. Operation panel 17 receives various operations from the user and displays information about MFP 1. For example, the operation panel 17 is composed of a liquid crystal touch panel or the like. The engine unit 18 is hardware for performing processing other than general-purpose information processing and communication for realizing a copy function, a scanner function, a fax function, and a printer function. For example, a scanner (image reading unit) that scans and reads an image of a document, a plotter (image forming unit) that prints on a sheet material such as paper, and a fax unit that performs fax communication are provided. Further, a specific option such as a finisher for sorting printed sheet materials or an ADF (automatic document feeder) for automatically feeding a document can be provided.

FIG. 3 is a diagram showing an example of a program configuration on the MFP 1 alone. As shown in FIG. 3, the MFP 1 includes four layers of hardware, OS (operating system), service, and application. Of these, the OS, services, and applications are software, and each has a memory area for recording a debug log. The numerical value written in parentheses with each program name is an ID value indicating the debug log area. For example, "copy" in the application has the number 2000, and the OS has the numbers 100 to 150. Since the OS internally operates a plurality of programs such as device drivers, it may have a plurality of IDs.

The hardware is a physical element that constitutes the MFP 1, and has resources such as the engine unit 18, the HDD 14, the SD memory card 15, the memory including the debug log area, and the CPU 11.

The OS is a general-purpose operating system such as UNIX (registered trademark), and executes each service and application software in parallel as processes. In the service layer, dozens of service programs are constantly operating to monitor and manage the device status. For example, in FIG. 3, the service layer is divided into two layers. In the lower layer, service management that performs overall management of services, debug log recording that records the debug log area of each software on the HDD 14, and debug log that exchanges debug log information when a problem occurs between multiple MFPs 1 on the network 2 Network management (Master or Slave) operates. The relationship between Master and Slave will be described later. In the upper layer, start/stop control that controls the start and end of services and applications, energy-saving control that controls the power saving mode of the device, setting management that manages device settings, network management that manages the device network, device The failure management for managing the failure status of the device, the device door opening/closing management for managing the paper tray of the device and the door for feeding/discharging, and the application management for managing the application running on the device are operating.

The application is a software group for realizing a function that a person who operates the device wants to execute. For example, there are a copy that operates when it is desired to perform a copy operation, a printer operation, a scanner operation, a FAX operation, and the like, a firmware update that operates when updating the firmware of a printer, a scanner, a FAX, and an apparatus.

FIG. 4 is a diagram for explaining respective configurations of the Master-MFP 1 (hereinafter simply referred to as “Master”) and the Slave-MFP 1 (hereinafter simply referred to as “Slave”). The information processing system 100 according to the present embodiment includes a plurality of MFPs 1 that are arranged to be communicable on the network 2, and classifies the plurality of MFPs 1 into two types, Master and Slave, regarding log management. For convenience of explanation, each of the Master and the Slave is one, but the present invention is not limited to this, and a plurality of Masters and Slave may exist, for example.

As illustrated in FIG. 4, the Master includes Master management information 101, a notification reception program 102, a request program 103, and a management data display program 104. Although the details of the Master management information 101 will be described later, the Master management information 101 has fault information related to each fault under its control and its own device, and is managed in association with a fault log (fault log).

The notification receiving program 102 is a program that operates in cooperation with the slave notification program 112. Although the details will be described later, an operation of adding information to the Master management information 101 is performed in response to an event notification from Slave or Master.

The request program 103 is a program that operates in cooperation with the slave request reception program 113. Although details will be described later, the operation of transmitting a request from the master to the slave is performed in response to a request from the user through a UI operation. Depending on the request content, the acquired log is also written in the storage device such as the HDD 14 and the SD memory card 15. Further, depending on the content of the request, communication with a plurality of slaves will be performed.

The management data display program 104 is a program for browsing and operating the Master management information 101 on the operation panel 17. Details will be described later.

As shown in FIG. 4, the slave includes slave management information 111, a notification program 112, and a request reception program 113. Although omitted here for simplification of description, the slave may further include a program corresponding to the management data display program 104 included in the master. In order to display the management data on the slave side, the management data is inquired to the master, and after the reply is received, it is displayed on the slave side.

Although the details of the slave management information 111 will be described later, the slave management information 111 manages an individual identifier of the parent Master, a log relating to a failure that occurred in the own device, and the like. Also, in a situation where communication with the Master is interrupted, it also functions as an area for temporarily storing unnotified data. In the following description, the Master management information 101 and the Slave management information 111 may be collectively referred to as “MFP log management information”.

The notification program 112 is a program that operates in cooperation with the Master notification reception program 102, and will be described in detail later, but is a program that notifies an event to Master. When the Master does not exist, the information is stored locally to prepare for communication restart with the Master.

The request receiving program 113 is a program that operates in cooperation with the master request program 103, and will be described in detail later, but performs a process of receiving a request from the master and returning the result to the master. Depending on the content of the request, the log is pinned (setting that does not allow deletion of the log), and thereafter processing for preventing deletion is also performed.

Further, the Master and the Slave may be able to mutually send activation requests to each other and transition from the stopped state to the activated state. As a result, by activating one MFP 1 at hand, it is possible to acquire information on all the MFPs 1 existing on the network 2.

Next, the MFP log management information included in each of Master and Slave will be described. The Master management information 101 managed by Master and the Slave management information 111 managed by Slave are represented by this information.

As shown in FIG. 5, the MFP log management information includes parent information (parent), the number of children, and an individual information group.

The parent information is information on the MFP 1 that is the parent (Master) of the own device, and is represented by individual information described below. In the case of Master, there is no parent information. The number of children represents the number of MFPs 1 that are the slaves of the own device. In case of Slave, it becomes zero. The individual information group is a data string including a plurality of pieces of individual information described below, and is information for each child (Slave) of the own device. In the case of Slave, there is no individual information group.

As shown in FIG. 6, the individual information includes an individual identifier and a failure information group. The individual identifier is an example of “apparatus identification information”, and is information for identifying the MFP 1 existing on the network 2. For example, the individual identifier may be an IP address or the like. The failure information group is a data string including a plurality of failure information to be described later.

As shown in FIG. 7, the failure information includes an occurrence time, an occurrence source log ID, a failure identifier, and pin stop on/off information. The occurrence time indicates the time when the failure occurred. The source log ID is an example of “log identification information”, and is the log ID (information for identifying a log) for each program shown in FIG. The fault identifier is information for identifying the fault that has occurred. In this example, a number is assigned such as "S100" when the print information cannot be correctly generated at the time of copying, and "S001" when the program terminates illegally. The pin stop on/off information is an example of “erasability information” and is information indicating whether or not log erasing is permitted. In this example, the pin stop on information means that the log deletion is not permitted, and the pin stop off information means that the log deletion is permitted.

FIG. 8 is a diagram for explaining an event of the notification program 112 included in Slave. In this example, as shown in FIG. 8A, there are three types of events, “E1.start notification”, “E2.stop notification”, and “E3.failure occurrence notification”. “E1. Activation notification” is a notification for informing Master that the slave has been activated. “E2. Stop notification” is a notification for notifying Master that Slave has stopped. “E3. Failure occurrence notification” is a notification for notifying the Master that a failure has occurred in the slave, and as shown in FIG. 8B, the occurrence time, the occurrence source log ID, the failure identifier, and the pin stop on/ It includes off information. More specifically, an individual identifier and the like are also included. Upon receipt of this, the Master searches the Master management information 101 for the individual information of the corresponding MFP 1 and adds it to the failure information group. Further, when the notification is received as the pin stop off, the Master searches for the fault information having the same fault identifier, confirms whether the fault information including the pin stop on information exists from the fault information, If the failure information including stop on is present, a request for setting the pin stop to on is sent to the source Slave. As a result, if the MFP 1 group connected to the same network 2 has the same failure, it can be detected and managed as the same failure.

Next, a request, which is one of the commands transmitted from Master to Slave, will be described. FIG. 9 is a diagram showing a list of requests. As shown in FIG. 9, the request includes “R1. management information collection”, “R2. log collection-collective”, “R3. log collection-single”, “R4. log collection-pin unit”, “R5. There are five types of requests for "pin stop setting".

“R1. Collect management information” is a request for the Master to take up the information stored locally when the Slave cannot communicate with the Master. It is used when the Master is restarted.

The requests R2 to R4 are requests for collecting the actual status of the logs, not the log management information. In a normal operation, the Master grasps the information on the occurrence of the failure by the event notification. This request is used when collecting a log when a failure occurs, based on the information that is grasped.

“R2. Log collection-collective” collects logs when a failure occurs for all the MFPs 1 on the network 2 based on the Master management information 101. In “R3. Log collection-single unit”, the MFP 1 and the issuer log ID are specified to collect the log. By operating the Master, the log of the targeted MFP 1 can be collected. In “R4. Log collection-pin unit”, the log is collected for all the MFPs 1 on the network 2 based on the Master management information 101, for the pin-stopped target. As a result, it is possible to collectively collect information (logs) about failures that are expected to have the same content. “R5.pin stop setting” is a request for requesting the target slave to change the pin stop on/off information to on.

Next, the management data display program 104 will be described with reference to FIG. The management data display program 104 displays on the operation panel 17 a screen for displaying "fault information on the MFP network" shown in FIG. 10A and a screen for displaying "same fault information" shown in FIG. 10B. ..

First, the screen for displaying the “fault information on the MFP network” in FIG. 10A will be described from the left element of the screen. In the "machine list", based on the Master management information 101, the names of the MFPs 1 in which a failure has occurred even once are displayed in a list. When the "collect all" button at the bottom of the table is pressed, all the logs related to the failure are collected by network communication from all the MFPs 1 displayed in the list, and are stored in the master storage device. For example, the user can handle the failure log by saving it in a USB memory or the like.

When the name of any one of the MFPs 1 being displayed in the “machine list” is touched, a list of failures that occurred in the touched MFP 1 is displayed in the “fault list” on the right side. When the "collective collection" button at the bottom of the table is pressed, the failure logs for all the failures displayed in the "failure list" are collected by network communication and saved in the Master's storage device.

When any of the faults displayed in the “fault list” is touched, detailed information (fault information) of the touched fault is displayed in the “details” on the right side. Regarding "pin stop" among the details, a button for switching on/off is displayed on the right side. By operating this button, the user can instruct whether to stop the pin. The pin stop is an operation of locking the relevant failure log so as not to be erased from the MFP 1. Normally, the log recorded in the MFP 1 is continuously output, and therefore, it is common to employ a mechanism in which the log is overwritten or erased after a certain period of time. Therefore, if the log at the time of failure (fault log) is deleted, it becomes difficult to analyze. Therefore, a measure to stop the pin is taken. In the present system, the failure identifier of the pin-stop target is the same failure detection target, and when the master receives the failure identifier of the pin-stop target from the notification program 112, it immediately issues a pin-stop request to the slave. When the "collect" button at the bottom of the table is pressed, a log relating to the corresponding fault is collected by network communication and saved in the Master storage device. Further, when the detail-displayed fault indicates pin stop on, pressing the "same fault display" button at the bottom of the table causes a transition to the screen displaying the "same fault information" in FIG. 10B.

The screen displaying the “same fault information” in FIG. 10B will be described from the element on the left side of the screen. On this screen, fault information including the same fault identifier as the fault identifier included in the fault information displayed at the left end can be searched for from all the MFPs 1 connected to the network 2. In the "machine list" at the center of the screen, all the MFPs 1 on the network 2 in which the same failure has occurred are displayed. When the MFP 1 is selected, a list of occurrence times is displayed in the "fault list" on the right side. Also in this example, the log can be collected by pressing the button below each table.

FIG. 11 is a diagram illustrating an example of functions of each of Master and Slave. For convenience of explanation, in the example of FIG. 11, only the functions related to the present invention are mainly illustrated, but the functions possessed by each of Master and Slave are not limited to these. These functions are realized by the CPU 11 executing a program stored in a storage device such as the ROM 12, but not limited to this. For example, at least a part of these functions is a dedicated hardware circuit (for example, It may be realized by a semiconductor integrated circuit or the like).

As shown in FIG. 11, the slave has a first generation unit 121, a transmission unit 122, and a pin stop setting change unit 123. When a failure occurs, the first generation unit 121 associates at least the apparatus identification information for identifying its own apparatus, the failure identifier for identifying the failure, and the log identification information for identifying the log related to the failure. Generate the fault management information. In this example, the combination of the individual identifier described above and the failure information (see FIG. 7) corresponds to failure management information. In this example, the fault management information includes an individual identifier, a fault identifier, an issuer log ID, and pin stop on/off information (an example of “erasability information”) indicating whether or not to permit log erasure. Can be thought of as at least linked information. The first generation unit 121 generates failure management information every time a failure occurs in the own device.

The transmission unit 122 transmits the fault management information generated by the first generation unit 121 to Master. In this example, the transmission unit 122 transmits the generated fault management information to the Master each time the first generation unit 121 generates the fault management information.

The pin stop setting change unit 123 changes the pin stop off information included in the fault management information transmitted to the Master to the pin stop on information in response to a request from the change control unit 135 on the Master side, which will be described later. The information reflecting the change is returned to the change control unit 135. The specific content of the change control unit 135 will be described later.

As illustrated in FIG. 11, the Master includes a second generation unit 131, a reception unit 132, a storage unit 133, a collection unit 134, and a change control unit 135.

The second generation unit 131 generates failure management information (in this example, a combination of the individual identifier described above and the failure information described above) when a failure occurs. The second generation unit 131 generates failure management information every time a failure occurs in the own device.

The receiving unit 132 receives the fault management information from Slave. The storage unit 133 stores the failure management information generated by the second generation unit 131 or the failure management information received by the reception unit 132. It may be considered that the storage unit 133 stores the above Master management information 101.

In this example, the second generation unit 131 and the reception unit 132 described above each have an individual identifier (““ which identifies the own device or the slave when a failure occurs in the own device or one or more other slaves. "Device identification information"), a failure identifier for identifying a failure that has occurred, and an issuer log ID (an example of "log identification information") for identifying a log related to the failure. It can be considered to function as an “acquisition unit” for acquiring.

The collection unit 134 collects the log identified by the log identification information for each of all the log identification information associated with the failure identifier for identifying the designated failure. In this example, the collection unit 134 refers to the storage unit 133 and identifies all the combinations of issuer log IDs and individual identifiers that are associated with a failure identifier that identifies a failure designated by the user. Then, for each specified combination, the collection unit 134 acquires (collects) the log identified by the issuer log ID included in the combination from the slave identified by the individual identifier included in the combination. The collection target by the collection unit 134 of the present embodiment is a log identified by an issuer log ID associated with pin stop on/off information (pin stop on information) indicating that log deletion is not permitted.

The change control unit 135 uses the fault management information generated when the second generation unit 131 generates fault management information including pin stop on/off information (pin stop off information) indicating that log deletion is permitted. When the information is received by the receiving unit 132, the pin stop on/off information indicating that the deletion of the log is not permitted for the failure identifier that matches the failure identifier included in the failure management information in the storage unit 133. When the (pin stop on information) is linked, the control for changing the pin stop off information included in the failure management information to the pin stop on information is performed. In this example, the change control unit 135 requests the slave identified by the individual identifier included in the failure management information to change the pin stop on/off information to on (pin stop setting request). To send. Then, the response to the pin stop setting request is received from Slave and reflected in the Master management information 101.

FIG. 12 is a flowchart showing an operation example of the information processing system 100 when a failure occurs in Slave. In FIG. 12, the flow on the Slave side and the flow on the Master side are described separately.

First, the flow on the slave side will be described. When detecting the occurrence of a failure (step S1), the first generation unit 121 generates the failure management information described above (step S2). Then, the failure management information generated in step S2 is stored in the failure management information buffer for temporary storage (step S3).

If the notification program 112 has been started (step S4: Yes), the process is continued as it is, and the process proceeds to step S6 described later. When the notification program is not activated (step S4: No), the OS activates the notification program 112 (step S5). Then, the notification program 112 establishes communication with Master (step S6). Next, the notification program 112 (transmission unit 122) confirms whether or not there is failure management information in the failure management information buffer (step S7).

When the result of step S7 is affirmative (step S7: Yes), the notification program 112 (transmission unit 122) transmits the fault management information stored in the fault management information buffer to Master (step S8). Then, the reception of the response from the master is confirmed (step S9), and the processing from step S7 is repeated.

When the result of step S7 is negative (step S7: No), the communication program 112 closes the communication path with Master (step S10).

Next, the flow on the Master side will be described. The notification reception program 102 (reception unit 132) connects to the slave in response to the request from the slave (step S11). Next, the notification reception program 102 (reception unit 132) receives the failure management information from the slave (step S12). Next, the notification receiving program 102 stores the failure management information received in step S12 in the failure management information buffer (step S13). Then, a response to the failure management information received in step S12 is returned to the slave (step S14). After that, the notification receiving program 102 repeats the processing of steps S12 to S14 unless receiving a request for closing the communication path (disconnection request) from the slave. When receiving the disconnection request from the slave, the notification receiving program 102 disconnects the communication with the slave (step S15).

FIG. 13 is a flowchart showing an operation example of the information processing system 100 after Master receives the failure management information from the slave. In FIG. 13, the flow on the Master side and the flow on the Slave side are described separately.

First, the flow on the Master side will be described. As shown in FIG. 13, the Master confirms whether or not there is fault management information in the fault management information buffer (step S21). When the failure management information is present in the failure management information buffer (step S21: Yes), the Master confirms whether or not there is slave data corresponding to the MFP log management information (Master management information 101) (step S22). .. Specifically, the Master determines whether or not the master management information 101 includes a failure information group associated with an individual identifier matching the individual identifier included in the failure management information existing in the failure management information buffer. To confirm.

When the result of step S22 is negative (step S22: No), Master newly creates the slave data (step S23). After step S23 or when the result of step S22 is affirmative (step S22: Yes), Master additionally writes data to the failure information group in the slave data (step S24). More specifically, the Master includes in the failure management information 101 a failure information group associated with an individual identifier matching the individual identifier included in the failure management information read from the failure management information buffer in the Master management information 101. Add the failure information that is described.

Next, in the Master management information 101, Master refers to failure information that includes pin-stop-on information among one or more pieces of failure information that include a failure identifier that matches the failure identifier included in the failure management information read from the failure management information buffer. It is confirmed whether or not exists (step S25). When the result of step S25 is affirmative (step S25: Yes), data (pin stop setting request) is stored in the pin stop setting request buffer (step S26), and the process proceeds to step S27. On the other hand, when the result of step S25 is negative (step S25: No), the process directly proceeds to step S27.

In step S27, the OS activates the request program 103 and establishes communication with Slave (step S28). Then, the request program 103 confirms whether or not data exists in the pin stop setting request buffer (step S29). When the result of step S29 is affirmative (step S29: Yes), the request program 103 (change control unit 135) transmits the pin stop setting request stored in the pin stop setting request buffer to the target slave (step). S30). Then, the reception of the response from the slave is confirmed (step S31), and the processes from step S29 are repeated.

When the result of step S29 is negative (step S29: No), the request program 103 closes the communication path with Slave (step S32).

Next, the flow on the slave side will be described. The request reception program 113 connects to Master in response to the request from Master (step S33). Next, the request reception program 113 receives a pin stop setting request from Master (step S34). Next, the request reception program 113 (pin stop setting changing unit 123) sets the pin stop off information included in the target failure management information (transmitted failure management information) according to the pin stop setting request received in step S34. , Pin stop on information is changed (step S35), and a response is returned to Master (step S36). After that, the request receiving program 113 repeats the processing of steps S34 to S36 unless it receives a request to close the communication path (disconnection request) from the master. When receiving the disconnection request from the Master, the request reception program 113 disconnects the communication with the Master (step S37).

FIG. 14 is a flowchart showing an operation example of Master when collecting logs. As shown in FIG. 14, first, the management data display program 104 receives the designation of a failure from the user (step S41). For example, it may be considered that acceptance of pressing of the “collective collection” button under each table on the screen of FIG. 10B corresponds to acceptance of step S41. Next, the request program 103 (collection unit 134) refers to the Master management information 101 and identifies all the issuer log IDs associated with the failure identifier that identifies the failure specified in step S41 (step S42). .. Next, the request program 103 (collecting unit 134) collects logs for each issuer log ID specified in step S42 (step S43). In this example, a request for a log is sent to the slave, and the log is received as a response.

As described above, the MFP 1 functioning as the master of the present embodiment, when a failure occurs in its own device or one or more other MFPs 1 (Slave), an individual identifier and a failure identifier for identifying the failure that has occurred. Then, the failure management information associated with at least the issuer log ID for identifying the log relating to the failure is acquired and stored in the storage unit 133. Then, the log identified by the issuer log ID is collected for every issuer log ID associated with the fault identifier for identifying the fault specified by the user operation. As a result, it is possible to obtain sufficient information for solving the problem while suppressing the amount of logs collected.

Although the embodiments according to the present invention have been described above, the present invention is not limited to the above-described embodiments as they are, and constituent elements can be modified and embodied without departing from the scope of the invention in an implementation stage. Further, various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the above-described embodiments. For example, some components may be deleted from all the components shown in the embodiment.

The program executed by the MFP 1 of the above-described embodiment is a file in an installable format or an executable format, which is a CD-ROM, a flexible disk (FD), a CD-R, a DVD (Digital Versatile Disk), or a USB( It may be configured to be provided by being recorded on a computer-readable recording medium such as a Universal Serial Bus), or may be provided or distributed via a network such as the Internet. Further, various programs may be configured to be provided by being pre-installed in a ROM or the like.

1 MFP
2 Network 11 CPU
12 ROM
13 RAM
14 HDD
15 SD memory card 16 Communication I/F
17 Operation Panel 18 Engine Unit 101 Master Management Information 102 Notification Reception Program 103 Request Program 104 Management Data Display Program 111 Slave Management Information 112 Notification Program 113 Request Reception Program 121 First Generation Unit 122 Transmission Unit 123 Pin Stop Setting Change Unit 131 2 generation unit 132 reception unit 133 storage unit 134 collection unit 135 change control unit

Japanese Patent No. 5672491

Claims (7)

When a failure occurs in the own device or one or more other information processing devices, device identification information for identifying the own device or the one or more other information processing devices, a failure identifier for identifying the occurred failure, and An acquisition unit that acquires failure management information associated with at least log identification information that identifies a log related to a failure,
A storage unit that stores the failure management information acquired by the acquisition unit;
A collection unit that collects the logs identified by the log identification information for each of all the log identification information associated with the failure identifier that identifies the designated failure,
Information processing device. The fault management information is information in which the device identification information, the fault identifier, the log identification information, and erasability information indicating whether to permit erasing of the log are associated with each other,
The collection target by the collection unit is the log identified by the log identification information associated with the erasability information indicating that erasing of the log is not permitted,
The information processing apparatus according to claim 1. When the failure management information including the erasability information indicating permission to delete the log is acquired by the acquisition unit, the failure management information that matches the failure identifier included in the failure management information in the storage unit When the erasability information indicating that erasure of the log is not permitted is associated with the failure identifier, the erasure availability information included in the failure management information acquired by the acquisition unit is set to the log. Further comprising a change control unit that performs control for changing to the erasure permission information indicating that erasure of
The information processing apparatus according to claim 2 . The relationship between the information processing apparatus and the one or more other information processing apparatuses is a master/slave relationship, and the information processing apparatus functions as a master.
The information processing apparatus according to any one of claims 1 to 3. An information processing system including at least a first information processing device and a second information processing device,
When a failure occurs, the second information processing apparatus has at least a string of apparatus identification information for identifying its own apparatus, a failure identifier for identifying the failure that has occurred, and log identification information for identifying a log relating to the failure. A first generation unit that generates the attached fault management information;
A transmission unit that transmits the failure management information generated by the first generation unit to the first information processing device,
The first information processing device is
A second generation unit that generates the failure management information when a failure occurs;
A receiving unit that receives the failure management information from the second information processing device;
A storage unit that stores the fault management information generated by the second generation unit or the fault management information received by the reception unit;
A collection unit that collects the logs identified by the log identification information for each of all the log identification information associated with the failure identifier that identifies the designated failure,
Information processing system. When a failure occurs in the own device or one or more other information processing devices, device identification information for identifying the own device or the one or more other information processing devices, a failure identifier for identifying the occurred failure, and An acquisition step of acquiring the failure management information associated with at least the log identification information for identifying the log related to the failure,
By referring to a storage unit that stores the failure management information acquired by the acquisition step, all the log identification information associated with the failure identifier that identifies a specified failure is specified, and the specified log identification information is specified. And a collecting step of collecting the log identified by the log identification information for each
Information processing method. On the computer,
When a failure occurs in the own device or one or more other information processing devices, device identification information for identifying the own device or the one or more other information processing devices, a failure identifier for identifying the occurred failure, and An acquisition step of acquiring the failure management information associated with at least the log identification information for identifying the log related to the failure,
By referring to a storage unit that stores the failure management information acquired by the acquisition step, all the log identification information associated with the failure identifier that identifies a specified failure is specified, and the specified log identification information is specified. And a collecting step of collecting the log identified by the log identification information for each.

Images