Troubleshooting archiving-related issues

This topic provides information about the steps that you can take to troubleshoot various archiving-related issues.

Related topic

Troubleshooting issues related to permissions on the repository path

The following table lists scenarios in which you might face permission issues with repository path when archiving:

ScenarioProbable causes with solutions (if any)
After adding the repository path, the Indexer services are not running and you get a message stating that the Indexers are not running.

This can occur if the Indexer(s) are still restarting.

Solution: Wait for some time. It may take up to 15 minutes for the Indexer(s) to restart depending on the configuration settings of the Indexer(s).

Path to the repository does not exist or the path to the repository does not have read and write permissions and you get a message stating that either the path is invalid, or the assigned users do not have write permissions to the path.

This can occur if the path is not created in the remote computer.

Solution: Create the path in the remote computer. Ensure that the path has read and write permissions.


In a Windows environment, the path to the repository exists and the path also has read and write permissions, however, you still get a message that either the path is invalid, or the assigned users do not have write permissions to the path.

This can occur if the repository location that is specified during archiving is not accessible from Indexer(s).
Solution: Perform the following actions irrespective of whether the computers, including the computer hosting the repository, are in the same domain:

  1. Create users with same credentials on the following computers.
      • Where the repository is hosted
      • Where the Indexer services are running
  2. Change the log on account of the Indexer service to the user create by you in step 1. To do this, perform the following actions:
    1. Go to Services by running the command services.msc.
    2. Right-click on the service BMC TrueSight IT Data Analyitcs Indexer and select Properties.
    3. Open the Log On tab and select This account. Browse and select the user created by you in step1.

Note: If all the computers including the computer hosting the repository are in the same domain, the active directory computer account for the Indexer server must be given read and write permissions for the shared path.

In case of Linux flavored computers, you are unable to create a repository in NFS mounted shared drive when you have multiple Indexers.

This can occur when the path to the NFS mounted shared drive does not have read and write permissions for Indexer users.

Solution: The Indexer(s) users must have the same User ID (UID) to access the NFS mounted shared drive.

To find a user's UID in Unix, use the following command:
id -u username

to change a user's UID in Unix, use the following command:
usermod -u UID username


Troubleshooting issues related to cluster state

ScenarioProbable causes with solutions (if any)
After adding the repository path, the cluster state stays in a RED status for more than 20 minutes.

This can occur if you change the repository path multiple times within a short period of time.

Solution: Restart all the indexer services manually.

Was this page helpful? Yes No Submitting... Thank you

Comments