Elixir console error

Hello, I’m hitting an error trying to connect to one of my VMs using fly ssh console. I was following the post linked here IEx into Your Running App · Fly Docs

I have 2 VMs, the app is running fine. I’ve looked through other threads but I can’t seem to fine anything relevant.

Connecting to fdaa:c:22da… complete
Protocol ‘inet6_tcp’: the name …@fdaa:c:22da… seems to be in use by another Erlang node
Error: ssh shell: Process exited with status 1
Stacktrace:
goroutine 1 [running]:
runtime/debug.Stack()
runtime/debug/stack.go:26 +0x64
github.com/superfly/flyctl/internal/cli.printError(0x140003de0a0, 0x14000b99c0e, 0x140006cb208, {0x102825bc0, 0x140009b2030})
github.com/superfly/flyctl/internal/cli/cli.go:184 +0x44c
github.com/superfly/flyctl/internal/cli.Run({0x10284bee0?, 0x14000540a80?}, 0x140003de0a0, {0x1400012e5c0, 0xc, 0xc})
github.com/superfly/flyctl/internal/cli/cli.go:117 +0x874
main.run()
github.com/superfly/flyctl/main.go:47 +0x170
main.main()
github.com/superfly/flyctl/main.go:26 +0x20

Hi… This doesn’t look like a problem with flyctl; rather, it’s the process that it’s invoking via -C that’s failing.

(You can compare with fly ssh console -C 'bash -c "exit 7"', to see how the exit propagation works.)

I’d suggest posting the full name that it’s complaining about, since the part to the left of the at-sign (@) is the most likely source of conflicts…

Ok yes, it was the process that was crashing. flyctl was just outputting the stacktrace when debug was enabled.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.