<div dir="ltr"><div><div><div><div><div><div><div><div><div>Background:<br></div>- erts 17<br></div>- rebar3 (beta 4)<br></div>- We are building releases using rebar3 and relx<br></div><div>- In vm.args we are using the short name -sname my_app<br></div><div>- centos 6.3<br></div><div><br></div>Problem:<br></div>- When we call the generated shell script with a ping; "my_app ping", it calls the nodetool ping which calls <br><br>{true, pong} =
{net_kernel:hidden_connect_node( 'my_app@my-server'),net_adm:ping('my_app@my-server')}.<br><br></div><div>The tuple returned is usually either {false, pong}, {true, pang}, or {false, pang}. While this call does not fail every single time it does fail almost every time.<br></div><br></div><div>If I attach to the node and run the commands from the erlang cmd prompt, it consistently succeeds.<br></div><div><br>(my_app@my-server)242> {true, pong} =
{net_kernel:hidden_connect_node( 'my_app@my-server'),
net_adm:ping('my_app@my-server')}.<br>{true,pong}<br> <br></div>The interesting thing is that when I add an alias to the /etc/hosts file for my_app, the escript consistently succeeds.<br><br></div><div>Is the problem with the network configuration or with the erlang application configuration?<br></div><div><br></div>cat /etc/hosts<br></div>10.0.5.21 my_app<br><div><div><div><div><div><br><div>Any ideas?<br></div></div></div></div></div></div></div>