Bug #44315 Make agent report back to advisors if it has insufficient privileges
Submitted: 16 Apr 2009 11:07 Modified: 17 Apr 2009 6:32
Reporter: Simon Mudd (OCA) Email Updates:
Status: Verified Impact on me:
Category:MySQL Enterprise Monitor: Agent Severity:S4 (Feature request)
Version: OS:FreeBSD
Assigned to: Assigned Account CPU Architecture:Any
Tags: splitme, windmill
Triage: Needs Triage: D5 (Feature request)

[16 Apr 2009 11:07] Simon Mudd
When trying the 2.1 server with the 2.0 agent I get the following error message in the agent logs:

2009-04-16 09:55:49: (critical) executing 'SHOW /*!50000 ENGINE */ INNODB STATUS' failed: Access denied; you need the PROCESS privilege for this operation

It seems that mysqld 5.1 requires more elevated privileges compared to the 5.0 version.

I would suggest that the agents (if they are able to login to the db) are able to report to the merlin server that they have insufficient privileges for "expected operations".

The advisors can then report this to the DBA or system administrator in order for the problem to be fixed.

How to repeat:

Suggested fix:
See description.
[17 Apr 2009 6:32] Valeriy Kravchuk
Thank you for the reasonable feature request.
[10 Jul 2009 9:45] Enterprise Tools JIRA Robot
Kay Roepke writes: 
Certain problems will be hard to report as DCs, especially errors about connecting to mysqld, because the agent might not have sufficient information to initiate a full resync at that point.
Later errors/warnings, after being synchronized and connected to the Service Manager, should be always possible to expose as DCs.
With a special REST interface to report the first category of problems, we might still be able to do it.
[15 Apr 2010 12:13] Enterprise Tools JIRA Robot
Mark Leith writes: 
We do these checks in the agent installer now - so this should be mostly covered. 

We will look in to doing further checks such as this in versions after 2.2.