gistfile1.txt

$ bin/riak console
Exec: /home/ubuntu/riak-1.2.1/rel/riak/erts-5.9.1/bin/erlexec -boot /home/ubuntu/riak-1.2.1/rel/riak/releases/1.2.1/riak             -embedded -config /home/ubuntu/riak-1.2.1/rel/riak/etc/app.config             -pa ./lib/basho-patches             -args_file /home/ubuntu/riak-1.2.1/rel/riak/etc/vm.args -- console
Root: /home/ubuntu/riak-1.2.1/rel/riak
Erlang R15B01 (erts-5.9.1) [source] [64-bit] [async-threads:64] [kernel-poll:true]

** ./lib/basho-patches/etop_txt.beam hides /home/ubuntu/riak-1.2.1/rel/riak/lib/observer-1.1/ebin/etop_txt.beam
** /home/ubuntu/riak-1.2.1/rel/riak/lib/observer-1.1/ebin/etop_txt.beam hides /home/ubuntu/riak-1.2.1/rel/riak/lib/basho-patches/etop_txt.beam
** Found 2 name clashes in code paths
13:05:41.651 [info] Application lager started on node 'riak@10.MY.IP.HERE'
13:05:41.796 [info] Upgrading legacy ring
13:05:42.004 [error] gen_server riak_core_capability terminated with reason: no function clause matching orddict:fetch('riak@10.MY.IP.HERE', [{'riak@127.0.0.1',[{{riak_core,staged_joins},[true,false]},{{riak_core,vnode_routing},[proxy,legacy]},...]}]) line 72
/home/ubuntu/riak-1.2.1/rel/riak/lib/os_mon-2.2.9/priv/bin/memsup: Erlang has closed.
                                                                                      Erlang has closed
       {"Kernel pid terminated",application_controller,"{application_start_failure,riak_core,{bad_return,{{riak_core_app,start,[normal,[]]},{'EXIT',{{function_clause,[{orddict,fetch,['riak@10.MY.IP.HERE',[{'riak@127.0.0.1',[{{riak_core,staged_joins},[true,false]},{{riak_core,vnode_routing},[proxy,legacy]},{{riak_kv,legacy_keylisting},[false,true]},{{riak_kv,listkeys_backpressure},[true,false]},{{riak_kv,mapred_2i_pipe},[true,false]},{{riak_kv,mapred_system},[pipe,legacy]},{{riak_kv,vnode_vclocks},[true,false]}]}]],[{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,415}]},{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,208}]},{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]}}}}}}"}

Crash dump was written to: ./log/erl_crash.dump
Kernel pid terminated (application_controller) ({application_start_failure,riak_core,{bad_return,{{riak_core_app,start,[normal,[]]},{'EXIT',{{function_clause,[{orddict,fetch,['riak@10.MY.IP.HERE',[{'r

Also some info at top of erl_crash.dump

=erl_crash_dump:0.1
Fri Nov 2 13:31:22 2012
Slogan: Kernel pid terminated (application_controller) ({application_start_failure,riak_core,{bad_return,{{riak_core_app,start,[normal,[]]},{'EXIT',{{function_clause,[{orddict,fetch,['riak@10.MY.IP.HERE',[{'r
System version: Erlang R15B01 (erts-5.9.1) [source] [64-bit] [async-threads:64] [kernel-poll:true]
Compiled: Thu Oct 18 14:30:54 2012
Taints:
Atoms: 13084

If you're seeing this behavior, refer to http://riak-users.197444.n3.nabble.com/riak-fails-to-start-on-Ubtunu-Precise-td4025766.html ... I had to nuke everything in my rel/riak/data/ring directory in order to get this to work.

Context is -- on fresh install, had one node running on 127.0.0.1, tried to re-bind to a subnet ip 10.X.Y.Z but got the above crash characterized by

** ./lib/basho-patches/etop_txt.beam hides /home/ubuntu/riak-1.2.1/rel/riak/lib/observer-1.1/ebin/etop_txt.beam.

There were not multiple erlang instances running, and the address was not in use (EADDRINUSE not an issue). There was also not any issue in binding to the supplied address (ENOTAVAIL). Killing ring directory works fine here.