Could not connect to Redis at 127 0 0 1 6379 Connection refused with homebrew

Question

Using homebrew to install Redis but when I try to ping Redis it shows this error   Could not connect to Redis at 127 0 0 1 6379  Connection refused   Note    I tried to turn off firewall and edit conf file but still cannot ping  I am using macOS Sierra and homebrew version 1 1 11

User · Answer

Try this     sudo service redis-server restart

User · Answer

Error connecting Redis on Apple Silicon  Macbook Pro M1 - Dec 2020   you have to just know 2 things   Run the redis-server using a sudo will remove the server starting error  shell  sudo redis-server  For running it as a service  quot daemonize quot  it will allow you to run in the background  shell  sudo redis-server --daemonize yes Verify using below steps  shell  redis-cli ping Hope this helps all Macbook Pro M1 users who are really worried about lack of documentation on this

User · Answer

It s the better way to connect to your redis   At first  check the ip address of redis server like this      ps -ef   grep redis   The result is kind of   redis  1184   1   0         usr bin redis-server 172 x x x 6379  And then you can connect to redis with -h hostname  option like this      redis-cli -h 172 x x x

User · Answer

If after install you need to run redis on all time  just type in terminal   redis-server  amp   Running redis using upstart on Ubuntu  I ve been trying to understand how to setup systems from the ground up on Ubuntu  I just installed redis onto the box and here s how I did it and some things to look out for   To install   sudo apt-get install redis-server   That will create a redis user and install the init d script for it  Since upstart is now the replacement for using init d  I figure I should convert it to run using upstart   To disable the default init d script for redis   sudo update-rc d redis-server disable   Then create  etc init redis-server conf with the following script   description  redis server   start on runlevel  23  stop on shutdown  exec sudo -u redis  usr bin redis-server  etc redis redis conf  respawn   What this is the script for upstart to know what command to run to start the process  The last line also tells upstart to keep trying to respawn if it dies   One thing I had to change in  etc redis redis conf is daemonize yes to daemonize no  What happens if you don t change it then redis-server will fork and daemonize itself  and the parent process goes away  When this happens  upstart thinks that the process has died stopped and you won t have control over the process from within upstart   Now you can use the following commands to control your redis-server   sudo start redis-server sudo restart redis-server sudo stop redis-server   Hope this was helpful

User · Answer

Had that issue with homebrew MacOS the problem was some sort of permission missing on  usr local var log directory see issue here  In order to solve it I deleted the  usr local var log and reinstall redis brew reinstall redis

User · Answer

This work for me    sudo service redis-server start

User · Answer

I found this question while trying to figure out why I could not connect to redis after starting it via brew services start redis   tl dr  Depending on how fresh your machine or install is you re likely missing a config file or a directory for the redis defaults    You need a config file at  usr local etc redis conf  Without this file redis-server will not start  You can copy over the default config file and modify it from there with  cp  usr local etc redis conf default  usr local etc redis conf  You need  usr local var db redis  to exist  You can do this easily with  mkdir -p  usr local var db redis    Finally just restart redis with brew services restart redis   How do you find this out    I wasted a lot of time trying to figure out if redis wasn t using the defaults through homebrew and what port it was on  Services was misleading because even though redis-server had not actually started  brew services list would still show redis as  started   The best approach is to use brew services --verbose start redis which will show you that the log file is at  usr local var log redis log  Looking in there I found the smoking gun s   Fatal error  can t open config file   usr local etc redis conf    or  Can t chdir to   usr local var db redis    No such file or directory   Thankfully the log made the solution above obvious   Can t I just run redis-server   You sure can  It ll just take up a terminal or interrupt your terminal occasionally if you run redis-server  amp   Also it will put dump rdb in whatever directory you run it in  pwd   I got annoyed having to remove the file or ignore it in git so I figured I d let brew do the work with services

User · Answer

After installing redis  type from terminal   redis-server   And Redis-Server will be started

User · Answer

First you need to up start the all the redis nodes using below command  one by one for all conf files   Note   if you are setting up cluster then you should have 6 nodes  3 will be master and 3 will be slave redis-cli will automatically select master and slave out of 6 nodes using --cluster command as shown in my below commands    xxxxx localhost redis-stable   redis-server xxxx conf    then run    xxxxx localhost redis-stable   redis-cli --cluster create 127 0 0 1 7000 127 0 0 1 7001 127 0 0 1 7002 127 0 0 1 7003 127 0 0 1 7004 127 0 0 1 7005 --cluster-replicas 1   output of above should be like        gt  gt  gt  Performing hash slots allocation on 6 nodes      2nd way to set up all things automatically   you can use utils create-cluster scripts to set up every thing for you like  starting all nodes  creating cluster you an follow https   redis io topics cluster-tutorial  Thanks

User · Answer

I was stuck on this for a long time  After a lot of tries I was able to configured it properly  There can be different reasons of raising the error  I am trying to provide the reason and the solution to overcome from that situation   6379 Port is not allowed by ufw firewall  Solution  type following command sudo ufw allow 6379  The issue can be related to permission of redis user  May be redis user doesn t have permission of modifying necessary redis directories  The redis user should have permissions in the following directories    var lib redis  var log redis  run redis  etc redis  To give the owner permission to redis user  type the following commands   sudo chown -R redis redis  var lib redis sudo chown -R redis redis  var log redis sudo chown -R redis redis  run redis sudo chown -R redis redis  etc redis   Now restart redis-server by following command  sudo systemctl restart redis-server   Hope this will be helpful for somebody

User · Answer

In my case  it was the password that contained some characters like    after changing it the server started without problems

User · Answer

I just had this same problem because I had used improper syntax in my config file  I meant to add   maxmemory-policy allkeys-lru  to my config file  but instead only added   allkeys-lru  which evidently prevented Redis from parsing the config file  which in turn prevented me from connecting through the cli  Fixing this syntax allowed me to connect to Redis

User · Answer

Just like Aaron  in my case brew services list claimed redis was running  but it wasn t  I found the following information in my log file at  usr local var log redis log   4469 C 28 Feb 09 03 56 197   oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 4469 C 28 Feb 09 03 56 197   Redis version 4 0 9  bits 64  commit 00000000  modified 0  pid 4469  just started 4469 C 28 Feb 09 03 56 197   Configuration loaded 4469 M 28 Feb 09 03 56 198   Increased maximum number of open files to 10032  it was originally set to 256   4469 M 28 Feb 09 03 56 199   Creating Server TCP listening socket 192 168 161 1 6379  bind  Can t assign requested address   That turns out to be caused by the following configuration   bind 127 0 0 1   1 192 168 161 1   which was necessary to give my VMWare Fusion virtual machine access to the redis server on macOS  the host  However  if the virtual machine wasn t started  this binding failure caused redis not to start up at all  So starting the virtual machine solved the problem

User · Answer

In my case  someone had come along and incorrectly edited the redis conf file to this  bind 127 0 0 1   1 bind 192 168 1 7  when  it really needed to be this  one line   bind 127 0 0 1   1 192 168 1 7

[redis] Could not connect to Redis at 127.0.0.1:6379: Connection refused with homebrew

Examples related to redis

Examples related to redis-server