Comment 6 for bug 1103045

One the one hand, there's no error in the protocol data:

# MySQLProtocolParser:473 2953 Packet is from server; client state: undef
# MySQLProtocolParser:1161 2953 Server handshake data: ...
# MySQLProtocolParser:451 2953 Done parsing packet; client state: server_handshake

# MySQLProtocolParser:473 2953 Packet is from server; client state: server_handshake
# MySQLProtocolParser:477 2953 TCP retransmission
# MySQLProtocolParser:451 2953 Done parsing packet; client state: server_handshake

(from client)
# MySQLProtocolParser:282 2953 Client 100.0.0.2:44432
# MySQLProtocolParser:321 2953 Client state: server_handshake
# MySQLProtocolParser:342 2953 TCP control: ACK FIN

Since the client closes the connection, that's not an error. But since it closes it half-way through connecting, MySQL counts that internally towards Aborted_connects.

I have managed to capture this as "administrator command: Connect aborted\G", aka "CONNECT ABORTED" in the profile. This is caught when the client sends a FIN packet while it's in a handshake state.

Joe, please try the latest from the linked branch. It should work for you now too.