Hitachi

JP1 Version 12 JP1/Integrated Management 2 - Manager Messages


KNAN26095-E

The relevant log file can no longer be monitored. (Code: code, Host name: host-name, Monitoring-target-name: monitoring-target-name, Log file name: Log file name)

The relevant log file cannot be monitored correctly because its status is abnormal. For the cause of the error, see the value for code.

code = AL000026: The log file being monitored was deleted.

code = AL000027: The log file being monitored was re-created.

code = AL000028: The log file being monitored became smaller.

code = AL000045: The header size of the log file being monitored exceeded the maximum header size that can be monitored.

code = AL000046: The log file being monitored exceeded the maximum file size that can be monitored.

code = AL000052: An attempt to execute the OS command on the monitored host has failed.

The state of the remote log file trap when it was last stopped will not be inherited the next time the remote log file trap starts.

S:

Stops monitoring of the relevant log file.

O:
  • When code is AL000026 or AL000027:

    Check whether the log file being monitored was deleted or re-created.

    Make sure that you have access permission for the remote-monitoring target file.

    If no problem was found, review and correct the format of the log file (FILETYPE) specified in the action definition file, and then restart the remote log-file trap.

  • When code is AL000028:

    Make sure that the contents of the log file being monitored are not deleted.

    This code might be output when the size of the monitored file exceeds 2 gigabytes. Check and, if necessary, revise the size of the monitored file so that it does not exceed 2 gigabytes.

    Review and correct the format of the log file (FILETYPE) specified in the action definition file, and then restart the remote log-file trap.

  • When code is AL000045:

    Make sure that the header size specified for HEADLINE in the remote-monitoring log file trap action definition file does not exceed the maximum header size that can be monitored. Then, restart the remote log-file trap.

  • When code is AL000046:

    Make sure that the size of the log file being monitored does not exceed the maximum file size that can be monitored. If the maximum size is exceeded, review the log file output settings of the monitored log file so that the size of the monitored log file is not greater than the maximum. Then, restart the remote-monitoring log file trap.

  • When code is AL000052:

    Check the integrated trace log and take the corrective action given for the message that was output immediately before this message.