laptop crashed, booting fails because "waiting for redis to shutdown" (Ubuntu 14.04)

269 views
Skip to first unread message

Janna Maas

unread,
Dec 2, 2015, 4:32:52 PM12/2/15
to Redis DB
ok, after an unintentional shutdown - i think my laptop battery ran out and it tried to hibernate- i try to restart it. Reboot hangs; if i access the log(?) by pressing esc at the ubuntu start screen i just see
"Waiting for Redis to shutdown ..."
"Waiting for Redis to shutdown ..."
"Waiting for Redis to shutdown ..."

ad infinitum. This is a dual boot machine, the windows side boots up normally.

i have tried the following: boot in ubuntu recovery mode and go to command line:

* stop with redis-cli shutdown
> "could not connect to Redis at 127.0.0.1:6379: Connection refused"

* there is a redis process running:
ps -ef|grep "redis"
> root 750 700 0 22:58 tty1 00:00:00 grep --colour=auto redis

* however if i kill pid 750, and run ps again, there is a new redis pid.

* i can access /etc/init.d/redis_6379. /var/run/redis_6379 does not exist.

Any suggestions? I would be insanely grateful if i do not have to reinstall the ubuntu side..

Janna



Greg Andrews

unread,
Dec 2, 2015, 5:52:14 PM12/2/15
to redi...@googlegroups.com
As a quick and dirty technique to prevent whatever-it-is (probably upstart or systemd) from re-starting your Redis, find the executable program and remove it's executable permissions.  If the program is /usr/bin/redis, then "chmod 444 /usr/bin/redis" and then killing the current redis process ought to take it down and keep it down.

  -Greg

--
You received this message because you are subscribed to the Google Groups "Redis DB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redis-db+u...@googlegroups.com.
To post to this group, send email to redi...@googlegroups.com.
Visit this group at http://groups.google.com/group/redis-db.
For more options, visit https://groups.google.com/d/optout.

Janna Maas

unread,
Dec 3, 2015, 3:55:15 AM12/3/15
to Redis DB
thank you!

It turned out the problem was not directly related to Redis- some other service was happily writing to the error log at millisecond intervals and had completely filled my disk. This explains why googling for the error did not bring up much..

Janna
Reply all
Reply to author
Forward
0 new messages