riak won't start

David Smith dizzyd at basho.com
Sun Dec 20 07:40:14 EST 2009


On Sun, Dec 20, 2009 at 4:43 AM, francisco treacy
<francisco.treacy at gmail.com> wrote:
>
> ftreacy @ ~/work/sandbox/riak/rel/riak
>  =>  bin/riak ping
> Node 'riak at mbp-2.local' not responding to pings.
>
> =ERROR REPORT==== 20-Dec-2009::12:38:57 ===
> Error in process <0.37.0> on node 'riak_maint_1681 at mbp-2.local' with
> exit value: {badarg,[{erlang,list_to_existing_atom,["riak at mbp2.a.chello.nl"]},{dist_util,recv_challenge,1},{dist_util,handshake_we_started,1}]}

This is a DNS configuration problem. Notice how the first message
talks about 'riak at mbp-2.local' not being reachable, but the body of
the second message mentions 'riak at mbp2.a.chello.nl'.

Try starting riak in console mode (bin/riak console) -- I believe
you'll find that that the erlang node comes up with a name of
'riak at mbp-2.a.chello.nl'. If that's the case, you can try just
changing -name parameter in etc/vm.args to something like:

-name riak at mbp-2.local

and see if that works.

The bottom line here is that Distributed Erlang requires a working DNS
configuration when using -name. You're encountering a mismatch in DNS
names, probably as the result of being in a dynamic environment where
a search or/domain parameter is assigned via dhcp.

Hope that helps.

D.




More information about the riak-users mailing list