[MDEV-14736] Garbage in User/db field on connect Created: 2017-12-21  Updated: 2018-01-22  Resolved: 2018-01-22

Status: Closed
Project: MariaDB Server
Component/s: Server
Affects Version/s: 10.0.31
Fix Version/s: N/A

Type: Bug Priority: Critical
Reporter: Jan Vestergaard Assignee: Unassigned
Resolution: Incomplete Votes: 1
Labels: need_feedback


 Description   

We see a problem with version 10.0.31 when we connect to the database and use show full processlist or select database().

We then get information like this back

+-------+---------------+-----------------------------------+---------------+---------+------+-------+-----------------------+----------+
 
| Id    | User          | Host                              | db            | Command | Time | State | Info                  | Progress |
 
+-------+---------------+-----------------------------------+---------------+---------+------+-------+-----------------------+----------+
 
|  1714 | V�            | xxxxxx    | xxxxx        | Sleep   | 2532 |       | NULL                  |    0.000 |
 
| 26468 | e           | localhost                         | NULL          | Query   |    0 | init  | show full processlist |    0.000 |
 
+-------+---------------+-----------------------------------+---------------+---------+------+-------+-----------------------+----------+

For id 1714 it is a application user and id 26468 is root.

 Comments   
Comment by Jan Vestergaard [ 2017-12-21 ]

We found the problem. We found this in the errorlog

[ERROR] mysqld: File '/data/mysql-log/mysql-slow.log' not found (Errcode: 2 "No such file or directory")
 
[ERROR] Could not use /data/mysql-log/mysql-slow.log for logging (error 2). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.
 
[ERROR] mysqld: File '/data/mysql-log/mysql.log' not found (Errcode: 2 "No such file or directory")
 
[ERROR] Could not use /data/mysql-log/mysql.log for logging (error 2). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.

This was because the configuration for general_log_file and slow_query_log_file was wrong.

When the database started it crashed first and the started.

When we did a SELECT * FROM `information_schema`.`TABLES` and could crash the MySQL process.

After fixing the configuration and restart the MySQL process we did not see the problem anymore.

Comment by Elena Stepanova [ 2017-12-22 ]

Was it the only configuration change that you've made to get rid of the failures?
Strangely, I am not getting any problem even configuring the paths wrongly – logging simply gets turned off as it says.

What's your environment (OS, MariaDB packages and such)?
Could you please paste or attach your configuration file(s)?
Do you still have a stack trace from the crashes that you were getting upon reading from information_schema.TABLES?

Generated at Thu Feb 08 08:15:53 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.