-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Submitting an Issue
NOTE: this is a copy of MSOpenTech/redis/wiki/Submitting an Issue page with all URLs pointing to this repo (this page is mentioned in crash bug report shown by Redis and should be read before submitting an issue).
From http://redis.io/topics/problems:
We have a long history of users experiencing crashes with Redis that actually turned out to be servers with broken RAM. Please test your RAM using redis-server --test-memory in case Redis is not stable in your system. Redis built-in memory test is fast and reasonably reliable, but if you can you should reboot your server and use memtest86.
Starting with the 2.8.21 release the built-in memory test is also available on Redis on Windows:
redis-server.exe --test-memory <megabytes>
If the issue you are reporting is a crash, please take the time to run the Redis memory test first or even better the Windows Memory Diagnostic tool.
Another common source of crashes on Windows is an inadequate size of the system paging file. If the system paging file size limit is reached during a fork operation, Redis will crash even if there is plenty of physical RAM available. To make sure the system paging file size is large enough please follow the Memory Configuration guidelines.
Starting with the 2.8.21 release, Redis on Windows produces a BUG REPORT when Redis crashes:
=== REDIS BUG REPORT START: Cut & paste starting from here ===
[6840] 23 Jun 23:58:33.208 # --- EXCEPTION_ACCESS_VIOLATION
[6840] 23 Jun 23:58:33.209 # --- STACK TRACE
.....
redis-server.exe!debugCommand(c:\redis\src\debug.c:261)(0xF73F22F0, 0xBF55D2AF, 0xF73800F0, 0x4007038C)
redis-server.exe!call(c:\redis\src\redis.c:2016)(0x5589D689, 0x40087DD0, 0x00000001, 0x00000006)
redis-server.exe!processCommand(c:\redis\src\redis.c:2235)(0xF73F22F0, 0x00000006, 0x0000001D, 0x00000001)
redis-server.exe!processInputBuffer(c:\redis\src\networking.c:1278)(0xF73F22F0, 0x00000000, 0x0000001D, 0x00000000)
redis-server.exe!readQueryFromClient(c:\redis\src\networking.c:1333)(0xF73000D0, 0x00000001, 0xF73D6F00, 0x00000001)
redis-server.exe!aeMain(c:\redis\src\ae.c:487)(0x5589D67F, 0xF7386968, 0x00000002, 0x002CD190)
redis-server.exe!redis_main(c:\redis\src\redis.c:3544)(0x00000000, 0x00000000, 0x5589D67F, 0x00000000)
redis-server.exe!main(c:\redis\src\win32_interop\win32_qfork.cpp:1383)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
.....
[6840] 23 Jun 23:58:33.241 # --- INFO OUTPUT
# Server
redis_version:2.8.21
redis_git_dirty:0
redis_build_id:e84b20ff4e0813fa
redis_mode:standalone
os:Windows
arch_bits:64
multiplexing_api:winsock_IOCP
process_id:6840
run_id:83c78034115fe370d363ac730d2d55129c9a263b
tcp_port:6379
uptime_in_seconds:10
uptime_in_days:0
.....
[6840] 23 Jun 23:58:33.250 #
=== REDIS BUG REPORT END. Make sure to include from START to END. ===
When reporting a bug that caused Redis to crash, please make sure to include the full BUG REPORT from START to END. In some cases the BUG REPORT includes only the STACK TRACE section but not the INFO OUTPUT.
Report the crash by opening an issue at http://github.com/tporadowski/redis/issues
If you are experiencing redis-server crashes and the log isn't reporting the Stack Trace information, please enable the Windows crash mini dump report as explained in the following wiki page: Mini Dump Configuration Instructions
When submitting an issue that doesn't have a BUG REPORT, please include the following information:
- Redis version number.
- Redis server configuration: # of slaves, # of sentinels.
- Redis configuration files for master, slaves, sentinels.
- Windows version.
If possible describe the steps to reproduce the issue (a script or code that can automate the steps would be ideal).
Report the issue at http://github.com/tporadowski/redis/issues