How can I stop redis-server?
Asked Answered
P

30

540

I apparently have a redis-server instance running because when I try to start a new server by entering redis-server, I'm greeted with the following:

Opening port: bind: Address already in use

I can't figure out how to stop this server and start a new one.

Is there any command I can append to redis-server when I'm typing in the CLI?

My OS is Ubuntu 10.04.

Pulmonary answered 2/8, 2011 at 10:7 Comment(2)
Ladies and gentlemen, if you did not install redis via the package manager, and you installed it from source, then it might not work with systemv or upstart or systemd on ubuntu. Thus, the selected answer will not work by default. The second answer, which is not marked correct, appears to be more reliable.Wise
Tip: testing whether a Redis server is running can be done via redis-cli ping. A running Redis server will respond with PONG.Chrominance
S
858

Either connect to node instance and use shutdown command or if you are on ubuntu you can try to restart redis server through init.d:

/etc/init.d/redis-server restart

or stop/start it:

/etc/init.d/redis-server stop
/etc/init.d/redis-server start

On Mac

redis-cli shutdown
Saenz answered 2/8, 2011 at 10:19 Comment(8)
You can only do that if you set up redis that way. Kevin McTigue's answer works with minimal setup.Negris
On OS X you'll probably have to use launchctl to do this, and on other systems, systemctl or service.Burgee
On some machines sudo /etc/init.d/redis stop will workIntertexture
On modern Ubuntu, I just use service redis-server stop and service redis-server start, after having installed it with apt-get install redis-server.Myca
This only works if you have redis-server running as a service. If it is running as a stand alone executable, then you will need to explicitly stop the process. Here are the steps I used to stop the process: pkill redis-server on a linux boxMatrimony
on WSL (Windows subsystem for Linux) redis-cli shutdown worked for meDeaton
Hi reader, be careful about the shudown command flushing your AOF persistence redis.io/commands/shutdownLongways
(*) on Mac what worked for me was brew services stop redis - the redis-cli shutdown was basically a no-op.Cholecystectomy
V
229

A cleaner, more reliable way is to go into redis-cli and then type shutdown

In redis-cli, type help @server and you will see this near the bottom of the list:

SHUTDOWN - summary: Synchronously save the dataset to disk and then shut down the server since: 0.07

And if you have a redis-server instance running in a terminal, you'll see this:

User requested shutdown...
[6716] 02 Aug 15:48:44 * Saving the final RDB snapshot before exiting.
[6716] 02 Aug 15:48:44 * DB saved on disk
[6716] 02 Aug 15:48:44 # Redis is now ready to exit, bye bye...
Valor answered 2/8, 2011 at 19:51 Comment(12)
Or don't even start redis-cli. Just send it from the command line via redis-cli shutdown. (you can send any command like this, for example redis-cli set cat dog; redis-cli get cat)Johnnie
The only caveat to @jessebuesking comment is that if you've set up password protection, redis-cli set cat dog; redis-cli get cat changes to redis-cli -a mypassword set cat dog; redis-cli -a mypassword get cat, which can be annoying after a few commands.Excavate
@Excavate one thing you could do to avoid the redundancy is set an alias for your current bash session, for instance alias redis-cli="redis-cli -a mypassword". This way you can make the calls like in my original comment without having to re-supply your password on each use.Johnnie
@jessebuesking very creative! Wouldn't have thought about solution. For some reason I'm a little afraid of putting passwords in config filesExcavate
@Excavate don't take my word for it, but I think doing this will only store it in memory for the current session (aka don't add it to your bashrc or bash_profile, just enter it as-is from your prompt).Johnnie
@JesseBuesking, but the shell may remember a history of all commands that you have entered, just to you can use the "Up" arrow or Ctrl+R.Maecenas
@SergeyOrshanskiy this is true. You could go in and delete that entry from your history if you'd like, but your password might still be written to an audit log if it's set up. I'm not a security expert by any means and personally wouldn't do this if you have concerns about security.Johnnie
+1 to @JesseBuesking: I was getting "(error) ERR operation not permitted" for SHUTDOWN. Passing password using -a made my day. I am a newbie to Redis and was getting frustrated.Persnickety
Can one similarly restart the redis server via redis-cli restart (or something comparable)?Lupe
@HassanBaig, no. redis-cli restart will report that it can't connect to Redis.Chrominance
It is strange though that this option to shutdown Redis is apparently so hard to find (initially, also for me), even though it is rather obvious. That we need to start a redis-cli and then type help @server and scroll down in a long list... I expected that redis-cli --help would have mentioned this as well somewhere.Chrominance
As pointed out here: #50705460, this method does not work for everyone; my process kept respawining with a different PID. The accepted answer from @Saenz is the only working method to stop redis service for me.Dirtcheap
F
167

redis-cli shutdown is most effective. The accepted answer does not work for me (OSX Lion). Thanks, @JesseBuesking.

Finesse answered 10/6, 2013 at 22:3 Comment(5)
yep, the accepted answer works only for Linux systems with Redis set up as a service in the depicted wayExcavate
This also works on Windows. redis-cli.exe shutdownGaggle
As I mentioned above, it's a pity that this (rather obvious) method is so hard to find. I expected that redis-cli --help could have covered this case.Chrominance
I'm on Ubuntu and get a failure: "(error) ERR unknown command shutdown, with args beginning with:"Absently
I'm on Ubuntu and redis-cli shutdown nosave did the trick.Tractile
L
71

For OSX, I created the following aliases for starting and stopping redis (installed with Homebrew):

alias redstart='redis-server /usr/local/etc/redis/6379.conf'
alias redstop='redis-cli -h 127.0.0.1 -p 6379 shutdown'

This has worked great for local development!

Homebrew now has homebrew-services that can be used to start, stop and restart services. homebrew-services

brew services is automatically installed when run.

brew services start|run redis 
brew services stop redis
brew services restart redis

If you use run, then it will not start it at login (nor boot). start will start the redis service and add it at login and boot.

Lightheaded answered 16/8, 2013 at 16:59 Comment(10)
If you installed redis using homebrew, brew services stop redis also works! :)Earthshaking
I would recommend using brew services now for handling the starting and stopping for the defaults. If you need a little more control then there are also other options.Lightheaded
This is the best answer as it works on all linux flavours and mac, including those installed using apt, yum , brew or downloading. Wether they have upstart or init or system d scripts or not. ThanksHindrance
I like the name of the aliases :) Cool!Badman
what should I do if I want to restart and not shutdown @RayHunterGrinnell
what should i do to check the status?? @HindranceGrinnell
@AATHITHRAJENDRAN redis-cli does not have a restart command. If you are on mac you can use the homebrew command brew services restart redis to do a stop/start which uses launchctl under the hood. You can create another alias that uses the commands above to do the stop and start. alias redrestart='redis-cli -h 127.0.0.1 -p 6379 shutdown && redis-server /usr/local/etc/redis/6379.conf'. You can also write a function to do it too.Lightheaded
Sorry for this confusion But service restart redis_6379 restarts the redis, @rayGrinnell
@AATHITHRAJENDRAN that is particular to your system and how it was installed. It will probably be different on different systems.Lightheaded
works for me. Thanks for answer in here stackoverflow platformUranyl
E
47

stop the redis server type in terminal with root user

sudo service redis-server stop

the message will be display after stop the redis-server

Stopping redis-server: redis-server.

if you want to start the redis-server type

sudo service redis-server start

if you want to restart the server type

sudo service redis-server restart
Edgebone answered 1/10, 2016 at 13:4 Comment(2)
I wonder if this is still valid for new Redis versions if configured by default. Issuing service --status-all won't show redis, hence any service command will fail against redis-server. But redis does show in ps -ef. I just cannot find any related document.Deas
Looks on Ubuntu 18.04 sudo service redis start/stop/status does the same, both go.Welcy
W
26

Type SHUTDOWN in the CLI

or

if your don't care about your data in memory, you may also type SHUTDOWN NOSAVE to force shutdown the server.

Warfore answered 6/9, 2012 at 6:52 Comment(0)
F
20

Try killall redis-server. You may also use ps aux to find the name and pid of your server, and then kill it with kill -9 here_pid_number.

Firstling answered 2/8, 2011 at 10:12 Comment(6)
This is great, works on mac / unix. (Mac tested, unix approved)Volk
Bad idea to hard-kill a DB server. Always prefer a proper shutdown, or at least, kill -15 instead of kill -9.Ornate
@ZsoltSzilagy you should provide a link or somewhat of an explanation why it's a bad idea. Like how redis does delayed writes, so that there will still be uncommited data in memory.Schism
@notbad.jpeg, of course, you can also drop your computer on the floor. If the table is high enough, this should also stop the server. Do I need a link or somewhat of an explanation as to why this is a bad idea?Maecenas
With this method you're not thinking about the redis database state. You're using an OS functionality to shutdown an application instead of using the application itself or a daemon, which is probably using application functionality too. This solution is like unplugging the cable to shutdown the TV.Ring
Redis has a whole documentation page on what Unix Signals it can handle. "The SIGTERM and SIGINT signals tell Redis to shut down gracefully. When the server receives this signal, it does not immediately exit. Instead, it schedules a shutdown similar to the one performed by the SHUTDOWN command." Signals are given integer values. for most Linux systems, 9 is the SIGKILL signal, which tells the OS to stop the Redis process without allowing Redis to clean up. SIGTERM, or 15, does allow Redis to clean up after itself. redis.io/docs/reference/signalsYusem
F
20

