One of our nodes fails to start
$ sudo riak console
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.1/riak -embedded -config
/etc/riak/app.config -pa /usr/lib/riak/lib/basho-patches
-args_file /etc/riak/vm.args -- console
Root: /usr/lib/riak
Erlang R15B01 (erts-5.9.1) [source] [64-bit] [smp:4:4] [async-threads:64]
[kernel-poll:true]
** /usr/lib/riak/lib/basho-patches/etop_txt.beam hides
/usr/lib/riak/lib/observer-1.1/ebin/etop_txt.beam
** Found 1 name clashes in code paths
13:22:47.424 [info] Application lager started on node 'riak@10.173.240.1'
13:22:47.466 [error] CRASH REPORT Process <0.149.0> with 0 neighbours
exited with reason: bad argument in call to erlang:binary_to_term(<<>>) in
riak_core_ring_manager:read_ringfile/1 line 154 in gen_server2:init_it/6
line 384
/usr/lib/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,{shutdown,{riak_core_app,start,[normal,[]]}}}"}
Crash dump was written to: /var/log/riak/erl_crash.dump
Kernel pid terminated (application_controller) ({application_start_failure,
riak_core,{shutdown,{riak_core_app,start,[normal,[]]}}})
Which suggest that something happened to ring files?
Any idea what and why it happened?
Dump file available at:
http://www.filedropper.com/erlcrash
Regards
Daniel
_______________________________________________
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
