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
remote_console is broken under elixir 1.9 #692
Comments
Sorry, thought this was related to the other issue, can you try and reproduce with 2.1.1? |
@bitwalker I can also confirm that this is still an issue with 2.1.1 |
Tested with 2.1.1 - works -
Thanks @bitwalker ! |
I fixed my problem. I was getting an error with tzdata because the format changed. Bumping the version to include bitwalker/timex#542 now allows me to connect via However I think there may be an underlying problem here that prevented |
Steps to reproduce
Under k8s/Docker this works :
iex --erl "-hidden -kernel"
--name "elixir_plug_poc111@elixir-plug-poc-0.elixir-plug-poc.default.svc.cluster.local"
--cookie "cookie"
--remsh "elixir_plug_poc@elixir-plug-poc-0.elixir-plug-poc.default.svc.cluster.local"
But this fails with error :
I can see from instrumenting
releases/0.0.1/libexec/commands/remote_console.sh
thatit isn't getting past the require_live_node check.
I also get the error "--logger-sasl-reports : Unknown option" reported in #687
Here follows two examples you can try for yourself - one built using 'bitwalker/alpine-elixir:1.8.2' the other using 'bitwalker/alpine-elixir:1.9' - the build with 1.8.2 works correctly, with 1.9.0 it exibits the failure of
remote_console
and--logger-sasl-reports : Unknown option
message when running ping (which succeeds).Then using image built from bitwalker/alpine-elixir:1.8.2
Remote console works
The text was updated successfully, but these errors were encountered: