[MXS-36] bugzillaId-671: wrong message if SHOW DATABASES privilege is missing Created: 2014-01-30  Updated: 2015-06-17  Resolved: 2015-04-28

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 1.0.2
Fix Version/s: 1.1.1

Type: Bug Priority: Minor
Reporter: Kolbe Kegel (Inactive) Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None
Environment:

All OS


 Description   

This is imported from bugzilla item: http://bugs.mariadb.com/show_bug.cgi?id=671

Description Kolbe Kegel 2014-12-30 22:35:45 UTC
If the SHOW DATABASES privilege is missing for the user MaxScale tries to use to get authentication information, this message is written to the MaxScale error log:

Dec 30 14:30:07 max1 MaxScale[19360]: RW Split Router: Unable to load database grant information, MaxScale authentication will proceed without including database permissions. To correct this GRANT select permission on msql.db to the user maxuser.

a) This message mis-spells "mysql" as "msql".
b) This message should refer to the SHOW DATABASES privilege instead of to SELECT on mysql.db.

 Comments   
Comment by Dipti Joshi (Inactive) [ 2015-03-10 ]

This is comment history imported from bugzilla

Mark Riddoch 2015-02-13 10:19:11 UTC
Fixed typo.

Query that is run is 

SELECT * FROM ( (SELECT COUNT(1) AS ndbs FROM
 
INFORMATION_SCHEMA.SCHEMATA) AS tbl1, 
(SELECT GRANTEE,PRIVILEGE_TYPE from INFORMATION_SCHEMA.USER_PRIVILEGES 
WHERE privilege_type='SHOW DATABASES' AND
 
 REPLACE(GRANTEE, \'\\'\',\'\')=CURRENT_USER()) AS tbl2)
 
 

It is this that is failing and not the later show databases.

Error message should be improved.

Comment by markus makela [ 2015-04-28 ]

Fixed by changing the error message to:

<service>: Unable to load database grant information, MaxScale authentication will proceed without including database permissions. To correct this GRANT SHOW DATABASES ON . privilege to the user <user>.

Comment by Timofey Turenko [ 2015-04-29 ]

checked manually, closing

Comment by Timofey Turenko [ 2015-05-12 ]

verified by manual check of error log content

Generated at Thu Feb 08 03:56:18 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.