Home/ Questions/How to deal with "could not connect to redis at 127.0.0.1:6379: connection refused" error.
Next
Answered
geovannirath
  • 3
Asked: 2022-06-20T10:30:50+00:00 In:

How to deal with “could not connect to redis at 127.0.0.1:6379: connection refused” error.

  • 3

. Advertisement .

..3..

. Advertisement .

..4..

Hi, everyone. I am having a problem that “can not connect to redis at 127.0.0.1:6379: connection refused” when I log in to it. The problem is as follow:

[[email protected] ~]# redis-cli
Could not connect to Redis at 127.0.0.1:6379: Connection refused
Could not connect to Redis at 127.0.0.1:6379: Connection refused
not connected> exit
[[email protected] ~]#

If everyone have any suggestions to solve this problem, please reply to me as soon as possible. Thanks!

not connect to redis at 127.0.0.1:6379: connection refused
Share

1 Answer

  1. Best Answer
    Expert

    The cause:

    You are get this problem because the redis server startup failure and the server have to be begun first.

    Solution:

    How to open the server: Open redis.conf file to edit in the redis installation directory. 

    Next, you take the following steps:

    Firstly, alter the daemon no in redis.conf to daemon yes because of the redis no running as a daemon.

    # By default Redis does not run as a daemon. Use 'yes' if you need it.
# Note that Redis will write a pid file in /var/run/redis.pid when daemonized.
daemonize yes

# If you run Redis from upstart or systemd, Redis can interact with your
# supervision tree. Options:
# supervised no - no supervision interaction
# supervised upstart - signal upstart by putting Redis into SIGSTOP mode
# supervised systemd - signal systemd by writing READY-1 to $NOTIFY_SOCKET
# supervised auto - detect upstart or systemd method based on
# UPSTART_JOB or NOTIFY_SOCKET environment variables
# Note: these supervision methods only signal "process is ready."
# They do not enable continuous liveness pings back to your supervisor.
supervised no

# If a pid file is specified, Redis writes it where specified at startup
# and removes it at exit.
#
# When the server runs non daemonized, no pid file is created if none is
# specified in the configuration. When the server is daemonized, the pid file
# is used even if not specified, defaulting to "/var/run/redis.pid".
"redis.conf" 1293L, 57766C

    Secondly, unlock the client.

    cd src # Nhập thư mục src trong thư mục cài đặt redis

    Carry out redis-server in this directory.

    ./redis-server/opt redis-4.0.2/redis.conf

    Finally, you can log in the redis.

    [[email protected] src]# redis-cli
127.0.0.1:6379> set name zwz
OK

    Here are my suggestions and hope it helps you. Good luck!!!        

    • 3

Leave an answer

You must login to add an answer.

Need An Account,