zkteco-home/redis-windows

Native port of Redis for Windows,it can be installed as service.

redis-windows's Issues

SocketException

Thank you about sentinel, but I have another issue:
When I try to connect to Redis, SocketException is thrown. Redis service is stopped.
redis.windows-service.conf

port 6379

loglevel notice
logfile "Logs/redis_log.txt"

slave-serve-stale-data yes
slave-read-only yes

repl-diskless-sync no
repl-diskless-sync-delay 5
repl-disable-tcp-nodelay no

maxmemory 256mb
appendonly no
maxmemory-policy allkeys-lru

Application error in Event Viewer

Faulting application name: redis-server.exe, version: 7.0.0.0, time stamp: 0x621adc90
Faulting module name: redis-server.exe, version: 7.0.0.0, time stamp: 0x621adc90
Exception code: 0xc0000005
Fault offset: 0x000000000007b578
Faulting process id: 0x5040
Faulting application start time: 0x01d82c9f89ec08e7
Faulting application path: C:\Redis\redis-server.exe
Faulting module path: C:\Redis\redis-server.exe
Report Id: 6818c6c1-176e-40da-aa21-22a02f4c6484
Faulting package full name: 
Faulting package-relative application ID: 

Fault bucket 2092848452791133116, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: redis-server.exe
P2: 7.0.0.0
P3: 621adc90
P4: redis-server.exe
P5: 7.0.0.0
P6: 621adc90
P7: c0000005
P8: 000000000007b578
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER728B.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7328.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7338.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER733A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER736A.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_redis-server.exe_c749f1588964366085baee65654c61d83964911_d8653adc_dd74f9f3-c5b9-4110-a534-34aef3f71470

Analysis symbol: 
Rechecking for solution: 0
Report Id: 6818c6c1-176e-40da-aa21-22a02f4c6484
Report Status: 268435456
Hashed bucket: eb7f41269b79617fcd0b4a94555763bc

My code uses StackExchange.Redis
var connection =ConnectionMultiplexer.Connect("localhost");
Thank you in advance.

REDIS BUG REPORT

Version 7.0.4 latest release

