192.168.49.18:7001 is not configured as a cluster node. [root@localhost cluster]# CLUSTER NODES

The error message suggests that the IP address and port 192.168.49.18:7001 is not configured as a cluster node in your cluster.

To resolve this issue, you should add the node to the cluster by using the `CLUSTER MEET` command. For example, if you have another node with IP address 192.168.49.19 and port 7001, you can add it to the cluster by running the following command on one of the existing nodes:

CLUSTER MEET 192.168.49.19 7001

After running this command, you can check the status of your nodes by running the `CLUSTER NODES` command again.

相关问题

Get "http://192.168.200.10:5000/v2/": dial tcp 192.168.200.10:5000: connect: connection refused

This error message indicates that the client was unable to establish a connection with the server at the specified IP address and port number. The most likely causes of this error are:

- The server is not running or is not listening on the specified port.
- The network connection between the client and server is not functioning correctly.
- A firewall or other security software is blocking the connection.

To resolve this issue, you should check that the server is running and listening on the correct port, verify that the network connection is functioning properly, and ensure that any firewalls or security software are configured to allow the necessary traffic.

Liveness probe failed: Get "https://192.168.58.3:8443/livez": dial tcp 192.168.58.3:8443: connect: connection refused

This error message indicates that the liveness probe for a Kubernetes container has failed. The liveness probe is a mechanism that Kubernetes uses to check if a container is running as expected. In this case, the probe failed because Kubernetes was unable to establish a connection to the container at the specified IP address and port.

There could be several reasons why Kubernetes was unable to connect to the container. One possibility is that the container is not running or has crashed. Another possibility is that there is a firewall or network configuration issue preventing the connection.

To troubleshoot this issue, you can start by checking the logs for the container to see if there are any error messages indicating why it failed. You can also try connecting to the container manually using the IP address and port specified in the error message to see if there are any network issues. Additionally, you can check the Kubernetes configuration to ensure that the container is configured correctly and that there are no firewall or network issues preventing the connection.