Step 1 has been done. The bug (this bug) is marked as "fix released".
Step 2: The impact of the bug is that any user executing the "flush logs" command will experience a crash of the mysql server process that they send it to, if expire-log-days is enabled but log-bin is disabled in /etc/mysql/my.cnf. The logrotate process does this every day, and generates an error email as described above. I believe that in the development branch, it was addressed by updating to a more recent version of mysqld. My Hardy system has 5.0.51a- 3ubuntu5.4, the bug was fixed in 5.0.33. The exact, minimal patch that fixes this problem is here: http://lists.mysql.com/commits/15790 TEST CASE: enable expire_log_days and disable log-bin in /etc/my.cnf, restart mysqld, run mysqladmin flush-logs. The only regression potential that I can see in the patch is that a case where the SQL FLUSH LOGS statement might previously cause an error, when check_db_used(thd, all_tables) returns non-zero, no longer returns an error. I doubt that that is a significant regression. -- MySQL daemon crashes daily on logrotate's flush-logs https://bugs.launchpad.net/bugs/333813 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
