Databases
StackOverflow2013
Postsdbo
POStarting an Erlang slave node in escript fails when using custom Erlang in Ubuntu 10.4
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POStarting an Erlang slave node in escript fails when using custom Erlang in Ubuntu 10.4
    primarykey
    data
    text
    <p>I have the following escript:</p> <pre><code>#!/usr/bin/env escript %%! -name test_starter@127.0.0.1 main(_) -&gt; NodeName = test, Host = '127.0.0.1', Args = "", {ok, _Node} = slave:start_link(Host, NodeName, Args), io:format("Node started successfully!"). </code></pre> <p>When running it on Ubuntu 10.04 I get this:</p> <pre><code>$ ./start_slave Node started successfully! $ </code></pre> <p>I want to install my own Erlang (latest version, debug compiled files for dialyzer etc) since the stock install of Erlang on Ubuntu lacks some features. I put my Erlang binaries inside <code>~/Applications/bin</code>. Starting Erlang normally works, and starting slave nodes inside an Erlang shell works as well.</p> <p>However, now my escript doesn't work. After about 60 seconds it returns an error:</p> <pre><code>$ ./start_slave escript: exception error: no match of right hand side value {error,timeout} </code></pre> <p>Even if I change the first line to the escript to use my erlang version, it still does not work:</p> <pre><code>#!/home/user/Applications/bin/escript </code></pre> <p>The slave node is started with a call to <code>erlang:open_port/2</code> which seems to be using <code>sh</code> which in turn does not read my <code>.bashrc</code> file that sets my custom <code>PATH</code> environment variable. The timeout seems to occur when <code>slave:start_link/3</code> waits for the slave node to respond, which it never does.</p> <p><em>How can I roll my own installation of Erlang and start slave nodes inside escripts on Ubuntu 10.4?</em></p> <p><strong>Update:</strong> I've tried to add the path to my custom Erlang inside <code>/etc/environment</code> (where the original <code>PATH</code> in Ubuntu is set) but this does not change anything...</p> <p><strong>Update 2:</strong> Accepting the only answer given (even though it didn't solve the problem). The Ubuntu and Erlang versions are a bit old now and this might not be an issue anymore.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAdam Lindberg
    1. USAdam Lindberg
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POStarting an Erlang slave node in escript fails when using custom Erlang in Ubuntu 10.4
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POStarting an Erlang slave node in escript fails when using custom Erlang in Ubuntu 10.4
      1. USAdam Lindberg
      1. VTBountyStart
    3. VO
      singulars
      1. POStarting an Erlang slave node in escript fails when using custom Erlang in Ubuntu 10.4
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAre you sure you want to use `start_link` instead of `start`? This way, your slaves automatically quits when your script terminates itself (which appens, after main has been called). See the docs for `start_link` for this.
      singulars
      1. POStarting an Erlang slave node in escript fails when using custom Erlang in Ubuntu 10.4
      1. USZeissS
    2. COThe point is that the node starting times out even before `start_link/3 returns'.
      singulars
      1. POStarting an Erlang slave node in escript fails when using custom Erlang in Ubuntu 10.4
      1. USAdam Lindberg
    3. COAlso, the point is to run tests, so I'm okay with the node dying when the script dies. :-)
      singulars
      1. POStarting an Erlang slave node in escript fails when using custom Erlang in Ubuntu 10.4
      1. USAdam Lindberg
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload