KNAN26039-E

An error occurred at startup of the remote-monitoring log file trap.

S:

Terminates 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. Check the contents of the action definition file.

• Authentication failed.

  If the OS for the monitored host is UNIX, check the following item:

  • Has SSH authentication been configured correctly?

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

  If the OS for the monitored host is Windows, check the following item:

  • Are the user name, password, and domain name specified correctly in the System Common Settings or Remote Monitoring Settings window?

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

• Acquisition of an SSH private key failed.

  Check the path for the SSH private key.

• An attempt to connect monitored host failed.

  Confirm that the monitored host exists.

• The collection of log files did time-out.

  If the OS for the monitored host is UNIX, check the following items, and then restart 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 restart 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 or if a timeout occurred during collection of log files, check the following items:

  • Is the system in high load status?

  • Is the host running?

  • Has the number of connections exceeded the maximum?

  • Has the IM host account been specified correctly in the system common settings?

  • Is DCOM configured correctly on the manager host and monitored host?

• An attempt to access the monitored file failed.

  Check the following items:

  • Does the log file exist?

  • Has the path for the log file been specified correctly for remote monitoring?

  • Has the log file access permission been set correctly?

  • If the monitored host is a Windows host, has the maximum number of users permitted to connect to the file share been exceeded? Is communication with the monitored host possible?

  If no error is found by checking the above items, check the following items:

  • If the monitored host is a Windows host, have the NetBIOS (NetBIOS over TCP/IP) connection and WMI connection been configured correctly?

  • If the monitored host is a UNIX host, has the SSH connection been configured correctly? In addition, does the path of a monitoring target file contain any characters other than alphanumeric characters and hyphens (-), underscores (_), periods (.), and slashes (/)?

  If you want to perform monitoring even if no log files exist, specify the -r option for either the jcfallogstart or jcfallogdef commands.

• The size of the monitored log file has exceeded the limit that can be monitored.

  Make sure that the size of the monitored log file does not exceed the maximum size that can be monitored. If it has exceeded the maximum size, revise the log file output settings so that the size of the monitored log file is not greater than the maximum.

• 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.

• 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 either 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.

• The specified command option is invalid.

  An incorrect startup option is specified. Check the startup options.

  • Can the option and its value be specified with additional options?

• Communication with JP1/Base failed.

  If possible, restart JP1/Base.

• JP1/Base command execution error

  Check the JP1/Base environment.

• The maximum number of collection processes has been reached.

  The number of collection processes has reached the maximum. Stop unnecessary log file traps, and then restart.

• Creation of the jcfallogtrap process failed.

  If the OS of the manager host is Windows, check the IM host account specified in the system common settings.

  If the OS is UNIX, check the OS settings related to startup of processes.

• The specified command option is invalid.

  An incorrect startup option is specified. Check the startup option.

  • Is the maximum number of monitoring log files exceeded?

  • Can the option and its value be specified with additional options?

• An attempt to connect to the JP1 Event service failed.

  If possible, start the event service.

• The JP1/Base command arguments are invalid.

  Check the startup options.

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