Bug #90281 | mysqlsh \q command generates "aborted connections" notes in error log | ||
---|---|---|---|
Submitted: | 2 Apr 2018 18:17 | Modified: | 9 May 2018 13:21 |
Reporter: | Leonardo Abraham Figueroa Tapia | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Shell General / Core Client | Severity: | S4 (Feature request) |
Version: | 1.0.11 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[2 Apr 2018 18:17]
Leonardo Abraham Figueroa Tapia
[6 Apr 2018 7:44]
MySQL Verification Team
Hello Leonardo, Thank you for the report and feature request! I have noticed that "Abort" note is logged not when you run "\q" but most likely when connected session exhausting number of seconds(interactive_timeout/wait_timeout) the server waits for activity on a noninteractive connection before closing it. 2018-04-06T07:34:37.595870Z 7 [Note] Aborted connection 7 to db: 'unconnected' user: 'root' host: 'localhost' (Got timeout reading communication packets) When you execute "\q", normally below is logged: 2018-04-06T07:29:51.932078Z 0 [Note] Plugin mysqlx reported: 'X Plugin listens on TCP (bind-address:'::', port:33060)' 2018-04-06T07:29:51.932096Z 0 [Note] Plugin mysqlx reported: 'X Plugin listens on UNIX socket (/tmp/mysqlx.sock)' 2018-04-06T07:29:51.932164Z 0 [Note] Plugin mysqlx reported: 'Server starts handling incoming connections' -- after \q from mysqlsh session (no matter tcp or socket connection session) 2018-04-06T07:30:58.466026Z 4 [Note] Plugin mysqlx reported: '1: ERROR reading from socket Connection reset by peer (104) 0' 2018-04-06T07:31:47.468486Z 5 [Note] Plugin mysqlx reported: '2: ERROR reading from socket Connection reset by peer (104) 0' 2018-04-06T07:35:14.941354Z 8 [Note] Plugin mysqlx reported: '3: ERROR reading from socket Connection reset by peer (104) 0' Thanks, Umesh
[6 Apr 2018 22:22]
Leonardo Abraham Figueroa Tapia
Hello Umesh, My mysql instance still logging aborted connection whenever I hit the \q from mysqlshell. Do you know why am I getting this? Also the customer who I raised the bug on behalf from was seeing this behavior, any clue about that? SR - 3-17161610151
[8 May 2018 18:43]
Juan Rene Ramirez Monarrez
Posted by developer: This problem has been solved with a session handling refactoring done in 8.0
[9 May 2018 13:19]
Margaret Fisher
Posted by developer: Changelog entry added for MySQL Shell 8.0.12: When the \quit command was used to exit MySQL Shell, this event could be noted in the error log as an aborted connection. The issue has now been fixed.