This section explains messages starting with Mpcmtoolo [UNIX version]/mpcmtoolo [Windows version].
These messages are output by Operation Environment Maintenance Wizard, Backup/Restore commands of Systemwalker Operation Manager.
[Description]
The backup command terminated successfully.
[Description]
The backup command terminated abnormally.
[System Administrator Response]
Remove the cause of the abnormal termination according to detailed error message "Mpcmtoolo: ERROR: 00002".
[Description]
Detailed error message output when the backup command terminates abnormally.
[Parameter]
%1: Detailed error message
[System Administrator Response]
Refer to the detailed error message and remove the cause of the abnormal termination.
[Description]
The restore command terminated successfully.
[Description]
The restore command terminated abnormally.
[System Administrator Response]
Remove the cause of the abnormal termination according to detailed error message "Mpcmtoolo: ERROR: 00102".
[Description]
The restore command terminated abnormally.
[Parameter]
%1: Detailed error message
[System Administrator Response]
Refer to the detailed error message and remove the cause of the abnormal termination.
[Description]
Failed to add the target node as a distributed execution server when servers are added with the provisioning of ServerView Resource Coordinator (*1).
*1: ServerView Resource Coordinator was formerly known as Systemwalker Resource Coordinator.
[Parameter]
%1: Node name
[Cause]
The cause can be attributed to the following factors:
The environment setting for distributed execution configuration is incorrect.
Linkages with the site management server of ServerView Resource Coordinator is defined on a system where no linkage with distributed execution configuration is required.
The target node has already been registered as a distributed execution server.
[System Administrator Response]
Take the following measures against the above factors respectively.
Set the environment for distributed execution configuration correctly and add the target node by executing the mjdjadd command.
Disable linkages with the site management server of ServerView Resource Coordinator.
No action is required.
[Description]
Failed to delete the target node from the distributed execution server when servers are deleted with the provisioning of ServerView Resource Coordinator (*1).
*1: ServerView Resource Coordinator was formerly known as Systemwalker Resource Coordinator.
[Parameter]
%1: Node name
[Cause]
The cause can be attributed to the following factors:
The environment setting for distributed execution configuration is incorrect.
Linkages with the site management server of ServerView Resource Coordinator is defined on a system where no linkage with distributed execution configuration is required.
The target node has not been registered as a distributed execution server.
[System Administrator Response]
Take the following measures against the above factors respectively.
Set the environment for distributed execution configuration correctly and delete the target node by executing the mjdjadd command.
Disable linkages with the site management server of ServerView Resource Coordinator.
No action is required.
[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]
When an attempt was made to add a server using the ServerView Resource Coordinator (*1) provisioning function, the target node could not be added as a distributed execution server.
*1: ServerView Resource Coordinator was formerly known as Systemwalker Resource Coordinator.
[Parameter]
%1: Node name
[Cause]
The following are possible causes:
The environment settings for the distributed execution configuration may not be correct
A system that does not need to be linked to the distributed execution configuration may have been defined so as to link to the ServerView Resource Coordinator site management server
The node that an attempt was made to add may have already been registered as a distributed execution server
[System Administrator Response]
Take the following actions for each of these possible causes:
Correct the environment settings for the distributed execution environment, and then add the target node using the mjdjadd command.
Cancel the definitions for linking the system to the ServerView Resource Coordinator site management server
No action is required.
[Description]
When an attempt was made to delete a server using the ServerView Resource Coordinator (*1) provisioning function, the target node could not be deleted from the list of distributed execution servers.
*1: ServerView Resource Coordinator was formerly known as Systemwalker Resource Coordinator.
[Parameter]
%1: Node name
[Cause]
The following are possible causes:
The environment settings for the distributed execution configuration may not be correct
A system that does not need to be linked to the distributed execution configuration may have been defined so as to link to the ServerView Resource Coordinator site management server
The node that an attempt was made to delete may not have been registered as a distributed execution server
[System Administrator Response]
Take the following actions for each of these possible causes:
Correct the environment settings for the distributed execution environment, and then delete the target node using the mjdjdel command.
Cancel the definitions for linking the system to the ServerView Resource Coordinator site management server
No action is required.
[Description]
An error occurred during the backup or the restore process.
[Parameter]
%1: Backup or restore
%2: The error message indicating the cause of failure in backup or restore
[Corrective Measures]
Refer to the detailed error message and remove the cause of the abnormal termination.
[Description]
A backup has been created successfully.
[Description]
The file has been restored successfully.
[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.
