Error message
One of the following messages is output:
[Windows versions]
Source: MpJobsch Type: Error Event ID: 6198 Description: Failure in communicating with the jobscheduler(client). |
Source: MpJobsch Type: Error Event ID: 6199 Failure in connecting with the jobscheduler (client). |
[UNIX versions]
MpJobsch: ERROR: 0198: Failure in communicating with the jobscheduler (client). |
MpJobsch: ERROR: 0199: Failure in connecting with the jobscheduler (client). |
Applicable versions and levels
Windows versions: V5.0L10 or later
Solaris versions: 5.0 or later
Linux versions: 5.2, V10.0L10 or later
Linux for Itanium versions: V12.0L10 or later
HP-UX versions: 5.1 or later
AIX versions: 5.1 or later
DS versions: V20L10
Action
Cause
An error occurred in communication between the Jobscheduler service/daemon and the Systemwalker Operation Manager client.
The reason for the communication error (the reason for the error in the TCP/IP socket level) is described in the error message that is output after the error.
A typical inherited error message that is output is as follows:
[Windows versions]
Source:MpJobsch Type: Error Event ID: 8301 func=JOBSCH_read:recv() Socket function error occurred. (code=10054) |
Source:MpJobsch Type: Error Event ID: 8301 func=JOBSCH_write:send() Socket function error occurred. (code=10054) |
[UNIX versions]
MpJobsch: ERROR: write() broken pipe |
MpJobsch: ERROR: read() Connection reset by peer |
MpJobsch: ERROR: 0412:write() broken pipe |
MpJobsch: ERROR: 0412:read() Connection reset by peer |
The main cause in each case is that the socket was illegally disconnected, or that the Systemwalker Operation Manager client was not stopped normally.
Action method
As the system action, the socket that was illegally disconnected will be correctly handled, therefore no action is required by the operator for this error message. However, if this message is output frequently, the following is possible, therefore, you should review operation.
Operations in which the Systemwalker Operation Manager client is not disconnected normally (for example, when the client PC is frequently reset)
Problems that occur on the network pathway
Inappropriate communication or unauthorized access from an external source.
