KNAN26350-W

The backup files for the monitored host for which remote monitoring was performed could not be found.

The log entries that were output to backup files between the previous collection time and the current collection time are not output as JP1 events.

The executed command line displayed in the message includes the OS command below, which was executed to search for the backup files. The OS command was executed by the user indicated in the message.

• find monitored-directory-path -xdev -inum inode-of-backup-files-of- monitored-log-files

S:

Continues remote monitoring.

O:

Log in to the monitored host, and then check whether there is a backup file in the inode displayed in command-line-executed in the message.

If there is a backup file, check the log data that was output between the previous collection time and the current collection time.

The user specified in the Remote Monitoring Settings window or the System Common Settings window might not have the required permissions. Check whether the specified user has permission to read the backup file. In addition, check whether the user has read and write permissions for the directory that holds the backup file and for all the directories above it, and set the permissions as necessary.

After setting the permissions, execute executed-command-line as indicated in the message, and make sure that the backup file appears in the standard output.

If there are no backup files, check the following:

• The backup files might have been removed during monitoring.

  After a backup file is created, do not delete it untile the next time the log file is trapped.

• The format of the monitoring-target log file might not be SEQ2, which is the format specified for FILETYPE in the action definition file for the remote-monitoring log file trap.

  Using the SEQ2 format, you cannot monitor files that are in a format in which a backup file is created by copying the monitoring target file. Make sure that the format of the monitoring-target log file is SEQ2.

  If the format of the monitoring-target log file is not SEQ2, change the specification for FILETYPE in the action definition file for the remote-monitoring log file trap, and then start remote monitoring again.

  For details about log file formats that can be monitored by the remote-monitoring log file traps, see the chapter that describes log information that can be monitored in the JP1/Integrated Management 2 - Manager Overview and System Design Guide.