[SOLVED] Error : You can't use locks with log tables (after upgrade to ZCS OSE 7)

[phoenix]

I haven't seen this error yet, but rest assured I would be very upset if my root credentials would appear in an email to me as plain text.

Then use one of the solutions available in the forums if it bothers you that much.

[liverpoolfcfan]

I personally think that an warning message that is emailing out your root MySQL password is a critical issue! MySQL bug or not, you can certainly spend a few moments to at least filter it out for your users.

Seems they have gone to the trouble of spending that "few moments" for release 7.2

The locks error still exists - but they have masked the password.

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=XXXXXXXX
mysql.general_log
 Error    : You can't use locks with log tables.
 mysql.slow_log
 Error    : You can't use locks with log tables.

[bhwong]

I think you need to read what you've posted earlier.

I'll say it again, nobody from Zimbra has made such a statement in this thread (or on these forums).

But someone did make such statement in this thread:

The product that causes this problem is Open Source (as are most of the ZCS components), you're not paying for Zimbra to fix problems in third party products.

[phoenix]

But someone did make such statement in this thread:

I didn't say nobody had made that comment, what I was disagreeing with was your assertion that somebody 'from Zimbra' made that statement and nobody from Zimbra has even posted in this thread.

If you're talking about my comment earlier then I'm just another person posting here and I'm not 'from Zimbra'. Anyone who posts here does so voluntarily and in their free time, any comments made in these forums are the opinion of the person posting and do not represent official Zimbra (or VMware) policy.

If you think that your support contract entitles you to demand that Zimbra fixes bugs in third party products then file a report or open a support case, that would be the correct course of action.

[661]

Personally, I loath "error" messages that can be safely ignored; so I did something about it.

Please to enjoy...

  unless (open(CMD, "$cmd --password=${mysql_root_passwd} |")) {
    addToReport("can't run $cmd: $!\n");
    return undef;
  }
  my @output = <CMD>;

############################################
# BEGIN FILTER PATCH - zmdbintegrityreport
# If the ouput of mysqlcheck is the following, and ONLY the following, it
# may be safely ignored; so filter it out.  I'm sure there is a more
# elegant way to do this... but it works.

  my $filter = "mysql.general_log\n" .
               "Error    : You can't use locks with log tables.\n" .
               "mysql.slow_log\n" .
               "Error    : You can't use locks with log tables.\n";

  my $ouput2str = join("",@output);

  if (scalar @output != 0 && $ouput2str eq $filter) { @output = (); }

# END FILTER PATCH
############################################


  if (scalar @output != 0) {
    addToReport("Database errors found.\n");
    addToReport("$cmd --password=XXXXXXXX\n");
    addToReport("@output");
  } else {
    addToReport("No errors found\n") if $verbose;
  }