KNAN22500-E

An attempt to start the log file trap failed due to one of the following causes:

• A database access error occurred.

• The log file trap service is not running.

• A startup option is invalid.

• The syntax of a configuration file is invalid.

• The maximum number of monitored files is exceeded.

• The specified log file does not exist.

• The specified log file trap is already running.

• An attempt to execute the command that starts the log file trap failed.

• Allocation of an action definition file failed.

• The event service is not running.

• An attempt to update the startup definition file failed.

S:

Stops starting the log file trap.

O:

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

• There is no access permission.

  The agent configuration on the manager might be different from the agent configuration enabled in the system, or the agent configuration on the manager might have been deleted.

  In the IM Configuration Management window, click Operation, and then Verify IM Configuration to make sure that the agent configuration matches the agent configuration enabled in the system. If the agent configurations do not match, in the Edit Agent Configuration window, click Operation and then Apply Agent Configuration to use batch distribution to make the agent configurations match. Also, check the setting of the host access control definition file (jbsdfts_srv.conf) in JP1/Base on the agent.

• The host information might have been changed. Please collect the host information again.

  The host information might be different from the actual environment. Collect the host information again. If this message appears again after the host information is collected, the operating environment for JP1/Base running on the host might not be correct. Check whether a JP1/Base error message or warning message was output to the integrated trace log. Also make sure that there are write and read permissions for the JP1/Base conf directory.

• Failed to write the configuration file.

  Make sure that you have write permission for the log-file trap action definition file and the log-file trap startup definition file and that another application has not locked the file. In addition, make sure that a JP1/Base error message or warning message was not output to the integrated trace log on the target host and that you have write permission for the JP1/Base conf directory on the target host.

• Failed to read the configuration file.

  Make sure that you have read permission for the configuration file and for the log-file trap startup definition file and that another application has not locked these files. In addition, make sure that a JP1/Base error message or warning message was not output to the integrated trace log and that you have read permission for the JP1/Base conf directory.

• IM Configuration Management database-access error

  Execute the jimdbstatus command to check whether the IM database service is running. If the IM database service is not running, start it.

• The log file trap service is not running.

  Make sure that the log file trap service is running. If the log file trap service is not running, start it and then retry the operation.

• The start options were invalid.

  Check the following items:

  • Has the startup option been specified correctly?

  • Is the -f or -a option specified as an additional option?

• The log file trap of the monitoring target name "monitoring-target-name" has already been started.

  Check the log file trap running on the agent host.

• The syntax of the configuration file is invalid, or the specified log file does not exist.

  Check the following items:

  • Are the contents of the configuration file correct?

  • Does the specified log file exist?

  • If the specified log file path contains space characters, is it enclosed in double quotation marks (")?

  • Can the specified startup locale be configured for the OS of the agent host?

  • If a multi-process trace file is monitored, is HTRACE specified for the FILETYPE parameter in the configuration file?

  • Is the log file trap service running?

  • Are there sufficient OS resources such as disk space and memory, on the agent host?

  • Is the maximum number of monitored files exceeded? (Check whether a JP1 event was issued.)

• Failed to relocate the configuration file. (path = path)

  Check the following on the agent host, and then retry the operation.

  • Has access permission for the path indicated in the message been set correctly?

  • Is it possible to overwrite a file, if any, reached by the path indicated in the message?

  • Is there sufficient disk space?

• The event service is not running.

  Make sure that the event service on the agent host is running.

• An attempt to update the startup definition file "startup-definition-file-path" failed.

  Check the following on the agent host, and then retry the operation.

  • Has the format of the startup definition file been set correctly?

  • Has the access permission for the startup definition file been set correctly?

  • Is there sufficient disk space?

• The directory does not exist.

  Make sure that the log-file trap action definition file and the log-file trap startup definition file exists and that it is accessible.

• A system error occurred.

  Make sure that the log-file trap action definition file and the log-file trap startup definition file exists and that it is accessible.

  If the problem cannot be resolved by taking the above action, use the data collection tool to collect the following data, and then contact a system administrator.

  • In agent host: JP1/IM-Manager, JP1/Base

  • In manager host: JP1/Base

• The configuration file for rollback failed to be created.

  Make sure that you have access permission for the displayed configuration file and the log-file trap startup definition file and that another application has not locked the file.

  Check the network condition and status with the acquired target.

  Also make sure that JP1/Base is running.

  If the problem cannot be resolved by taking the above action, use the data collection tool to collect the following data, and then contact a system administrator.

  • In agent host: JP1/IM-Manager, JP1/Base

  • In manager host: JP1/Base

• Another session has exclusive rights.

  In the Login User List window, determine whether a user has acquired exclusive access permission. If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and click the Release Exclusive Editing button to release exclusive permission.

  Make sure that JP1/Base is running on agent host.

  If the problem cannot be resolved by taking the above action, use the data collection tool to collect the following data, and then contact a system administrator.

  • In agent host: JP1/IM-Manager, JP1/Base

  • In manager host: JP1/Base

• A communication error occurred.

  Check the network condition and status with the acquired target.

  Also make sure that JP1/Base is running on the target host.

  If JP1/Base is not running on the target host, take the following actions:

  Start the service or process.

  In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

If the problem cannot be solved by taking the above actions, execute the JP1/Base jevlogstart command on the agent host by specifying the same settings as those specified for IM Configuration Management. Then make sure that the log file trap starts normally.

If the jevlogstart command starts the log file trap normally, use the JP1/IM - Manager data collection tool to collect data, and then contact a system administrator.

If the jevlogstart command does not start the log file trap normally, take the corrective action for the displayed error message.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.