Intermittent crash on startup #227

Closed
jonmeredith opened this Issue Sep 11, 2012 · 3 comments

Comments

Projects
None yet
4 participants
@jonmeredith
Contributor

jonmeredith commented Sep 11, 2012

Intermittent crash on startup - 6 node cluster, 32 vnodes.

 {"Kernel pid terminated",application_controller,"{application_start_failure,riak_core,{bad_return,{{riak_core_app,start,[normal,[]]},{'EXIT',{{function_clause,[{orddict,fetch,['riak@mgmt.r1s15',[{'riak@mgmt.r1s16',[{{riak_core,staged_joins},[true,false]},{{riak_core,vnode_routing},[proxy,legacy]}]}]],[{file,[111,114,100,100,105,99,116,46,101,114,108]},{line,72}]},{riak_core_capability,renegotiate_capabilities,1,[{file,[115,114,99,47,114,105,97,107,95,99,111,114,101,95,99,97,112,97,98,105,108,105,116,121,46,101,114,108]},{line,417}]},{riak_core_capability,handle_call,3,[{file,[115,114,99,47,114,105,97,107,95,99,111,114,101,95,99,97,112,97,98,105,108,105,116,121,46,101,114,108]},{line,216}]},{gen_server,handle_msg,5,[{file,[103,101,110,95,115,101,114,118,101,114,46,101,114,108]},{line,588}]},{proc_lib,init_p_do_apply,3,[{file,[112,114,111,99,95,108,105,98,46,101,114,108]},{line,227}]}]},{gen_server,call,[riak_core_capability,{register,{riak_core,vnode_routing},{capability,[proxy,legacy],legacy,{riak_core,legacy_vnode_routing,[{true,legacy},{false,proxy}]}}},infinity]}}}}}}"}
@evanmcc

This comment has been minimized.

Show comment
Hide comment
@evanmcc

evanmcc Aug 9, 2013

Contributor

Is this not the mismatched nodename issue?

Contributor

evanmcc commented Aug 9, 2013

Is this not the mismatched nodename issue?

@slfritchie

This comment has been minimized.

Show comment
Hide comment
@slfritchie

slfritchie Sep 27, 2013

Contributor

@evanmcc Time for some belated repo curating ... "mismatched" meaning changing vm.args while leaving behind an old ring with a different node name? Or something else?

Looking at a recent'ish version of riak_core_capability:renegotiate_capabilities() ... if the orddict:fetch is a orddict:find() instead, and if find doesn't find it, then ... do what the first func clause does, i.e., nothing?

Contributor

slfritchie commented Sep 27, 2013

@evanmcc Time for some belated repo curating ... "mismatched" meaning changing vm.args while leaving behind an old ring with a different node name? Or something else?

Looking at a recent'ish version of riak_core_capability:renegotiate_capabilities() ... if the orddict:fetch is a orddict:find() instead, and if find doesn't find it, then ... do what the first func clause does, i.e., nothing?

@jrwest

This comment has been minimized.

Show comment
Hide comment
@jrwest

jrwest Mar 24, 2014

Contributor

this is a known nodename mismatch issue and duplicate of both #266 and #244. closing.

Contributor

jrwest commented Mar 24, 2014

this is a known nodename mismatch issue and duplicate of both #266 and #244. closing.

@jrwest jrwest closed this Mar 24, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment