not reading correct innodb_log_file_size in mysql4.0 cnf file

[ts77]

I've got a mysql-4.0.27 setup on x86_64 which has the following in its my.cnf:
set-variable = innodb_log_file_size=512M
set-variable = innodb_log_files_in_group=2

xtrabackup incorrectly reports:
xtrabackup: innodb_log_files_in_group = 2
xtrabackup: innodb_log_file_size = 5242880
InnoDB: Error: log file /var/lib/mysql/ib_logfile0 is of different size 0 536870912 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!

changing my.cnf to
innodb_log_file_size=512M
innodb_log_files_in_group=2

solves this but I assume, that xtrabackup should read the set-variable settings too as mysql does.

[Robin Bowes (robinbowes)]

I've just hit this - to me it's a definite bug.

xtrabackup should read my.cnf *exactly* like mysql does.

[David Stainton (david-spinn3r)]

Greetings,

I noticed xtrabackup exits with an error message which indicates that it isn't picking up my innodb_log_file_size;
My my.cnf had: set-variable = innodb_log_file_size=524288000

This problem went away when I got rid of the "set-variable = " and only specified the variable=value like this:

innodb_log_file_size=524288000

I hope this helps!

Cheers,
David

[Peter Zaitsev (pz-percona)]

David,

I think this is item for documentation rather than to fix.
set-variable is not needed since MySQL 4.0 and I always clean up
my.cnf files once I get my hand on them if I see this option used.

On Mon, Nov 8, 2010 at 11:39 AM, David Stainton <email address hidden> wrote:

>
> Greetings,
>
> I noticed xtrabackup exits with an error message which indicates that it
> isn't picking up my innodb_log_file_size;
> My my.cnf had: set-variable = innodb_log_file_size=524288000
>
> This problem went away when I got rid of the "set-variable = " and only
> specified the variable=value like this:
>
> innodb_log_file_size=524288000
>
> I hope this helps!
>
> Cheers,
> David
>
> --
> not reading correct innodb_log_file_size in mysql4.0 cnf file
> https://bugs.launchpad.net/bugs/372054
> You received this bug notification because you are a member of Percona
> developers, which is the registrant for Percona-XtraBackup.
>
> Status in Open source backup tool for InnoDB and XtraDB: New
>
> Bug description:
> I've got a mysql-4.0.27 setup on x86_64 which has the following in its
> my.cnf:
> set-variable = innodb_log_file_size=512M
> set-variable = innodb_log_files_in_group=2
>
> xtrabackup incorrectly reports:
> xtrabackup: innodb_log_files_in_group = 2
> xtrabackup: innodb_log_file_size = 5242880
> InnoDB: Error: log file /var/lib/mysql/ib_logfile0 is of different size 0
> 536870912 bytes
> InnoDB: than specified in the .cnf file 0 5242880 bytes!
>
> changing my.cnf to
> innodb_log_file_size=512M
> innodb_log_files_in_group=2
>
> solves this but I assume, that xtrabackup should read the set-variable
> settings too as mysql does.
>
>
>

--
Peter Zaitsev, CEO, Percona Inc.
Tel: [phone] ext 501 Skype: peter_zaitsev
24/7 Emergency Line [phone] ext 911

Percona Training Workshops
http://www.percona.com/training/

[Vadim Tkachenko (vadim-tk)]

Assigned to Fred for documentation

[Baron Schwartz (baron-xaprb)]

I am documenting this limitation now.

[Baron Schwartz (baron-xaprb)]

Fred, I think this is documented -- please check me and close if you want:

http://www.percona.com/docs/wiki/percona-xtrabackup:xtrabackup:limitations
and
http://www.percona.com/docs/wiki/percona-xtrabackup:xtrabackup:configuration

On Tue, Nov 9, 2010 at 2:05 PM, Baron Schwartz <email address hidden> wrote:
> I am documenting this limitation now.

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-527