open-consul/website/content/docs/nia/usage/errors-ref.mdx

---
layout: docs
page_title: Error Messages
description: >-
  Look up Consul-Terraform-Sync error message to learn how to resolve potential issues using CTS.
---

# Error Messages

This topic explains error messages you may encounter when using Consul-Terraform-Sync (CTS). 

## Example error log messages

If you configured the CTS cluster to run in [high availability mode](/docs/nia/usage/run-ha) and the the local module is missing, then the following message appears in the log:

```shell-session
[ERROR] ha.compat: error="compatibility check failure: stat ./example-module: no such file or directory"
```

The resolution is to add the missing local module on the incompatible CTS instance. Refer to the [`module` documentation](/docs/nia/configuration#module) in the CTS configuration reference for additional information. 

## Example API and CLI error messages

**Error**:

```json
{
    "error": {
        "message": "redirect requests to leader 'cts-01' at cts-01.example.com:8558"
    }
}
```

**Conditions**:

- CTS can determine the leader.
- `high_availability.instance.address` is configured for the leader.
- The CTS instance you sent the request to is not the leader.



**Resolution**:

Redirect the request to the leader instance, for example:

```shell-session
$ curl --request GET cts-01.example.com:8558/v1/tasks
```
---


**Error**:

```json
{
    "error": {
        "message": "redirect requests to leader 'cts-01'"
    }
}
```

**Conditions**:

* CTS can determine the leader.
* The CTS instance you sent the request to is not the leader.
* `high_availability.instance.address` is not configured.

**Resolution**:

Identify the leader instance address and redirect the request to the leader. We recommend deploying a cluster that has three instances. You can query each instance until the leader responds. 

---

**Error**:

```json
{
    "error": {
        "message": "redirect requests to leader"
    }
}
```

**Conditions**:

* The CTS instance you sent the request to is not the leader. 
* The CTS is unable to determine the leader. 
* Note that these conditions are rare.


**Resolution**:

Identify and send the request to the leader CTS instance. You can identify the leader by either making a call to the [`status` API endpoint](/docs/nia/api/status) or by checking the logs for the following entry:

```shell-session
[INFO] ha: acquired leadership lock: id=<ID-OF-CTS-INSTANCE>
```