1

No matter what I do I can't seem to kill redis without another instance popping up immediately with a different PID -- I checked to make sure I was killing the parent process and I was. Any suggestions?? I've already tried restarting my machine. I've also tried the answers from this SO post. Here are the commands I ran to kill and check: 

ascourtas@ascourtas-VirtualBox:~$ ps -ef | grep redis
redis     2573     1  0 12:11 ?        00:00:00 /usr/bin/redis-server 
0.0.0.0:6379
ascourt+  2991  2501  0 12:25 pts/6    00:00:00 grep --color=auto 
redis

ascourtas@ascourtas-VirtualBox:~$ pgrep redis | xargs -i pstree -ps 
{}
systemd(1)───redis-server(2573)─┬─{redis-server}(2575)
                            └─{redis-server}(2576)

ascourtas@ascourtas-VirtualBox:~$ sudo kill -9 2573

ascourtas@ascourtas-VirtualBox:~$ ps -ef | grep redis
redis     3069     1  0 12:26 ?        00:00:00 /usr/bin/redis-server 
0.0.0.0:6379
ascourt+  3077  2501  0 12:26 pts/6    00:00:00 grep --color=auto 
redis
ascourtas
  • 227
  • 2
  • 10

1 Answers1

6

Figured it out! Turns out when I had tried the second answer provided at this SO post, I had done cd /etc/init.d and then ran redis-server stop, when I actually should've run /etc/init.d/redis-server stop. I do not know why this matters though.

ascourtas
  • 227
  • 2
  • 10
  • 1
    Thank you for this Q&A, really useful. I had made the exact same error when following the SO post. Also no other method seem to work for me. If you ever find out the reason behind this, or anything more about this topic, please consider updating the answer. – alelom Dec 04 '18 at 14:46
  • I definitely will! Although I have not yet been enlightened. I'm glad it was helpful for you! – ascourtas Jan 22 '19 at 03:54