Brian, Can you please contact enstratus about this. I'm not sure why this is even happening since our installer is tested on precise but these requests should come through enStratus as the installer creates a working Riak install that shouldn't need any changes.
You can either email [email protected], your internal contact here or me directly. On Wed, Oct 24, 2012 at 12:26 PM, [email protected] <[email protected]> wrote: > I installed enstratus which makes use of riak and unfortunately, i can't get > riak to start. Here is the console output: > > Attempting to restart script through sudo -H -u riak > Exec: /usr/lib/riak/erts-5.9.1/bin/erlexec -boot > /usr/lib/riak/releases/1.2.0/riak -embedded -config > /etc/riak/app.config -pa /usr/lib/riak/basho-patches > -args_file /etc/riak/vm.args -- console > Root: /usr/lib/riak > Erlang R15B01 (erts-5.9.1) [source] [64-bit] [smp:2:2] [async-threads:64] > [kernel-poll:true] > > > =INFO REPORT==== 24-Oct-2012::12:25:46 === > alarm_handler: {set,{system_memory_high_watermark,[]}} > ** /usr/lib/riak/lib/observer-1.1/ebin/etop_txt.beam hides > /usr/lib/riak/lib/basho-patches/etop_txt.beam > ** Found 1 name clashes in code paths > 12:25:46.667 [info] Application lager started on node '[email protected]' > 12:25:46.762 [info] Upgrading legacy ring > 12:25:46.991 [error] gen_server riak_core_capability terminated with reason: > no function clause matching orddict:fetch('[email protected]', []) line 72 > Erlang has closed > > =INFO REPORT==== 24-Oct-2012::12:25:47 === > alarm_handler: {clear,system_memory_high_watermark} > /usr/lib/riak/lib/os_mon-2.2.9/priv/bin/memsup: 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,['[email protected]',[]],[{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,414}]},{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: /var/log/riak/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,['[email protected]',[]],[{ > > > _______________________________________________ > 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
