Crash report
=== REDIS BUG REPORT START: Cut & paste starting from here ===
6257:M 22 Nov 18:48:15.128 # Redis 4.0.10 crashed by signal: 11
6257:M 22 Nov 18:48:15.128 # Accessing address: 0xffffffffffffffff
6257:M 22 Nov 18:48:15.129 # Failed assertion: <no assertion failed> (<no file>:0)
------ STACK TRACE ------
/opt/redis-4.0.10/bin/redis-server 0.0.0.0:6379(logStackTrace+0x50)[0x46cad8]
------ INFO OUTPUT ------
# Server
redis_version:4.0.10
redis_git_sha1:00000000
redis_git_dirty:0
redis_build_id:e72b66fe03796dbd
redis_mode:standalone
os:Linux 4.19.90-11.ky10.aarch64 aarch64
arch_bits:64
multiplexing_api:epoll
atomicvar_api:atomic-builtin
gcc_version:5.4.0
process_id:6257
run_id:b1d6a988889a45c024a7dc0f1c61bbafd815e169
tcp_port:6379
uptime_in_seconds:262451
uptime_in_days:3
hz:10
lru_clock:10188143
executable:/opt/redis-4.0.10/bin/redis-server
config_file:/opt/redis-4.0.10/redis.conf
# Clients
connected_clients:6
client_longest_output_list:0
client_biggest_input_buf:0
blocked_clients:0
# Memory
used_memory:1521480
used_memory_human:1.45M
used_memory_rss:9109504
used_memory_rss_human:8.69M
used_memory_peak:3293232
used_memory_peak_human:3.14M
used_memory_peak_perc:46.20%
used_memory_overhead:990972
used_memory_startup:819376
used_memory_dataset:530508
used_memory_dataset_perc:75.56%
total_system_memory:33692123136
total_system_memory_human:31.38G
used_memory_lua:37888
used_memory_lua_human:37.00K
maxmemory:524288000
maxmemory_human:500.00M
maxmemory_policy:allkeys-lru
mem_fragmentation_ratio:5.99
mem_allocator:jemalloc-4.0.3
active_defrag_running:0
lazyfree_pending_objects:0
# Persistence
loading:0
rdb_changes_since_last_save:242
rdb_bgsave_in_progress:0
rdb_last_save_time:1637577815
rdb_last_bgsave_status:ok
rdb_last_bgsave_time_sec:0
rdb_current_bgsave_time_sec:-1
rdb_last_cow_size:2621440
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
# Stats
total_connections_received:8
total_commands_processed:643907
instantaneous_ops_per_sec:0
total_net_input_bytes:361961188
total_net_output_bytes:823919170
instantaneous_input_kbps:0.04
instantaneous_output_kbps:0.23
rejected_connections:0
sync_full:0
sync_partial_ok:0
sync_partial_err:0
expired_keys:5948
expired_stale_perc:0.00
expired_time_cap_reached_count:0
evicted_keys:0
keyspace_hits:269615
keyspace_misses:163129
pubsub_channels:0
pubsub_patterns:9
latest_fork_usec:236
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
# Replication
role:master
connected_slaves:0
master_replid:d7aa5b20a0034bd27410613db5c1ca3045974008
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:120.75
used_cpu_user:58.62
used_cpu_sys_children:0.28
used_cpu_user_children:1.92
# Commandstats
cmdstat_psubscribe:calls=4,usec=27,usec_per_call=6.75
cmdstat_get:calls=419105,usec=1218601,usec_per_call=2.91
cmdstat_auth:calls=8,usec=17,usec_per_call=2.12
cmdstat_setex:calls=77369,usec=354901,usec_per_call=4.59
cmdstat_punsubscribe:calls=1,usec=94,usec_per_call=94.00
cmdstat_publish:calls=211,usec=1416,usec_per_call=6.71
cmdstat_hmset:calls=382,usec=2894,usec_per_call=7.58
cmdstat_hgetall:calls=626,usec=2953,usec_per_call=4.72
cmdstat_pexpire:calls=2198,usec=4955,usec_per_call=2.25
cmdstat_sadd:calls=382,usec=1497,usec_per_call=3.92
cmdstat_smembers:calls=13120,usec=35110,usec_per_call=2.68
cmdstat_del:calls=71623,usec=334733,usec_per_call=4.67
cmdstat_setnx:calls=57917,usec=280542,usec_per_call=4.84
cmdstat_keys:calls=14,usec=1891,usec_per_call=135.07
cmdstat_append:calls=382,usec=1212,usec_per_call=3.17
cmdstat_srem:calls=79,usec=397,usec_per_call=5.03
cmdstat_select:calls=4,usec=5,usec_per_call=1.25
cmdstat_config:calls=2,usec=28,usec_per_call=14.00
cmdstat_exists:calls=480,usec=411,usec_per_call=0.86
# Cluster
cluster_enabled:0
# Keyspace
db1:keys=591,expires=585,avg_ttl=10740474
------ CLIENT LIST OUTPUT ------
id=10 addr=143.8.69.236:44310 fd=8 name= age=1086 idle=1 flags=N db=0 sub=0 psub=3 multi=-1 qbuf=0 qbuf-free=0 obl=0 oll=0 omem=0 events=r cmd=psubscribe
id=5 addr=127.0.0.1:48554 fd=9 name= age=262448 idle=1 flags=N db=0 sub=0 psub=3 multi=-1 qbuf=0 qbuf-free=0 obl=0 oll=0 omem=0 events=r cmd=psubscribe
id=6 addr=127.0.0.1:48566 fd=10 name= age=262448 idle=1 flags=N db=1 sub=0 psub=0 multi=-1 qbuf=0 qbuf-free=0 obl=0 oll=0 omem=0 events=r cmd=del
id=7 addr=127.0.0.1:48568 fd=11 name= age=262448 idle=1 flags=N db=0 sub=0 psub=3 multi=-1 qbuf=0 qbuf-free=0 obl=0 oll=0 omem=0 events=r cmd=psubscribe
id=8 addr=127.0.0.1:48570 fd=12 name= age=262448 idle=15 flags=N db=1 sub=0 psub=0 multi=-1 qbuf=0 qbuf-free=0 obl=0 oll=0 omem=0 events=r cmd=get
id=9 addr=143.8.69.236:44306 fd=7 name= age=1091 idle=3 flags=N db=1 sub=0 psub=0 multi=-1 qbuf=0 qbuf-free=0 obl=0 oll=0 omem=0 events=r cmd=del
------ REGISTERS ------
------ FAST MEMORY TEST ------
6257:M 22 Nov 18:48:15.129 # Bio thread for job type #0 terminated
6257:M 22 Nov 18:48:15.130 # Bio thread for job type #1 terminated
6257:M 22 Nov 18:48:15.130 # Bio thread for job type #2 terminated
*** Preparing to test memory region 540000 (65536 bytes)
*** Preparing to test memory region 3d9a0000 (196608 bytes)
*** Preparing to test memory region fffcb6600000 (4194304 bytes)
*** Preparing to test memory region fffcb6be0000 (8388608 bytes)
*** Preparing to test memory region fffcb73f0000 (8388608 bytes)
*** Preparing to test memory region fffcb7c00000 (10485760 bytes)
*** Preparing to test memory region fffcbf000000 (2097152 bytes)
*** Preparing to test memory region fffcbf690000 (65536 bytes)
.O.O.O.O.O.O.O.O
Fast memory test PASSED, however your memory can still be broken. Please run a memory test for several hours if possible.
=== REDIS BUG REPORT END. Make sure to include from START to END. ===
Additional information
- OS: kylinos 10 ，aarch64
- Redis-server crashed after running for half a month
Comment From: oranagra
For some reason the stack trace is incomplete. There's really nothing we can do without further info. Maybe there's something else in the log file just before the crash?
Comment From: ksmrp
Thank you for your reply I uploaded the log file on this comment, further more , I pasted the part of the log file /var/log/messages under this line. Please check it again , thanks again
Nov 22 18:47:54 host-143-8-69-236 avahi-daemon[3754]: Host name conflict, retrying with linux-401741
Nov 22 18:47:54 host-143-8-69-236 avahi-daemon[3754]: Registering new address record for fe80::807:7c:c664:8c8a on eth0.*.
Nov 22 18:47:54 host-143-8-69-236 avahi-daemon[3754]: Registering new address record for fe80::424:aad1:7d07:afd7 on eth0.*.
Nov 22 18:47:54 host-143-8-69-236 avahi-daemon[3754]: Registering new address record for fe80::6e0a:b555:5563:82e1 on eth0.*.
Nov 22 18:47:54 host-143-8-69-236 avahi-daemon[3754]: Registering new address record for 143.8.69.236 on eth0.IPv4.
Nov 22 18:47:54 host-143-8-69-236 avahi-daemon[3754]: Registering HINFO record with values 'AARCH64'/'LINUX'.
Nov 22 18:48:15 host-143-8-69-236 abrt-hook-ccpp: Process 6257 (redis-server) of user 0 killed by SIGSEGV - dumping core
Nov 22 18:48:15 host-143-8-69-236 systemd: redis.service: main process exited, code=dumped, status=11/SEGV
Nov 22 18:48:15 host-143-8-69-236 systemd: Unit redis.service entered failed state.
Nov 22 18:48:15 host-143-8-69-236 systemd: redis.service failed.
Nov 22 18:48:15 host-143-8-69-236 abrt-server: Package 'redis' isn't signed with proper key
Nov 22 18:48:15 host-143-8-69-236 abrt-server: 'post-create' on '/var/spool/abrt/ccpp-2021-11-22-18:48:15-6257' exited with 1
Nov 22 18:48:15 host-143-8-69-236 abrt-server: Deleting problem directory '/var/spool/abrt/ccpp-2021-11-22-18:48:15-6257'
Comment From: oranagra
i'm sorry. i don't see anything usable in these logs. all i can do is suggest you upgrade to a (much) more recent version. this may resolve the problem that causes the crash, and if not, it'll at least very likely to resolve the problem with incomplete stack traces, so we know what happens. the version you're using is very old, and no longer maintained.
Comment From: qinqin111
@ksmrp Hello, can you tell me how to solve the problem? Is it an upgrade ？