Excerpts from Sangeetha.PattabiRaman2's message of 2012-08-07 21:15:16 +1000:
> Hi ,
>
> Can any one help me on the start up error ..thx in advance
> [root@CTSINGMRGTO riak]# cat console.log
> 2012-08-07 09:13:54.260 [error] <0.164.0> CRASH REPORT Process
> riak_core_capability with 0 neighbours
a path.
rgh
> Still the same .unable to start
>
> -Original Message-----
> From: riak-users-boun...@lists.basho.com
> [mailto:riak-users-boun...@lists.basho.com] On Behalf Of Richard Heycock
> Sent: Wednesday, August 08, 2012 9:00 AM
> To: riak-users
> Subject: Re: ri
.the other node 170 is fine
> ..please tell me hw to resume the cluster back wit hone machine up and other
> down...
> Thanks
> Sangeetha
>
> -Original Message-
> From: riak-users-boun...@lists.basho.com
> [mailto:riak-users-boun...@lists.basho.com] On Behalf Of Ri
Excerpts from Joseph Blomstedt's message of 2012-08-08 16:30:14 +1000:
> The error you're getting is related to "riak_core_capability" which
> didn't exist in Riak until Riak 1.2.0. It looks like you somehow ended
> up installing Riak 1.2 RC1, not Riak 1.1.4. Keep in mind that RC1 was
> the first "
I've been running riak for about a month and I'm using it as a
persistent cache. Everything has been fine until tonight that is where
it appears to have had a catastrophic failure. Basically when I make a
request using the http interface I get a failure. I cannot be more
specific than that as there
r five times. I should clarify here that when I say "harder to
start" it does start but as soon as I try to do anything it fails.
The contents of /var/log/riak are here:
http://stuff.roughage.com.au/riak-failure-2.log.tar.gz
rgh
--
Richard Heycock
http://topikality.com
+6
atch is here:
> >
> > http://github.com/wagerlabs/couchdb/commit/23527eb8165f81e63d47b230f3...
> >
> > ---http://twitter.com/wagerlabs
> >
> >
> > erlang-questions (at) erlang.org mailing list.
> > S
{gen_fsm,init_it,6},
{proc_lib,init_p_do_apply,3}]}}},
[{riak_core_vnode_master,get_vnode,2},
{riak_core_vnode_master,handle_cast,2},
{gen_server,handle_msg,5},
{proc_lib,init_p_do_apply,3}]}
The logs can be found here:
