Hitachi

JP1 Version 12 JP1/Integrated Management 2 - Manager Messages


KNAN21180-E

Application of the log file trap for monitoring-target-name failed.

Details: details

The startup definition file of the host "host-name" has been overwritten by IM Configuration Management because rollback of the startup definition file failed.

An attempt to apply the log file trap failed.

The startup definition file was overwritten by IM Configuration Management because an attempt to roll back the startup definition file failed.

S:

Suspends processing.

O:

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

  • There is no access permission.

    Check the setting of the host access control definition file (jbsdfts_srv.conf) in JP1/Base on the agent host.

  • Another session has exclusive rights.

    In the Login User List window, check whether the user has acquired exclusive access permission.

    If there is no problem, select the check box for the user that has acquired exclusive permission, and click the Release Exclusive Editing button to release exclusive permission.

  • The directory does not exist.

    Make sure that the specified directory exists and is accessible.

  • A required service or process is not running.

    Make sure that the relevant service or process is running. If it is not running, take the following actions, and then retry the operation:

    • Start the service or process.

    • In the Display/Edit Profiles window, click Rebuild Profile Tree.

  • A communication error occurred.

    Check the condition and status of the network connected to the target host.

    Also make sure that JP1/Base is running.

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

    • Start the service or process.

    • In the Display/Edit Profiles window, click Rebuild Profile Tree.

  • The processing is busy. Please try again.

    Wait a while, and then retry the operation.

  • A memory shortage occurred on the manager host.

    Make sure that there is enough free memory on the manager host, and then retry the operation.

  • A memory shortage occurred on the agent host.

    Make sure that there is enough free memory on the agent host, and then retry the operation.

  • Operations cannot be performed on the file.

    Check the following items, and then retry the operation.

    • Is there sufficient memory?

    • Does the file exist?

    • Has the file access permission been set correctly?

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

  • The configuration file for rollbacks failed to be created.

    Make sure that there are sufficient OS resources such as disk space and memory.

  • The data that was acquired while connected to the host is invalid.

    Invalid data might have been sent from JP1/Base on the target host.

    Make sure that JP1/Base is running properly on the target host.

  • There might be a mistake in a configuration file definition, or JP1/Base might not be running properly.

    Make sure that the relevant service or process is running and that the configuration file is configured correctly.

    If the service or process is not running, take the following actions, and then retry the operation:

    • Start the service or process.

    • In the Display/Edit Profiles window, click Rebuild Profile Tree.

  • A request was executed in an invalid operating environment.

    The IM configuration (system hierarchy information) might have been deleted.

    Click Operation, and then Verify IM Configuration to confirm that the current configuration is correct.

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