Can't bind TCP listener *:6379 using Redis on Windows

Question

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.

Now service is normally.I run `redis-cli.exe` in the same window,and it connect correctly.Then I typed `shutdown`,the service is over.Reopen a command windows,type `redis-server`.The service run correctly.But I still did not understand why `# Creating Server TCP listening socket *:6379:No such file or directory` came out. — inOut, Aug 02 '15 at 06:29
I ran into the same problem this morning on Win 2008 R2. Your comment worked so you should post and accept it as the answer :) — pulsar, Aug 18 '15 at 10:16

score 102 · Answer 1 · answered Dec 09 '15 at 19:52

102

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.

answered Dec 09 '15 at 19:52

FeignMan

1,186
2
7
8

3

perfect answer. – tObi Feb 14 '17 at 22:32
3

Perfect answer! – SexyBeast Apr 30 '17 at 20:23
1

That's nice to hear from a SexyBeast. My life is complete ;) – FeignMan Feb 16 '18 at 10:54
If you want to completely remove running Redis as a service, on windows: Windows key (Run) > Regedit > "HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/Redis" > right mouse click > delete – Pascalculator Aug 07 '18 at 13:10
1

Great answer! This helped alot. I thought there was a problem but turns out it isn't a problem. Just needed to know this. – manpikin Mar 18 '20 at 09:37

liyuhui · Answer 2 · 2017-08-04T01:41:09.830

76

cdto the bin directory of Redis, and run

redis-cli.exe
shutdown
exit

open another cmd window, cd to the bin directory of Redis, and run

4.redis-server.exe

edited Aug 04 '17 at 01:41

answered Aug 01 '17 at 07:30

liyuhui

1,210
12
17

11

A few words of explanation would make this more helpful. – GhostCat Aug 01 '17 at 07:55
1

You are an angel. Thank you! – David Lasry Aug 13 '18 at 12:05
It worked even if it said that server was not running – Ruslan López May 30 '19 at 14:29
Thanks! Worked like a charm – Gibs Jan 18 '21 at 16:47

score 27 · Accepted Answer · answered Aug 19 '15 at 08:27

27

Now service is normally.I run redis-cli.exe in the same window,and it connect correctly.Then I typed shutdown,the service is over.Reopen a command windows,type redis-server.The service run correctly.But I still did not understand why # Creating Server TCP listening socket *:6379:No such file or directory came out.

answered Aug 19 '15 at 08:27

inOut

1,123
1
9
15

nope. When I run redis-cli.exe, I see a black screen. Can't even type. So change the port to 6380 and it worked ! – Stephane Sep 23 '16 at 11:41
"But I still did not understand why # Creating Server TCP listening socket *:6379:No such file or directory came out." - because you had a Redis server running as a windows service. Your shutdown command stopped it. Alternatively you can go into Computer Management > Services and Applications > Services and stop Redis and set it to not start automatically at startup. – FeignMan Aug 08 '19 at 15:36

score 10 · Answer 4 · answered Oct 20 '16 at 21:15

We had a similar/related "redis-server.exe" service hosting issue.

After installing the Redis Windows Service, we could access the service on port 6379 locally, but not from a remote client (even though the firewall was configured to allow inbound traffic on the port).

In order to resolve the issue, we had to edit the redis.windows-service.conf configuration file and change the following:

bind 127.0.0.1 needed use the actual IP address
protected-mode yes needed to be set to "no"

After making the above changes, we restarted the Redis service and were able to connect from all clients.

This solved my problem. This probably is the answer if: everything (including firewall, server, etc) is configure properly, and accessible from same host, but not from other host. — Zeeshan, Dec 31 '19 at 06:30

score 8 · Answer 5 · answered Jun 22 '21 at 04:12

Its simple and works for me nice: -open redis-cli (default in C:\Program Files\Redis) and run this command:

shutdown

Finished.

now open cmd and try redis-server again.

I know its a little late for answering but because maybe others faced this problem later I answered it.

score 3 · Answer 6 · answered Mar 26 '16 at 21:04

3

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.

answered Mar 26 '16 at 21:04

satya_fury

51
3

score 2 · Answer 7 · answered Oct 19 '17 at 05:15

check the port(if something else is using redis port)
use redis-server xxx.conf to run a server with your configuration
try to use redis-cli
check redis issues(https://github.com/ServiceStack/redis-windows/wiki/Issues-might-happen)

C:\redis>redis-server.exe --service-install [8124] 03 Feb 23:58:14.573 # HandleServiceCommands: system error caught. error c ode=1073, message = CreateService failed: unknown error

C:\redis>redis-server --service-install redis.windows.conf --loglevel verbose [10848] 04 Feb 00:00:40.508 # HandleServiceCommands: system error caught. error code=1073, message = CreateService failed: unknown error

C:\redis>redis-server --service-install -–service-name redisService1 –port 100 01 Failed to open the .conf file: 10001 CWD=C:\redis

C:\redis>redis-server --service-install redis.windows.conf -–service-name redis Service1 –port 10001 Failed to open the .conf file: 10001 CWD=C:\redis

C:\redis>redis-server --service-install redis.windows.conf -–service-name redis Service1 –port 10001 Failed to open the .conf file: 10001 CWD=C:\redis

C:\redis>redis-server --service-install C:\redis\redis.windows.conf -–service-n ame redisService1 –port 10001 Failed to open the .conf file: 10001 CWD=C:\redis

C:\redis>redis-server --service-install C:\redis\redis.windows.conf -–service-n ame redisService1 –port 10001 Failed to open the .conf file: 10001 CWD=C:\redis

C:\redis>redis-server --service-install redis.windows.conf -–service-name redis Service1 –port 10001 Failed to open the .conf file: 10001 CWD=C:\redis

C:\redis> C:\redis>redis-server --service-install redis.windows.conf -–service-name redis Service1 –port 10001 Failed to open the .conf file: 10001 CWD=C:\redis

C:\redis>redis-server --service-install redis.windows.conf --loglevel verbose [11572] 04 Feb 00:03:34.847 # HandleServiceCommands: system error caught. error code=1073, message = CreateService failed: unknown error

C:\redis>redis-server --service-install redis.windows.conf --loglevel verbose -- service-name redisService [7484] 04 Feb 00:03:53.610 # Granting read/write access to 'NT AUTHORITY\Network Service' on: "C:\redis" "C:\redis" [7484] 04 Feb 00:03:53.612 # Redis successfully installed as a service.

score -1 · Answer 8 · answered Oct 16 '15 at 07:50

-1

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.

answered Oct 16 '15 at 07:50

Alex G

1

score -1 · Answer 9 · answered Feb 01 '16 at 12:34

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.

score -1 · Answer 10 · answered Apr 10 '17 at 09:29

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

score -1 · Answer 11 · answered Jun 05 '21 at 12:53

-1

For windows after installing using windows installer. So Check if your Redis server is already up and running. check by going to redis-cli

redis-cli 127.0.0.1:6379>

answered Jun 05 '21 at 12:53

Pratik Desai

1
1
1

Can't bind TCP listener *:6379 using Redis on Windows

11 Answers11

Linked