Also, I'm using the

riak_1.1.1-1_amd64.deb

On Thu, Mar 15, 2012 at 5:41 PM, Eric Siegel <siegel.e...@gmail.com> wrote:

> *riak-admin diag*
> Attempting to restart script through sudo -u riak
>
> *riak-admin ringready*
> Attempting to restart script through sudo -u riak
> TRUE All nodes agree on the ring ['riak@10.249.136.3','riak@10.249.136.4',
>                                                   'riak@10.249.136.5','
> riak@10.249.136.6']
>
> *riak-admin transfers*
> Attempting to restart script through sudo -u riak
> No transfers active
>
> *riak-admin cluster_info*
> This creates a very large file, is there any section in particular that
> you are interested in.
> I could send it to you directly.
>
>
>
>
> On Thu, Mar 15, 2012 at 4:55 PM, Jared riak-admin transfersMorrow <
> ja...@basho.com> wrote:
>
>> What do the following commands return:
>>
>> 'riak-admin diag'
>> 'riak-admin ringready'
>> 'riak-admin transfers'
>> 'riak-admin cluster_info'
>>
>> -Jared
>>
>>
>> On Mar 15, 2012, at 5:39 PM, Eric Siegel wrote:
>>
>> Running riak-admin times out, but only for one of my vms.
>>
>>
>> Attempting to restart script through sudo -u riak
>>  Failed to write test value: {error,timeout}
>>
>>
>> The weird part is that this timeout will no longer happen if I remove any
>> of the other nodes from the cluster of four.
>>
>> For example, I have nodes A,B,C,D all apart of my cluster.
>> riak-admin test passes on all but node A.
>> Removing either B,C,or D, now riak-test passes on node A.
>>
>> I have verified that I can telnet to all the required ports from all the
>> machines.
>>
>> What does riak-admin do, and why would it work and not work situationally.
>>
>> Eric
>>  _______________________________________________
>> 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

Reply via email to