Starting Redis on Windows failing -
i'm trying start redis on windows 10. when run redis-server.exe following message though:
c:\program files\redis>redis-server.exe [4680] 01 jun 19:57:30.844 # windows version of redis allocates memory mapped heap sharing forked process used persistence operations. in order share memory, windows allocates system paging file portion equal size of redis heap. @ time there insufficient contiguous free space available in system paging file operation (windows error 0x5af). work around may either increase size of system paging file, or decrease size of redis heap --maxheap flag. reboot defragment system paging file sufficiently operation complete successfully. please see documentation included binary distributions more details on --maxheap flag. redis can not continue. exiting. i've tried adding --maxheap value, causes application crash , print out crash dump:
c:\program files\redis>redis-server.exe --maxheap 150 [6728] 01 jun 19:57:41.063 # === redis bug report start: cut & paste starting here === [6728] 01 jun 19:57:41.063 # redis version: 2.8.2400 [6728] 01 jun 19:57:41.063 # out of memory allocating 16 bytes. [6728] 01 jun 19:57:41.094 # --- abort [6728] 01 jun 19:57:41.094 # --- stack trace redis-server.exe!logstacktrace(c:\release\redis\src\win32_interop\win32_stacktrace.cpp:95)(0x00000016, 0x00001c1d, 0x00000000, 0x00000001) redis-server.exe!aborthandler(c:\release\redis\src\win32_interop\win32_stacktrace.cpp:207)(0x00000001, 0xa222916f, 0x00000000, 0xda31c9a7) redis-server.exe!raise(f:\dd\vctools\crt\crtw32\misc\winsig.c:587)(0x00000001, 0x00000000, 0x00000010, 0x00000018) redis-server.exe!abort(f:\dd\vctools\crt\crtw32\misc\abort.c:82)(0xffe97bc0, 0x40141940, 0x00000010, 0x00000000) redis-server.exe!redisoutofmemoryhandler(c:\release\redis\src\redis.c:3404)(0x00000000, 0x4013fc28, 0x00001c1d, 0x0014fb80) redis-server.exe!createsharedobjects(c:\release\redis\src\redis.c:1326)(0x4013bd44, 0x00000000, 0x00000001, 0x00000001) redis-server.exe!initserver(c:\release\redis\src\redis.c:1733)(0x4013bd44, 0x4013bd44, 0x00000000, 0x4013bd44) redis-server.exe!redis_main(c:\release\redis\src\redis.c:3504)(0x00490470, 0x00000000, 0x574f3e35, 0x00000000) redis-server.exe!main(c:\release\redis\src\win32_interop\win32_qfork.cpp:1338)(0x00000000, 0x00000000, 0x00000000, 0x0034f000) redis-server.exe!__tmaincrtstartup(f:\dd\vctools\crt\crtw32\startup\crt0.c:255)(0x00000000, 0x400344cc, 0x00000000, 0x00000000) kernel32.dll!basethreadinitthunk(f:\dd\vctools\crt\crtw32\startup\crt0.c:255)(0xd9e580e0, 0x00000000, 0x00000000, 0x00000000) ntdll.dll!rtluserthreadstart(f:\dd\vctools\crt\crtw32\startup\crt0.c:255)(0x00000000, 0x00000000, 0x00000000, 0x00000000) ntdll.dll!rtluserthreadstart(f:\dd\vctools\crt\crtw32\startup\crt0.c:255)(0x00000000, 0x00000000, 0x00000000, 0x00000000) [6728] 01 jun 19:57:41.172 # === redis bug report end. make sure include start end. === please report bug following instructions at: http://github.com/msopentech/redis/wiki/submitting-an-issue suspect ram error? use redis-server --test-memory verify it. i've tried running rest memory option suggested @ end of crash dump, gives me same error running executable did without it:
c:\program files\redis>redis-server.exe --test-memory [756] 01 jun 19:58:34.376 # windows version of redis allocates memory mapped heap sharing forked process used persistence operations. in order share memory, windows allocates system paging file portion equal size of redis heap. @ time there insufficient contiguous free space available in system paging file operation (windows error 0x5af). work around may either increase size of system paging file, or decrease size of redis heap --maxheap flag. reboot defragment system paging file sufficiently operation complete successfully. please see documentation included binary distributions more details on --maxheap flag. redis can not continue. exiting. i have 14gb of memory, i'm finding hard believe it's memory issue.
found answer after wee bit of google-ing: https://gist.github.com/anthavio/38d0ba4c916ab1911a47
instead of using --maxheap option, seems nothing add value config:
maxheap 1000000000 