Check YugabyteDB processes

1. Are the YugabyteDB processes running?

Connect to the local node where YugabyteDB is running.

On the local setup, this is your local machine (or a Docker instance running on your local machine). On a multi-node cluster, you may need to ssh into the machines where the YugabyteDB nodes are running.

$ ps aux | grep yb-tserver

If you are expecting a master process on this node, you can also do the following.

$ ps aux | grep yb-master

If the processes are not running you can start them with:

• yb-ctl when using a local cluster.

• bin/yb-tserver and bin/yb-master binaries when using a multi-node cluster.

Once the processes are running, if they are not accessible from your client machine this may be a network issue (see below).

2. Are the yb-master and yb-tserver endpoints accessible?

Generally, the endpoints are:

However, in some setups these endpoints may not be accessible, depending on the configuration on your physical machines or on your cloud-provider account.

IP not accessible

• Private vs Public IP: Consider setting up a VPN or using the node’s public IP (e.g. get it from the machine status on your cloud-provider account).

Ports closed

• Cloud Account Configuration: Open the relevant ports (see below), for TCP traffic on your cloud-provider account (e.g. security group rules).

• SELinux turned on: If your host has SELinux turned on, run the following commands to open the ports using firewall exceptions.

sudo firewall-cmd --zone=public --add-port=7000/tcp;
sudo firewall-cmd --zone=public --add-port=7100/tcp;
sudo firewall-cmd --zone=public --add-port=9000/tcp;
sudo firewall-cmd --zone=public --add-port=9100/tcp;
sudo firewall-cmd --zone=public --add-port=11000/tcp;
sudo firewall-cmd --zone=public --add-port=12000/tcp;
sudo firewall-cmd --zone=public --add-port=9300/tcp;
sudo firewall-cmd --zone=public --add-port=9042/tcp;
sudo firewall-cmd --zone=public --add-port=6379/tcp;