My redid server has 'crashed by signal 7' for many times, this is the last error report in log file.
[8045] 09 Apr 10:20:24.849 # Redis 2.6.12 crashed by signal: 7
[8045] 09 Apr 10:20:24.849 # Failed assertion:
Clients
connected_clients:35 client_longest_output_list:0 client_biggest_input_buf:9688 blocked_clients:0
Memory
used_memory:11354190296 used_memory_human:10.57G used_memory_rss:11493699584 used_memory_peak:12291064984 used_memory_peak_human:11.45G used_memory_lua:31744 mem_fragmentation_ratio:1.01 mem_allocator:jemalloc-3.2.0
Persistence
loading:0 rdb_changes_since_last_save:19228 rdb_bgsave_in_progress:1 rdb_last_save_time:1365473843 rdb_last_bgsave_status:ok rdb_last_bgsave_time_sec:94 rdb_current_bgsave_time_sec:74 aof_enabled:0 aof_rewrite_in_progress:0 aof_rewrite_scheduled:0 aof_last_rewrite_time_sec:43 aof_current_rewrite_time_sec:-1 aof_last_bgrewrite_status:ok
Stats
total_connections_received:7064 total_commands_processed:390737745 instantaneous_ops_per_sec:5482 rejected_connections:0 expired_keys:1059754 evicted_keys:0 keyspace_hits:5802182 keyspace_misses:166180430 pubsub_channels:0 pubsub_patterns:0 latest_fork_usec:322257
Replication
role:master connected_slaves:0
CPU
used_cpu_sys:8609.80 used_cpu_user:4619.94 used_cpu_sys_children:8007.14 used_cpu_user_children:91079.27
Commandstats
cmdstat_get:calls=10000,usec=12350,usec_per_call=1.24 cmdstat_set:calls=10000,usec=37096,usec_per_call=3.71 cmdstat_del:calls=33,usec=2341,usec_per_call=70.94 cmdstat_incr:calls=10000,usec=18459,usec_per_call=1.85 cmdstat_rpush:calls=6298097,usec=12745271,usec_per_call=2.02 cmdstat_lpush:calls=12099420,usec=228862803,usec_per_call=18.92 cmdstat_rpop:calls=8250692,usec=190227070,usec_per_call=23.06 cmdstat_lpop:calls=10000,usec=17518,usec_per_call=1.75 cmdstat_llen:calls=167969175,usec=410939768,usec_per_call=2.45 cmdstat_lrange:calls=40011,usec=1166505,usec_per_call=29.15 cmdstat_sadd:calls=10000,usec=14323,usec_per_call=1.43 cmdstat_srem:calls=1,usec=6,usec_per_call=6.00 cmdstat_spop:calls=9999,usec=9921,usec_per_call=0.99 cmdstat_mset:calls=10000,usec=60130,usec_per_call=6.01 cmdstat_select:calls=180052300,usec=394088273,usec_per_call=2.19 cmdstat_expire:calls=3963425,usec=33103481,usec_per_call=8.35 cmdstat_keys:calls=27,usec=16132927,usec_per_call=597515.81 cmdstat_ping:calls=356563,usec=604246,usec_per_call=1.69 cmdstat_bgsave:calls=2,usec=103169,usec_per_call=51584.50 cmdstat_bgrewriteaof:calls=2,usec=98032,usec_per_call=49016.00 cmdstat_type:calls=1,usec=4,usec_per_call=4.00 cmdstat_multi:calls=24733,usec=53736,usec_per_call=2.17 cmdstat_exec:calls=24732,usec=16766604,usec_per_call=677.93 cmdstat_flushdb:calls=1,usec=4180,usec_per_call=4180.00 cmdstat_info:calls=18,usec=17055,usec_per_call=947.50 cmdstat_monitor:calls=5,usec=8,usec_per_call=1.60 cmdstat_ttl:calls=11588508,usec=21594197,usec_per_call=1.86
Keyspace
db5:keys=3113939,expires=2986553 hash_init_value: 1364357537
[8045] 09 Apr 10:20:25.282 # --- CLIENT LIST OUTPUT
Hardware: Intel(R) Xeon(R) CPU X3430 @ 2.40GHz + 16G Ram with Centos6.4
what's the happen?
Comment From: antirez
Hello, are the other crash reports similar to this one from the point of view of the stack trace?
Did you performed a memory test in this box?
Is the output really truncated to "CLIENT LIST OUTPUT" and there is nothing more?
Thanks, Salvatore
Comment From: litrin
Thaks u very much! I already used the --test-memory for my server, no prob. I'm sure 'CLIENT LIST OUTPUT' is the last line.
But I found my swap partition had bad blocks.
dmesg | tail
sd 1:0:0:0: [sdb] Add. Sense: Unrecovered read error - auto reallocate failed
sd 1:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 32 88 00 01 00 00
Buffer I/O error on device sdb1, logical block 1371
Buffer I/O error on device sdb1, logical block 1372
Buffer I/O error on device sdb1, logical block 1373
Buffer I/O error on device sdb1, logical block 1374
Buffer I/O error on device sdb1, logical block 1375
Buffer I/O error on device sdb1, logical block 1376
Buffer I/O error on device sdb1, logical block 1377
Buffer I/O error on device sdb1, logical block 1378
Buffer I/O error on device sdb1, logical block 1379
Buffer I/O error on device sdb1, logical block 1380
PS: sdb1 is the swap partition
And this would be relevant?
Comment From: 631086083
it's often caused by memory error, you can look up the system logs by using command "dmesg | grep -i err"