Databases
StackOverflow2013
Postsdbo
POrabbitmq-erlang-client, using rebar friendly pkg, works on dev env fails on rebar release
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POrabbitmq-erlang-client, using rebar friendly pkg, works on dev env fails on rebar release
    primarykey
    data
    text
    <p>I am successfully using the rebar-friendly package of rabbitmq-erlang-client for a simple Hello World rebarized and OTP "compliant" app and things work fine on the dev environment. I am able to fire up an erl console and do my <code>application:start(helloworld).</code> and connect to the broker, open up a channel and communicate to queues.</p> <p>However, then I proceed to do <code>rebar generate</code> and it builds up the release just fine, but when I try to fire up from the self contained release package then things suddenly explode.</p> <p>I know rebar releases are known to be an obscure art, but I would like to know what are my options as far as deployment for an app using the rabbitmq-erlang-client.</p> <p>Below you will find the output of the console on the crash:</p> <pre><code>=INFO REPORT==== 18-Dec-2012::16:41:35 === application: session_record exited: {{{badmatch, {error, {'EXIT', {undef, [{amqp_connection_sup,start_link, [{amqp_params_network,&lt;&lt;"guest"&gt;&gt;,&lt;&lt;"guest"&gt;&gt;,&lt;&lt;"/"&gt;&gt;, "127.0.0.1",5672,0,0,0,infinity,none, [#Fun&lt;amqp_auth_mechanisms.plain.3&gt;, #Fun&lt;amqp_auth_mechanisms.amqplain.3&gt;], [],[]}], []}, {supervisor2,do_start_child_i,3, [{file,"src/supervisor2.erl"},{line,391}]}, {supervisor2,handle_call,3, [{file,"src/supervisor2.erl"},{line,413}]}, {gen_server,handle_msg,5, [{file,"gen_server.erl"},{line,588}]}, {proc_lib,init_p_do_apply,3, [{file,"proc_lib.erl"},{line,227}]}]}}}}, [{amqp_connection,start,1, [{file,"src/amqp_connection.erl"},{line,164}]}, {hello_qp,start_link,0,[{file,"src/hello_qp.erl"},{line,10}]}, {session_record_sup,init,1, [{file,"src/session_record_sup.erl"},{line,55}]}, {supervisor_bridge,init,1, [{file,"supervisor_bridge.erl"},{line,79}]}, {gen_server,init_it,6,[{file,"gen_server.erl"},{line,304}]}, {proc_lib,init_p_do_apply,3, [{file,"proc_lib.erl"},{line,227}]}]}, {session_record_app,start,[normal,[]]}} type: permanent {"Kernel pid terminated",application_controller </code></pre> <p><strong>EDIT:</strong> As requested in the comments.</p> <p><code>reltool.config</code></p> <pre><code>{sys, [ {lib_dirs, ["..", "../deps"]}, {erts, [{mod_cond, derived}, {app_file, strip}]}, {app_file, strip}, {rel, "session_record", "0.1.0", [ kernel, stdlib, sasl, session_record ]}, {rel, "start_clean", "", [ kernel, stdlib ]}, {boot_rel, "session_record"}, {profile, embedded}, {incl_cond, derived}, {mod_cond, derived}, {excl_archive_filters, [".*"]}, %% Do not archive built libs {excl_sys_filters, ["^bin/.*", "^erts.*/bin/(dialyzer|typer)", "^erts.*/(doc|info|include|lib|man|src)"]}, {excl_app_filters, ["\.gitignore"]}, {app, session_record, [{mod_cond, app}, {incl_cond, include}, {lib_dir, ".."}]}, {app, hipe, [{incl_cond, exclude}]} ]}. {target_dir, "session_record"}. {overlay, [ {mkdir, "log/sasl"}, {copy, "files/erl", "\{\{erts_vsn\}\}/bin/erl"}, {copy, "files/nodetool", "\{\{erts_vsn\}\}/bin/nodetool"}, {copy, "files/session_record", "bin/session_record"}, {copy, "files/session_record.cmd", "bin/session_record.cmd"}, {copy, "files/start_erl.cmd", "bin/start_erl.cmd"}, {copy, "files/install_upgrade.escript", "bin/install_upgrade.escript"}, {copy, "files/sys.config", "releases/\{\{rel_vsn\}\}/sys.config"}, {copy, "files/vm.args", "releases/\{\{rel_vsn\}\}/vm.args"} ]}. </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USlegoscia
    1. USlfurrea
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POrabbitmq-erlang-client, using rebar friendly pkg, works on dev env fails on rebar release
      1. This table or related slice is empty.
      1. VTUpMod
    1. COCould you post your `reltool.config` file?
      singulars
      1. POrabbitmq-erlang-client, using rebar friendly pkg, works on dev env fails on rebar release
      1. USkjw0188
    2. CO@kjw0188 I posted the requested config file, the strange thing is that generating the release does not fail and the code that seems to be failing is from amqp_client while opening the connection. I tripled checked all network settings on the rabbitmq server a.s.o. Thanks for your help
      singulars
      1. POrabbitmq-erlang-client, using rebar friendly pkg, works on dev env fails on rebar release
      1. USlfurrea
    3. COGenerating the release just moves files around, so it's possible your release is not including the amqp client, leading to an undefined error.
      singulars
      1. POrabbitmq-erlang-client, using rebar friendly pkg, works on dev env fails on rebar release
      1. USkjw0188
 

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