KNAN22503-E

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

• An attempt to delete the configuration file failed.

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

S:

Stops attempting to delete the log file trap.

O:

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

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

• Deletion of the configuration file "file-name" from IM Configuration Management failed.

  Check the following items, and then retry the operation.

  • Is there sufficient memory?

  • Does the file indicated in the message exist?

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

  • Has the file indicated in the message been opened (locked) by another application?

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

• A system call error occurred

  Check the following, and then retry the operation.

  • Make sure that you have access permission for the log-file trap startup definition file on the agent host.

  • Check the OS log of the agent host to see if a shortage has occurred in other OS resources such as file descriptors.

  In Windows: Windows event log

  In UNIX: System log (syslog)

  • If an application on the agent host that locks files (such as virus check software) is running, this message might appear due to a contention with that application. Stop the application that locks files, and then retry the operation.

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

• The configuration file for rollback failed to be created.

  Make sure that you have read 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

• Failed to read the configuration file.

  Make sure that you have read permission for the displayed configuration 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 read permission for the JP1/Base conf directory on the target host.

• There is no access permission.

  Check the settings of the host access control definition file (jbsdfts_srv.conf) in JP1/Base on the agent, confirm that the access from a manager host is admitted.

• 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 detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.