Bug #30487 | mysql_upgrade mislead. errors / mysqlcheck 'You can't use locks with log table.' | ||
---|---|---|---|
Submitted: | 18 Aug 2007 1:32 | Modified: | 27 Aug 2007 9:27 |
Reporter: | Omer Barnir (OCA) | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: General | Severity: | S3 (Non-critical) |
Version: | 5.1.21,5.5.0m2 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | pushbuild, sporadic, test failure |
[18 Aug 2007 1:32]
Omer Barnir
[27 Aug 2007 9:27]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/33134 ChangeSet@1.2572, 2007-08-27 11:27:03+02:00, msvensson@pilot.(none) +1 -0 Bug#30487 mysql_upgrade reports misleading errors - Update result file to include these "misleading errors", better to run mysql_upgrade with them than not at all.
[4 Sep 2007 17:11]
Bugs System
Pushed into 5.1.23-beta
[5 Jan 2010 9:14]
Roel Van de Paar
Just had this on 5.5.0m2: ./mysqlcheck -uroot --check --all-databases --auto-repair [...] mysql.general_log Error : You can't use locks with log tables. status : OK mysql.help_category OK mysql.help_keyword OK mysql.help_relation OK mysql.help_topic OK mysql.host OK mysql.ndb_binlog_index OK mysql.plugin OK mysql.proc OK mysql.procs_priv OK mysql.servers OK mysql.slow_log Error : You can't use locks with log tables. status : OK [...] Any plans to fix?
[5 Aug 2010 9:19]
Sasi Levi
Happened to me on MySQL 5.1.49.
[2 Sep 2010 18:28]
Quanah Gibson-Mount
We are seeing this error with MySQL 5.1.48: Database errors found. /opt/zimbra/mysql/bin/mysqlcheck --defaults-file=/opt/zimbra/conf/my.cnf -S /opt/zimbra/db/mysql.sock -A -C -s -u root --password=xxxxxxxxxxxxxx mysql.general_log Error : You can't use locks with log tables. mysql.slow_log Error : You can't use locks with log tables. It looks like this should be re-opened.
[5 Oct 2010 8:36]
Susanne Ebrecht
Bug #43829 is set as duplicate of this bug here.