I would suggest to disable Redis-server, which prevents auto start while computer restarts and very useful to use docker like tools etc.

Step 1: Stop the redis-server

sudo service redis-server stop

Step 2: Disable the redis-server

sudo systemctl disable redis-server

if you need redis, you can start it as:

sudo service redis-server start
Furcula answered 18/1, 2021 at 2:43 Comment(0)
S
16

Option 1: go to redis installation directory and navigate to src , in my case :

/opt/redis3/src/redis-cli -p 6379 shutdown

where 6379 is the default port.

Option 2: find redis process and kill

ps aux | grep redis-server

t6b3fg   22292  0.0  0.0 106360  1588 pts/0    S+   01:19   0:00 /bin/sh /sbin/service redis start
t6b3fg   22299  0.0  0.0  11340  1200 pts/0    S+   01:19   0:00 /bin/sh /etc/init.d/redis start

And Then initiate kill:

kill -9 22292

kill -9 22299

I'm using Centos 6.7 , x86_64

hope it helps

Spodumene answered 15/9, 2015 at 1:24 Comment(1)
failed: no such process 😯Pussy
F
12

Another way could be:

ps -ef | grep -i 'redis-server'
kill -9 PID owned by redis

Works on *NIX & OSX

Fed answered 18/8, 2014 at 9:35 Comment(1)
@JoenasE, no, this should not be the accepted answer IMO. Having the OS kill a running process neglects the case that the application might have some data in memory not yet saved to a more persistent store. Shutting down the application via a method provided by the application is preferably a better option.Chrominance
S
12

if you did make install (e.g ubuntu) while installing redis then you can do:

redis-cli shutdown

as pointed by @yojimbo87 :)

Slotnick answered 24/12, 2019 at 7:17 Comment(0)
I
10

MacOSX - It Worked :)

Step 1 : Find the previously Running Redis Server

ps auxx | grep redis-server

Step 2 : Kill the specific process by finding PID (Process ID) - Redis Sever

kill -9 PID
Inness answered 22/8, 2016 at 18:11 Comment(0)
F
7

Another way could be :

brew services stop redis
Fortitude answered 25/3, 2018 at 20:47 Comment(1)
+10 for this, it works without apology on mac! this also works ™brew services start redis™ ¢brew services restart redis¢Ferdinand
M
7

If Redis is installed via snap:

sudo snap stop redis.server
Molybdenous answered 8/7, 2021 at 22:56 Comment(0)
G
6

systemd, ubuntu 16.04:

$ sudo systemctl is-active redis-server
active

$ sudo systemctl is-enabled redis-server
enabled

$ sudo systemctl disable redis-server
Synchronizing state of redis-server.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable redis-server
Removed /etc/systemd/system/redis.service.

$ sudo systemctl stop redis-server
Geraldgeralda answered 17/11, 2016 at 15:32 Comment(0)
R
6

Usually this problem arises after I shut down my computer ( or leaving running ) an irregular way.. I believe the port gets stuck open, while the process stops but continues to be bound to the previous port.

9/10 times the fix can be:

$ ps aux | grep redis

-> MyUser 2976  0.0  0.0  2459704    320   ??  S    Wed01PM   0:29.94 redis-server *:6379

$ kill 2976

$ redis-server

Good to go.

Rompish answered 12/1, 2017 at 18:56 Comment(0)
G
6

If you know on which port(default:6379) your redis server is running you can go with option 1 or you can check your redis process and you can kill with option 2

option 1:
Kill process on port:

check     : sudo lsof -t -i:6379
kill      : sudo kill `sudo lsof -t -i:6379`

option 2:
Find the previously Running Redis Server:

 ps auxx | grep redis-server

Kill the specific process by finding PID (Process ID) - Redis Sever

kill -9 PID

Now start your redis server with

redis-server /path/to/redis.conf 
Grinnell answered 23/5, 2019 at 9:57 Comment(0)
F
5

If you know on what port it would be running(by default it would be 6379), you can use below command to get the pid of the process using that port and then can execute kill command for the same pid.

sudo lsof -i : <port> | awk '{print $2}'

the above command will give you pid.

kill <pid>;

This would shutdown your server.

Fixed answered 16/1, 2014 at 6:20 Comment(0)
P
5

If you are running redis in a docker container, none of the present answers will help. You have to stop redis container. Otherwise, redis process will keep respawning.

$ docker ps
CONTAINER ID        IMAGE                    PORTS                             
e1c008ab04a2        bitnami/redis:4.0.8-r0   0.0.0.0:6379->6379/tcp

$ docker stop e1c008ab04a2
e1c008ab04a2
Piano answered 19/10, 2018 at 11:5 Comment(0)
P
4

Following worked for me on MAC

 ps aux | grep 'redis-server' | awk '{print $2}' | xargs sudo kill -9
