This is the list of messages output by Systemwalker Operation Manager standard function. Source name is "MpJmSrv".
[Description]
Trace function stops due to occurrence of some error in it.
[Parameter]
XXXX : Execution program name
[System Action]
Stops outputting trace information for XXXX.
[Description]
Environment variable LANG value is incorrect.
[System Action]
Service or daemon operates in English environment.
[User Response]
Restart service or daemon, after correcting environment variable LANG value.
[Description]
There is a mistake in the argument of the Systemwalker Operation Manager authentication process (mpjmsrv).
[System Action]
Aborts the process.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Failed to initialize communication between the Systemwalker Operation Manager authentication process (mpjmsrv) and PC.
[System Action]
Aborts the process.
[User Response]
If this message is output frequently, check if an operation is disconnecting the Operation Management Client or other machines abnormally (e.g., a client PC is resetting frequently), if there is a problem in the network path, or if an incorrect communication or an illegal access from outside the system is being performed.
[Description]
Communication between the Systemwalker Operation Manager authentication process (mpjmsrv) and PC has failed.
Cause of communication error (error cause of socket level on TCP/IP) is indicated in the message output just before this error message.
The following are typical messages:
"MpJmSrv: ERROR: write() broken pipe"
"MpJmSrv: ERROR: read() Connection reset by peer"
Both of them indicate that the socket was wrongly disconnected and individual clients of Systemwalker Operation Manager were not shut down successfully.
[System Action]
Fixes the socket and aborts the process.
[System Administrator Response]
If this message appears frequently, the cause can be attributed to the following factors so review the environment.
Individual clients of Systemwalker Operation Manager are not disconnected successfully according to the system operation (client PC is reset frequently, etc.)
A problem related to the network path has occurred
[Description]
The length of the local host name exceeds 64 bytes.
[System Action]
Aborts the process.
[System Administrator Response]
Specify the length of the local host name up to 64 bytes.
[Description]
Failed to acquire service name JMSRV used while communicating with Systemwalker Operation Manager (client).
[System Action]
Disables the use of Systemwalker Operation Manager (client).
[System Administrator Response]
Specify service name JMSRV (default value 9367/tcp) in the system route \etc\services file. Set up name service when host is using it.
[Description]
Restart the Systemwalker MpJmSrv service in 1 minute.
[System Administrator Response]
Start the Systemwalker Operation Manager authentication process service 1 minute after disconnecting PC.
[Description]
Error occurred in the getaddrinfo function.
[System Action]
Aborts the process.
[System Administrator Response]
Check the network setting on the relevant server.
[Description]
Error occurred in the select system call.
[System Action]
Aborts the process.
[System Administrator Response]
Check that there is no problem with the network.
[Description]
Systemwalker mpjmsrv daemon has started.
[Description]
Systemwalker mpjmsrv daemon has ended.
[Description]
An error occurred while creating a shared memory.
[System Action]
Aborts the process.
[System Administrator Response]
Refer to the message displayed before this message, and resolve the problem.
[Description]
An error occurred while obtaining the shared memory.
[System Action]
Aborts the process.
[System Administrator Response]
Refer to the message displayed before this message, and resolve the problem.
[Description]
The Systemwalker OperationMGR authentication process (mpjmsrv) is already running.
[Description]
The inter-process communication resource with the key "XXXX" is already used by another application.
[Parameter]
XXXX: Key
[System Action]
Uses another key.
[Description]
The inter-process communication resource is created with the key "XXXX".
[Parameter]
XXXX: Key
[Description]
The system failed to open the file to obtain the key for creating inter-process communication resource.
[System Action]
Aborts the process.
[System Administrator Response]
Refer to the message displayed before this message, and resolve the problem.
[Description]
The argument of the multi-server monitoring process (tskhmsrv) is invalid.
[System Action]
Aborts the process.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
The host name of the local host is incorrect.
[System Action]
Aborts the process.
[System Administrator Response]
Specify the local host name of the computer currently in use.
[Description]
The communication failed between the multi-server monitoring process (tskhmsrv) and PC.
[System Action]
Aborts the process.
[System Administrator Response]
Check the network between the client and connection destination host. For instance, check if a connection from the client to the server can be made with the ping command.
[Description]
The communication failed between the multi-server monitoring process (tskhmsrv) and the monitored host.
[Parameter]
XXXX: IP address of the monitored host
[System Action]
Aborts the process.
[System Administrator Response]
Check if there is a problem with the network connection to the monitored host.
[Description]
A monitoring request of a non-monitored host was sent to the multi-server monitoring process (tskhmsrv).
[System Action]
Aborts the process.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Failed to send a control request to the monitored host.
[System Action]
Aborts the process.
[System Administrator Response]
Check the status of the monitored host. If it is running, try it again.
[Description]
The monitored host denied the access.
[System Action]
Aborts the process.
[System Administrator Response]
Add the monitoring host to the Monitoring Permission Host on the monitored host.
[Description]
System function returned an abnormal value.
[Parameter]
XXXX: System function name
YYYY: Message
[System Action]
Aborts the process.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
An error occurred in the system function
[Parameters]
XXXX: System function name
YYYY: Message
[System Action]
Aborts the process.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
The system failed to load the library.
[System Action]
Aborts the process.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
The access to the file is denied.
[Parameter]
XXXX: File name
[System Action]
Aborts the process.
[System Administrator Response]
Refer to the message displayed before this message, and resolve the problem.
[Description]
The communication failed between the multi-server monitoring process (tskhmsrv) and the monitored host.
[Parameter]
XXXX: IP address of the monitored host
[System Action]
Aborts the process.
[Description]
The communication failed between the multi-server monitoring process (tskhmsrv) and multi-server monitoring (client).
[System Action]
Aborts the process.
[Description]
The communication failed between the multi-server monitoring process (tskhmsrv) and multi-server monitoring (client).
[System Action]
Aborts the process.
[System Administrator Response]
Check the network between the client and connection destination host. For instance, check if a connection from the client to the server can be made with the ping command.
[Description]
Communication between the Systemwalker Operation Manager authentication process (mpjmsrv) and PC has failed.
[System Action]
Aborts the process.
[Description]
Failed to send a control request to the monitored host.
[System Action]
Aborts the process.
[Description]
The monitored host denied the access.
[System Action]
Aborts the process.
[Description]
XXXX=3, YYYY=0
A connection error occurred.
XXXX=8, YYYY=11
Failed to obtain a semaphore.
XXXX=16, YYYY=0
Failed to convert the code.
Other than the above, an error occurred in ACL Manager process
[Parameter]
XXXX: Error code
YYYY: Detail code
[System Action]
Aborts the process.
[Corrective Measures]
XXXX=3, YYYY=0
Check that the following process is running on the Operation Manager Server. If the error persists even if the process is active, collect maintenance information with the maintenance information collection command swcolinf (for servers) and contact a Fujitsu's system engineer.
/usr/lib/MpFwsec
XXXX=8, YYYY=11
Check that the setup value related to the semaphore of system parameters is suitable for the operating environment.
See the Systemwalker Operation Manager Installation Guide for tuning of system parameters.
XXXX=16, YYYY=0
Make sure that the mandatory SUNWjfpu software is installed. For the mandatory software for Systemwalker Operation Manager, see the Release Note.
In other cases, collect maintenance information with the maintenance information collection command swcolinf (for servers) and contact a Fujitsu's system engineer. See the Systemwalker Operation Manager Reference Guide for the use of the swcolinf command.
[Description]
The audit log could not be output because a problem occurred when an attempt was made to load the library used to output the audit log.
[System Action]
Continues processing, but does not output the audit log.
[Corrective Measures]
Check whether the following files exist. If they do, one or more of the files may have become corrupted. In such cases, either reinstall Systemwalker Operation Manager or contact a Fujitsu SE.
/opt/systemwalker/lib/libmpaudito.so
/opt/systemwalker/lib/libmpaudito_nt.so
/opt/systemwalker/lib/libmpaudito.sl
/opt/systemwalker/lib/libmpaudito_nt.sl
[Description]
The audit log could not be output because a problem occurred when an attempt was made to open the audit log output file.
[System Action]
Continues processing, but does not output the audit log.
[Corrective Measures]
Check that there is sufficient free space.
Check that the directory where the audit log is to be output exists.
Check the permissions/rights associated with the directory where the audit log is to be output. If user restriction definitions are not used, the directory must be able to be written to by General Users/Everyone.
The audit log output file may be corrupt. Back up the damaged file and then delete it.
If a problem has occurred on the disk where the audit log is to be output, it may be necessary to replace or restore the hard disk.
The audit log output file and directory can be specified using the mpsetlogsend_omgr command. Refer to the Systemwalker Operation Manager Reference Guide for details on the mpsetlogsend_omgr command.
[Description]
The Systemwalker User Management function cannot be used because it is not installed.
[Description]
Trace function stops due to occurrence of some error in it.
[Parameter]
XXXX : Execution program name
[System Action]
Stops outputting trace information for XXXX.
[Description]
Environment variable LANG value is incorrect.
[System Action]
Service or daemon operates in English environment.
[User Response]
Restart service or daemon, after correcting environment variable LANG value.
[Description]
There is a mistake in argument of the Systemwalker Operation Manager authentication process (mpjmsrv).
[System Action]
Aborts the process.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Failed to initialize communication between the Systemwalker Operation Manager authentication process (mpjmsrv) and PC.
[System Action]
Aborts the process.
[User Response]
Find out the cause of the error by referring to the message output just before the current message.
[Description]
Communication between the Systemwalker Operation Manager authentication process (mpjmsrv) and PC has failed.
Cause of communication error (error cause of socket level on TCP/IP) is indicated in the message output just before this error message.
The following are typical messages:
"MpJmSrv: ERROR: write() broken pipe"
"MpJmSrv: ERROR: read() Connection reset by peer"
Both of them indicate that the socket was wrongly disconnected and individual clients of Systemwalker Operation Manager were not shut down successfully.
[System Action]
Fixes the socket and aborts the process.
[System Administrator Response]
If this message appears frequently, the cause can be attributed to the following factors so review the environment.
Individual clients of Systemwalker Operation Manager are not disconnected successfully according to the system operation (client PC is reset frequently, etc.)
A problem related to the network path has occurred
[Description]
The length of the local host name exceeds 64 bytes.
[System Action]
Aborts the process.
[System Administrator Response]
Specify the length of the local host name up to 64 bytes.
[Description]
Failed to acquire service name JMSRV used while communicating with Systemwalker Operation Manager (client).
[System Action]
Disables the use of Systemwalker Operation Manager (client).
[System Administrator Response]
Specify service name JMSRV (default value 9367/tcp) in the system route \etc\services file. Set up name service when host is using it.
[Description]
At the previous termination of the Systemwalker Operation Manager authentication process, any PC had been connected. Therefore the Systemwalker Operation Manager authentication process cannot be started.
[System Action]
Aborts the process.
[System Administrator Response]
Start the Systemwalker Operation Manager authentication process service 1 minute after disconnecting PC.
[Description]
Error occurred in the getaddrinfo function.
[System Action]
Aborts the process.
[System Administrator Response]
Check the network setting on the relevant server.
[Description]
Error occurred in the select system call.
[System Action]
Aborts the process.
[System Administrator Response]
Check that there is no problem with the network.
[Description]
The Systemwalker Operation Manager authentication process (mpjmsrv) has started.
[Description]
The Systemwalker Operation Manager authentication process (mpjmsrv) has ended.
[Description]
An error occurred while creating a shared memory.
[System Action]
Aborts the process.
[System Administrator Response]
Refer to the message displayed before this message, and resolve the problem.
[Description]
An error occurred while obtaining the shared memory.
[System Action]
Aborts the process.
[System Administrator Response]
Refer to the message displayed before this message, and resolve the problem.
[Description]
The system was unable to allocate memory to generate the process.
[System Action]
Aborts the process.
[System Administrator Response]
Insufficient memory occurred. Add more memory.
[Description]
The argument of the mutli-server monitoring process (tskhmsrv) is invalid.
[System Action]
Aborts the process.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
The local host name is invalid.
[System Action]
Aborts the process.
[System Administrator Response]
Specify the local host name of the computer currently in use.
[Description]
The communication failed between the multi-server monitoring process (tskhmsrv) and PC.
[System Action]
Aborts the process.
[System Administrator Response]
Check the network between the client and connection destination host. For instance, check if a connection from the client to the server can be made with the ping command.
[Description]
The communication failed between the multi-server monitoring process (tskhmsrv) and the monitored host.
[Parameter]
XXXX: IP address of the monitored host
[System Action]
Aborts the process.
[System Administrator Response]
Check the network between the connection destination host and the monitored host displayed. For instance, check if a connection from the client to the server can be made with the ping command.
[Description]
A monitoring request of a non-monitored host was sent to the multi-server monitoring process (tskhmsrv).
[System Action]
Aborts the process.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
The system failed to send a control request to the monitored host.
[System Action]
Aborts the process.
[User Response]
Check the status of the monitored host, and try again if it is running.
[Description]
The monitored host denied the access.
[System Action]
Aborts the process.
[System Administrator Response]
Add the monitoring host to Monitoring Permission Host of the monitored host.
[Description]
The system failed to load the library.
[System Action]
Aborts the process.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
The communication failed between the multi-server monitoring process (tskhmsrv) and the monitored host.
[Parameter]
XXXX: IP address of the monitored host
[System Action]
Aborts the process.
[Description]
The communication failed between the multi-server monitoring process (tskhmsrv) and multi-server monitoring (client).
[System Action]
Aborts the process.
[Description]
The communication failed between the multi-server monitoring process (tskhmsrv) and multi-server monitoring (client).
[System Action]
Aborts the process.
[System Administrator Response]
Check the network between the connection destination host and the monitored host. For instance, check if a connection from the client to the server can be made with the ping command.
[Description]
Communication between the Systemwalker Operation Manager authentication process (mpjmsrv) and PC has failed.
[System Action]
Aborts the process.
[Description]
Failed to send a control request to the monitored host.
[System Action]
Aborts the process.
[Description]
The monitored host denied the access.
[System Action]
Aborts the process.
[Description]
XXXX=3, YYYY=0
A connection error occurred.
Other than the above, an error occurred in ACL Manager process
[Parameter]
XXXX: Error code
YYYY: Detail code
[System Action]
Aborts the process.
[Corrective Measures]
XXXX=3, YYYY=0
Check that the following process is running on the Operation Manager Server. Check that the Systemwalker ACL Manager service is running on the Operation Manager Server.
If the service is running or in cases other than the above, collect maintenance information of Framework - Security with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
The audit log could not be output because a problem occurred when an attempt was made to load the library used to output the audit log.
[System Action]
Continues processing, but does not output the audit log.
[Corrective Measures]
Check whether the following files exist. If they do, one or more of the files may have become corrupted. In such cases, either reinstall Systemwalker Operation Manager or contact a Fujitsu SE.
Systemwalker installation directory\MPWALKER.JM\bin\mpaudito.dll
[Description]
The audit log could not be output because a problem occurred when an attempt was made to open the audit log output file.
[System Action]
Continues processing, but does not output the audit log.
[Corrective Measures]
Check that there is sufficient free space.
Check that the directory where the audit log is to be output exists.
Check the permissions/rights associated with the directory where the audit log is to be output. If user restriction definitions are not used, the directory must be able to be written to by General Users/Everyone.
The audit log output file may be corrupt. Back up the damaged file and then delete it.
If a problem has occurred on the disk where the audit log is to be output, it may be necessary to replace or restore the hard disk.
The audit log output file and directory can be specified using the mpsetlogsend_omgr command. Refer to the Systemwalker Operation Manager Reference Guide for details on the mpsetlogsend_omgr command.
[Description]
The Systemwalker User Management function cannot be used because it is not installed.
[Description]
System function returned an abnormal value.
[Parameter]
XXXX: Call source function name
YYYY: Function name in which error has occurred
CCCC: Error number
ZZZZ: System error message
[System Action]
Aborts the process.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Socket function returned an error.
[Parameter]
XXXX: Call source function name
YYYY: Socket function name
ZZZZ: Code
[System Action]
Aborts the process.
[Description]
Error occurred in system function.
[Parameter]
XXXX: Call source function name
YYYY: Function name in which error has occurred
ZZZZ: Error message of system
[System Action]
Aborts the process.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Error occurred in system function.
[Parameter]
XXXX: Call source function name
YYYY: Function name in which error has occurred
CCCC: Error number
ZZZZ: Error message of system
[System Action]
Aborts the process.
[System Administrator Response]
If the message after "func" is "CreateFile() 32: Process cannot access the file", check if no application is configured to access the file stored in the Jobscheduler database directory, and make sure that no application accesses the file stored in the Jobscheduler database directory while Jobscheduler is running.
In cases other than the above, collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Error occurred in system function (WindowsSockets).
[Parameter]
XXXX: Call source function name
YYYY: Function name in which error has occurred
ZZZZ: Error code of system
[System Action]
Aborts the process.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
