Error message
Windows versions
MpJmSrv: ERROR: 4: Failure in communicating with the Systemwalker Operation Manager(client). |
MpJmSrv: ERROR: 5: Failure in connecting with the Systemwalker OperationMGR(Client). |
UNIX versions
MpJmSrv: ERROR: 0004: Failure in communicating with the Systemwalker Operation Manager(client). |
MpJmSrv: ERROR: 0005: Failure in connecting with the Systemwalker OperationMGR(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
A communication error occurred between the Systemwalker Operation Manager infrastructure service/daemon and a Systemwalker Operation Manager client.
The reason is described in an error message output at the same time, such as the examples below:
Windows
ID:8301 func=JMSRV_read:recv() Socket function error occurred (code = 10054). |
ID:8301 func=JMSRV_write:send() Socket function error occurred (code = 10054). |
UNIX versions
MpJmSrv: ERROR: write() broken pipe |
MpJmSrv: ERROR: read() Connection reset by peer |
MpJmSrv: ERROR: accept() Software caused connection abort |
The main reason why this error might occur is if the Systemwalker Operation Manager client is wrongly disconnected during communication, preventing it from ending normally.
Action method
No action is required for this error message. However, if it is output frequently, you should review operation - the following are possible causes:
The Systemwalker Operation Manager client does not end normally (for example, the client PC frequently resets).
There is a problem on the network path.
Inappropriate communication or unauthorized access from an external source was attempted.
