Authentication handshake failed: tls peer certificate verification error: tlsopts error: peer ID did not match requested ID

`2019-07-17T05:32:04.622Z        DEBUG   kademlia:endpoint       connection to node failed       {"error": "node error: transport error: connection error: desc = \"transport: authentication handshake failed: tls peer certificate verification error: tlsopts error: peer ID did not match requested ID\"", "errorVerbose": "node error: transport error: connection error: desc = \"transport: authentication handshake failed: tls peer certificate verification error: tlsopts error: peer ID did not match requested ID\"\n\tstorj.io/storj/pkg/transport.(*Transport).DialNode:107\n\tstorj.io/storj/pkg/kademlia/kademliaclient.(*Dialer).dialNode:175\n\tstorj.io/storj/pkg/kademlia/kademliaclient.(*Dialer).PingNode:95\n\tstorj.io/storj/pkg/kademlia.(*Kademlia).Ping:253\n\tstorj.io/storj/pkg/kademlia.(*Endpoint).pingback:57\n\tstorj.io/storj/pkg/kademlia.(*Endpoint).Query:42\n\tstorj.io/storj/pkg/pb._Nodes_Query_Handler.func1:535\n\tstorj.io/storj/pkg/server.logOnErrorUnaryInterceptor:39\n\tstorj.io/storj/pkg/pb._Nodes_Query_Handler:537\n\tgoogle.golang.org/grpc.(*Server).processUnaryRPC:998\n\tgoogle.golang.org/grpc.(*Server).handleStream:1278\n\tgoogle.golang.org/grpc.(*Server).serveStreams.func1.1:717", "nodeID": "1nh2MhdP2CjJYwBNHLi4fr5R4UADVaimkjEky6PuQA5hKVa2nJ"}`

authentication handshake failed: tls peer certificate verification error: tlsopts error: peer ID did not match requested ID

Tons of messages like that. With debug log level.
Is it normal?

Looks like that, not closed properly connections, appears with an INVALID conntrack state in netfilter.

DEBUG errors are beyond the scope of this document as most aren’t logging in debug mode. Also, we just had a major update yesterday and a minor update today so some errors do crop up at those points.