hugowan / maatkit

Automatically exported from code.google.com/p/maatkit
0 stars 0 forks source link

mk-audit more out-of-sync false-positives #138

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
   PROBLEMS ______________________________________________________________
        - open_files_limit: online=16384 config=0
        - log_slow_queries: online=ON config=/var/log/mysql/slow.log
        - log_bin: online=ON config=mysql-bin.log

#1: open-files-limit is in my.cnf ... mk-audit should recognize that.

#2: log_bin & log_slow_queries will generally have differing values ...
That is just the nature of the beast:)
http://dev.mysql.com/doc/refman/5.0/en/server-options.html#option_mysqld_log-slo
w-queries

Original issue reported on code.google.com by ryan.a.l...@gmail.com on 30 Nov 2008 at 5:41

GoogleCodeExporter commented 9 years ago

Original comment by dan...@percona.com on 12 Dec 2008 at 4:50

GoogleCodeExporter commented 9 years ago
Target these for release end of January 2009.

Original comment by baron.schwartz on 4 Jan 2009 at 5:04

GoogleCodeExporter commented 9 years ago
I'm working on this.

Original comment by dan...@percona.com on 6 Jan 2009 at 5:04

GoogleCodeExporter commented 9 years ago
log_bin was fixed in issue 102 r2766. log_slow_queries is the same kind of var 
so
I'll handle it like log_bin and it'll be fixed too.

Other vars like open_file_limits, tmpdir, and innodb_log_group_home I will fix 
by
adding a new eq test function because these vars are such that if the config 
value is
undefined, then whatever the online value is is correct--it's the MySQL built-in
default. So, technically speaking, they're not out-of-sync, they're just 
default values.

Original comment by dan...@percona.com on 6 Jan 2009 at 5:29

GoogleCodeExporter commented 9 years ago
While I'm at it, I'll fix other little pathological cases like 2.2 being 
considered
out of sync with 2.20 (for long_query_time)...

Original comment by dan...@percona.com on 6 Jan 2009 at 5:59

GoogleCodeExporter commented 9 years ago
log_error is another notable case. It seems that in MySQL v4.1 and 5.0, if no 
config
val is given, then no online val is shown for log_error. But, in 5.1, if no 
config
val is given, then the default val is shown for online.

Original comment by dan...@percona.com on 6 Jan 2009 at 6:40

GoogleCodeExporter commented 9 years ago
Fixed in r2782.

Summary was "mk-audit: Non-Problems reported as problems"

Original comment by dan...@percona.com on 6 Jan 2009 at 7:09