Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Trivial
-
Resolution: Not a Bug
-
Affects Version/s: 5.5.45
-
Fix Version/s: N/A
-
Component/s: Documentation, Scripts & Clients
-
Labels:None
-
Environment:Server version: 5.5.45-MariaDB-1~trusty-log mariadb.org binary distribution
Distributor ID: Ubuntu
Description: Ubuntu 14.04.3 LTS
Release: 14.04
Codename: trusty
Description
I open a connection and run a few queries against a DB on localhost. About 571-597 seconds after the connection is established, I get the error:
Sep 25 16:08:20 HOSTNAME mysqld: 150925 16:08:20 [Warning] Aborted connection 126 to db: 'DB_NAME' user: 'USER' host: 'localhost' (Unknown error)
There don't seem to be any variables like '%timeout%' for this much time. The next time the client tries to run a query, I get the error:
oursql.OperationalError: (2006, 'MySQL server has gone away', None)
I don't have a MariaDB development environment setup, but most of the relevant code appears to be in less ./sql/sql_connect.cc.
while (thd_is_connection_alive(thd))
{ mysql_audit_release(thd); if (do_command(thd)) break; }end_connection(thd);
There don't seem to be any other logs around here. There are no other processes, and no queries, running on the mysql server.
Please let me know if I can provide any more information.
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Thanks for the fast response and the info!
I suggest MariaDB indicates a timeout rather than an unknown error. What do you think? If you agree, can you change this to a feature request?
Jeffrey Yunes
It would actually be a bug, not a feature request, but we already have it filed: MDEV-7775.
Jeffrey Yunes,
Given oursql.OperationalError, I assume we are talking not about the MySQL client, but about a non-interactive client.
Debian packages install my.cnf which, among other options, has wait_timeout=600. You cannot see this value when you are running show variables from inside an open MySQL client connection, because the value only has effect on non-interactive connections, for interactive ones it's overridden with interactive_timeout. But you can get it if you do mysql -e "show variables like '%timeout'".