-
Notifications
You must be signed in to change notification settings - Fork 232
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
extended_bin: Ignore ERL_DIST_PORT on OTP 22 #890
Conversation
Don't set the kernel options 'inet_dist_listen_{min,max}' on Erlang/OTP versions prior to 23.0. On those versions, the 'remote_console' VM and nodetool would attempt to listen on the same port and therefore fail to start up.
Hey, sorry for the delay on review. I'm not sure this is right. ERL_DIST_PORT is set by the user and so that code is only used if the user is trying to use that feature which only exists in 23+. It feels like the script should instead exit with an error message rather than ignore the user set port. |
Yes, makes sense. So just replace the current fallback solution with such an error exit? (Shall I (force-)push a new patch?) |
Actually, maybe a warning instead of an exit? Not everyone needs the local remote shell, so exit'ing may be too disruptive,but letting them know that remote shell, rpc, eval aren't going to work would be important. |
Sounds good! I'm easy to convince 🤣 |
@weiss I was hoping to make a release today so a new rebar3 can be released with |
Sorry, wasn't clear to me whether you're waiting for an update. I can certainly update the patch this weekend but not sure if today. |
BTW, my own use case was shipping a setup where |
@weiss ah, I see. Yea, sadly I think since it has been being honored we shouldn't change that behaviour. |
Don't set the kernel options
inet_dist_listen_{min,max}
on Erlang/OTP releases prior to 23.0. On those versions, theremote_console
VM and nodetool would attempt to listen on the same port as the main VM (because-dist_listen false
is not yet supported), and therefore fail to start up.