CODEWITHSUNDEEP
amazon-web-servicesamazon-ec2erlang
Martin Kristiansen
Martin Kristiansen

Reputation: 10222

Starting erlang without fully qualified hostnames in AWS

when starting erlang on my local machine I am able to do

erl -name testnode

this starts up an erlang node with the fully qualified hostname of my machine 

~ erl -name test
Erlang/OTP 18 [erts-7.3] [source-d2a6d81] [64-bit] [smp:4:4] [async-threads:10] [hipe] [kernel-poll:false]

Eshell V7.3  (abort with ^G)
([email protected])1>

when I do the same thing on AWS I get back

({application_start_failure,kernel,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,net_kernel,{'EXIT',nodistribution}}}}}

what am I missing?

Upvotes: 0

Views: 189

Answers (2)

legoscia
legoscia

Reputation: 41578

If you don't need fully qualified hostnames in your Erlang node names, you can use -sname instead of -name:

erl -sname testnode

(to be clear, it seems like the the Erlang node cannot determine its FQDN for some reason, and using -sname instead of -name works around this problem by removing the need for FQDNs.)

Upvotes: 1

Vitalii Kulchevych
Vitalii Kulchevych

Reputation: 366

It is not fqdn problem. This is network issue. Disable firewall and try to start again.

Upvotes: 1

Related Questions