erl_call -q

[Bogdan Andu]

Hello,

I want to stop a node started with switch -proto_dist inet_tls :
$ /usr/lib/erlang/lib/erl_interface-5.2.1/bin/erl_call -q -c proxy -name
'node-name@REDACTED'

doesn't kill the node:
$ erl -name node-name@REDACTED -setcookie proxy -proto_dist inet_tls
Erlang/OTP 24 [erts-12.3] [source] [64-bit] [smp:4:4] [ds:4:4:10]
[async-threads:1]

Eshell V12.3  (abort with ^G)
(node-name@REDACTED)1> =NOTICE REPORT==== 25-Mar-2022::08:55:56.447550 ===
TLS server: In state hello at tls_record.erl:564 generated SERVER ALERT:
Fatal - Unexpected Message
 - {unsupported_record_type,0}

(node-name@REDACTED)1>

Because the ssl handshake fails the node does not 'catch' the
command to terminate itself.


The execution of command shows the error:
$ /usr/lib/erlang/lib/erl_interface-5.2.1/bin/erl_call -c proxy -name
node-name@REDACTED -a "init stop"
erl_call: failed to connect to node node-name@REDACTED

Actually the erl_call node connects to 'node-name@REDACTED'  but is
rejected with the same error as above.

Because the erl_call cannot connect to a tls erlang node, erl_call cannot
stop suc node.

If the node is started like this:
$ erl -name node-name@REDACTED -setcookie proxy -proto_dist inet_tcp

erl_call is able to stop it.

Is there a solution to this problem?

Cheers,

Bogdan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20220325/36bc291b/attachment.htm>