Comments - MariaDB is not starting with InnoDB.

1 year, 5 months ago Sandeep Sharma

Hi,

This is my log output. After my MariaDB crushed I have increase InnoDB buffer pool from 3G to 4G. It's not starting without this InnoDB buffer pool increase.

2019-11-18 13:48:34 140358717319360 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2019-11-18 13:48:34 140358717319360 [Note] InnoDB: Uses event mutexes 2019-11-18 13:48:34 140358717319360 [Note] InnoDB: Compressed tables use zlib 1.2.7 2019-11-18 13:48:34 140358717319360 [Note] InnoDB: Using Linux native AIO 2019-11-18 13:48:34 140358717319360 [Note] InnoDB: Number of pools: 1 2019-11-18 13:48:34 140358717319360 [Note] InnoDB: Using SSE2 crc32 instructions 2019-11-18 13:48:34 140358717319360 [Note] InnoDB: Initializing buffer pool, total size = 4G, instances = 4, chunk size = 128M 2019-11-18 13:48:35 140358717319360 [Note] InnoDB: Completed initialization of buffer pool 2019-11-18 13:48:35 140353619793664 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriori ty(). 2019-11-18 13:48:35 140358717319360 [ERROR] InnoDB: Log file ./ib_logfile1 is of different size 2147483648 bytes than other log files 3221225472 bytes! 2019-11-18 13:48:35 140358717319360 [ERROR] InnoDB: Plugin initialization aborted with error Generic error 2019-11-18 13:48:36 140358717319360 [Note] InnoDB: Starting shutdown... 2019-11-18 13:48:36 140358717319360 [ERROR] Plugin 'InnoDB' init function returned error. 2019-11-18 13:48:36 140358717319360 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2019-11-18 13:48:36 140358717319360 [Note] Plugin 'FEEDBACK' is disabled. 2019-11-18 13:48:36 140358717319360 [Note] Server socket created on IP: '127.0.0.1'. 2019-11-18 13:48:36 140358717319360 [Warning] 'user' entry 'root@hostname' ignored in --skip-name-resolve mode. 2019-11-18 13:48:36 140358717319360 [Warning] 'user' entry 'user@hostname' ignored in --skip-name-resolve mode. 2019-11-18 13:48:36 140358717319360 [Warning] 'user' entry 'user@hostname' ignored in --skip-name-resolve mode. 2019-11-18 13:48:36 140358717319360 [Warning] 'user' entry 'user@hostname' ignored in --skip-name-resolve mode. 2019-11-18 13:48:36 140358717319360 [Warning] 'user' entry 'user@hostname' ignored in --skip-name-resolve mode. 2019-11-18 13:48:36 140358717319360 [Warning] 'user' entry 'user@hostname' ignored in --skip-name-resolve mode. 2019-11-18 13:48:36 140358717319360 [Warning] 'user' entry 'user@hostname' ignored in --skip-name-resolve mode. 2019-11-18 13:48:36 140358717319360 [Warning] 'user' entry 'user@hostname' ignored in --skip-name-resolve mode. 2019-11-18 13:48:36 140358717319360 [Warning] 'user' entry 'user@hostname' ignored in --skip-name-resolve mode. 2019-11-18 13:48:36 140358717319360 [Warning] 'user' entry 'user@hostname' ignored in --skip-name-resolve mode. 2019-11-18 13:48:36 140358717319360 [Warning] 'user' entry 'user@hostname' ignored in --skip-name-resolve mode. 2019-11-18 13:48:36 140358717319360 [Warning] 'user' entry 'user@hostname' ignored in --skip-name-resolve mode.

Thanks, Sandeep Sharma

 
1 year, 5 months ago Sandeep Sharma

Also, I have moved the ib_logfile1 file to /tmp and restart again the MariaDB service. It gives me the below logs.

