KNAN26081-E

An attempt to reload the remote-monitoring log file trap failed.

S:

Suspends reload processing.

O:

If the following detailed information is displayed, take the indicated corrective action.

• The operation definition file is invalid.

  The action definition file contains an invalid specification.

  From the integrated trace log of the manager host, refer to the JP1/Base KAVA3633-E message that is output immediately before this message. Correct the error in the action definition file, and then retry the operation.

• A parameter other than MARKSTR and ACTDEF was changed.

  A parameter whose profile cannot be applied by reloading was changed before attempting the reload.

  From the integrated trace log of the manager host, refer to the JP1/Base KAVA3634-E message that is output immediately before this message, and check the parameter whose profile could not be applied. If you want to reload the remote log-file trap, check the Valid Configuration Information page, make sure the listed values for all parameters other than MARKSTR or ACTDEF match the current values, and then re-execute the reload command.

  If you want to change a parameter whose profile cannot be applied by reloading, apply the profile by starting the remote-monitoring log file trap again.

• The JP1/Base command arguments are invalid.

  Check the startup option.

• Log file trap service does not start.

  Check the following items:

  • Make sure that the log file trap service is running. If the log file trap service has stopped, start it, and then restart the remote-monitoring log file trap or remote-monitoring event log trap.

  • Check the integrated trace log to see if the JP1/Base KAVA3663-E or KAVA3917-E message was output. If the message was output, take the corrective action given for that message.

• Event service is not started.

  Make sure that the event service is running. If the event service has stopped, start it, and then restart the remote log-file trap or remote event-log trap.

• JP1/Base command execution error

  Check the JP1/Base environment.

  Check whether the JP1/Base LogTrap service or daemon has stopped or restarted. If the JP1/Base LogTrap service or daemon has stopped, start it and then start or restart all the remote monitoring profiles. If the JP1/Base LogTrap service or daemon has restarted, stop all the remote monitoring profiles, and then start or restart them.

• The specified log file trap is not running.

  Check the operation status of the specified log file trap.

• The collection of log files did time-out.

  If the OS for the monitored host is UNIX, check the following items, and then reload the remote log-file trap.

  • Is communication with the monitored host possible?

  • Has the remote communication type for the monitored host name been set correctly?

  • Is the SSH server running on the monitored host?

  If no error is found by checking the above items, make sure that the SSH connection has been configured correctly.

  If the OS for the monitored host is Windows, check the following items, and then reload the remote log-file trap.

  • Is communication with the monitored host possible?

  • Has the remote communication type for the monitored host name been set correctly?

  • Has the number of connections exceeded the maximum for Windows?

  If no error is found by checking the above items, make sure that the NetBIOS (NetBIOS over TCP/IP) connection has been configured correctly.

  If the above methods cannot resolve the problem, check the following items:

  • Check the load on the system.

  • Make sure that the host is running.

  • Check whether the number of connections exceeds the maximum.

  • Make sure that the IM host account has been specified correctly in the system common settings.

• The number of monitored files has exceeded the limit.

  Check whether the total number of files monitored by remote monitoring has exceeded the maximum number of monitored files that can be managed. Stop remote monitoring, and then reduce the number of files to be monitored.

In any other case, use the data collection tool to collect data, and then contact a system administrator.