Potshot answered 10/10, 2018 at 10:16 Comment(0)
S
3

In my case it was:

/etc/init.d/redismaster stop
/etc/init.d/redismaster start

To find out what is your service name, you can run:

sudo updatedb
locate redis

And it will show you every Redis files in your system.

Salvia answered 3/2, 2016 at 8:42 Comment(0)
S
3

To stop redis server

sudo service redis-server stop

and check the status of it using

sudo service redis-server status
Stoneman answered 17/8, 2020 at 5:45 Comment(0)
I
1

I don't know specifically for redis, but for servers in general:

What OS or distribution? Often there will be a stop or /etc/init.d/... command that will be able to look up the existing pid in a pid file.

You can look up what process is already bound to the port with sudo netstat -nlpt (linux options; other netstat flavors will vary) and signal it to stop. I would not use kill -9 on a running server unless there really is no other signal or method to shut it down.

Iasis answered 2/8, 2011 at 10:16 Comment(0)
T
1

The commands below works for me on Ubuntu Server

$ service /etc/init.d/redis_6379 stop
$ service /etc/init.d/redis_6379 start
$ service /etc/init.d/redis_6379 restart
Tatiana answered 1/10, 2016 at 12:14 Comment(0)
P
1

Redis has configuration parameter pidfile (e.g. /etc/redis.conf - check redis source code), for example:

# 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".
#
pidfile /var/run/redis.pid

If it is set or could be set, instead of searching for process id (pid) by using ps + grep something like this could be used:

kill $(cat /var/run/redis.pid)

If required one can make redis stop script like this (adapted default redis 5.0 init.d script in redis source code):

PIDFILE=/var/run/redis.pid
if [ ! -f $PIDFILE ]
then
    echo "$PIDFILE does not exist, process is not running"
else
    PID=$(cat $PIDFILE)
    echo "Stopping ..."
    kill $PID
    while [ -x /proc/${PID} ]
    do
        echo "Waiting for Redis to shutdown ..."
        sleep 1
    done
    echo "Redis stopped"
fi
Palomino answered 20/4, 2020 at 8:19 Comment(0)
P
1

The service name of redis is redis-server, so you can disable and stop redis with this command:

sudo systemctl disable redis-server 
sudo systemctl stop redis-server 
Palladic answered 3/11, 2022 at 14:43 Comment(0)
P
0

On MacOSX,

This is what worked for me

/etc/init.d/redis restart

/etc/init.d/redis stop

/etc/init.d/redis start
Palladium answered 9/12, 2015 at 2:43 Comment(0)
S
0

One thing to check if the redis commands are not working for you is if your redis-server.pid is actually being created. You specify the location of where this file is in

/etc/systemd/system/redis.service 

and it should have a section that looks something like this:

[Service]
Type=forking
User=redis
Group=redis
ExecStart=/usr/bin/redis-server /etc/redis/redis.conf
PIDFile=/run/redis/redis-server.pid
TimeoutStopSec=0
Restart=always

Check the location and permissions of the PIDFile directory (in my case, '/run/redis'). I was trying to restart the service logged in as deploy but the directory permissions were listed as

drwxrwsr-x  2 redis    redis      40 Jul 20 17:37 redis

If you need a refresher on linux permissions, check this out. But the problem was I was executing the restart as my deploy user which the permissions above are r-x, not allowing my user to write to the PIDFile directory.

Once I realized that, I logged in using root, reran the restart command on the redis (service redis restart) and everything worked. That was a headache but hopefully this saves someone a little time.

Same answered 24/7, 2018 at 16:11 Comment(0)
L
0

To gracefully shutdown specific instances with passwords and not resorting to brute-force kill commands, use:

redis-cli -p <port> -a <pass> shutdown

root@machine:~# ps aux
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root       105  0.1  0.0  60552 10772 ?        Ssl  23:27   0:02 redis-server 127.0.0.1:10002
root       111  0.1  0.0  60552 10900 ?        Ssl  23:28   0:02 redis-server 127.0.0.1:10003
root       117  0.1  0.0  60552 10872 ?        Ssl  23:28   0:02 redis-server 127.0.0.1:10004

root@machine:~# redis-cli -p 10002 -a mypassword shutdown
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.

root@machine:~# ps aux
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root       111  0.1  0.0  60552 10900 ?        Ssl  23:28   0:02 redis-server 127.0.0.1:10003
root       117  0.1  0.0  60552 10872 ?        Ssl  23:28   0:02 redis-server 127.0.0.1:10004

root@machine:~#

Having a ton of instances warrants writing a batch script to loop through them all for a master shutdown.

Lunar answered 12/10, 2022 at 5:55 Comment(0)
A
-2

You can try this code:

sudo kill -9 $(ps aux | grep 'redis' | awk '{print $2}')
Aggregation answered 28/9, 2020 at 7:36 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.