Bug #40933 | Agent unable to SELECT FROM mysql.inventory | ||
---|---|---|---|
Submitted: | 21 Nov 2008 17:26 | Modified: | 4 Mar 2009 9:52 |
Reporter: | Jonas Sundin | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Enterprise Monitor: Agent | Severity: | S3 (Non-critical) |
Version: | 2.0.0.7102 | OS: | Solaris (Solaris 10 5/08 s10x_u5wos_10 X86) |
Assigned to: | MC Brown | CPU Architecture: | Any |
[21 Nov 2008 17:26]
Jonas Sundin
[18 Dec 2008 20:23]
Mark Leith
We're looking at fixing the master_uuid stuff to make it work end to end on 2.0.x, so this needs doing as part of that work too. I think we need to be descriptive in the error (tell them that they need to GRANT SELECT ON mysql.inventory TO "user@host"; (filling in the user and host that are returned in the error), on the master server.
[3 Mar 2009 21:12]
Diego Medina
Verified fixed on 2.0.5.7148 We now see on the agent log (critical) job_collect_mysql.c:710: [devapps] (master-uuid) mysql_real_query(SELECT value FROM mysql.inventory WHERE name='uuid') failed: SELECT command denied to user 'slave'@'192.168.2.1' for table 'inventory' (1142) Check that mysql.inventory exists on this slave's master, if it does, run on the master: GRANT SELECT ON mysql.inventory TO 'slave'@'%';
[4 Mar 2009 9:52]
Tony Bedford
An entry was added to the 2.0.5 changelog: The Agent started without problems and connected to the master. But it was unable to perform a SELECT from the table mysql.inventory in order to obtain server information.