Erlang. Why does an error occur when installing a release using rebar?

Question

Erlang

Good day,% habrauser%!
I deal with the assembly and installation of releases and using rebar. Faced a problem - on the test computer, the command to run the assembled release

cd rel/dummy_0.1
bin/dummy console

works, but when transferred to the server it says:

{"init terminating in do_boot",{'cannot load',error_handler,get_files}}

Crash dump was written to: erl_crash.dump
init terminating in do_boot ()

I tried to google, but I didn’t find anything worthwhile, except for the mention of a mismatch between erlang versions. Both packages are installed from the repository, the first one is in ubuntu, the second one is on the server in Centos

Erlang/OTP 17 [erts-6.3] [source-e2a0928] [64-bit] [smp:4:4] [async-threads:10] [hipe] [kernel-poll:false]
Erlang/OTP 17 [erts-6.3] [source] [64-bit] [smp:2:2] [async-threads:10] [kernel-poll:false]

I collect the code in ubuntu according to the manual https://github.com/rebar/rebar/wiki/Upgrades .
And another question to catch up, my application has dependencies, when launched from the release folder, these dependencies do not cling. How to include them in the assembly?

Answer 1

I found a problem, it was necessary to add application dependencies to the rebar config.

Answer 2

Unlike reltool, the new release managers relx and mad themselves resolve all dependencies (sorting the application launch sequence based on dependencies), and mad also makes small compact releases of 8MB in size. Works just like relx, via sasl/systools. Doing releases via reltool/rebar is a slow and deprecated way.