Closed GoogleCodeExporter closed 8 years ago
You have an older version of Redis installed on your operating system. Please
start redis-server by pointing to the exact path of the binary. When your
working directory is the root of the archive you downloaded, you can start it
by executing "src/redis-server".
Original comment by pcnoordh...@gmail.com
on 20 Mar 2011 at 9:58
Thanks.. When I do that I get Opening port: bind: Address already in use
But I don't have a server running. Do you know how to fix that?
Original comment by Sebou...@gmail.com
on 20 Mar 2011 at 10:16
You have something running on that port, whether it is Redis itself or
something else. That needs to be killed/quitted first. Otherwise, you can run
Redis on a different, unused, port.
Original comment by pcnoordh...@gmail.com
on 20 Mar 2011 at 10:26
How would I find out what's running on the port and quit it? And how can I run
it on a different port?
Original comment by Sebou...@gmail.com
on 20 Mar 2011 at 11:12
btw NMAP says port 631 is open.
PORT STATE SERVICE
631/tcp open ipp
Original comment by Sebou...@gmail.com
on 20 Mar 2011 at 11:17
Use "lsof -i :6379 | grep -i listen" to find out which process is listening on
the default Redis port. Change the config file to make Redis listen on another
port.
Original comment by pcnoordh...@gmail.com
on 20 Mar 2011 at 12:00
That command shows that nothing is running on port 6379. I can't seem to get it
to work. What's the best way to uninstall and install again?
Original comment by Sebou...@gmail.com
on 21 Mar 2011 at 1:22
You're passing a config file when starting Redis. Please double check that
nothing is running on the port that is specified in that config file (6379 is
the default, but when Redis quits saying that the port is already in use, and
6379 is not bound, you probably have a non-default port number specified in you
config file?).
Original comment by pcnoordh...@gmail.com
on 21 Mar 2011 at 7:58
I've verified that nothing is running on port 6379. I've checked the default
port and it's 6379. I need to run redis on this port to make it work with
juggernaut. I've tried deleting the folder and reinstalling, and I get the same
result. Has this happened to anyone else? What do you recommend? Thanks..
Original comment by Sebou...@gmail.com
on 21 Mar 2011 at 10:37
I have the same problem on ubuntu 10.10
Original comment by soufiane...@gmail.com
on 4 Apr 2011 at 7:57
yes even i am facing the same problem..
Original comment by rajitha....@gmail.com
on 15 Sep 2011 at 12:03
same problem i am facing if I go to config file and then change port to
something else the redis server is running but the issue is i need to integrate
it with juggernaut..... how to run it at default port ?????????/
Original comment by sahil20g...@gmail.com
on 20 Sep 2011 at 8:14
Hi, I just included the port number in the error message when Redis can't bind
the listening socket so that troubleshooting will be simpler the next time.
However this is not a Redis bug but a setup issue.
Salvatore
Original comment by anti...@gmail.com
on 20 Sep 2011 at 8:49
how to resolve that issue then ?? @anti
Original comment by sahil20g...@gmail.com
on 20 Sep 2011 at 8:57
not sure I understand your issue but you can try writing to the Redis Google
Group.
If the problem is that you can't change port, likely you specify a port number
in redis.conf but then don't run redis-server with "redis-server
/path/to/config/file".
Original comment by anti...@gmail.com
on 20 Sep 2011 at 9:24
I have the same problem after I install a new version redis. After I reboot my
computer, all the problem is gone. I guess this problem is because there is an
old version redis running on your computer.
Original comment by hanqch...@gmail.com
on 7 Mar 2012 at 5:10
Is this issue solved? I found nothing run at port 6379 but redis says the
address already in use. Sometimes reboot may helps.
Original comment by create0...@gmail.com
on 5 Aug 2014 at 12:16
This bug tracker is no longer in use, it has been migrated to
github.com/antirez/redis .
Your problem is not a bug with Redis, but is caused by your usage of Redis. You
should email the Redis mailing list
(https://groups.google.com/forum/#!forum/redis-db) with your problem, what you
have done to diagnose your problem, and what you would like to happen.
Original comment by josiah.c...@gmail.com
on 5 Aug 2014 at 12:51
please help me.
my case error same like sebou :
root@satria-pc:/home/satria# service redis-server restart
Stopping redis-server: redis-server.
Starting redis-server:
*** FATAL CONFIG FILE ERROR ***
Reading the configuration file, at line 709
>>> 'unixsocket /tmp/redis.sock echo unixsocket /tmp/redis.sock'
Bad directive or wrong number of arguments
failed
Original comment by edysatri...@gmail.com
on 27 Jun 2015 at 2:57
A few things:
1) Bug tracking was moved to Github, as I last stated August 4, 2014
2) This isn't a bug with Redis, this is a problem with your configuration file,
which is why it has a status of "invalid"
3) The error reported by Redis tells you exactly what is wrong: "bad directive
or wrong number of arguments" - line 709 *should* read 'unixsocket
/tmp/redis.sock' without the quotes, assuming that is the socket path you want
Original comment by josiah.c...@gmail.com
on 27 Jun 2015 at 3:59
Original issue reported on code.google.com by
Sebou...@gmail.com
on 20 Mar 2011 at 9:49