Reedis Resolve startup Flashback under Windows

The first boot error for Redis under Windows installation is:

[2368] APR 02:57:05.611 # Creating Server TCP listening socket 127.0.0.1:6379:bind:no error

Workaround: Run on the command line

CD D:\redis

Redis-cli.exe

127.0.0.1:6379>shutdown

Not Connected>exit

Then rerun Redis-server.exe redis.windows.conf, start successfully!

Start Redis

Open the Command window directly in the directory, run:

1. Redis-server Redis. Windows. conf

The result is tragic, hint: QForkMasterInit: system error caught. error code=0x000005af, message=VirtualAllocEx failed.: unknown error . The reason is the memory allocation problem (if your computer is tough enough, it may not be a problem). There are two workarounds, first: Use the --maxmemory command to limit Redis memory when booting:

1. Redis-server Redis. Windows. Conf --maxmemory 200m

The second method is to modify the configuration file redis.windows.conf :

1. MaxMemory 209715200

Note that the units are bytes, and the following changes are completed:

Then redis-server redis.windows.conf you can start the operation again:

But the problem again, close the cmd window will turn off Redis, is the server always open? This is obviously unscientific, see below how to deploy on the server.

Deploying Redis

In fact, Redis can be installed as a Windows service, boot from boot, the command is as follows:

1. Redis-Server -service-install Redis. Windows. conf

Once installed, you can see that Redis is already a Windows service:

However, after installation, Redis does not start, and the Start command is as follows:

1. Redis-Server -service-start

Stop command:

1. Redis-Server -service-stop

Reedis Resolve startup Flashback under Windows