Douvi

Douvi

I’m running my Phoenix in production inside a docker everything works perfectly.
I would like to be able to open my server into iex console.
So when I run iex --sname prod01@172.31.56.165

and I got this error:

2017-08-06 01:37:38 Can't set short node name!
Please check your configuration

2017-08-06 01:37:38 crash_report        
    initial_call: {net_kernel,init,['Argument__1']}
    pid: <0.48.0>
    registered_name: []
    error_info: {exit,{error,badarg},[{gen_server,init_it,6,[{file,"gen_server.erl"},{line,344}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,247}]}]}
    ancestors: [net_sup,kernel_sup,<0.35.0>]
    messages: []
    links: [<0.45.0>]
    dictionary: [{longnames,false}]
    trap_exit: true
    status: running
    heap_size: 610
    stack_size: 27
    reductions: 180
2017-08-06 01:37:38 supervisor_report   
    supervisor: {local,net_sup}
    errorContext: start_error
    reason: {'EXIT',nodistribution}
    offender: [{pid,undefined},{id,net_kernel},{mfargs,{net_kernel,start_link,[['prod01@172.31.56.165',shortnames],true]}},{restart_type,permanent},{shutdown,2000},{child_type,worker}]
2017-08-06 01:37:38 supervisor_report   
    supervisor: {local,kernel_sup}
    errorContext: start_error
    reason: {shutdown,{failed_to_start_child,net_kernel,{'EXIT',nodistribution}}}
    offender: [{pid,undefined},{id,net_sup},{mfargs,{erl_distribution,start_link,[]}},{restart_type,permanent},{shutdown,infinity},{child_type,supervisor}]
2017-08-06 01:37:38 crash_report        
    initial_call: {application_master,init,['Argument__1','Argument__2','Argument__3','Argument__4']}
    pid: <0.34.0>
    registered_name: []
    error_info: {exit,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,net_kernel,{'EXIT',nodistribution}}}}},{kernel,start,[normal,[]]}},[{application_master,init,4,[{file,"application_master.erl"},{line,134}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,247}]}]}
    ancestors: [<0.33.0>]
    messages: [{'EXIT',<0.35.0>,normal}]
    links: [<0.33.0>,<0.32.0>]
    dictionary: []
    trap_exit: true
    status: running
    heap_size: 376
    stack_size: 27
    reductions: 153
2017-08-06 01:37:38 std_info            
    application: kernel
    exited: {{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,net_kernel,{'EXIT',nodistribution}}}}},{kernel,start,[normal,[]]}}
    type: permanent
{"Kernel pid terminated",application_controller,"{application_start_failure,kernel,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,net_kernel,{'EXIT',nodistribution}}}}},{kernel,start,[normal,[]]}}}"}
Kernel pid terminated (application_controller) ({application_start_failure,kernel,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,net_kernel,{'EXIT',nodistribution}}}}},{ker

Crash dump is being written to: erl_crash.dump...done

Do you know why I have this error?

Showing Posts 1 to 4

OvermindDL1

OvermindDL1

This is a full node name, not a short node name. A short node name would be like prod01, a full node name is like prod01@172.31.56.165. Short node names are only really accessible (short tunnelling and such) on the local machine. You probably want to use a long node name, I.E. don’t use --sname, but rather --name if I recall correctly. :slight_smile:

Douvi

Douvi OP

Thanks for your answer but unfortunately that do not work :frowning:

iex --name prod01@172.31.56.165 Protocol 'inet_tcp': the name prod01@172.31.56.165 seems to be in use by another Erlang node

To show I set the right name here my conf:
epmd -names epmd: up and running on port 4369 with data: name prod01 at port 9100

OvermindDL1

OvermindDL1

Precisely that then, you have a duplicate name created. :slight_smile:

Douvi

Douvi OP

The solution I had it to call from the server 1 the server 2 and server 2 the server 1. Thanks it works

— All posts loaded —

Where Next? Top

Trending in Questions Top

water
I’m aware of 2 such projects, are there others? git: GitHub - team-alembic/realworld: A fullstack Phoenix LiveView application with back...
New
katta
I having some trouble figuring out if I have set myself too strict of standards for my production server. Currently I can handle 75% of r...
New
peck
Hi everyone. My team and I have been working on a fairly modest app based around video streaming and chat, but we’ve landed a customer t...
New
bradley
I really like the adapter patterns that ecto, nebulex, waffle, etc. use and would love find something similar for a key management servic...
New
unaware8150
Hello folks! So at work, we are seeing some situations where we have to define some “fixed” strings that are used across the codebase in...
New
Alvinkariuki
How Can I Optimise Compile Time Dependencies I have been building an elixir application for about 2 years now. Many modules and files ha...
New

Other Trending Topics Top

budgie
A little off-topic, but I feel like people here have a good head on their shoulders. I used to be quite good at making software. Was luc...
New
KristerV
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
mudasobwa
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
juhalehtonen
There has been a thread to discuss the Stack Overflow Developer Survey on this forum every year since 2018, so here’s yet another one for...
New
budgie
I love Elixir. It’s one of 2 programming languages I’ve ever fallen in love with. But I don’t use it anymore. Serverless was the promis...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews