Sometimes things aren't started up in time when you use 'riak-admin test'
right after 'riak start'. I've seen that happen before. Try starting
riak, waiting a minute or so and doing riak-admin test again and see if it
starts writing.
-Jared
On Fri, Jul 12, 2013 at 7:54 AM, prog112 <prog...@gmail.com> wrote:
> So I rolled back stats to default, adding your two changes. Made sure the
> ring folder is gone. Changed the uname -n. Also changed number of threads
> in
> vm.args from 64 to 16 and it worked! However...
>
> [root@s16976525 riak]# riak start
> [root@s16976525 riak]# riak-admin test
> Failed to read test value:
> {error,{insufficient_vnodes,0,need,1}}[root@s16976525 riak]#
>
> What did I do wrong? :(
>
>
>
>
>
> --
> View this message in context:
> http://riak-users.197444.n3.nabble.com/Can-t-start-Riak-Erlang-crashes-immediately-Memory-problem-tp4028271p4028298.html
> Sent from the Riak Users mailing list archive at Nabble.com.
>
> _______________________________________________
> riak-users mailing list
> riak-users@lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>
_______________________________________________
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
