Environment Watch Troubleshooting

Issue 1: Insufficient Memory

  • Running the .\elasticsearch.bat command occasionally triggers errors related to insufficient memory.

Troubleshooting Steps:

  1. Disk Space: Ensure that there is sufficient disk space available. Elasticsearch requires adequate disk space for indexing and storing data.

Issue 2: Elastic search service issues

Troubleshooting Steps:

  1. Verify if Elasticsearch running a.- Open powershell and use the command 'Get-Service -Name elasticsearch' to check the status of the Elasticsearch service.

    Get-Service -Name elasticsearch

    Status Name DisplayName
    Running elasticsearch Elasticsearch (Elasticsearch)

  2. Verify if Elasticsearch accessible from a given host:

    1. Check if elasticsearch is accessible by accessing https://emttest:9200/

    2. If the service is not running, elasticsearch can be started using

      .\elasticsearch-service.bat start Elasticsearch

  3. Verify the SSL/TLS URL

    1. Check if the URL is correct for accessing Elasticsearch with SSL enabled. The URL should start with https:// if SSL is configured.

    2. Check Elasticsearch elasticsearch.yml configuration and verify that SSL/TLS settings are correctly defined.
      alt text

Issue 3: SSL certificate issue

alt text

Troubleshooting Steps:

  1. While logging into ElasticSearch URL, if it shows not secure. Export that certificate of the highest hierarchy and save to your local directory.
  2. Go to that directory where you saved the certificate. Double click on the certificate and then click Install Certificate
    alt text
  3. Select Local Machine
    alt text
  4. Select Next, Click yes
  5. Select Place all the certificates in the following store
  6. Click on Browse, select Enterprise Trust
  7. Select Next, It should get imported
  8. Open MMC, go to files and click on Add/Remove Snap-IN
    alt text
  9. Add Certificates
    alt text
  10. Click Computer Account
    alt text
  11. Click Next -> Finish
  12. On the left side bar click the dropdown under Certificates
  13. Right Click on Trusted Root Certification Authorities, All Task → Import
    alt text
  14. Select the Certificate which being saved few steps earlier under browse and click on Finish
  15. Import certificate for all the selected folders below.
    alt text
  16. Close all search engine and re-login to ElasticSearch URL
    alt text

Issue 4: Issues while extracting the kibana-8.xx.x-windows-x86_64.zip

Troubleshooting Steps:

  1. Windows must be updated to support Long Paths to enable the Local Group Policy Editor

    1. Run the "gpedit.msc" to navigate into Local Group Policy Editor
      alt text

    2. Select Computer Configuration → Administrative Template → System → Filesystem.
      alt text

    3. Double click on enable the Long path.

Issue 5: Kibana service issues

Troubleshooting Steps:

  1. Verify Kibana Service Status:

    1. Run the service and verify if service is up and running
      alt text

    2. If Windows service fails to start is likely due to a configuration or environmental problem. Verify kibana configuration by following ElasticSearch setup

    3. Check if Kibana is running by navigating to Kibana URL

Issue 6: Kibana authentication issue

Troubleshooting Steps:

Update your Kibana config file with below steps:

  1. Generate encryption key by executing below command
    Copy
    ./kibana-encryption-keys generate
  2. In the kibana.yml configuration file, add the xpack.encryptedSavedObjects.encryptionKey setting.
    alt text
  3. Restart Kibana

Issue 7: APM service issues

Troubleshooting Steps:

  1. Verify APM Service Status

    1. Check if APM server is running using the PowerShell command
    Copy 
     Get-Service -Name apm-server
    Status Name DisplayName
    Running apm-server
    1. If the service is not running, start service using
    Copy 
     Start-Service -Name apm-server
    1. Check if APM is running by navigating to APM URL http://emttest:8200/ in any supported Web browser.

  2. If Windows service fails to start is likely due to a configuration or environmental problem

    1. Verify APM configuration by following ElasticSearch setup
    2. Verify the "publish_ready" property is true/false.
    3. If the value of publish_ready is still false and elasticsearch is configured to use https, perform the below changes under "Elasticsearch output"
      1. Update protocol to https and uncomment the line
      2. Update ssl.enabled to true and uncomment the line
      3. Update ssl.verification_mode to none and uncomment the line
      4. Restart the apm service ({.BeatName | title})

Relativity Server CLI - Environment Watch Setup

Issue 1: Unauthorized issue:

Troubleshooting Steps:

  1. Verify your Relativity admin username and password, and provide valid credentials.
  2. Verify your Elasticsearch admin username and password, and provide valid credentials.

Issue 2: Server URLs are incorrect:

Troubleshooting Steps:

  1. Verify your Relativity/Elastic/APM/kibana URL, and provide valid URLs.

Issue 3: ElasticSearch server credentials are incorrect

Troubleshooting Steps:

  1. The user should verify the Elasticsearch admin username and password and provide valid credentials

Issue 4: Retry limit reached:

Troubleshooting Steps:

  1. The user reached the maximum number of attempts. Please rerun the Relativity.Server.Cli with the setup command relsvr.exe setup using Command Terminal.

Relativity Server CLI - DataGrid/Audit Setup

Issue 1: Unauthorized issue:

Troubleshooting Steps:

  1. Verify your Elasticsearch admin username and password, and provide valid credentials.

Issue 2: Elasticsearch server credentials are incorrect:

Troubleshooting Steps:

  1. Verify your Elasticsearch admin username, password, and URL, and provide valid credentials.

Issue 3: Retry limit reached:

Troubleshooting Steps:

  1. The user reached the maximum number of attempts. Please rerun the Relativity.Server.Cli with the setup command relsvr.exe setup using Command Terminal.

Troubleshooting Environment Watch installer on Windows

Issue 1: Product cannot be installed because user is not added in Local security policy

Troubleshooting Steps:

  1. Add user to Local security policy.

Issue 2: Product cannot be installed because relativity secret store is not accessible.

Troubleshooting Steps:

  1. Start the Relativity Secret store service
  2. To view whitelisted machines, run this command:
    Copy
     .\secretstore whitelist read
  3. If server is not whitelisted, whitelist servers on secret store to grant permission by running the below command:
    Copy
     .\secretstore whitelist write (server-name)
    For more details refer to: https://help.relativity.com/Server2024/Content/System_Guides/Secret_Store/Secret_Store.htm

Issue 3: Product cannot be installed, once or more secrets are invalid

Troubleshooting Steps:

  1. Verify if the one-time setup using the relsvr.exe CLI was executed properly and ensure that it has been completed as required.

Issue 4: Product cannot be installed because Elasticsearch service is not running

Troubleshooting Steps:

  1. Verify elasticsearch is running or not by following steps under [Elastic search service]

Issue 5: Product cannot be installed because Kibana server is not running

Troubleshooting Steps:

  1. Verify kibana is running or not by following steps under kibana service

Issue 6: Product cannot be installed because APM server is not running

Troubleshooting Steps:

  1. Verify APM server is running or not by following steps under apm service

Issue 7: Relativity service is inaccessible

Troubleshooting Steps:

  1. Verify user is able to successfully login to Relativity
  2. If unable to login to relativity, Check the Relativity services in IIS and start them
  3. Verify whether the version matches the minimum required version as per the Environment Watch release. Also verify Service Host is running within the web server
  4. If there are any issues, refer https://help.relativity.com/Server2024/Content/System_Guides/Service_Host_Manager.htm: