MySQL Bugs: #71629: mysqldiskusage cannot report log information with -a

Bug #71629	mysqldiskusage cannot report log information with -a
Submitted:	7 Feb 2014 16:40	Modified:	28 May 2016 2:01
Reporter:	Meiji Kimura	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Utilities	Severity:	S3 (Non-critical)
Version:	1.3.6	OS:	Windows
Assigned to:		CPU Architecture:	Any

Description:
mysqldiskusage can report logs information on POSIX environment.

But in MS Windows environment, it cannot report log information even if mysqldiskusage is executed with admin privilege.

How to repeat:
general_log & error_log said 'information is not accessible. Check your permissions.' even if the executor have root privilege.

C:\Program Files (x86)\MySQL\MySQL Utilities>mysqldiskusage --server=root:root@l
ocalhost:3306 -a
# Source on localhost: ... connected.
# Database totals:
+---------------------+-------------+
| db_name             |      total  |
+---------------------+-------------+
| mydb                | 406,979     |
| mysql               | 1,645,921   |
| performance_schema  | 510,023     |
| sakila              | 30,495,478  |
| test                | 15,810      |
| world               | 471,349     |
+---------------------+-------------+

Total database disk usage = 33,545,560 bytes or 31.99 MB

# Log information.
# general_log information is not accessible. Check your permissions.
# The slow_query_log is turned off on the server.
# log_error information is not accessible. Check your permissions.
# Binary logging is turned off on the server.
# Server is not an active slave - no relay log information.
# InnoDB tablespace information:
+--------------+----------------+
| innodb_file  |          size  |
+--------------+----------------+
| ib_logfile0  |    50,331,648  |
| ib_logfile1  |    50,331,648  |
| ibdata1      | 1,061,158,912  |
+--------------+----------------+

Total size of InnoDB files = 1,161,822,208 bytes or 1.08 GB

#...done.

Suggested fix:
It should display logs information like POSIX environment.

Please post the startup command for your server and/or the values in your configuration file so that we can attempt to reproduce.

Currently, you get the access error if the log is missing, not turned on, or if it is not accessible by the user running mysqldiskusage. We need to see your startup values for mysqld so we can determine if this is something unique to Windows.

Changing status to "Need Feedback"

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".