Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Erlang VM exited when using -internal_epmd and rebar 3.14 #62

Closed
maehjam opened this issue Oct 29, 2020 · 5 comments
Closed

Erlang VM exited when using -internal_epmd and rebar 3.14 #62

maehjam opened this issue Oct 29, 2020 · 5 comments
Assignees
Labels

Comments

@maehjam
Copy link
Member

maehjam commented Oct 29, 2020

When deploying a GRiSP application with rebar 3.14 the OTP patch to add the -internal_epmd flag (i.e. grisp/otp@5ebbd6a) gets lost in the build process.

When starting GRiSP using internal epmd (e.g. when having wifi configurations as described in the wiki) it results in

Protocol 'inet_tcp': register/listen error: econnrefused
Erlang VM exited
@maehjam
Copy link
Member Author

maehjam commented Nov 4, 2020

This might be caused by a bug in with the system_libs flag in relx 4.0.0 see erlware/relx#823

@peerst
Copy link
Member

peerst commented Nov 19, 2020

Out now: rebar 3.14.2

Is this maybe fixed there? The issue above is close now and its supposed to be fixed here:

erlware/relx#834

So first we need to figure out if this is part of 3.14.2 and if yes figure out that we can fix our problem with this version (possibly not breaking 3.13.x and before if possible)

@maehjam
Copy link
Member Author

maehjam commented Nov 20, 2020

Not fixed, but with rebar 3.14.2 we now get the error already when we try to deploy the GRiSP application:

$ rebar3 grisp deploy -n robot -v 0.1.0
===> Verifying dependencies...
===> Analyzing applications...
===> Compiling robot
* Downloading pre-built OTP package (bb415d58)
* Cached file is up to date
===> Application needed for release not found: kernel

@joaohf
Copy link

joaohf commented Feb 11, 2021

Hello,

Seems that we have the same issue as described here: erlang/rebar3#2496

@eproxus
Copy link
Member

eproxus commented Feb 10, 2022

Pretty sure this is not an issue in later versions of Rebar (3.16+?) and rebar3_grisp. Closing for now.

@eproxus eproxus closed this as completed Feb 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants