Error on RAAS logs, "Could not connect to Redis at <Redis Node FQDN>:6379: Connection refused"
search cancel

Error on RAAS logs, "Could not connect to Redis at <Redis Node FQDN>:6379: Connection refused"

book

Article ID: 383596

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Users may encounter a scenario where the Redis service is running but inaccessible on port 6379.

Connectivity tests result in a "Connection Refused" error, preventing external services such as RAAS from establishing a connection.

Environment

Aria Config 8.x

Cause

The Redis server was configured in the "/etc/redis/redis.conf" file to bind only to the loopback IP address 127.0.0.1, restricting external connections.

Binding Redis to the loopback address (127.0.0.1) limits its accessibility to the local machine, preventing services like RAAS from communicating with Redis.

Resolution

Verification Steps

  1. Verified the Redis service status using appropriate commands (e.g., service redis status).
  2. Performed connectivity tests with:
    • netstat -entlp
    • curl -v telnet://redis:6379
  3. Observed that all connectivity tests to port 6379 failed with a "Connection Refused" error.

 

Solution

  1. Update Redis Configuration:

    • Edit the redis.conf file located "/etc/redis/redis.conf"
    • Change the binding from 127.0.0.1 to the server’s actual IP address.

    Example:

    bind <IP address of Redis Server>  
    
  2. Restart the Redis Service:

    • Apply the changes by restarting the Redis service:
      service redis restart  
      

Updating the redis.conf file to bind Redis with IP address resolved the connectivity issue. Post-configuration changes:

  • The RAAS node was able to connect successfully to Redis on port 6379.
  • All external services dependent on Redis functioned as expected.

Additional Information

Additional Notes

  • Ensure the updated binding does not expose Redis to unauthorized access. Use proper firewall rules and authentication settings for security.
  • Refer to the official Redis documentation for further details on configuration best practices.

This solution ensures seamless communication between Redis and external services, improving overall system functionality.