olindata / puppet-mariadb

A puppet module to manage mariadb
Apache License 2.0
2 stars 0 forks source link

my.cnf - innodb default causes errors on first deployment #5

Open grooverdan opened 12 years ago

grooverdan commented 12 years ago

The innodb defaults seem to create a confusion for the mysql server that sees a 1M innodb file and a 100M configuration option and barks.

The error caused on start up was:

InnoDB: The InnoDB memory heap is disabled InnoDB: Mutexes and rw_locks use GCC atomic builtins InnoDB: Compressed tables use zlib 1.2.3.4 120131 1:32:55 InnoDB: Initializing buffer pool, size = 700.0M 120131 1:32:55 InnoDB: Completed initialization of buffer pool InnoDB: Error: auto-extending data file /var/lib/mysql/ibdata1 is of a different size InnoDB: 640 pages (rounded down to MB) than specified in the .cnf file: InnoDB: initial 6400 pages, max 0 (relevant if non-zero) pages! InnoDB: Could not open or create data files. InnoDB: If you tried to add new data files, and it failed here, InnoDB: you should now edit innodb_data_file_path in my.cnf back InnoDB: to what it was, and remove the new ibdata files InnoDB created InnoDB: in this failed attempt. InnoDB only wrote those files full of InnoDB: zeros, but did not yet use them in any way. But be careful: do not InnoDB: remove old data files which contain your precious data!

walterheck commented 12 years ago

Different versions of mysql seem to have a different size here, ideas?