Bug #39469 mysqladmin flush-logs doesnot open a new slow query log
Submitted: 16 Sep 2008 6:01 Modified: 16 Sep 2008 7:43
Reporter: kris dba Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server Severity:S2 (Serious)
Version:5.0.51a-log OS:Linux
Assigned to: CPU Architecture:Any
Tags: flush-logs, mysqladmin, slow_query.log

[16 Sep 2008 6:01] kris dba
Description:
I use mysqladmin flush-logs cmd to rotate mysql logs and open new log files.
however,doing mysqladmin flush-logs rotating all other logs like bin-log,error_log,etc. except slow_query.log.

How to repeat:
executing mysqladmin flush-logs # times doesnot create a new slow query log.
[16 Sep 2008 6:03] kris dba
currently no updates are happening to the slow log.
[16 Sep 2008 6:57] Sveta Smirnova
Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://dev.mysql.com/doc/ and the instructions on
how to report a bug at http://bugs.mysql.com/how-to-report.php

Please read at http://dev.mysql.com/doc/refman/5.0/en/log-file-maintenance.html about what a log flushing operation does: "If general query logging (--log) or slow query logging (--log-slow-queries) to a log file is enabled, the server closes and reopens the general query log file or slow query log file."
[16 Sep 2008 7:43] kris dba
Hi,
Thanks for the update.
I have followed the same steps mentioned in the documentation,slow query log is enabled on the server and Iam moving the current slow log file before doing flush-logs.

The command is successfully closing and opening all other mysql logs except the slow query log.
 
I have followed the same steps to rotate mysql logs previously,This is the first time Iam having issues with slow log.
[16 Sep 2008 8:12] Sveta Smirnova
Thank you for the feedback.

If I understood you correctly you complain about slow log does not recreates after it has moved. I can not repeat described behavior in my environment on Linux. Please upgrade to current version 5.0.67, try with it and if problem still exists provide us error log file.