MySQL Bugs: #26579: Agent error if user lacks SUPER privilege

Bug #26579	Agent error if user lacks SUPER privilege
Submitted:	22 Feb 2007 20:06	Modified:	8 May 2007 19:00
Reporter:	Kolbe Kegel	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Agent	Severity:	S3 (Non-critical)
Version:	1.1.0.4810	OS:	Linux (Linux)
Assigned to:	Jan Kneschke	CPU Architecture:	Any

Description:
If MySQL user used by Agent lacks the SUPER privilege, the Agent will be unable to execute SHOW INNODB STATUS. This will cause the Agent to write this to log/mysql-service-agent.log :

2007-02-22 11:40:00: (critical) agent/src/job_collect_mysql.c.320: I have no SHOW INNODB STATUS output ... strange

How to repeat:
obvious.

Suggested fix:
Agent should check this on install, check privileges before executing SHOW INNODB STATUS, write a more thorough and descriptive error message, etc.

A warning in the Dashboard that the Agent doesn't have enough privileges to execute this command, or even just a warning that a needed variable cannot be retrieved would be very helpful.

Jan has a patch but we will wait until 1.1.1 to commit it.

Re-opening for patch in 1.1.1

fix has been committed in rev [5195]

we now check at startup if SHOW INNODB STATUS succeeds and don't announce the items as collectable if not. 

This handles two cases:
- merlin account has no SUPER privileges
- mysqld is started with skip-innodb

tested OK with 1.1.1.5370

Added to the changelog.