=== REDIS BUG REPORT START: Cut & paste starting from here === 2899:M 02 Feb 16:32:02.437 # ------------------------------------------------ 2899:M 02 Feb 16:32:02.438 # !!! Software Failure. Press left mouse button to continue 2899:M 02 Feb 16:32:02.439 # Guru Meditation: "Unknown object type" #rdb.c:1077 2899:M 02 Feb 16:32:02.440 # (forcing SIGSEGV in order to print the stack trace) 2899:M 02 Feb 16:32:02.441 # ------------------------------------------------ 2899:M 02 Feb 16:32:02.441 # Redis 3.0.7 crashed by signal: 11 2899:M 02 Feb 16:32:02.443 # SIGSEGV caused by address: 0xffffffff 2899:M 02 Feb 16:32:02.443 # Failed assertion: (:0) 2899:M 02 Feb 16:32:02.444 # --- STACK TRACE 2899:M 02 Feb 16:32:02.446 # --- INFO OUTPUT 2899:M 02 Feb 16:32:02.448 # # Server redis_version:3.0.7 redis_git_sha1:00000000 redis_git_dirty:0 redis_build_id:d046e9d631282f4e redis_mode:standalone os:Linux 4.1.12-ti-r29 armv7l arch_bits:32 multiplexing_api:epoll gcc_version:4.8.4 process_id:2899 run_id:a0c4eed6d295f3d204b524fff3f3f2343387f048 tcp_port:6379 uptime_in_seconds:0 uptime_in_days:0 hz:10 lru_clock:11590146 config_file:

Clients

connected_clients:0 client_longest_output_list:0 client_biggest_input_buf:0 blocked_clients:0

Memory

used_memory:406432 used_memory_human:396.91K used_memory_rss:0 used_memory_peak:406432 used_memory_peak_human:396.91K used_memory_lua:26624 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:1454430722 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:1454430722 loading_total_bytes:307729 loading_loaded_bytes:0 loading_loaded_perc:0.00 loading_eta_seconds:1

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.02 used_cpu_user:0.03 used_cpu_sys_children:0.00 used_cpu_user_children:0.00

Commandstats

Cluster

cluster_enabled:0

Keyspace

db0:keys=5,expires=0,avg_ttl=0 hash_init_value: 1454717265

2899:M 02 Feb 16:32:02.453 # --- CLIENT LIST OUTPUT 2899:M 02 Feb 16:32:02.454 # 2899:M 02 Feb 16:32:02.455 # --- REGISTERS 2899:M 02 Feb 16:32:02.455 # --- FAST MEMORY TEST 2899:M 02 Feb 16:32:02.457 # Bio thread for job type #0 terminated 2899:M 02 Feb 16:32:02.459 # Bio thread for job type #1 terminated Testing b5000 49152 Testing 1bf0000 135168 Testing b5401000 8384512 Testing b5c01000 16773120 Testing b6ea7000 12288 Testing b6ec3000 8192 Testing b6f51000 28672 2899:M 02 Feb 16:32:04.525 # Fast memory test PASSED, however your memory can st ill be broken. Please run a memory test for several hours if possible. 2899:M 02 Feb 16:32:04.526 # === REDIS BUG REPORT END. Make sure to include from START to END. ===

   Please report the crash by opening an issue on github:

       http://github.com/antirez/redis/issues

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

Segmentation fault


I get this errors when I try to restore a dump.rdb that I had as a backup. I have passed the memory test and everything fine. I have tested in other pc and I get the same error. What can it be? Thanks in advance.

Comment From: badboy

"Unknown object type" #rdb.c:1077

Your RDB is corrupted. There is a tool called redis-check-rdb, which will tell you the same, but there is no automatic way to fix it.

Comment From: filipecosta90

asking core team to close this one given:

"Unknown object type" #rdb.c:1077

Your RDB is corrupted. There is a tool called redis-check-rdb, which will tell you the same, but there is no automatic way to fix it.