Created attachment 910486 [details] log files for install Description of problem: 00:29:17.924 ERROR : Error appeared during Puppet run: 172.16.7.20_mysql.pp 00:29:17.924 Error: Could not start Service[mysqld]: Execution of '/sbin/service mysqld start' returned 1: MySQL Daemon failed to start. PuppetError: Error appeared during Puppet run: 172.16.7.20_mysql.pp Error: /Stage[main]/Mysql::Config/Exec[mysqld-restart]: Failed to call refresh: service mysqld restart returned 1 instead of one of [0][0m You will find full trace in log /var/tmp/packstack/20140619-124254-h4MshD/manifests/172.16.7.20_mysql.pp.log See attached logs for details
Review approved
When packstack installs mariadb, it edits /etc/my.cnf.d/innodb.cnf to change innodb_log_file_size. When mysqld starts, it looks at /var/lib/mysql/ib_logfile*. If they are not there, it will create them with innodb_log_file_size. If they are there and not the same size, it will error.
(In reply to Marius Palimariu from comment #2) > When packstack installs mariadb, it edits /etc/my.cnf.d/innodb.cnf to change > innodb_log_file_size. > When mysqld starts, it looks at /var/lib/mysql/ib_logfile*. If they are not > there, it will create them with innodb_log_file_size. If they are there and > not the same size, it will error. What we do is that on 6.5 we try to change innodb.cnf before mysql/maria starts and if we change innodb.cnf file it triggers exec to stop daemon, remove ib_log and notify restart. To be fair it's racy but atm there's no way to tell that the logs are of the required innodb_log_file_size (or I just don't know the way) so we just have to guess that we need to remove them.