Thank you for speaking up. The riak logs are not much more help (at least to
me). The crash.log looks like:
2013-03-12 18:09:58 =ERROR REPORT====
** State machine <0.686.0> terminating
** Last event in was
{work,{fold,#Fun<riak_kv_eleveldb_backend.3.50402265>,#Fun<riak_kv_vnode.14.110730501>},{fsm,{97787215,{753586781748746817198774991869333432010090217472,'[email protected]'}},<0.25660.27>}}
** When State == ready
** Data == {state,{[],[]},<0.687.0>,[],undefined}
** Reason for termination =
**
{timeout,{gen_server,call,[<0.689.0>,{work,<0.687.0>,{fold,#Fun<riak_kv_eleveldb_backend.3.50402265>,#Fun<riak_kv_vnode.14.110730501>},{fsm,{97787215,{753586781748746817198774991869333432010090217472,'[email protected]'}},<0.25660.27>}}]}}
2013-03-12 18:09:58 =CRASH REPORT====
crasher:
initial call: riak_core_vnode_worker_pool:init/1
pid: <0.686.0>
registered_name: []
exception exit:
{{timeout,{gen_server,call,[<0.689.0>,{work,<0.687.0>,{fold,#Fun<riak_kv_eleveldb_backend.3.50402265>,#Fun<riak_kv_vnode.14.110730501>},{fsm,{97787215,{753586781748746817198774991869333432010090217472,'[email protected]'}},<0.25660.27>}}]}},[{gen_fsm,terminate,7,[{file,"gen_fsm.erl"},{line,611}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,227}]}]}
ancestors: [<0.684.0>,riak_core_vnode_sup,riak_core_sup,<0.138.0>]
messages:
[{#Ref<0.0.40.231987>,ok},{'$gen_all_state_event',{checkin,<0.689.0>}}]
links: [<0.684.0>]
dictionary: []
trap_exit: false
status: running
heap_size: 610
stack_size: 24
reductions: 219
neighbours:
. . . .
The erlang log looks like:
18:09:58.956 [error] gen_fsm <0.686.0> in state ready terminated with reason:
{timeout,{gen_server,call,[<0.689.0>,{work,<0.687.0>,{fold,#Fun<riak_kv_eleveldb_backend.3.50402265>,#Fun<riak_kv_vnode.14.110730501>},{fsm,{97787215,{753586781748746817198774991869333432010090217472,'[email protected]'}},<0.25660.27>}}]}}^M
18:09:58.961 [error] CRASH REPORT Process <0.686.0> with 0 neighbours exited
with reason:
{timeout,{gen_server,call,[<0.689.0>,{work,<0.687.0>,{fold,#Fun<riak_kv_eleveldb_backend.3.50402265>,#Fun<riak_kv_vnode.14.110730501>},{fsm,{97787215,{753586781748746817198774991869333432010090217472,'[email protected]'}},<0.25660.27>}}]}}
in gen_fsm:terminate/7 line 611
. . . .
The console.log looks like:
2013-03-12 18:09:58.961 [error] <0.686.0> CRASH REPORT Process <0.686.0> with 0
neighbours exited with reason:
{timeout,{gen_server,call,[<0.689.0>,{work,<0.687.0>,{fold,#Fun<riak_kv_eleveldb_backend.3.50402265>,#Fun<riak_kv_vnode.14.110730501>},{fsm,{97787215,{753586781748746817198774991869333432010090217472,'[email protected]'}},<0.25660.27>}}]}}
in gen_fsm:terminate/7 line 611
About all I can get from this is that something in eleveldb_backend is not
happy. I am not sure how to fix it.
The eleveldb config in app.config looks like:
%% eLevelDB Config
{eleveldb, [
{data_root, "/var/lib/riak/leveldb"},
{max_open_files, 100},
{cach_size, 83886080}
]},
From: riak-users [mailto:[email protected]] On Behalf Of
Jeremiah Peschka
Sent: Tuesday, March 12, 2013 6:34 PM
To: <[email protected]>
Subject: Re: Error interpretation
Your Riak search hook crashed. There is a bad argument being sent to Erlang.
Check your Riak logs for more detail.
--
Jeremiah Peschka - Founder, Brent Ozar Unlimited
MCITP: SQL Server 2008, MVP
Cloudera Certified Developer for Apache Hadoop
On Mar 12, 2013, at 4:23 PM, "Kevin Burton" <[email protected]> wrote:
I am writing a value to a 4 node Riak cluster with a CorrugatedIron client and
am getting the following error:
Riak returned an error. Code '0'. Message:
{precommit_fail,{hook_crashed,{riak_search_kv_hook,precommit,error,badarg}}}
I don’t know how to interpret this error. Any help would be appreciated.
Thank you.
_______________________________________________
riak-users mailing list
[email protected]
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
_______________________________________________
riak-users mailing list
[email protected]
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
