Starting MySQL daemon... Waiting for MySQL to be available... InnoDB: Error: auto-extending data file ./ibdata1 is of a different size InnoDB: 0 pages (rounded down to MB) than specified in the .cnf file: InnoDB: initial 640 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! 090720 21:22:07 [ERROR] /usr/libexec/mysqld: Incorrect information in file: './mysql/host.frm' 090720 21:22:07 [ERROR] /usr/libexec/mysqld: Incorrect information in file: './mysql/host.frm' 090720 21:22:07 [ERROR] Fatal error: Can't open and lock privilege tables: Incorrect information in file: './mysql/host.frm' Waiting for MySQL to be available... Waiting for MySQL to be available... Waiting for MySQL to be available... Waiting for MySQL to be available... Waiting for MySQL to be available... mysqladmin: connect to server at 'localhost' failed error: 'Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)' Check that mysqld is running and that the socket: '/tmp/mysql.sock' exists! Could not create bookmarks database rmdir: /onetimeinit: Directory not empty ERROR. An install-time config step failed.
This issue occurs because /var/log/mysqld and /var/log/mysqld.log are not removed from the appliance when factory_reset_tool is run. A workaround is available.
Workaround and Resolution:
Warning SonicWall strongly recommends that users not familiar or comfortable with the command line contact SonicWall product support for assistance. Use the command line at your own risk.
Please see KB item #2500 for some suggestions on enabling SSH access to the appliance and getting onto the command line.
From the command line of the appliance, run the following command: rm -rf /var/log/mysql*
Attempt the appliance upgrade again.
This knowledge item will be updated when the factory_reset_tool has been updated to clean up /var/log/mysqld and /var/log/mysqld.log.