Top
Systemwalker Operation Manager  Message Guide
FUJITSU Software

2.4 Messages Starting with MpAuditLogO

This section explains messages starting with MpAuditLogO.

These messages are generated by the audit log function.

[Windows]MpAuditLogO: ERROR: 1: The audit log was not able to be initialized. The log is not output to the operation after this.(target:file, detail code:error string)
[UNIX]MpAuditLogO: ERROR: 001: The audit log was not able to be initialized. The log is not output to the operation after this.(target:file, detail code:error string)

[Description]

The initialization process that is needed to output the audit log failed. Audit logs will not be output until the system returns to normal.

[Parameter]

file: Name of the audit log file that failed to be initialized

error string: Detailed information about the cause of the error

[Corrective Measures]

Possible causes are listed below. Check the system where the error occurred and take appropriate action to eliminate the cause of the problem.

  • The log output destination settings are incorrect.

    Use the mpsetlogsend_omgr command to change the log output destination to a suitable location.

  • The audit log output destination directory does not exist.

    Create the directory that was set using the mpsetlogsend_omgr command.

  • It is not possible to write to the audit log output destination directory.

    If user restriction definitions are not used, the audit log output destination directory must be able to be written to by General Users/Everyone. Check the permissions/rights associated with the directory and make corrections if necessary.

  • There is not enough free space on audit log output destination disk

    Either delete any unnecessary files stored in the same disk area or use the mpsetlogsend_omgr command to change the audit log output destination to a different disk.

There is no need to restart Systemwalker Operation Manager after performing the above checks and actions.

However, if a problem occurs on the audit log output destination disk for any reason not listed above, the hard disk may need to be replaced or restored.

In such cases, the system will need to be shut down.

Note that when the cause of an error is relatively minor (insufficient disk space, for example), the following message will be output after the cause is eliminated, and log output will recover automatically:

[Windows version]

MpAuditLogO: INFO: 3: The audit log output is restarted. (target:file)

[UNIX version]

MpAuditLogO: INFO: 003: The audit log output is restarted. (target:file)

For other errors, check the detail code and eliminate the cause of the problem.

[Windows]MpAuditLogO: ERROR: 2: The audit log was not able to be output. The log is not output to the operation after this. (target:file, detail code:error string)
[UNIX]MpAuditLogO: ERROR: 002: The audit log was not able to be output. The log is not output to the operation after this. (target:file, detail code:error string)

[Description]

An error occurred when the audit log was output. Audit logs will not be output until the system returns to normal.

[Parameter]

file: Name of the audit log file that failed to be written

error string: Detailed information about the cause of the error

[Corrective Measures]

Possible causes are listed below. Check the system where the error occurred and take appropriate action to eliminate the cause of the problem.

  • The audit log output destination directory has been deleted.

    Recreate the output destination directory that was set using the mpsetlogsend_omgr command.

  • The write permissions of the audit log output destination directory have changed.

    If user restriction definitions are not used, the audit log output destination directory must be able to be written to by General Users/Everyone. Check the permissions/rights associated with the directory and make corrections if necessary.

  • There is not enough free space on audit log output destination disk

    Either delete any unnecessary files stored in the same disk area or use the mpsetlogsend_omgr command to change the audit log output destination to a different disk.

There is no need to restart Systemwalker Operation Manager after performing the above checks and actions.

However, if a problem occurs on the audit log output destination disk for any reason not listed above, the hard disk may need to be replaced or restored.

In such cases, the system will need to be shut down.

Note that when the cause of an error is relatively minor (insufficient disk space, for example), the following message will be output after the cause is eliminated, and log output will recover automatically:

[Windows version]

MpAuditLogO: INFO: 3: The audit log output is restarted. (target:file)

[UNIX version]

MpAuditLogO: INFO: 003: The audit log output is restarted. (target:file)

For other errors, check the detail code and eliminate the cause of the problem.

[Windows]MpAuditLogO: INFO: 3: The audit log output is restarted. (target:file)
[UNIX]MpAuditLogO: INFO: 003: The audit log output is restarted. (target:file)

[Description]

This message is output when the cause of failure to initialize or output audit logs has been eliminated and audit log output can resume.

[Parameter]

file: Name of audit log output file that can be output again

[Corrective Measures]

This message notifies the user that audit logs can be output normally.

There is no need to take any immediate action.

However, if this message appears frequently, the user should check that the audit log output destination disk has sufficient free space and is functioning normally.

[Windows]MpAuditLogO: WARNING: 5: There is an invalid value to the audit log definition file. Processing is continued by initialization. (target:file, section:section, key:key, detail code:error string)
[UNIX]MpAuditLogO: WARNING: 005: There is an invalid value to the audit log definition file. Processing is continued by initialization. (target:file, section:section, key:key, detail code:error string)

[Description]

This message is output when installation has failed or when an error has occurred with the mpsetlogsend_omgr command settings.

[Parameter]

file: Name of the audit log output definition file that contains the error

section: Name of the section of the audit log output definition file that contains the error

key: Name of the key in the audit log output definition file that contains the error

error string: Detailed information about the cause of the error

[Corrective Measures]

Set up audit log output with the mpsetlogsend_omgr command again.

If installation has failed, reinstall Systemwalker Operation Manager.

[Windows]MpAuditLogO: INFO: 6: Audit log settings have been modified. Audit log is now enabled. (LOG NAME: log name)
[UNIX]MpAuditLogO: INFO: 006: Audit log settings have been modified. Audit log is now enabled. (LOG NAME: log name)

[Description]

The audit log output settings were updated with the mpsetlogsend_omgr command.

The audit log will be output.

[Parameter]

log name: Name of the target audit log

  • OMGRLog (audit logs for Systemwalker Operation Manager)

[Windows]MpAuditLogO: INFO: 7: Audit log settings have been modified. Audit log is now disabled. (LOG NAME: log name)
[UNIX]MpAuditLogO: INFO: 007: Audit log settings have been modified. Audit log is now disabled. (LOG NAME: log name)

[Description]

The audit log output settings were updated with the mpsetlogsend_omgr command.

The audit log will not be output.

[Parameter]

log name: Name of the target audit log

  • OMGRLog (audit logs for Systemwalker Operation Manager)