Sohil - That's surprising since that's the standard reason for that error. I would recommend checking your vm.args files using "diff" or a hex editor to ensure they are identical.
You can then use "riak attach" to attach to your nodes and retrieve the cookie value using this statement: erlang:get_cookie(). -- Luke Bakken CSE lbak...@basho.com On Fri, Oct 11, 2013 at 7:42 PM, raghwani sohil <sohil4...@gmail.com> wrote: > Hi Luke , > It's same on all nodes. I didn't change *-cookie *parameter in vm.args > file , > > Thanks, > Sohil > > > On Fri, Oct 11, 2013 at 8:44 PM, Luke Bakken <lbak...@basho.com> wrote: > >> Hello Sohil, >> >> Could you please check the `vm.args' file on your existing node and your >> new node to ensure that the `-cookie' parameter is the same on each? >> >> -- >> Luke Bakken >> CSE >> lbak...@basho.com >> >> >> On Fri, Oct 11, 2013 at 7:02 AM, raghwani sohil <sohil4...@gmail.com>wrote: >> >>> Hi , >>> >>> I have three node riak(0.14.2) cluster on production(all nodes running >>> on RHEL OS). >>> >>> I have one CentOS system on which one riak node(0.14.2) is setup using >>> RHEL binary. >>> >>> When I m trying add CentOS riak node to existing cluster then I am >>> getting >>> >>> error *Node r...@a.b.c.xxx is not reachable! *and in sasl-error.log >>> file it's showing >>> >>> *Connection attempt from disallowed node 'riak@**a.d.c.YYY**'* >>> * >>> * >>> can any one help on the same? >>> * >>> * >>> thanks, >>> Sohil >>> >>
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
