Crash report
Paste the complete crash log between the quotes below. Please include a few lines from the log preceding the crash report to provide some context.
[2072] 02 Jun 10:45:55.789 * Redis 3.2.100 (00000000/0) 64 bit, standalone mode, port 6379, pid 2072 ready to start.
[2072] 02 Jun 10:45:55.789 # Server started, Redis version 3.2.100
=== REDIS BUG REPORT START: Cut & paste starting from here ===
Redis version: 3.2.100
[2072] 02 Jun 10:45:55.806 # === ASSERTION FAILED OBJECT CONTEXT ===
[2072] 02 Jun 10:45:55.806 # Object type: 0
[2072] 02 Jun 10:45:55.806 # Object encoding: 0
[2072] 02 Jun 10:45:55.806 # Object refcount: 1
[2072] 02 Jun 10:45:55.806 # Object raw string len: 0
[2072] 02 Jun 10:45:55.806 # Object raw string content: ""
[2072] 02 Jun 10:45:55.806 # === ASSERTION FAILED ===
[2072] 02 Jun 10:45:55.806 # ==> ..\src\db.c:164 'retval == DICT_OK' is not true
[2072] 02 Jun 10:45:55.806 # --- EXCEPTION_ACCESS_VIOLATION
[2072] 02 Jun 10:45:55.814 # --- STACK TRACE
redis-server.exe!LogStackTrace(c:\release\redis\src\win32_interop\win32_stacktrace.cpp:95)(0x00D0E340, 0x00D0FF60, 0x40028F20, 0x4013A7F8)
redis-server.exe!UnhandledExceptiontHandler(c:\release\redis\src\win32_interop\win32_stacktrace.cpp:185)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
KERNELBASE.dll!UnhandledExceptionFilter(c:\release\redis\src\win32_interop\win32_stacktrace.cpp:185)(0xED43E1EC, 0xED40F838, 0x00000000, 0x00000000)
ntdll.dll!memset(c:\release\redis\src\win32_interop\win32_stacktrace.cpp:185)(0x00D0FF60, 0xED43E1EC, 0x00D0E410, 0x00000000)
ntdll.dll!_C_specific_handler(c:\release\redis\src\win32_interop\win32_stacktrace.cpp:185)(0x00000000, 0x00D0E910, 0x00D0EFF0, 0x00D0EFF0)
ntdll.dll!_chkstk(c:\release\redis\src\win32_interop\win32_stacktrace.cpp:185)(0x00D0EFF0, 0xED2C0000, 0xED2C485B, 0xED43E1EC)
ntdll.dll!RtlRestoreContext(c:\release\redis\src\win32_interop\win32_stacktrace.cpp:185)(0x0145EB40, 0x00000000, 0x5006AEC0, 0x40170C6A)
ntdll.dll!KiUserExceptionDispatcher(c:\release\redis\src\win32_interop\win32_stacktrace.cpp:185)(0x5006AEC0, 0x40170C50, 0x4016FC40, 0x000000A4)
redis-server.exe!dbAdd(c:\release\redis\src\db.c:164)(0x00000000, 0x00000000, 0x00D0F3E0, 0x5006AEC0)
redis-server.exe!rdbLoad(c:\release\redis\src\rdb.c:1414)(0x8C2BD761, 0x00000002, 0x00000031, 0x0000002F)
redis-server.exe!loadDataFromDisk(c:\release\redis\src\server.c:3850)(0x60B799A3, 0x40178288, 0x00D0EF10, 0x00D0EF30)
redis-server.exe!redis_main(c:\release\redis\src\server.c:4134)(0x005771B0, 0x60B799A3, 0x021439B0, 0x00000002)
redis-server.exe!main(c:\release\redis\src\win32_interop\win32_qfork.cpp:1241)(0x00000016, 0xFFFFFFFF, 0x00000016, 0x00000000)
redis-server.exe!ServiceWorkerThread(c:\release\redis\src\win32_interop\win32_service.cpp:484)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
KERNEL32.DLL!BaseThreadInitThunk(c:\release\redis\src\win32_interop\win32_service.cpp:484)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
ntdll.dll!RtlUserThreadStart(c:\release\redis\src\win32_interop\win32_service.cpp:484)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
ntdll.dll!RtlUserThreadStart(c:\release\redis\src\win32_interop\win32_service.cpp:484)(0x00000000, 0x00000000, 0x00000000, 0x00000000)
[2072] 02 Jun 10:45:55.830 # --- INFO OUTPUT
# Server
redis_version:3.2.100
redis_git_sha1:00000000
redis_git_dirty:0
redis_build_id:dd26f1f93c5130ee
redis_mode:standalone
os:Windows
arch_bits:64
multiplexing_api:WinSock_IOCP
process_id:2072
run_id:ecbd063fe6ea03616d4ec032d1aacadb497a1783
tcp_port:6379
uptime_in_seconds:0
uptime_in_days:0
hz:10
lru_clock:12032419
executable:C:\Program Files\Redis\"C:\Program Files\Redis\redis-server.exe"
config_file:C:\Program Files\Redis\redis.windows-service.conf
# Clients
connected_clients:0
client_longest_output_list:0
client_biggest_input_buf:0
blocked_clients:0
# Memory
used_memory:1044368
used_memory_human:1019.89K
used_memory_rss:0
used_memory_rss_human:0B
used_memory_peak:1044368
used_memory_peak_human:1019.89K
total_system_memory:0
total_system_memory_human:0B
used_memory_lua:37888
used_memory_lua_human:37.00K
maxmemory:2097152000
maxmemory_human:1.95G
maxmemory_policy:noeviction
mem_fragmentation_ratio:0.00
mem_allocator:jemalloc-3.6.0
# Persistence
loading:1
rdb_changes_since_last_save:0
rdb_bgsave_in_progress:0
rdb_last_save_time:1622645155
rdb_last_bgsave_status:ok
rdb_last_bgsave_time_sec:-1
rdb_current_bgsave_time_sec:-1
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
loading_start_time:jd
loading_total_bytes:1622645155
loading_loaded_bytes:670807
loading_loaded_perc:0.00
loading_eta_seconds:jd
# Stats
total_connections_received:0
total_commands_processed:0
instantaneous_ops_per_sec:0
total_net_input_bytes:0
total_net_output_bytes:0
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
evicted_keys:0
keyspace_hits:0
keyspace_misses:0
pubsub_channels:0
pubsub_patterns:0
latest_fork_usec:0
migrate_cached_sockets:0
# Replication
role:master
connected_slaves:0
master_repl_offset:0
repl_backlog_active:0
repl_backlog_size:1048576
repl_backlog_first_byte_offset:0
repl_backlog_histlen:0
# CPU
used_cpu_sys:0.05
used_cpu_user:0.11
used_cpu_sys_children:0.00
used_cpu_user_children:0.00
# Commandstats
# Cluster
cluster_enabled:0
# Keyspace
db0:keys=1,expires=0,avg_ttl=0
[2072] 02 Jun 10:45:55.830 #
=== REDIS BUG REPORT END. Make sure to include from START to END. ===
I was trying to start my redis server using redis-server.exe, and this error came up. Redis does not start upon reboot in services.msc, and when I run redis-cli, I get a separate issue saying "Could not connect to Redis at 127.0.0.1:6379: No connection could be made because the target machine actively refused it." Any clues with how to fix this?
Using Windows 10 Home, build 21390.1 Just tried to start redis-server.exe using redis-server with a command prompt in C:/Program Files/Redis
Comment From: oranagra
Redis (the one in this repository) does not run on windows, so you probably need to open this issue on another repo. By looking at the crash log I would guess that for some reason the RDB file has two keys with the same name. you can try to load that rdb file into normal (Linux) redis or analyze it with some other rdb processing tool (like redis-rdb-tools) to try and prove that theory. If that's correct, then the question is how that happened, and then you need to look into the redis (I assume the windows fork) that generated that rdb file (which looks like it's based on a very old version of Redis).
Comment From: my9988
if you want to use windows version,you can try to download redis6.2.5 from [link removed by @oranagra], it is stable
Comment From: oranagra
@my9988 that link seems suspicious to me and I decided to remove it. Redis is open source, and github is usually used to store source code. This link referred to a repo that was created just a few weeks ago, and contained binary files for which the content cannot be verified. Had this been a link to another repo hosting sources or a commercial or free company offering redis binaries, I wouldn't probably mind.
Also, considering porting redis to windows is complicated, and the very fact that there are commercial companies offering that, makes me wonder about the content of these binary files too.
Hope I'm wrong and you can clear that up.