-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Closed
Description
Running rethinkdb 2.3.0~0jessie (GCC 4.9.2)...
Running on Linux 4.2.2-coreos-r2 x86_64
Loading data from directory /data/rethinkdb_data
Listening for intracluster connections on port 29015
Connected to proxy proxy-c5d7b685-acb9-4071-aa42-0535f73647ed
Listening for client driver connections on port 28015
Listening for administrative HTTP connections on port 8080
Listening on cluster addresses: 127.0.0.1, 10.244.88.37, ::1, fe80::42:aff:fef4:5825%76
Listening on driver addresses: 127.0.0.1, 10.244.88.37, ::1, fe80::42:aff:fef4:5825%76
Listening on http addresses: 127.0.0.1, 10.244.88.37, ::1, fe80::42:aff:fef4:5825%76
Server ready, "rethinkdb1_oliv4_rv1" 9cb8f5fb-d27c-45db-af9c-0ba09619e4a8
Version: rethinkdb 2.3.0~0jessie (GCC 4.9.2)
error: Error in src/rdb_protocol/lazy_btree_val.cc at line 22:
error: Guarantee failed: [res == archive_result_t::SUCCESS] Deserialization of rdb value failed with error archive_result_t::RANGE_ERROR.
error: Backtrace:
error: Tue Apr 12 08:00:06 2016
1 [0xadfb70]: backtrace_t::backtrace_t() at ??:?
2 [0xadfee9]: format_backtrace(bool) at ??:?
3 [0xd93c53]: report_fatal_error(char const*, int, char const*, ...) at ??:?
4 [0x947a83]: get_data(rdb_value_t const*, buf_parent_t) at ??:?
5 [0x80133d]: post_construct_traversal_helper_t::handle_pair(scoped_key_value_t&&, concurrent_traversal_fifo_enforcer_signal_t) at ??:?
6 [0xa50a01]: concurrent_traversal_adapter_t::handle_pair_coro(scoped_key_value_t*, semaphore_acq_t*, fifo_enforcer_write_token_t, auto_drainer_t::lock_t) at ??:?
7 [0xa507c6]: callable_action_instance_t<std::_Bind<std::_Mem_fn<void (concurrent_traversal_adapter_t::*)(scoped_key_value_t*, semaphore_acq_t*, fifo_enforcer_write_token_t, auto_drainer_t::lock_t)> (concurrent_traversal_adapter_t*, scoped_key_value_t*, semaphore_acq_t*, fifo_enforcer_write_token_t, auto_drainer_t::lock_t)> >::run_action() at ??:?
8 [0x9ed088]: coro_t::run() at ??:?
error: Exiting.
Using Python 2.7, running in custom docker image with debian:jessie with just rethinkdb and python2.7 and python-pip installed.
Is there any way to figure out which value triggered this? I'll be happy to supply more information.
crestenstclair
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Done