polypush135
How to Node.connect to a node spun up by edeliver/distilery?
I’ve been having an issue connecting to a remove node.
note: xxx is my ip for my server
[error] ** System NOT running to use fully qualified hostnames **
** Hostname xx.xxx.xxx is illegal **
I’m currently using edeliver to deploy to my server and noticed that it (“edeliver”) rewrites the vm.args on every mix edeliver restart|start|stop
The name is set to be app_name@127.0.0.1
I’m also noticing that I can’t find a way to set the name in vm.args via /rel/config.exs or /.deliver/config
And as one last opservation I noticed that there is a discrepancy in the vm.args cookies vs ~/.erlang.cookie
In this case which cookie should I be using?
Most Liked
OvermindDL1
It randomizes ports, you need to constrain it to a range. Here’s a mailing list thread about it:
http://erlang.org/pipermail/erlang-questions/2006-May/020564.html
gregvaughn
I wish I had a quick and easy solution. I’ve faced your difficulties, but I’ve not delved into the details I’ve seen in some blogs (and now books) to make it clean. You can set the nodename in distillery, which should be covered well in its hexdocs. I have settled for ssh-ing to the server in question and running bin/myappname remote_console to use the distillery script to connect a hidden beam node to the production vm.
polypush135
Whooohooo, ssh port-forwarding for the win!!
Thank you Erich Kist!
This is what I’ve been trying to do all day







