Troubleshooting installation issues

This topic describes the issues that you might encounter when installing the application, database, or Elasticsearch.

Elasticsearch (DCA Index) services fail to start after installation

Issue

Sometimes, the Elasticsearch (DCA Index) services fail to start after the Elasticsearch installation with the following error message:

Starting DCA Index Service Daemon...  
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                 
Dload  Upload   Total   Spent    Left  Speed  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     
0curl: (7) Failed connect to 169.254.169.254:80; No route to host

Workaround

Follow these steps to fix the issue:

  1. Navigate to the <TSVM_INSTALL_DIR>/elasticsearch/infra-ext/es/DCAIndexService/resources folder.
  2. Open the DCAIndexService script with a text editor.
  3. Look for the following code snippet and delete it.

    track_process_start() {
    instanceID=`curl http://169.254.169.254/latest/meta-data/instance-id`
    if [[
    "$instanceID" == i-* ]]; then       
    echo "Tracking process start"       
    aws cloudwatch put-metric-data --metric-name ProcessRestart --namespace
    'Custom/App' --unit None --value 1 --dimensions InstanceId=$instanceID
    fi
    } 
  4. Look for the track_process_start function call and delete it.
  5. Ensure that you have downloaded and extracted the Stack Manager tool (TSVM<versionNo>-SM-LIN64.zip) from the BMC Electronic Product Distribution (EPD).
  6. In the extracted directory structure, navigate to the TSVM<versionNo>-SM-LIN64/truesight-sm directory,
  7. Run the following command to deploy Elasticsearch:
    python truesight-sm.py start --deployment elasticsearch
  8. Verify the status of Elasticsearch deployment by running the following command:
    python truesight-sm.py status --deployment elasticsearch

You cannot install the application due to subnet conflict

Issue

The subnet prefix for the application containers' network that you provide during the application input file creation conflicts with your datacenter's subnet CIDR or the IP address (172.xx.0.0/16) for the docker0 (docker network adapter/ bridge). As a result, you cannot install the application.

Resolution

Perform the following steps to resolve the issue:

  1. Stop the docker service by running the  following command:
    systemctl stop docker
  2. On the machine where you want to install the application, navigate to the /etc/docker/ directory.
  3. Open the daemon.json file with a text editor (create the file if it does not exist).
  4. Add the following lines with the updated subnet prefix (replace x.x with the required subnet prefix) so that it doesn’t conflict with your dataceneter's subnet prefix or IP address (172.xx.0.0/16) for the docker0 (docker network adapter/ bridge):

    {

      "bip": "x.x.0.1/16"

    }

    Where x represents an octet.

  5. Remove the docker0 network by using the following command:
    ip link del docker0
  6. Start the docker service by running the following command:
    systemctl start docker
Was this page helpful? Yes No Submitting... Thank you

Comments