Cluster & Node Setup Troubleshooting

On this page Carat arrow pointing down
Warning:
As of November 10, 2018, CockroachDB v1.0 is no longer supported. For more details, refer to the Release Support Policy.

If you're having trouble starting or scaling your cluster, this page will help you troubleshoot the issue.

Before You Begin

Terminology

To use this guide, it's important to understand some of CockroachDB's terminology:

  • A Cluster acts as a single logical database, but is actually made up of many cooperating nodes.
  • Nodes are single instances of the cockroach binary running on a machine. It's possible (though atypical) to have multiple nodes running on a single machine.

Using This Guide

To diagnose issues, we recommend beginning with the simplest scenario and then increasing its complexity until you discover the problem. With that strategy in mind, you should proceed through these troubleshooting steps sequentially.

We also recommend executing these steps in the environment where you want to deploy your CockroachDB cluster. However, if you run into issues you cannot solve, try the same steps in a simpler environment. For example, if you cannot successfully start a cluster using Docker, try deploying CockroachDB in the same environment without using containers.

Locate Your Issue

Proceed through the following steps until you locate the source of the issue with starting or scaling your CockroachDB cluster.

1. Start a Single-Node Cluster

  1. Terminate any running cockroach processes and remove any old data:

    $ pkill -9 cockroach
$ rm -r testStore

  2. Start a single insecure node and log all activity to your terminal:

    $ cockroach start --insecure --logtostderr --store=testStore

    Errors at this stage potentially include:

    • CPU incompatibility

    • Other services running on port 26257 or 8080 (CockroachDB's default port and http-port respectively). You can either stop those services or start your node with different ports, specified with the --port and --http-port.

      If you change the port, you will need to include the --port=[specified port] flag in each subsequent cockroach command or change the COCKROACH_PORT environment variable.

    • Networking issues that prevent the node from communicating with itself on its hostname. You can control the hostname CockroachDB uses with the --host flag.

      If you change the host, you will need to include --host=[specified host] in each subsequent cockroach command.

  3. If the node appears to have started successfully, open a new terminal window, and attempt to execute the following SQL statement:

    $ cockroach sql --insecure -e "SHOW DATABASES"

    You should receive a response that looks similar to this:

    +--------------------+
|      Database      |
+--------------------+
| crdb_internal      |
| information_schema |
| pg_catalog         |
| system             |
+--------------------+

    Errors at this stage potentially include:

    • getsockopt: connection refused, which indicates you have not included some flag that you used to start the node (e.g., --port or --host). We have additional troubleshooting steps for this error here.
    • The node crashed. You can identify if this is the case by looking for the cockroach process through ps. If you cannot locate the cockroach process (i.e., it crashed), file an issue.

Next step: If you successfully completed these steps, try starting a multi-node cluster.

2. Start a Multi-Node Cluster

  1. Terminate any running cockroach processes and remove any old data on the additional machines::

    $ pkill -9 cockroach
$ rm -r testStore
    Note:
    If you're running all nodes on the same machine, skip this step. Running this command will kill your first node making it impossible to proceed.

  2. On each machine, start the CockroachDB node, joining it to the first node:

    $ cockroach start --insecure --logtostderr --store=testStore \
--join=[first node's host]
    Note:
    If you're running all nodes on the same machine, you will need to change the --port, --http-port, and --store flags. For an example of this, see Start a Local Cluster.

    Errors at this stage potentially include:

  3. Visit the Admin UI on any node at http://[node host]:8080. All nodes in the cluster should be listed and have data replicated onto them.

    Errors at this stage potentially include:

Next step: If you successfully completed these steps, try securing your deployment (troubleshooting docs for this coming soon) or reviewing our other support resources.

Troubleshooting Information

Use the information below to resolve issues you encounter when trying to start or scale your cluster.

Networking Troubleshooting

Most networking-related issues are caused by one of two issues:

  • Firewall rules, which require your network administrator to investigate

  • Inaccessible hostnames on your nodes, which can be controlled with the --host and --advertise-host flags on cockroach start

However, to efficiently troubleshoot the issue, it's important to understand where and why it's occurring. We recommend checking the following network-related issues:

  • By default, CockroachDB advertises itself to other nodes using its hostname. If your environment doesn't support DNS or the hostname is not resolvable, your nodes cannot connect to one another. In these cases, you can:

    • Change the hostname each node uses to advertises itself with --advertise-host
    • Set --host=[node's IP address] if the IP is a valid interface on the machine

  • Every node in the cluster should be able to ping each other node on the hostnames or IP addresses you use in the --join, --host, or --advertise-host flags.

  • Every node should be able to connect to other nodes on the port you're using for CockroachDB (26257 by default) through telnet or nc:

    • telnet [other node host] 26257
    • nc [other node host] 26257

Again, firewalls or hostname issues can cause any of these steps to fail.

Node Will Not Join Cluster

When joining a node to a cluster, you might receive one of the following errors:

no resolvers found; use --join to specify a connected node

node belongs to cluster {"cluster hash"} but is attempting to connect to a gossip network for cluster {"another cluster hash"}

Solution: Disassociate the node from the existing directory where you've stored CockroachDB data. For example, you can do either of the following:

  • Choose a different directory to store the CockroachDB data:

    # Store this node's data in [new directory]
$ cockroach start [flags] --store=[new directory] --join=[cluster host]:26257

  • Remove the existing directory and start a node joining the cluster again:

    # Remove the directory
$ rm -r cockroach-data/

# Start a node joining the cluster
$ cockroach start [flags] --join=[cluster host]:26257

Explanation: When starting a node, the directory you choose to store the data in also contains metadata identifying the cluster the data came from. This causes conflicts when you've already started a node on the server, have quit cockroach, and then tried to join another cluster. Because the existing directory's cluster ID doesn't match the new cluster ID, the node cannot join it.

Replication Error in a Multi-Node Cluster

If data is not being replicated to some nodes in the cluster, we recommend checking out the following:

  • Ensure every node but the first was started with the --join flag set to the hostname and port of first node (or any other node that's successfully joined the cluster).

    If the flag was not set correctly for a node, shut down the node and restart it with the --join flag set correctly. See Stop a Node and Start a Node for more details.

  • Nodes might not be able to communicate on their advertised hostnames, even though they're able to connect.

    You can try to resolve this by stopping the nodes, and then restarting them with the --advertise-host flag set to an interface all nodes can access.

  • Check the logs for each node for further detail, as well as these common errors:

Something Else?

If we do not have a solution here, you can try using our other support resources, including:


Yes No
On this page

Yes No

Product

Resources

Learn

Support Channels

Company

Get developer news