=== REDIS BUG REPORT START: Cut & paste starting from here ===
[004916] 09 Aug 17:57:40.322 # --- EXCEPTION_ACCESS_VIOLATION
[004916] 09 Aug 17:57:40.322 # --- STACK TRACE
redis-server.exe!((null):0)(0x1401E2B40, 0x00E7FF60, 0x00E7E9A0, 0x00E7E9A0)
redis-server.exe!((null):0)(0x00E7E9A0, 0x00E7FF01, 0x1401197F0, 0x140123990)
KERNELBASE.dll!UnhandledExceptionFilter((null):0)(0x00E7EFC0, 0x7FFEB6BF3090, 0x00000000, 0x00000000)
ntdll.dll!memset((null):0)(0x00000000, 0x7FFEB6AB3100, 0x00E7F630, 0x00E7EF68)
ntdll.dll!_C_specific_handler((null):0)(0x00000000, 0x00E7EF50, 0x00000000, 0x140000000)
ntdll.dll!_chkstk((null):0)(0x00E7EF50, 0x00000000, 0x7FFEB3D8BC3C, 0x7FFEB3CE0000)
ntdll.dll!RtlWalkFrameChain((null):0)(0x00E7F1E0, 0x00000008, 0x7FE11C004980, 0x1400C1C92)
ntdll.dll!KiUserExceptionDispatcher((null):0)(0x14002CBE1, 0x00000000, 0x140093856, 0x0217AC00)
ntdll.dll!KiUserExceptionDispatcher((null):0)(0x00000000, 0x140093856, 0x0217AC00, 0x00000002)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x7FE10B8002A0, 0x00000000, 0x00000000, 0x00000000)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00000000, 0x440000001B, 0x00000002, 0x00000002)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00001334, 0x1401DC600, 0x00000000, 0x7FE109400EA0)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x0217AC00, 0x0217AC00, 0x0217AC00, 0x00000002)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00623A40, 0x00623A40, 0x00623A40, 0x0217AC00)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
KERNEL32.DLL!BaseThreadInitThunk((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
ntdll.dll!RtlUserThreadStart((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
ntdll.dll!RtlUserThreadStart((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
[004916] 09 Aug 17:57:40.322 # 
=== REDIS BUG REPORT END. Make sure to include from START to END. ===

       Please report this bug by following the instructions at:

     https://github.com/zkteco-home/redis-windows/wiki/Submitting-an-Issue

    Suspect RAM error? Use redis-server --test-memory to verify it.

Could you please investigate it?

listen: Unknown error

[030812] 04 Aug 18:00:47.789 # RedisWin is starting ......
[030812] 04 Aug 18:00:47.789 # RedisWin version=7.0.4, bits=64, commit=07/20/2022, modified=0, pid=30812, just started
[030812] 04 Aug 18:00:47.790 # Configuration loaded
[030812] 04 Aug 18:00:47.793 * monotonic clock: POSIX clock_gettime
[030812] 04 Aug 18:00:47.795 # Warning: Could not create server TCP listening socket ::1:6379: listen: Unknown error
[030812] 04 Aug 18:00:47.795 # Failed listening on port 6379 (TCP), aborting.

System is Win10 X64，Help please, Thanks~~~

redis-server v7.011 fails almost once a day

[002744] 03 Jul 20:30:19.530 * 10000 changes in 60 seconds. Saving...
[002744] 03 Jul 20:30:19.561 * Background saving started by pid 8652

=== REDIS BUG REPORT START: Cut & paste starting from here ===
[008652] 03 Jul 20:30:19.881 # --- EXCEPTION_ACCESS_VIOLATION
[008652] 03 Jul 20:30:19.881 # --- STACK TRACE
redis-server.exe!((null):0)(0x1401F17C0, 0x0014FF60, 0x000CD2A0, 0x000CD2A0)
redis-server.exe!((null):0)(0x000CD2A0, 0x0014FF01, 0x140122230, 0x7FFDEB5236D1)
KERNELBASE.dll!UnhandledExceptionFilter((null):0)(0x00000000, 0x7FFDEB662FF8, 0x00000000, 0x00000000)
ntdll.dll!memset((null):0)(0x00000000, 0x00000000, 0x000CDF30, 0x000CD868)
ntdll.dll!_C_specific_handler((null):0)(0x00000000, 0x000CD850, 0x00000000, 0x140000000)
ntdll.dll!_chkstk((null):0)(0x000CD850, 0x00000000, 0x7FFDE88EBC30, 0x7FFDE8840000)
ntdll.dll!RtlWalkFrameChain((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
ntdll.dll!KiUserExceptionDispatcher((null):0)(0x2322F1C0, 0x00000000, 0x7FA52AFFFF4F, 0x7FA50F8060D7)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x048019E0, 0x048019E0, 0x0014ED70, 0x0014E9D0)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x048019E0, 0x7FA529800000, 0x0014ED70, 0x0014ED70)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x7FA500000000, 0x00000001, 0x7FA507400690, 0x00000467)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x0014ED70, 0x00000015, 0x00000400, 0x0014ED70)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x7FA503C216F1, 0x05C00000, 0x000004C1, 0x05C00000)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00510650, 0x00000000, 0x00000000, 0x00000004)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00000000, 0x00000000, 0x1401DE600, 0x000021CC)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00000000, 0x00170000, 0x0C000509, 0x00000204)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00000254, 0x00000006, 0x00000254, 0x2AAAAAAAAAAAAAAB)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00000000, 0x140128055, 0x004F5170, 0x00000000)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
KERNEL32.DLL!BaseThreadInitThunk((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
ntdll.dll!RtlUserThreadStart((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
ntdll.dll!RtlUserThreadStart((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
[008652] 03 Jul 20:30:19.881 #
=== REDIS BUG REPORT END. Make sure to include from START to END. ===

   Please report this bug by following the instructions at:

 https://github.com/zkteco-home/redis-windows/wiki/Submitting-an-Issue

Suspect RAM error? Use redis-server --test-memory to verify it.

[002744] 03 Jul 20:30:21.886 # fork operation failed
[002744] 03 Jul 20:30:21.917 # Background saving terminated by signal 1
[002744] 03 Jul 20:30:25.057 * 10000 changes in 60 seconds. Saving...
[002744] 03 Jul 20:30:25.057 * Background saving started by pid 2904
[002744] 03 Jul 20:30:25.405 # fork operation complete

crash on win11

=== REDIS BUG REPORT START: Cut & paste starting from here ===
[033472] 30 Mar 00:30:46.183 # --- EXCEPTION_ACCESS_VIOLATION
[033472] 30 Mar 00:30:46.198 # --- STACK TRACE
redis-server.exe!((null):0)(0x1401EFA20, 0x0014FF60, 0x00000001, 0x0014DF00)
redis-server.exe!((null):0)(0x0014DF00, 0x00000001, 0x00000000, 0x00010040)
KERNELBASE.dll!UnhandledExceptionFilter((null):0)(0x0005AA19, 0x7FF80A1D1688, 0x00000000, 0x7FF80A090B4A)
ntdll.dll!RtlMoveMemory((null):0)(0x0014DFD0, 0x00000000, 0x0014DF88, 0x0014E570)
ntdll.dll!_C_specific_handler((null):0)(0x00000000, 0x0014E4D0, 0x0014EBB0, 0x0014EBB0)
ntdll.dll!_chkstk((null):0)(0x0014EBB0, 0x7FF80A070000, 0x7FF80A0CA9F8, 0x7FF80A1FCBF8)
ntdll.dll!RtlFindCharInUnicodeString((null):0)(0x05400008, 0x1400E0723, 0x7FCE80C000C0, 0x7FCE91C02131)
ntdll.dll!KiUserExceptionDispatcher((null):0)(0x140074C4B, 0x7FCE80C000C0, 0x32C91DF3852E245, 0x00000081)
ntdll.dll!KiUserExceptionDispatcher((null):0)(0x7FCE80C000C0, 0x32C91DF3852E245, 0x00000081, 0x7FCE79C011F1)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00000000, 0x1400C7607, 0x00000030, 0x0014F1E0)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x7FCE79C011F1, 0x07C00000, 0x00000007, 0x07C00000)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x02B5D5C0, 0x02260000, 0x00000000, 0x02B5D5C0)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x02260000, 0x03602BF0, 0x00000000, 0x000001CC)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x000001CC, 0x00000006, 0x000001CC, 0x2AAAAAAAAAAAAAAB)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00000000, 0x1401278F5, 0x005EC380, 0x00000000)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
KERNEL32.DLL!BaseThreadInitThunk((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
ntdll.dll!RtlUserThreadStart((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
ntdll.dll!RtlUserThreadStart((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
[033472] 30 Mar 00:30:46.198 #
=== REDIS BUG REPORT END. Make sure to include from START to END. ===

Needs in your little help with file versions.

Hello gentlemens,

A lot of thanks for your work and supporting the tool! I also find your product very helpful!

I just have one small request.

I have noticed that several *.exe files (listed below) have version 7.0.0.0 on the "Details" tab in the file's properties.
redis-benchmark.exe
redis-check-aof.exe
redis-check-rdb.exe
redis-cli.exe
redis-server.exe

Is it correct behaviour?

if not... would you kindly change the file versions for 7.0.7 and 7.0.8 releases to avoid misunderstandings in the future.

Unable to restore Redis Linux dump

I keep getting this error:

[016728] 04 Nov 19:07:23.894 # --- EXCEPTION_ACCESS_VIOLATION
[016728] 04 Nov 19:07:23.894 # --- STACK TRACE
redis-check-rdb.exe!((null):0)(0x1401E3C90, 0x0014FF60, 0x14011A460, 0x0014E300)
redis-check-rdb.exe!((null):0)(0x0014E300, 0x14011A401, 0x00000000, 0x7FFF91400800)
KERNELBASE.dll!UnhandledExceptionFilter((null):0)(0x0014E3B0, 0x7FFF914F7658, 0x00000000, 0x0014E348)
ntdll.dll!memset((null):0)(0x7FFF91524A24, 0x7FFF913B0000, 0x0014E3B0, 0x7FFF913E0E7B)
ntdll.dll!_C_specific_handler((null):0)(0x00000000, 0x0014E8B0, 0x0014EF70, 0x00000000)
ntdll.dll!_chkstk((null):0)(0x00000000, 0x0014E8B0, 0x0014EF70, 0x00000000)
ntdll.dll!RtlRaiseException((null):0)(0xE2A3B133BDD5, 0x14013FC84, 0x00000000, 0x02FEEA90)
ntdll.dll!KiUserExceptionDispatcher((null):0)(0x00000000, 0x00000000, 0x7FA52880007A, 0x14008646A)
redis-check-rdb.exe!KiUserExceptionDispatcher((null):0)(0x3330333839353331, 0x400003332, 0xD000000002, 0x00000000)
redis-check-rdb.exe!KiUserExceptionDispatcher((null):0)(0x7FA52880007A, 0x7FA522C2BF91, 0x0014F2F0, 0x14012F0C4)
redis-check-rdb.exe!KiUserExceptionDispatcher((null):0)(0x7FA52880007A, 0x00000000, 0x7FA528800070, 0x510D5D33)
redis-check-rdb.exe!KiUserExceptionDispatcher((null):0)(0x0000000C, 0x00000063, 0x0014F420, 0x7FA528800070)
redis-check-rdb.exe!KiUserExceptionDispatcher((null):0)(0x0000000C, 0x7FA528800070, 0x0014F420, 0x140276AF0)
redis-check-rdb.exe!KiUserExceptionDispatcher((null):0)(0x0000000C, 0x00000000, 0x00000008, 0x140276AF0)
redis-check-rdb.exe!KiUserExceptionDispatcher((null):0)(0x1401D2D18, 0x005B9115, 0x636538BB, 0x140123DF5)
redis-check-rdb.exe!KiUserExceptionDispatcher((null):0)(0x00000002, 0x005B90F8, 0x00000000, 0x1D8F06786A8ABDE)
redis-check-rdb.exe!KiUserExceptionDispatcher((null):0)(0x00000002, 0x00000002, 0x00000002, 0x005D0010)
redis-check-rdb.exe!KiUserExceptionDispatcher((null):0)(0x00000000, 0x00000000, 0x005B90E0, 0x00000000)
redis-check-rdb.exe!KiUserExceptionDispatcher((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
KERNEL32.DLL!BaseThreadInitThunk((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
ntdll.dll!RtlUserThreadStart((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
ntdll.dll!RtlUserThreadStart((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
[016728] 04 Nov 19:07:23.895 #

I tried starting redis-check-rdb.exe and it says the same.

There's no data show on redis desktop manager, but data is exist

this issue on 7.0.10

migrating the dump.rdb file

When I migrate the dump.rdb file generated by the unofficial, alpha repo at https://github.com/tporadowski/redis/releases to your project, the windows service automatically stops and fails to load. Is there a solution?

Memory leaks occurs after running for a long time

Although the total amount of mem used by the redis-db has not increased, but the memory usage of the entire Redis process has multiplied by several times. Could anyone explain why this happens?

Range index is wrong.

redis_version:6.2.6
According to https://redis.io/commands/zrange,
Command: zrange XXX 0 -1 should return all members in that zSet, but it currently return only 1 member.
I tried the cli and Lettuce(java), both interfaces have this problem.

Logs do not work

Logs do not work:

port 6379

loglevel debug 
logfile "Logs/redis_log.txt"

In 6.2.6.4 logs work as expected.

Thank you for your wonderful work

Thank you for your wonderful work, hope you will continue this great project. could you please update on 7.0.12

Loading a module is not working

When trying to load any .dll module (e.g: https://github.com/tporadowski/rejson) redis-server is crashing.

Setup

• Windows 10 Entreprise
• Version 20H2

Errors

Loading from redis.conf

[014332] 20 Apr 09:36:08.936 # RedisWin is starting ......
[014332] 20 Apr 09:36:08.936 # RedisWin version=7.0.0, bits=64, commit=03/27/2022, modified=0, pid=14332, just started
[014332] 20 Apr 09:36:08.936 # Configuration loaded
[014332] 20 Apr 09:36:08.938 * monotonic clock: POSIX clock_gettime
                _._
           _.-``__ ''-._
      _.-``    `.  `_.  ''-._           RedisWin 7.0.0 (03/27/2022/0) 64 bit
  .-`` .-```.  ```\/    _.,_ ''-._
 (    '      ,       .-`  | `,    )     Running in standalone mode
 |`-._`-...-` __...-.``-._|'` _.-'|     Port: 6379
 |    `-._   `._    /     _.-'    |     PID: 14332
  `-._    `-._  `-./  _.-'    _.-'
 |`-._`-._    `-.__.-'    _.-'_.-'|
 |    `-._`-._        _.-'_.-'    |
  `-._    `-._`-.__.-'_.-'    _.-'
 |`-._`-._    `-.__.-'    _.-'_.-'|
 |    `-._`-._        _.-'_.-'    |
  `-._    `-._`-.__.-'_.-'    _.-'
      `-._    `-.__.-'    _.-'
          `-._        _.-'
              `-.__.-'

[014332] 20 Apr 09:36:08.943 # Server initialized


=== REDIS BUG REPORT START: Cut & paste starting from here ===
[014332] 20 Apr 09:36:08.950 # --- EXCEPTION_ACCESS_VIOLATION
[014332] 20 Apr 09:36:08.950 # --- STACK TRACE
redis-server.exe!((null):0)(0x1401E2EA0, 0x0014FF60, 0x140118E30, 0x0014EA40)
redis-server.exe!((null):0)(0x0014EA40, 0x140118E01, 0x00000000, 0x00000000)
KERNELBASE.dll!UnhandledExceptionFilter((null):0)(0x0014EAF0, 0x7FF9F551662C, 0x00000000, 0x0014EA88)
ntdll.dll!memset((null):0)(0x7FF9F5542A24, 0x7FF9F53D0000, 0x0014EAF0, 0x7FF9F5400E7B)
ntdll.dll!_C_specific_handler((null):0)(0x00000000, 0x0014EFF0, 0x0014F6B0, 0x00000000)
ntdll.dll!_chkstk((null):0)(0x00000000, 0x0014EFF0, 0x0014F6B0, 0x00000000)
ntdll.dll!RtlRaiseException((null):0)(0x00000006, 0x00000006, 0x00000001, 0x7FF9F2D10312)
ntdll.dll!KiUserExceptionDispatcher((null):0)(0x7FF9DD7FE32B, 0x7FA589800600, 0x1400BC68E, 0x140254BD0)
ntdll.dll!KiUserExceptionDispatcher((null):0)(0x7FA589800600, 0x1400BC68E, 0x140254BD0, 0x00000000)
ntdll.dll!KiUserExceptionDispatcher((null):0)(0x1400BC68E, 0x140254BD0, 0x00000000, 0x00000000)
ntdll.dll!KiUserExceptionDispatcher((null):0)(0x140254BD0, 0x00000000, 0x00000000, 0x7FF9DD7FEB7C)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00000000, 0x00000008, 0x00000000, 0x00000000)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00000008, 0x00000000, 0x00000000, 0x00000040)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00000008, 0x00000000, 0x00000000, 0x00000040)
[014332] 20 Apr 09:36:08.952 #
=== REDIS BUG REPORT END. Make sure to include from START to END. ===

       Please report this bug by following the instructions at:

     https://github.com/zkteco-home/redis-windows/wiki/Submitting-an-Issue

    Suspect RAM error? Use redis-server --test-memory to verify it.

Loading from the CLI console

127.0.0.1:6379> MODULE LOAD C:\Users\tixwell\Desktop\redis-windows-master\ReJSON.dll
(error) ERR MODULE command not allowed. If the enable-module-command option is set to "local", you can run it from a local connection, otherwise you need to set this option in the configuration file, and then restart the server.

crash on lua , redis7

Question: RedisTimeSeries

I have been evaluating the Windows Redis and so far so good.

Thank you for sharing what must have been a technically challenging undertaking.

A quick question if I may, would it be possible to use the timeseries module on Windows:
https://github.com/RedisTimeSeries/RedisTimeSeries

Keep up the good work! And thank you too.

Redis crashes after a while

Redis crashes after a while. It is random. I cannot see a regular time schema.
After that problem, there will be a lot of from this error message: Error registering fd event for the new client: No error

ReJSON compatibility

OS: Windows 11
ReJSON: 2.2 compiled by cargo/rust successfully
redis-windows 7.0.5 (6.2.6 same problem)

Currently there is no way to run redis windows with ReJSON module. It immediately quits every time, but without ReJSON everything works fine.

// links

https://github.com/RedisJSON/RedisJSON/tree/2.2

The redis service stops without error

The problem still exists I have used the default config which is in your zip file and I have run the install script as administrator no changes made

Release notes documentation

Hello.
Thank you for your work.
Please add release note to Redis 7.0.5.
Is there fixed CRITICAL CVE-2022-35951 vulnerability?

Redis is an in-memory database that persists on disk. Versions 7.0.0 and above, prior to 7.0.5 are vulnerable to an Integer Overflow. Executing an `XAUTOCLAIM` command on a stream key in a specific state, with a specially crafted `COUNT` argument may cause an integer overflow, a subsequent heap overflow, and potentially lead to remote code execution. This has been patched in Redis version 7.0.5. No known workarounds exist.

Which license agreement shall we accept to use your product?
Could you please clarify your license agreement additionally instead of README?
Thank you in advance.

Scan is malfunction.

Hello, I have another issue.
I tried both scan and sscan, and they return some duplicated items which could not be right. The options seems don't work too. I'm not sure of hscan and zscan.

great work!

Does it support TLS？

redis-windows bug-report

helllo ,i used redis-7.0.11-windows ,it often crashed , The frequency of persistent hard drives is a little high,

save 300 1
save 100 10
save 60 100

redislog:

=== REDIS BUG REPORT START: Cut & paste starting from here ===
[001008] 31 May 02:24:32.224 # --- ABORT
[001008] 31 May 02:24:32.224 # --- STACK TRACE
redis-server.exe!((null):0)(0x00000016, 0x7FCE1E800E00, 0x140122550, 0x14025B550)
redis-server.exe!((null):0)(0x14025B550, 0x140141DA7, 0x0013E888, 0x0013E870)
redis-server.exe!((null):0)(0x0013E801, 0x00000000, 0x00000000, 0x00000C02)
redis-server.exe!((null):0)(0x001300A0, 0x140214160, 0x00000C02, 0x00000051)
redis-server.exe!((null):0)(0x00000C05, 0x00000C05, 0x0013EDA0, 0x0013ECA0)
redis-server.exe!((null):0)(0x00000C05, 0x0013EDA0, 0x0013EDA0, 0x11800000)
redis-server.exe!((null):0)(0x00000C05, 0x7FCE1E800E00, 0x0013EDA0, 0x0013EDA0)
redis-server.exe!((null):0)(0x001C7440, 0x140153FE2, 0x00000000, 0x7FCE079674C0)
redis-server.exe!((null):0)(0x0013EDA0, 0x00000010, 0x7FCE07E4B404, 0x0013EDA0)
redis-server.exe!((null):0)(0x7FCE07E4B3D1, 0x05400000, 0x00000322, 0x05400000)
redis-server.exe!((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
redis-server.exe!((null):0)(0x001C7440, 0x00000000, 0x00000000, 0x00000004)
redis-server.exe!((null):0)(0x00160CC0, 0x00000000, 0x1401DE600, 0x000003F0)
redis-server.exe!((null):0)(0xFFFFFFFFFFFFFFFF, 0x11000514, 0x00000000, 0x0000011C)
redis-server.exe!((null):0)(0x00000154, 0x00000006, 0x00000154, 0x2AAAAAAAAAAAAAAB)
redis-server.exe!((null):0)(0x140128000, 0x140128055, 0x001C79A0, 0x7FF5FFFFE000)
redis-server.exe!((null):0)(0x14012804C, 0x7FF5FFFFE000, 0x00000000, 0x00000000)
KERNEL32.DLL!BaseThreadInitThunk((null):0)(0x7FFF188813F0, 0x00000000, 0x00000000, 0x00000000)
ntdll.dll!RtlUserThreadStart((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
ntdll.dll!RtlUserThreadStart((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
[001008] 31 May 02:24:32.224 #
=== REDIS BUG REPORT END. Make sure to include from START to END. ===

RediSearch

Hi,

first of all: many thanks for your work!!!! I'm always looking for an updated REDIS-server version for Windows.

One short question: do you expect to bring also the RediSearch module for Windows? If so, is there any timeline?

Thanks
Best

Log File breaks Service

If the configuration entry in the conf file has the word "Redis" in it for "logfile" (for instance, I used both logfile C:/Logs/redis.txt and logfile C:/Logs/Redis/logs.txt), then the command redis-server --service-start will fail with the message: "Redis service failed to start." and nothing logged to the log file (obviously) or event viewer related to the error. However, by changing the entry to logfile C:/Logs/red_is.txt, the service starts without issue.

Enable RediSearch?

Is there a way to enable the RediSearch module?

Pubsub messages are unordered

Pubsub messages are unordered even though they are sent sequentially on the subscriber side they came in a mixed order. The same does not happen with Redis on docker.

"install_redis.cmd" does fail when path has blanks

When starting "install_redis.cmd" from e.g.

"C:\Program Files\redis"

The service installs but fails to start.

I did not investigate further, but instead put redis into a path without blanks, e.g.

"C:\redis"

crash with cluster mode errorcode c0000005

node config like this
port from 6380-6385

It takes more than 2 seconds when I connect using php_redis

I don't expect to be able to fix this, if you have any insight please let me know

Does the REJSON module be supported?

https://github.com/RedisJSON/RedisJSON

EXCEPTION_ACCESS_VIOLATION

=== REDIS BUG REPORT START: Cut & paste starting from here ===
[016564] 27 Apr 16:13:39.714 # --- EXCEPTION_ACCESS_VIOLATION
[016564] 27 Apr 16:13:39.715 # --- STACK TRACE
redis-server.exe!((null):0)(0x1401F17C0, 0x0100FF60, 0x140122230, 0x0100E880)
redis-server.exe!((null):0)(0x0100E880, 0x140122201, 0x00000000, 0x00000000)
KERNELBASE.dll!UnhandledExceptionFilter((null):0)(0x0100E930, 0x7FFD26657618, 0x00000000, 0x0100E8C8)
ntdll.dll!memset((null):0)(0x7FFD26684A24, 0x7FFD26510000, 0x0100E930, 0x7FFD26540E7B)
ntdll.dll!_C_specific_handler((null):0)(0x00000000, 0x0100EE30, 0x0100F4F0, 0x00000000)
ntdll.dll!_chkstk((null):0)(0x00000000, 0x0100EE30, 0x0100F4F0, 0x00000000)
ntdll.dll!RtlRaiseException((null):0)(0x00000030, 0x00000000, 0x7FCD72000DC0, 0x4000000000002)
ntdll.dll!KiUserExceptionDispatcher((null):0)(0x7FCD8A802D80, 0x14003CC6A, 0x1D978E88E2C1D10, 0x00000000)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x7FCD72000DC0, 0x00000000, 0x00000000, 0x00000000)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x7FCD72000DC0, 0x00000138, 0x00000000, 0x0100F8F8)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x7FCD738002A0, 0x00000138, 0x7FCD738002A0, 0x00000014)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x7FCD738002A0, 0x7FCD738002A0, 0x00000000, 0x000001A8)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00000138, 0x10000001B, 0x00000002, 0xCB1F00000000)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x000040B4, 0x1401EAEA8, 0x1401CC074, 0x7FCD71400B70)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00000000, 0x00000000, 0x00000091, 0x00000002)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x0000008F, 0x0000009F, 0x0000008F, 0x00582690)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
KERNEL32.DLL!BaseThreadInitThunk((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
ntdll.dll!RtlUserThreadStart((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
ntdll.dll!RtlUserThreadStart((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
[016564] 27 Apr 16:13:39.723 #
=== REDIS BUG REPORT END. Make sure to include from START to END. ===

Redis crashing every couple of hours: EXCEPTION_ACCESS_VIOLATION

Describe the bug/issue
The instance is crashing every couple of hours while not performing anything intensive. Restarting the service brings it back

To Reproduce
The instance is serving HGETALL throughout the day and is updated once per 24h. Crashes every couple of hours. RAM is free, pagination settings are fine, test-memory passed. No special config, max memory is set to 2G, database is ~700MB

Redis version=6.2.6
OS Name Microsoft Windows Server 2019 Standard
Version 10.0.17763 Build 17763

Crash report

=== REDIS BUG REPORT START: Cut & paste starting from here ===
Redis version: 6.2.6
[10580] 01 Feb 19:11:25.668 # --- EXCEPTION_ACCESS_VIOLATION
[10580] 01 Feb 19:11:25.668 # --- STACK TRACE
redis-server.exe!((null):0)(0x1401B77F0, 0x025AFF60, 0x025AE8A0, 0x025AE8A0)
redis-server.exe!((null):0)(0x025AE8A0, 0x025AFF01, 0x1400FCE50, 0x140109EB0)
KERNELBASE.dll!UnhandledExceptionFilter((null):0)(0x025AEEC0, 0x7FFB35242020, 0x00000000, 0x00000000)
ntdll.dll!memset((null):0)(0x00000000, 0x00000000, 0x025AF530, 0x025AEE68)
ntdll.dll!_C_specific_handler((null):0)(0x00000000, 0x025AEE50, 0x00000000, 0x140000000)
ntdll.dll!_chkstk((null):0)(0x025AEE50, 0x00000000, 0x7FFB3273CC3C, 0x7FFB32690000)
ntdll.dll!RtlWalkFrameChain((null):0)(0x00000000, 0x025AF098, 0x14020A080, 0x025AF0B0)
ntdll.dll!KiUserExceptionDispatcher((null):0)(0x00000000, 0x14010DAD1, 0x00000000, 0x029B0720)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x025AF918, 0x00000008, 0x00000000, 0x029B0730)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00000006, 0x00000000, 0x00000002, 0x7FCD00000000)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00000002, 0xFFFFFFFF0000001B, 0x00000000, 0x186A000000000)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00002954, 0x1401B1610, 0x00171080, 0x00008000)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x004B79D0, 0x004B79D0, 0x0049FD60, 0x004B79D0)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x01653CE0, 0x01653CE0, 0x01653CE0, 0x004B79D0)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
KERNEL32.DLL!BaseThreadInitThunk((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
ntdll.dll!RtlUserThreadStart((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
ntdll.dll!RtlUserThreadStart((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
[10580] 01 Feb 19:11:25.696 # --- INFO OUTPUT
# Server
redis_version:6.2.6
redis_git_sha1:00000000
redis_git_dirty:0
redis_build_id:164b73bbc4ccd2e9
redis_mode:standalone
os:Windows  
arch_bits:64
multiplexing_api:WinSock_IOCP
atomicvar_api:pthread-mutex
gcc_version:0.0.0
process_id:10580
process_supervised:no
run_id:37438219c8cf954fca2f7de9ab06679e645e98ee
tcp_port:6379
server_time_usec:1643735485663412
uptime_in_seconds:5398
uptime_in_days:0
hz:10
configured_hz:10
lru_clock:16345533
executable:C:\redis\"c:\redis\redis-server.exe"
config_file:C:\redis\redis.conf
io_threads_active:0

# Clients
connected_clients:65
cluster_connections:0
maxclients:3168
client_recent_max_input_buffer:8
client_recent_max_output_buffer:0
blocked_clients:0
tracking_clients:0
clients_in_timeout_table:0

# Memory
used_memory:747906048
used_memory_human:713.26M
used_memory_rss:747904256
used_memory_rss_human:713.26M
used_memory_peak:747906048
used_memory_peak_human:713.26M
used_memory_peak_perc:100.00%
used_memory_overhead:322993304
used_memory_startup:393568
used_memory_dataset:424912744
used_memory_dataset_perc:56.84%
allocator_allocated:748082072
allocator_active:1216348160
allocator_resident:1233125376
total_system_memory:0
total_system_memory_human:0B
used_memory_lua:37888
used_memory_lua_human:37.00K
used_memory_scripts:0
used_memory_scripts_human:0B
number_of_cached_scripts:0
maxmemory:2147483648
maxmemory_human:2.00G
maxmemory_policy:allkeys-lru
allocator_frag_ratio:1.63
allocator_frag_bytes:468266088
allocator_rss_ratio:1.01
allocator_rss_bytes:16777216
rss_overhead_ratio:0.61
rss_overhead_bytes:-485221120
mem_fragmentation_ratio:1.00
mem_fragmentation_bytes:0
mem_not_counted_for_evict:0
mem_replication_backlog:0
mem_clients_slaves:0
mem_clients_normal:1331720
mem_aof_buffer:0
mem_allocator:jemalloc-5.2.1-redis
active_defrag_running:0
lazyfree_pending_objects:0
lazyfreed_objects:0

# Persistence
loading:0
current_cow_size:0
current_cow_size_age:0
current_fork_perc:0.00
current_save_keys_processed:0
current_save_keys_total:0
rdb_changes_since_last_save:0
rdb_bgsave_in_progress:0
rdb_last_save_time:1643730087
rdb_last_bgsave_status:ok
rdb_last_bgsave_time_sec:-1
rdb_current_bgsave_time_sec:-1
rdb_last_cow_size:0
aof_enabled:0
aof_rewrite_in_progress:0
aof_rewrite_scheduled:0
aof_last_rewrite_time_sec:-1
aof_current_rewrite_time_sec:-1
aof_last_bgrewrite_status:ok
aof_last_write_status:ok
aof_last_cow_size:0
module_fork_in_progress:0
module_fork_last_cow_size:0

# Stats
total_connections_received:3351
total_commands_processed:21444
instantaneous_ops_per_sec:0
total_net_input_bytes:874114
total_net_output_bytes:14170206
instantaneous_input_kbps:0.00
instantaneous_output_kbps:0.00
rejected_connections:0
sync_full:0
sync_partial_ok:0
sync_partial_err:0
expired_keys:0
expired_stale_perc:0.00
expired_time_cap_reached_count:0
expire_cycle_cpu_milliseconds:2
evicted_keys:0
keyspace_hits:8396
keyspace_misses:1
pubsub_channels:0
pubsub_patterns:0
latest_fork_usec:0
total_forks:0
migrate_cached_sockets:0
slave_expires_tracked_keys:0
active_defrag_hits:0
active_defrag_misses:0
active_defrag_key_hits:0
active_defrag_key_misses:0
tracking_total_keys:0
tracking_total_items:0
tracking_total_prefixes:0
unexpected_error_replies:0
total_error_replies:10
dump_payload_sanitizations:0
total_reads_processed:19587
total_writes_processed:19279
io_threaded_reads_processed:0
io_threaded_writes_processed:0

# Replication
role:master
connected_slaves:0
master_failover_state:no-failover
master_replid:07e983cd39ff89fe20f736d6f05cc1bbe577b7d5
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:0
second_repl_offset:-1
repl_backlog_active:0
repl_backlog_size:1048576
repl_backlog_first_byte_offset:0
repl_backlog_histlen:0

# CPU
used_cpu_sys:2.781250
used_cpu_user:10.062500
used_cpu_sys_children:0.000000
used_cpu_user_children:0.000000

# Modules

# Commandstats
cmdstat_info:calls=3248,usec=386313,usec_per_call=118.94,rejected_calls=0,failed_calls=0
cmdstat_client:calls=3248,usec=9815,usec_per_call=3.02,rejected_calls=0,failed_calls=0
cmdstat_auth:calls=3286,usec=20952,usec_per_call=6.38,rejected_calls=0,failed_calls=0
cmdstat_role:calls=3248,usec=20114,usec_per_call=6.19,rejected_calls=0,failed_calls=0
cmdstat_hgetall:calls=8397,usec=35294,usec_per_call=4.20,rejected_calls=9,failed_calls=0
cmdstat_ping:calls=17,usec=0,usec_per_call=0.00,rejected_calls=1,failed_calls=0

# Errorstats
errorstat_LOADING:count=10

# Cluster
cluster_enabled:0

# Keyspace
db0:keys=6353978,expires=0,avg_ttl=0
[10580] 01 Feb 19:11:25.698 # 
=== REDIS BUG REPORT END. Make sure to include from START to END. ===

Event Log
Don't see anything in particular here, redis fork operation was completed successfully 2 hours before the crash.

Additional context

[10580] 01 Feb 17:41:27.161 # Redis is starting ......
[10580] 01 Feb 17:41:27.161 # Redis version=6.2.6, bits=64, commit=00000000, modified=0, pid=10580, just started
[10580] 01 Feb 17:41:27.162 # Configuration loaded
[10580] 01 Feb 17:41:27.165 * Running mode=standalone, port=6379.
[10580] 01 Feb 17:41:27.165 # Server initialized
[10580] 01 Feb 17:41:27.166 * Loading RDB produced by version 6.2.6
[10580] 01 Feb 17:41:27.166 * RDB age 7705 seconds
[10580] 01 Feb 17:41:27.166 * RDB memory usage when created 0.00 Mb
[10580] 01 Feb 17:41:33.772 # RDB file was saved with checksum disabled: no check performed.
[10580] 01 Feb 17:41:33.773 # Done loading RDB, keys loaded: 6353978, keys expired: 0.
[10580] 01 Feb 17:41:33.773 * DB loaded from disk: 6.608 seconds
[10580] 01 Feb 17:41:33.773 * Ready to accept connections

Redis cannot start with an imported source

I have an RDB source that I cannot import. The source works with a different build. Do you have any ideas on how I could import it into this build? (The source comes from a Redis 5.0.10 build for Windows and contains many stream elements in DB 1.)

PS C:\code\redis-windows> .\redis-check-rdb.exe C:\code\test.rdb
[offset 0] Checking RDB file C:\code\test.rdb
[offset 29] AUX FIELD redis-ver = '5.0.14.1'
[offset 43] AUX FIELD redis-bits = '64'
[offset 55] AUX FIELD ctime = '1688541401'
[offset 70] AUX FIELD used-mem = '564236664'
[offset 86] AUX FIELD aof-preamble = '0'
[offset 88] Selecting DB ID 0
[offset 14342796] Selecting DB ID 1


=== REDIS BUG REPORT START: Cut & paste starting from here ===
[032920] 05 Jul 11:50:28.244 # --- EXCEPTION_ACCESS_VIOLATION
[032920] 05 Jul 11:50:28.244 # --- STACK TRACE
redis-check-rdb.exe!((null):0)(0x1401F17C0, 0x0014FF60, 0x00000001, 0x0014E280)
redis-check-rdb.exe!((null):0)(0x0014E280, 0x00000001, 0x00000000, 0x00010040)
KERNELBASE.dll!UnhandledExceptionFilter((null):0)(0x0005AA89, 0x7FFEF9E716A0, 0x00000000, 0x7FFEF9D30B4A)
ntdll.dll!RtlMoveMemory((null):0)(0x0014E350, 0x00000000, 0x0014E308, 0x0014E8F0)
ntdll.dll!_C_specific_handler((null):0)(0x00000000, 0x0014E850, 0x0014EF30, 0x0014EF30)
ntdll.dll!_chkstk((null):0)(0x0014EF30, 0x7FFEF9D10000, 0x7FFEF9D6AA68, 0x7FFEF9E9CBF8)
ntdll.dll!RtlFindCharInUnicodeString((null):0)(0x00000000, 0x7FCD89000008, 0x7FCD9DC0000A, 0x7FCD89000008)
ntdll.dll!KiUserExceptionDispatcher((null):0)(0x7FCD89000220, 0x140139600, 0x00000000, 0x1400E8900)
redis-check-rdb.exe!KiUserExceptionDispatcher((null):0)(0x7FCD9DC0000A, 0x00000000, 0x7FCD9DC00000, 0x00000000)
redis-check-rdb.exe!KiUserExceptionDispatcher((null):0)(0x7FCD9DC0000A, 0x00000000, 0x7FCD00000085, 0x7FCD9DC0000D)
redis-check-rdb.exe!KiUserExceptionDispatcher((null):0)(0x7FCD9DC00000, 0x00000CC9, 0x0014F3F0, 0x00000CC9)
redis-check-rdb.exe!KiUserExceptionDispatcher((null):0)(0x0000000E, 0x7FCD00000000, 0x00000008, 0x14026B000)
redis-check-rdb.exe!KiUserExceptionDispatcher((null):0)(0x1401E0628, 0x00500672, 0x64A53CE3, 0x14012BCC5)
redis-check-rdb.exe!KiUserExceptionDispatcher((null):0)(0x00000002, 0x00500648, 0x00000000, 0x1D9AF2620B283D9)
redis-check-rdb.exe!KiUserExceptionDispatcher((null):0)(0x00000000, 0x00000000, 0x00518259, 0x00000002)
redis-check-rdb.exe!KiUserExceptionDispatcher((null):0)(0x00000000, 0x140128055, 0x00500630, 0x00000000)
redis-check-rdb.exe!KiUserExceptionDispatcher((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
KERNEL32.DLL!BaseThreadInitThunk((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
ntdll.dll!RtlUserThreadStart((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
ntdll.dll!RtlUserThreadStart((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
[032920] 05 Jul 11:50:28.251 #
=== REDIS BUG REPORT END. Make sure to include from START to END. ===

---

Memurai 4.x result

PS C:\Program Files\Memurai> .\memurai-check-rdb.exe C:\code\test.rdb
[offset 0] Checking RDB file C:\code\test.rdb
[offset 29] AUX FIELD redis-ver = '5.0.14.1'
[offset 43] AUX FIELD redis-bits = '64'
[offset 55] AUX FIELD ctime = '1688541401'
[offset 70] AUX FIELD used-mem = '564236664'
[offset 86] AUX FIELD aof-preamble = '0'
[offset 88] Selecting DB ID 0
[offset 14342796] Selecting DB ID 1
[offset 160442129] Selecting DB ID 2
[offset 161291906] Selecting DB ID 3
[offset 161305927] Selecting DB ID 4
[offset 161467387] Selecting DB ID 5
[offset 161469860] Selecting DB ID 6
[offset 161793171] Checksum OK
[offset 161793171] \o/ RDB looks OK! \o/
[info] 9585 keys read
[info] 441 expires
[info] 441 already expired

Redis 5.0.10 for Windows

PS C:\Program Files\Redis> .\redis-check-rdb.exe C:\code\test.rdb
[offset 0] Checking RDB file C:\code\test.rdb
[offset 29] AUX FIELD redis-ver = '5.0.14.1'
[offset 43] AUX FIELD redis-bits = '64'
[offset 55] AUX FIELD ctime = '1688541401'
[offset 70] AUX FIELD used-mem = '564236664'
[offset 86] AUX FIELD aof-preamble = '0'
[offset 88] Selecting DB ID 0
[offset 14342796] Selecting DB ID 1
[offset 160442129] Selecting DB ID 2
[offset 161291906] Selecting DB ID 3
[offset 161305927] Selecting DB ID 4
[offset 161467387] Selecting DB ID 5
[offset 161469860] Selecting DB ID 6
[offset 161793171] Checksum OK
[offset 161793171] \o/ RDB looks OK! \o/
[info] 9585 keys read
[info] 441 expires
[info] 441 already expired

Redis_version:7.0.11 (WSL2 Docker)

/data # /usr/local/bin/redis-check-rdb /data/test.rdb
[offset 0] Checking RDB file /data/test.rdb
[offset 29] AUX FIELD redis-ver = '5.0.14.1'
[offset 43] AUX FIELD redis-bits = '64'
[offset 55] AUX FIELD ctime = '1688541401'
[offset 70] AUX FIELD used-mem = '564236664'
[offset 86] AUX FIELD aof-preamble = '0'
[offset 88] Selecting DB ID 0
[offset 14342796] Selecting DB ID 1
[offset 160442129] Selecting DB ID 2
[offset 161291906] Selecting DB ID 3
[offset 161305927] Selecting DB ID 4
[offset 161467387] Selecting DB ID 5
[offset 161469860] Selecting DB ID 6
[offset 161793171] Checksum OK
[offset 161793171] \o/ RDB looks OK! \o/
[info] 9585 keys read
[info] 441 expires
[info] 441 already expired

No connection is active/available to service this operation: EVAL; An existing connection was forcibly closed by the remote host

after upgrade to 7.0 i get the following error

13:31:01 WRN] No connection is active/available to service this operation: EVAL; An existing connection was forcibly closed by the remote host., mc: 1/1/0, mgr: 10 of 10 available, clientName: CANZ-50099848H, IOCP: (Busy=0,Free=1000,Min=8,Max=1000), WORKER: (Busy=3,Free=32764,Min=8,Max=32767), v: 2.2.4.27433
StackExchange.Redis.RedisConnectionException: No connection is active/available to service this operation: EVAL; An existing connection was forcibly closed by the remote host., mc: 1/1/0, mgr: 10 of 10 available, clientName: CANZ-50099848H, IOCP: (Busy=0,Free=1000,Min=8,Max=1000), WORKER: (Busy=3,Free=32764,Min=8,Max=32767), v: 2.2.4.27433
---> StackExchange.Redis.RedisConnectionException: SocketFailure (ReadSocketError/ConnectionReset, last-recv: 56) on 127.0.0.1:6379/Subscription, Idle/Faulted, last: SUBSCRIBE, origin: ReadFromPipe, outstanding: 0, last-read: 8s ago, last-write: 8s ago, keep-alive: 60s, state: ConnectedEstablished, mgr: 7 of 10 available, in: 0, in-pipe: 0, out-pipe: 0, last-heartbeat: 0s ago, last-mbeat: 0s ago, global: 0s ago, v: 2.2.4.27433
---> Pipelines.Sockets.Unofficial.ConnectionResetException: An existing connection was forcibly closed by the remote host.
---> System.Net.Sockets.SocketException (10054): An existing connection was forcibly closed by the remote host.
at Pipelines.Sockets.Unofficial.Internal.Throw.Socket(Int32 errorCode) in //src/Pipelines.Sockets.Unofficial/Internal/Throw.cs:line 59
at Pipelines.Sockets.Unofficial.SocketAwaitableEventArgs.g__ThrowSocketException|10_0(SocketError e) in //src/Pipelines.Sockets.Unofficial/SocketAwaitableEventArgs.cs:line 86
at Pipelines.Sockets.Unofficial.SocketAwaitableEventArgs.GetResult() in //src/Pipelines.Sockets.Unofficial/SocketAwaitableEventArgs.cs:line 79
at Pipelines.Sockets.Unofficial.SocketConnection.DoReceiveAsync() in //src/Pipelines.Sockets.Unofficial/SocketConnection.Receive.cs:line 64
--- End of inner exception stack trace ---
at System.IO.Pipelines.Pipe.GetReadResult(ReadResult& result)
at System.IO.Pipelines.Pipe.GetReadAsyncResult()
at StackExchange.Redis.PhysicalConnection.ReadFromPipe() in /_/src/StackExchange.Redis/PhysicalConnection.cs:line 1496
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---
at StackExchange.Redis.ConnectionMultiplexer.ThrowFailed[T](TaskCompletionSource1 source, Exception unthrownException) in /_/src/StackExchange.Redis/ConnectionMultiplexer.cs:line 2760 --- End of stack trace from previous location --- at Microsoft.Extensions.Caching.StackExchangeRedis.RedisCache.SetAsync(String key, Byte[] value, DistributedCacheEntryOptions options, CancellationToken token) at Volo.Abp.Caching.DistributedCache2.<>c__DisplayClass51_0.<g__SetRealCache|0>d.MoveNext()
[13:31:01 WRN] ---------- Exception Data ----------
Redis-Multiplexer-Connects = 1/1/0
Redis-Manager = 10 of 10 available
Redis-Client-Name = CANZ-50099848H
Redis-ThreadPool-IO-Completion = (Busy=0,Free=1000,Min=8,Max=1000)
Redis-ThreadPool-Workers = (Busy=3,Free=32764,Min=8,Max=32767)
Redis-Busy-Workers = 3
Redis-Version = 2.2.4.27433
redis-command = EVAL
request-sent-status = WaitingToBeSent

Please correct some misleading information in this repo

The binaries provided here are not an official Redis port to Windows, and should not be presented as such.
Also, Redis 7.0 was not released yet so at best this port is based on a release candidate.

Could you share the code and build scripts?

Hi, I found there are only prebuild binaries in this repo, no code, patched, build scripts and documents are provided.

Could you share the code and build scripts? In such way, anyone else interested in this project could participate in and make contributions.

Upgrade the files version

Thx again for this greet job. You forgot to update the files version to 7.0.10 in the properties

Redis Bug Report

=== REDIS BUG REPORT START: Cut & paste starting from here ===
[002588] 19 Aug 21:26:45.831 # --- EXCEPTION_ACCESS_VIOLATION
[002588] 19 Aug 21:26:45.836 # --- STACK TRACE
redis-server.exe!((null):0)(0x1401E2B40, 0x0014FF60, 0x1401197F0, 0x0014DF40)
redis-server.exe!((null):0)(0x0014DF40, 0x140119701, 0x00000000, 0x00000000)
KERNELBASE.dll!UnhandledExceptionFilter((null):0)(0x0014DFF0, 0x7FFDB0C37654, 0x00000000, 0x0014DF88)
ntdll.dll!memset((null):0)(0x7FFDB0C64A24, 0x7FFDB0AF0000, 0x0014DFF0, 0x7FFDB0B20E7B)
ntdll.dll!_C_specific_handler((null):0)(0x00000000, 0x0014E4F0, 0x0014EBB0, 0x00000000)
ntdll.dll!_chkstk((null):0)(0x00000000, 0x0014E4F0, 0x0014EBB0, 0x00000000)
ntdll.dll!RtlRaiseException((null):0)(0x06800008, 0x1400D9073, 0x7FE146801C00, 0x05011200)
ntdll.dll!KiUserExceptionDispatcher((null):0)(0x7FE146801C00, 0x7FE13B400A42, 0x06400100, 0x7FE13B400A18)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x7FE146801C00, 0x7FE13B400A20, 0x7FE13B400A18, 0x7FE13B400A30)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x7FE13B400A10, 0x000000FF, 0x000000EF, 0x7FE139401403)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x7FE139405303, 0x18200000000, 0x7FE13B400A10, 0x00000000)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x0014F0E0, 0x08400000, 0x0014F140, 0x0014F1E0)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x7FE13D82C540, 0x0014F140, 0x0014F140, 0x08400000)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x03F3DAA0, 0x02850000, 0x00000000, 0x03F3DAA0)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x02850000, 0x02850000, 0x00000000, 0x00000270)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x0000025C, 0x00000000, 0x0000025C, 0x2AAAAAAAAAAAAAAB)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00000000, 0x00000000, 0x0056A4A0, 0x00000000)
redis-server.exe!KiUserExceptionDispatcher((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
KERNEL32.DLL!BaseThreadInitThunk((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
ntdll.dll!RtlUserThreadStart((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
ntdll.dll!RtlUserThreadStart((null):0)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
[002588] 19 Aug 21:26:45.869 #
=== REDIS BUG REPORT END. Make sure to include from START to END. ===

Thank you for everything

Thank you for your engineers' work, which has brought very convenient results for using this software on Windows platform! I hope you will continue this very meaningful project to benefit everyone!

what is EventLog.dll ？

how to build source code ？？

可否打包一下x86的 6.x 感谢

Sentinel failover aborted - failover-abort-not-elected error

Hello.
I have 2 redis and 3 sentinels.
Use it in 2 servers: master+ master-sentinel and slave + 2 slave-sentinels in separate services.
Use Redis 7.0.0 prerelease and master branch.
When master down, sentinels vote to elect a leader, and a leader was elected by voting, but no failover was performed and "failover-abort-not-elected" was reported. Thus, slave never come master.
When master server went down, sentinel does not set slave to master.
Version 3.0.504 for Windows with same config works as expected.
Master.config:

port 6379
requirepass "12345"
masterauth "12345"
loglevel notice
logfile "Logs/redis_log.txt"

replica-serve-stale-data yes
replica-read-only yes
repl-diskless-sync no
repl-diskless-sync-delay 5
repl-disable-tcp-nodelay no

Master-ssentinel.config

port 26379
loglevel notice
logfile "Logs/redis_sentinel_log.txt"
requirepass "12345"
masterauth "12345"

sentinel monitor redis-gsf 10.98.240.134 6379 2
sentinel down-after-milliseconds redis-gsf 6001
sentinel failover-timeout redis-gsf 60000
sentinel config-epoch redis-gsf 1
sentinel auth-pass redis-gsf "12345"

Slave.config

port 6379
requirepass "12345"
masterauth "12345"
loglevel notice
logfile "Logs/redis_log.txt"
replica-serve-stale-data yes
replica-read-only yes
repl-diskless-sync no
repl-diskless-sync-delay 5
repl-disable-tcp-nodelay no
replicaof 10.98.240.134 6379

Slave-sentinel1.config

port 26379
loglevel debug
logfile "Logs/redis_sentinel_log.txt"
requirepass "12345"
masterauth "12345"
sentinel monitor redis-gsf 10.98.240.134 6379 2
sentinel down-after-milliseconds redis-gsf 5000
sentinel failover-timeout redis-gsf 60000
sentinel config-epoch redis-gsf 1
sentinel auth-pass redis-gsf "12345"

Slave-sentinel2.config

port 26378
loglevel debug
logfile "Logs/redis_sentinel_log_2.txt"
requirepass "12345"
masterauth "12345"
sentinel monitor redis-gsf 10.98.240.134 6379 2
sentinel down-after-milliseconds redis-gsf 5000
sentinel failover-timeout redis-gsf 60000
sentinel config-epoch redis-gsf 1
sentinel auth-pass redis-gsf "12345"

Logs/redis_sentinel_log.txt

...
[037216] 05 Apr 11:43:05.457 # +sdown sentinel 27e0862078cd19da67f839b2ebaa3a363afc7b9e 10.98.240.134 26379 @ redis-gsf 10.98.240.134 6379
[037216] 05 Apr 11:43:18.391 # +sdown master redis-gsf 10.98.240.134 6379
[037216] 05 Apr 11:43:20.059 * Sentinel new configuration saved on disk
[037216] 05 Apr 11:43:20.059 # +new-epoch 53
[037216] 05 Apr 11:43:20.062 * Sentinel new configuration saved on disk
[037216] 05 Apr 11:43:20.063 # +vote-for-leader 92601948f2f8fd651dc26c352e42d6f6f93f1bbe 53
[037216] 05 Apr 11:43:20.543 # +odown master redis-gsf 10.98.240.134 6379 #quorum 2/2
[037216] 05 Apr 11:43:20.543 # Next failover delay: I will not start a failover before Tue Apr  5 11:45:20 2022
[037216] 05 Apr 11:45:20.622 # +new-epoch 54
[037216] 05 Apr 11:45:20.622 # +try-failover master redis-gsf 10.98.240.134 6379
[037216] 05 Apr 11:45:20.624 * Sentinel new configuration saved on disk
[037216] 05 Apr 11:45:20.624 # +vote-for-leader c8409d55794d04da09656e33761ec00adf19b0f5 54
[037216] 05 Apr 11:45:20.624 # -failover-abort-not-elected master redis-gsf 10.98.240.134 6379
[037216] 05 Apr 11:45:20.630 # 92601948f2f8fd651dc26c352e42d6f6f93f1bbe voted for c8409d55794d04da09656e33761ec00adf19b0f5 54
[037216] 05 Apr 11:45:21.699 # Next failover delay: I will not start a failover before Tue Apr  5 11:47:20 2022
[037216] 05 Apr 11:47:20.788 # +new-epoch 55
[037216] 05 Apr 11:47:20.788 # +try-failover master redis-gsf 10.98.240.134 6379
[037216] 05 Apr 11:47:20.790 * Sentinel new configuration saved on disk
[037216] 05 Apr 11:47:20.790 # +vote-for-leader c8409d55794d04da09656e33761ec00adf19b0f5 55
[037216] 05 Apr 11:47:20.790 # -failover-abort-not-elected master redis-gsf 10.98.240.134 6379
[037216] 05 Apr 11:47:20.796 # 92601948f2f8fd651dc26c352e42d6f6f93f1bbe voted for c8409d55794d04da09656e33761ec00adf19b0f5 55
[037216] 05 Apr 11:47:21.406 * Sentinel new configuration saved on disk
[037216] 05 Apr 11:47:21.406 # +new-epoch 56
[037216] 05 Apr 11:47:21.410 * Sentinel new configuration saved on disk
[037216] 05 Apr 11:47:21.410 # +vote-for-leader 92601948f2f8fd651dc26c352e42d6f6f93f1bbe 56
[037216] 05 Apr 11:47:21.846 # +new-epoch 57
[037216] 05 Apr 11:47:21.846 # +try-failover master redis-gsf 10.98.240.134 6379
[037216] 05 Apr 11:47:21.848 * Sentinel new configuration saved on disk
[037216] 05 Apr 11:47:21.848 # +vote-for-leader c8409d55794d04da09656e33761ec00adf19b0f5 57
[037216] 05 Apr 11:47:21.848 # -failover-abort-not-elected master redis-gsf 10.98.240.134 6379
[037216] 05 Apr 11:47:21.854 # 92601948f2f8fd651dc26c352e42d6f6f93f1bbe voted for c8409d55794d04da09656e33761ec00adf19b0f5 57
[037216] 05 Apr 11:47:22.901 # Next failover delay: I will not start a failover before Tue Apr  5 11:49:22 2022
...

Could you please inform me if you need additional information?
Thank you in advance.

Redis 7.0.12&&6.2.13&&7.2.0

Hello, can you help compile these versions?

Because these versions have fixed the following CVE：

• (CVE-2022-24834) A specially crafted Lua script executing in Redis can trigger
  a heap overflow in the cjson and cmsgpack libraries, and result in heap
  corruption and potentially remote code execution. The problem exists in all
  versions of Redis with Lua scripting support, starting from 2.6, and affects
  only authenticated and authorized users.

Which compiler?

Which compiler?

Problem setting up the server on SSL

Hi! I'm having issues setting up the server with "tls-port" parameter enabled.
If I uncomment that particular line in the config file I get a config parsing error:

*** FATAL CONFIG FILE ERROR ***
[003084] 11 Jul 08:08:07.529 # Reading the configuration file, at line 183
[003084] 11 Jul 08:08:07.530 # >>> 'tls-port 6379'
[003084] 11 Jul 08:08:07.531 # Bad directive or wrong number of arguments

Any ideas on that ?

how to build redis src in

how ? build src in windows sys

Docker: Working Example?

Thanks for porting Redis 7 to Windows.
I was trying to make it runnable in the docker env by reproducing the steps of the 3.x redis version for windows containers:
https://hub.docker.com/layers/redis/library/redis/windowsservercore/images/sha256-0a2ce94c3cdb33b022c12c24fb256cd3059585ef4e914e82000fd05850eec176?context=explore

Redis 3.x is not longer working with up2date StackExchange Extension for .net 6.
However after reproducing the above config I recieve from redis: "no active connection available".

Docker file I made below:

# escape=`
FROM mcr.microsoft.com/windows/servercore:ltsc2019 as base
ENV REDIS_DOWNLOAD_URL=https://github.com/zkteco-home/redis-windows/archive/refs/tags/redis7.0.zip
ENV REDIS_NAME="redis-windows-redis7.0"

FROM base as download
SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"]
WORKDIR /
# Setup Environment
RUN `
$newPath = ('C:\Redis;{0}' -f $env:PATH);`
Write-Host ('Updating PATH: {0}' -f $newPath);`
setx /M PATH $newPath;
# Install
RUN `
Write-Host ('Downloading {0} ...' -f $env:REDIS_DOWNLOAD_URL);`
Invoke-WebRequest -Uri $env:REDIS_DOWNLOAD_URL -OutFile 'redis.zip';`
Write-Host 'Expanding ...';` 	
Expand-Archive redis.zip -DestinationPath C:\redis-download; `
mkdir "Redis";`
Get-ChildItem -Path "C:\\redis-download\\$($env:REDIS_NAME)" -Recurse -File | Move-Item -Verbose -Force -Destination "Redis";`

Write-Host 'Verifying install ("redis-server --version") ...';`
redis-server --version;`
Write-Host 'Removing ...';`
Remove-Item redis.zip -Force
RUN dir
 
WORKDIR /   
RUN mkdir C:\data
VOLUME C:\data

WORKDIR /data

ADD ["redis.docker.conf", "/Redis"]
ADD ["redis.windows.conf", "/Redis"]
RUN (Get-Content C:\Redis\redis.windows.conf) 	-Replace '^(bind)\s+.*$', '$1 0.0.0.0' 	-Replace '^(protected-mode)\s+.*$', '$1 no' 	| Set-Content C:\Redis\redis.docker.conf

EXPOSE 6379/tcp
ENTRYPOINT [ "redis-server.exe", "redis.docker.conf" ]

Sentinel service is not working.

Hello.
I use versions 6.2.6 and 7.0.0 for Redis service and Redis sentinel.
redis.service.conf:

port 6379
loglevel notice
logfile "Logs/redis_log.txt"
slave-serve-stale-data yes
slave-read-only yes
repl-diskless-sync no
repl-diskless-sync-delay 5
repl-disable-tcp-nodelay no
maxmemory 256mb
appendonly no
maxmemory-policy allkeys-lru

redis.sentinel.conf:

loglevel notice
logfile "Logs/redis_sentinel_log.txt"
sentinel monitor redis-ptl 10.98.2.82 6379 2
sentinel down-after-milliseconds redis-ptl 6001
sentinel failover-timeout redis-ptl 60000
sentinel config-epoch redis-ptl 1

Installing script:

sc create Redis binPath= "%CD%\redis-server.exe --service-run redis.windows.conf" DisplayName= "Redis" start= auto depend= TCPIP
sc description Redis "Redis Cache Service"
net start redis
redis-server --service-stop --service-name Redis
redis-server --service-install redis.windows-service-sentinel.conf --service-name RedisSentinel_PTL --sentinel
redis-server --service-start --service-name Redis
redis-server --service-start --service-name RedisSentinel_PTL

Redis service is run and work correctly, but sentinel is fault after each connection.
Event:

Faulting application name: redis-server.exe, version: 7.0.0.0, time stamp: 0x620a489e
Faulting module name: redis-server.exe, version: 7.0.0.0, time stamp: 0x620a489e
Exception code: 0xc0000005
Fault offset: 0x0000000000080ee1
Faulting process id: 0x560
Faulting application start time: 0x01d8223d3ba2d636
Faulting application path: C:\Redis\redis-server.exe
Faulting module path: C:\Redis\redis-server.exe
Report Id: 9b899981-5f3b-4b4f-ad20-52f28d3b2622
Faulting package full name: 
Faulting package-relative application ID: 

and

Fault bucket 2183362293945992934, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: redis-server.exe
P2: 7.0.0.0
P3: 620a489e
P4: redis-server.exe
P5: 7.0.0.0
P6: 620a489e
P7: c0000005
P8: 0000000000080ee1
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7ECD.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7F1C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7F2C.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7F3C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7F5C.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_redis-server.exe_5577e98473d7b78ea97114c726f132a97b542_930bf4b9_7056d44a-9551-4b80-b097-bba40b9ff107

Analysis symbol: 
Rechecking for solution: 0
Report Id: 9b899981-5f3b-4b4f-ad20-52f28d3b2622
Report Status: 268435456
Hashed bucket: d613b560d85d99ed1e4cdc703aa206e6
Cab Guid: 0

Could you please fix this issue?

win10以服务方式运行，停止服务时不保存rdb文件

win10以服务方式运行，停止服务时不保存rdb文件。
如果以命令行方式运行，关闭命令行窗口时可以正常保存rdb文件。

安装服务的命令来自于README.md文件，版本为7.0.8.1

感谢