Dreaded: "inet_tcp",{{badmatch,{error,duplicate_name}}

David Smith dizzyd at basho.com
Tue Mar 6 10:42:03 EST 2012


This error means one of two things:

1. Riak is already running - check for beam.smp
2. epmd _thinks_ Riak is running - check/kill epmd

That should resolve the problem.

D.

On Mon, Mar 5, 2012 at 5:22 PM, Robert Lowe <rob at iblargz.com> wrote:
> Hi,
>
> Has anyone dealt with this error:
>
> "Protocol: ~p: register error:
> ~p~n",["inet_tcp",{{badmatch,{error,duplicate_name}}"
>
> http://hastebin.com/wucipobiho  - someone else having the same issue
>
> For some reason and I'm not completely sure of the root cause (something to
> due with epmd is my guess.)
>
> After `riak start` no crash is produced, but any command will see "Node is
> not up"
>
> However, if you run `riak console`, the crash snippet from above is
> produced.
>
> What's the resolution for this? Even kill -9'ing all riak related processes
> don't fix the issue.
>
> Even weirder is after a long while the issue goes away (or so I've seen on
> my staging environment)
>
> Regards,
>  - Rob
>
> _______________________________________________
> riak-users mailing list
> riak-users at lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>



-- 
Dave Smith
VP, Engineering
Basho Technologies, Inc.
dizzyd at basho.com




More information about the riak-users mailing list