Closed tmesser closed 3 years ago
Some further info:
The initial batch of log lines hint at connections being rejected by the peer.
Grepping the Casper nodes' logs for TLS handshake failed
yielded the following on node N0
only:
Nov 5 20:04:41 ec2-uw1-1a-p-testnet-rustN0 casper-node[13971]: {"timestamp":"Nov 05 20:04:41.993","level":"WARN","fields":{"message":"ff54..4652: TLS handshake failed","peer_address":"34.72.74.228:45346","err":"handshake error: the handshake failed: error:1408F09C:SSL routines:ssl3_get_record:http request:ssl/record/ssl3_record.c:322:"},"target":"casper_node::components::small_network"}
Nov 5 20:07:11 ec2-uw1-1a-p-testnet-rustN0 casper-node[13971]: {"timestamp":"Nov 05 20:07:11.116","level":"WARN","fields":{"message":"ff54..4652: TLS handshake failed","peer_address":"136.37.195.206:54027","err":"handshake error: the handshake failed: error:1408F09C:SSL routines:ssl3_get_record:http request:ssl/record/ssl3_record.c:322:"},"target":"casper_node::components::small_network"}
Running curl http://34.72.74.228:7777/status | jq
shows that this node has now been able to connect successfully to N0
(I can see "ff54..4652": "54.177.84.9:34553"
in the list of peers), so the failure was transient.
On each of N0
, N1
and N2
, we also have the following lines:
Nov 5 17:25:29 ec2-uw1-1a-p-testnet-rustN0 casper-node[13971]: {"timestamp":"Nov 05 17:25:29.224","level":"WARN","fields":{"message":"ff54..4652: receiving message failed, closing connection","err":"Connection reset by peer (os error 104)","peer_id":"9be8..2d7b"},"target":"casper_node::components::small_network"}
Nov 5 17:25:29 ec2-uw1-1a-p-testnet-rustN0 casper-node[13971]: {"timestamp":"Nov 05 17:25:29.224","level":"INFO","fields":{"message":"ff54..4652: connection closed","peer_id":"9be8..2d7b","peer_address":"34.72.74.228:43776"},"target":"casper_node::components::small_network"}
Nov 5 17:25:29 ec2-uw1-1a-p-testnet-rustN0 casper-node[13971]: {"timestamp":"Nov 05 17:25:29.224","level":"WARN","fields":{"message":"ff54..4652: outgoing connection closed","peer_id":"9be8..2d7b","peer_address":"34.72.74.228:34553"},"target":"casper_node::components::small_network"}
All three report the same messages with identical timestamps. This could tie in with 9be8..2d7b
panicking, however the panic reported in the OP is timestamped 18:06:21
whereas our nodes report this at 17:25:29
.
Transient issue, closing
While attempting to join the delta testnet, I provided public hex key
01329cc15cb92fca5d5ce6d7fcc881010161547f452e2caad4dff565708b00b8c7
, which was successfully funded. Upon launching the node and attempting to bond, I received some warnings of this form:Which soon turned into a ton of errors of this form:
Which ended in a panic of this form: