I'm using Redis 2.8 on Windows which I downloaded from github release. After unzip and I've set maxheap in redis.windows.conf
file. After running redis-server redis.windows.conf
I get # Creating Server TCP listening socket *:6379:No such file or directory
, but redis is not running correctly. I don't know why.
相关问题
- Getting Redis Master address from Sentinel C#
- Configuring Redis to play nice with AppHarbor
- Why do we need Redis for running CKAN?
- Problem in deserialize redis-cache to objects in S
- wait for all promises to finish in nodejs with blu
I just got the same error message, but the root cause was different: I copied the config file over from a different machine, but it contained a "bind" entry containing an IP address, which - for sure - was invalid for the new machine, i.e. bind 234.234.234.234
I changed it to the correct address and it was working as expected.
After getting this error,open the cli and press the command 'shutdown' and restart redis server. You are good to go. You will get the logo and everything is as expected.
cd
to the bin directory of Redis, and runopen another cmd window,
cd
to the bin directory of Redis, and run4.redis-server.exe
Got the same behavior after restart. Initially thought Redis is not running, but your question made me to dig some more. Apparently, there's Windows service, called "Redis" and it started after computer reboot.
You must've used the .msi installer. It automagically registers a windows service which starts instantly after the installation (at least on my win 10 machine).
This service uses the default config and binds to port 6379. When you start redis-server from the command line, if you haven't specified a different port through a config file, it picks up the default config again and tries to bind to port 6379 which fails.
Your cli works because it connects to the redis service that's already listening on 6379. Your shutdown command stops the service and from there things work as expected. Mystery solved. Case closed.
As @FeigMan said you must've used the .msi installer. It automagically registers a windows service which starts instantly after the installation.
I was getting below error:
[15052] 10 Apr 14:40:14.601 # Creating Server TCP listening socket *:6379: listen: Unknown error
If service is already running you will get above error.
As per need you can restart service by below commands:
redis-server --service-stop
redis-server --service-start