Empty Slow Query Log Displays An Error

[Art van Scheppingen]

On most of our servers we implemented a log rotate script that will flush the log files, resulting in “empty” logfiles containing this:

Quote:

/usr/sbin/mysqld, Server version: 5.1.58-rel12.9-log Percona Server (GPL), 12.9, Revision 271. started with:

Tcp port: 3306 Unix socket: /var/lib/mysql/mysql.sock

Time Id Command Argument

But MONyog shows me this error:

Quote:

Error

No queries were found.

Make sure you have given valid slow query log file. Slow Query Log and General Query Log have different formats. Make sure you have entered the correct filename. Click here to review settings for this connection

If a query gets logged the error will go away.

The second line is correct, but the first and third line will actually confuse our DBAs.

Can you add an extra check if the slow log file contains the header info?

Thanks!

[Mahesh]

Actually this is generic message we are showing in-case there is no query logged or by mistake user has specified incorrect file path for slow log section mentioned “General log” file path and vice-versa.

I have added your request regarding 3rd line:

Code:

Make sure you have given valid slow query log file. Slow Query Log and General Query Log have different formats. Make sure you have entered the correct filename. Click here to review settings for this connection

Program should have extra check, whether mentioned file path belongs to slow log or general log respectively or any other invalid file path.

[Author]

Posts