2019-11-18 13:57:27 140083691165888 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2019-11-18 13:57:27 140083691165888 [Note] InnoDB: Uses event mutexes 2019-11-18 13:57:27 140083691165888 [Note] InnoDB: Compressed tables use zlib 1.2.7 2019-11-18 13:57:27 140083691165888 [Note] InnoDB: Using Linux native AIO 2019-11-18 13:57:27 140083691165888 [Note] InnoDB: Number of pools: 1 2019-11-18 13:57:27 140083691165888 [Note] InnoDB: Using SSE2 crc32 instructions 2019-11-18 13:57:27 140083691165888 [Note] InnoDB: Initializing buffer pool, total size = 4G, instances = 4, chunk size = 128M 2019-11-18 13:57:27 140083691165888 [Note] InnoDB: Completed initialization of buffer pool 2019-11-18 13:57:27 140078597474048 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriori ty(). 2019-11-18 13:57:27 140083691165888 [Note] InnoDB: Highest supported file format is Barracuda. 2019-11-18 13:57:29 140083691165888 [Note] InnoDB: Upgrading redo log: 2*3221225472 bytes; LSN=82551713292 2019-11-18 13:57:29 140083691165888 [Note] InnoDB: Starting to delete and rewrite log files. 2019-11-18 13:57:30 140083691165888 [Note] InnoDB: Setting log file ./ib_logfile101 size to 3221225472 bytes 2019-11-18 13:57:30 140083691165888 [Note] InnoDB: Setting log file ./ib_logfile1 size to 3221225472 bytes 2019-11-18 13:57:30 140083691165888 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0 2019-11-18 13:57:30 140083691165888 [Note] InnoDB: New log files created, LSN=82551713292 2019-11-18 13:57:31 140083691165888 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2019-11-18 13:57:31 140083691165888 [ERROR] InnoDB: The error means the system cannot find the path specified. 2019-11-18 13:57:31 140083691165888 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2019-11-18 13:57:31 140083691165888 [ERROR] InnoDB: Cannot open datafile for read-only: './roundcube/attachments.ibd' OS error: 71 2019-11-18 13:57:31 140083691165888 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2019-11-18 13:57:31 140083691165888 [ERROR] InnoDB: The error means the system cannot find the path specified. 2019-11-18 13:57:31 140083691165888 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2019-11-18 13:57:31 140083691165888 [ERROR] InnoDB: Could not find a valid tablespace file for `roundcube/attachments`. Please refer to https://mariadb.com/kb/en/innodb- data-dictionary-troubleshooting/ for how to resolve the issue. 2019-11-18 13:57:31 140083691165888 [Warning] InnoDB: Ignoring tablespace for `roundcube`.`attachments` because it could not be opened. 2019-11-18 13:57:31 140083691165888 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2019-11-18 13:57:31 140083691165888 [ERROR] InnoDB: The error means the system cannot find the path specified. 2019-11-18 13:57:31 140083691165888 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2019-11-18 13:57:31 140083691165888 [ERROR] InnoDB: Cannot open datafile for read-only: './roundcube/cache.ibd' OS error: 71 2019-11-18 13:57:31 140083691165888 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2019-11-18 13:57:31 140083691165888 [ERROR] InnoDB: The error means the system cannot find the path specified. 2019-11-18 13:57:31 140083691165888 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2019-11-18 13:57:31 140083691165888 [ERROR] InnoDB: Could not find a valid tablespace file for `roundcube/cache`. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2019-11-18 13:57:31 140083691165888 [Warning] InnoDB: Ignoring tablespace for `roundcube`.`cache` because it could not be opened. 2019-11-18 13:57:31 140083691165888 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2019-11-18 13:57:31 140083691165888 [ERROR] InnoDB: The error means the system cannot find the path specified. 2019-11-18 13:57:31 140083691165888 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2019-11-18 13:57:31 140083691165888 [ERROR] InnoDB: Cannot open datafile for read-only: './roundcube/cache_index.ibd' OS error: 71 2019-11-18 13:57:31 140083691165888 [ERROR] InnoDB: Operating system error number 2 in a file operation.

Thanks, Sandeep Sharma

 
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.