[erlang-questions] rebar3 release console cannot be started

[Tristan Sloughter]

Yea. First, that "missing beam" is a relx warning, you can ignore it and
it is now a debug message only in recent relx versions.

As for the error message, Jesper is right, it is saying a node with that
name is already running. Maybe you ran a node with 'start' before
running console? If you want to attach to the running node that was
started with 'start' use 'remote_console'

--
Tristan Sloughter
t@REDACTED
 
 
 
On Sun, Jan 31, 2016, at 04:19 AM, Jesper Louis Andersen wrote:
>  
> On Sun, Jan 31, 2016 at 9:01 AM, Pavanan M S <pavananms@REDACTED> wrote:
>> What is/could be the reason for this error.
>  
> Immediate bet: you already have a node running on the machine with the name hello_erlang. You can verify that this is the case or not by asking epmd(1) what it thinks are running nodes on the machine:
>  
> epmd -names
>  
> alternatively, look for a running node with ps(1).
>  
> Can the node boot without networking enabled? Do you have a deliberately crippled environment (docker, ...) which can wreak havoc?
>  
>  
> -- 
> J.
> _________________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20160131/c6f328ad/attachment.htm>