Quote:
Originally Posted by berndbausch
I should have told you to redirect the journalctl output to a file in order to obtain full lines. When you run journalctl at the command prompt, it truncates lines to the width of the terminal by default.
Still, I think the important part is
Code:
Jan 21 09:59:05 mysqld[1759]: InnoDB: If you get repeated assertion failures or crashes, even
Jan 21 09:59:05 mysqld[1759]: InnoDB: immediately after the mysqld startup, there may be
Jan 21 09:59:05 mysqld[1759]: InnoDB: corruption in the InnoDB tablespace. Please refer to
Jan 21 09:59:05 mysqld[1759]: InnoDB: http://dev.mysql.com/doc/refman/5.6/...-recovery.html
Jan 21 09:59:05 mysqld[1759]: InnoDB: about forcing recovery.
Since you do get repeated crashes, see if the referenced web page https://dev.mysql.com/doc/refman/5.6...-recovery.html helps.
Personally, my MySQL/MariaDB/InnoDB skill level is not really high, so that I am not sure what precisely is wrong here. |
Hi before that copy paste data is not good at all so i did copy all log data to txt file and now few of them is these.
Check maybe you can find any problem.
Jan 21 13:40:20 systemd[1]: Starting MariaDB 10.1.36 database server...
Jan 21 13:40:20 mysqld[5672]: 2020-01-21 13:40:20 140117621954816 [Note] /usr/sbin/mysqld (mysqld 10.1.36-MariaDB) starting as process 5672 ...
Jan 21 13:40:20 mysqld[5672]: 2020-01-21 13:40:20 140117621954816 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
Jan 21 13:40:20 mysqld[5672]: 2020-01-21 13:40:20 140117621954816 [Note] InnoDB: Using mutexes to ref count buffer pool pages
Jan 21 13:40:20 mysqld[5672]: 2020-01-21 13:40:20 140117621954816 [Note] InnoDB: The InnoDB memory heap is disabled
Jan 21 13:40:20 mysqld[5672]: 2020-01-21 13:40:20 140117621954816 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Jan 21 13:40:20 mysqld[5672]: 2020-01-21 13:40:20 140117621954816 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
Jan 21 13:40:20 mysqld[5672]: 2020-01-21 13:40:20 140117621954816 [Note] InnoDB: Compressed tables use zlib 1.2.7
Jan 21 13:40:20 mysqld[5672]: 2020-01-21 13:40:20 140117621954816 [Note] InnoDB: Using Linux native AIO
Jan 21 13:40:20 mysqld[5672]: 2020-01-21 13:40:20 140117621954816 [Note] InnoDB: Using SSE crc32 instructions
Jan 21 13:40:20 mysqld[5672]: 2020-01-21 13:40:20 140117621954816 [Note] InnoDB: Initializing buffer pool, size = 128.0M
Jan 21 13:40:20 mysqld[5672]: 2020-01-21 13:40:20 140117621954816 [Note] InnoDB: Completed initialization of buffer pool
Jan 21 13:40:20 mysqld[5672]: 2020-01-21 13:40:20 140117621954816 [ERROR] InnoDB: auto-extending data file ./ibdata1 is of a different size 0 pages (rounded down to MB) than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-zero) pages!
Jan 21 13:40:20 mysqld[5672]: 2020-01-21 13:40:20 140117621954816 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
Jan 21 13:40:20 mysqld[5672]: 2020-01-21 13:40:20 140117621954816 [ERROR] Plugin 'InnoDB' init function returned error.
Jan 21 13:40:20 mysqld[5672]: 2020-01-21 13:40:20 140117621954816 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Jan 21 13:40:20 mysqld[5672]: 2020-01-21 13:40:20 140117621954816 [Note] Plugin 'FEEDBACK' is disabled.
Jan 21 13:40:20 mysqld[5672]: 2020-01-21 13:40:20 140117621954816 [ERROR] Unknown/unsupported storage engine: InnoDB
Jan 21 13:40:20 mysqld[5672]: 2020-01-21 13:40:20 140117621954816 [ERROR] Aborting
Jan 21 13:40:21 systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
Jan 21 13:40:21 systemd[1]: Failed to start MariaDB 10.1.36 database server.
Jan 21 13:40:21 systemd[1]: Unit mariadb.service entered failed state.
Jan 21 13:40:21 systemd[1]: mariadb.service failed.
Jan 21 13:40:53 systemd[1]: Starting MariaDB 10.1.36 database server...
Jan 21 13:40:53 mysqld[5780]: 2020-01-21 13:40:53 140358232692992 [Note] /usr/sbin/mysqld (mysqld 10.1.36-MariaDB) starting as process 5780 ...
Jan 21 13:40:54 mysqld[5780]: 2020-01-21 13:40:54 140358232692992 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
Jan 21 13:40:54 mysqld[5780]: 2020-01-21 13:40:54 140358232692992 [Note] InnoDB: Using mutexes to ref count buffer pool pages
Jan 21 13:40:54 mysqld[5780]: 2020-01-21 13:40:54 140358232692992 [Note] InnoDB: The InnoDB memory heap is disabled
Jan 21 13:40:54 mysqld[5780]: 2020-01-21 13:40:54 140358232692992 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Jan 21 13:40:54 mysqld[5780]: 2020-01-21 13:40:54 140358232692992 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
Jan 21 13:40:54 mysqld[5780]: 2020-01-21 13:40:54 140358232692992 [Note] InnoDB: Compressed tables use zlib 1.2.7
Jan 21 13:40:54 mysqld[5780]: 2020-01-21 13:40:54 140358232692992 [Note] InnoDB: Using Linux native AIO
Jan 21 13:40:54 mysqld[5780]: 2020-01-21 13:40:54 140358232692992 [Note] InnoDB: Using SSE crc32 instructions
Jan 21 13:40:54 mysqld[5780]: 2020-01-21 13:40:54 140358232692992 [Note] InnoDB: Initializing buffer pool, size = 128.0M
Jan 21 13:40:54 mysqld[5780]: 2020-01-21 13:40:54 140358232692992 [Note] InnoDB: Completed initialization of buffer pool
Jan 21 13:40:54 mysqld[5780]: 2020-01-21 13:40:54 140358232692992 [ERROR] InnoDB: auto-extending data file ./ibdata1 is of a different size 0 pages (rounded down to MB) than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-zero) pages!
Jan 21 13:40:54 mysqld[5780]: 2020-01-21 13:40:54 140358232692992 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
Jan 21 13:40:54 mysqld[5780]: 2020-01-21 13:40:54 140358232692992 [ERROR] Plugin 'InnoDB' init function returned error.
Jan 21 13:40:54 mysqld[5780]: 2020-01-21 13:40:54 140358232692992 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Jan 21 13:40:54 mysqld[5780]: 2020-01-21 13:40:54 140358232692992 [Note] Plugin 'FEEDBACK' is disabled.
Jan 21 13:40:54 mysqld[5780]: 2020-01-21 13:40:54 140358232692992 [ERROR] Unknown/unsupported storage engine: InnoDB
Jan 21 13:40:54 mysqld[5780]: 2020-01-21 13:40:54 140358232692992 [ERROR] Aborting
Jan 21 13:40:54 systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
Jan 21 13:40:54 systemd[1]: Failed to start MariaDB 10.1.36 database server.
Jan 21 13:40:54 systemd[1]: Unit mariadb.service entered failed state.
Jan 21 13:40:54 systemd[1]: mariadb.service failed.
Jan 21 13:42:21 systemd[1]: Starting MariaDB 10.1.36 database server...
Jan 21 13:42:21 mysqld[6079]: 2020-01-21 13:42:21 140010481858816 [Note] /usr/sbin/mysqld (mysqld 10.1.36-MariaDB) starting as process 6079 ...
Jan 21 13:42:21 mysqld[6079]: 2020-01-21 13:42:21 140010481858816 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
Jan 21 13:42:21 mysqld[6079]: 2020-01-21 13:42:21 140010481858816 [Note] InnoDB: Started in read only mode
Jan 21 13:42:21 mysqld[6079]: 2020-01-21 13:42:21 140010481858816 [Note] InnoDB: Using mutexes to ref count buffer pool pages
Jan 21 13:42:21 mysqld[6079]: 2020-01-21 13:42:21 140010481858816 [Note] InnoDB: The InnoDB memory heap is disabled
Jan 21 13:42:21 mysqld[6079]: 2020-01-21 13:42:21 140010481858816 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Jan 21 13:42:21 mysqld[6079]: 2020-01-21 13:42:21 140010481858816 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
Jan 21 13:42:21 mysqld[6079]: 2020-01-21 13:42:21 140010481858816 [Note] InnoDB: Compressed tables use zlib 1.2.7
Jan 21 13:42:21 mysqld[6079]: 2020-01-21 13:42:21 140010481858816 [Note] InnoDB: Using Linux native AIO
Jan 21 13:42:21 mysqld[6079]: 2020-01-21 13:42:21 140010481858816 [Note] InnoDB: Using SSE crc32 instructions
Jan 21 13:42:21 mysqld[6079]: 2020-01-21 13:42:21 140010481858816 [Note] InnoDB: Disabling background IO write threads.
Jan 21 13:42:21 mysqld[6079]: 2020-01-21 13:42:21 140010481858816 [Note] InnoDB: Initializing buffer pool, size = 128.0M
Jan 21 13:42:21 mysqld[6079]: 2020-01-21 13:42:21 140010481858816 [Note] InnoDB: Completed initialization of buffer pool
Jan 21 13:42:21 mysqld[6079]: 2020-01-21 13:42:21 140010481858816 [ERROR] InnoDB: auto-extending data file ./ibdata1 is of a different size 0 pages (rounded down to MB) than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-zero) pages!
Jan 21 13:42:21 mysqld[6079]: 2020-01-21 13:42:21 140010481858816 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
Jan 21 13:42:21 mysqld[6079]: 2020-01-21 13:42:21 140010481858816 [ERROR] Plugin 'InnoDB' init function returned error.
Jan 21 13:42:21 mysqld[6079]: 2020-01-21 13:42:21 140010481858816 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Jan 21 13:42:21 mysqld[6079]: 2020-01-21 13:42:21 140010481858816 [Note] Plugin 'FEEDBACK' is disabled.
Jan 21 13:42:21 mysqld[6079]: 2020-01-21 13:42:21 140010481858816 [ERROR] Unknown/unsupported storage engine: InnoDB
Jan 21 13:42:21 mysqld[6079]: 2020-01-21 13:42:21 140010481858816 [ERROR] Aborting
Jan 21 13:42:21 systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
Jan 21 13:42:21 systemd[1]: Failed to start MariaDB 10.1.36 database server.
Jan 21 13:42:21 systemd[1]: Unit mariadb.service entered failed state.
Jan 21 13:42:21 systemd[1]: mariadb.service failed.
Jan 21 13:45:02 systemd[1]: Starting MariaDB 10.1.36 database server...
Jan 21 13:45:03 mysqld[6666]: 2020-01-21 13:45:03 139698683406592 [Note] /usr/sbin/mysqld (mysqld 10.1.36-MariaDB) starting as process 6666 ...
Jan 21 13:45:03 mysqld[6666]: 2020-01-21 13:45:03 139698683406592 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
Jan 21 13:45:03 mysqld[6666]: 2020-01-21 13:45:03 139698683406592 [Note] InnoDB: Started in read only mode
Jan 21 13:45:03 mysqld[6666]: 2020-01-21 13:45:03 139698683406592 [Note] InnoDB: Using mutexes to ref count buffer pool pages
Jan 21 13:45:03 mysqld[6666]: 2020-01-21 13:45:03 139698683406592 [Note] InnoDB: The InnoDB memory heap is disabled
Jan 21 13:45:03 mysqld[6666]: 2020-01-21 13:45:03 139698683406592 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Jan 21 13:45:03 mysqld[6666]: 2020-01-21 13:45:03 139698683406592 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
Jan 21 13:45:03 mysqld[6666]: 2020-01-21 13:45:03 139698683406592 [Note] InnoDB: Compressed tables use zlib 1.2.7
Jan 21 13:45:03 mysqld[6666]: 2020-01-21 13:45:03 139698683406592 [Note] InnoDB: Using Linux native AIO
Jan 21 13:45:03 mysqld[6666]: 2020-01-21 13:45:03 139698683406592 [Note] InnoDB: Using SSE crc32 instructions
Jan 21 13:45:03 mysqld[6666]: 2020-01-21 13:45:03 139698683406592 [Note] InnoDB: Disabling background IO write threads.
Jan 21 13:45:03 mysqld[6666]: 2020-01-21 13:45:03 139698683406592 [Note] InnoDB: Initializing buffer pool, size = 128.0M
Jan 21 13:45:03 mysqld[6666]: 2020-01-21 13:45:03 139698683406592 [Note] InnoDB: Completed initialization of buffer pool
Jan 21 13:45:03 mysqld[6666]: 2020-01-21 13:45:03 139698683406592 [ERROR] InnoDB: auto-extending data file ./ibdata1 is of a different size 0 pages (rounded down to MB) than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-zero) pages!
Jan 21 13:45:03 mysqld[6666]: 2020-01-21 13:45:03 139698683406592 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
Jan 21 13:45:03 mysqld[6666]: 2020-01-21 13:45:03 139698683406592 [ERROR] Plugin 'InnoDB' init function returned error.
Jan 21 13:45:03 mysqld[6666]: 2020-01-21 13:45:03 139698683406592 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Jan 21 13:45:03 mysqld[6666]: 2020-01-21 13:45:03 139698683406592 [Note] Plugin 'FEEDBACK' is disabled.
Jan 21 13:45:03 mysqld[6666]: 2020-01-21 13:45:03 139698683406592 [ERROR] Unknown/unsupported storage engine: InnoDB
Jan 21 13:45:03 mysqld[6666]: 2020-01-21 13:45:03 139698683406592 [ERROR] Aborting
Jan 21 13:45:03 systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
Jan 21 13:45:03 systemd[1]: Failed to start MariaDB 10.1.36 database server.
Jan 21 13:45:03 systemd[1]: Unit mariadb.service entered failed state.
Jan 21 13:45:03 systemd[1]: mariadb.service failed.
Jan 21 13:45:04 systemd[1]: Starting MariaDB 10.1.36 database server...
Jan 21 13:45:04 mysqld[6715]: 2020-01-21 13:45:04 139899987421440 [Note] /usr/sbin/mysqld (mysqld 10.1.36-MariaDB) starting as process 6715 ...
Jan 21 13:45:04 mysqld[6715]: 2020-01-21 13:45:04 139899987421440 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
Jan 21 13:45:04 mysqld[6715]: 2020-01-21 13:45:04 139899987421440 [Note] InnoDB: Started in read only mode
Jan 21 13:45:04 mysqld[6715]: 2020-01-21 13:45:04 139899987421440 [Note] InnoDB: Using mutexes to ref count buffer pool pages
Jan 21 13:45:04 mysqld[6715]: 2020-01-21 13:45:04 139899987421440 [Note] InnoDB: The InnoDB memory heap is disabled
Jan 21 13:45:04 mysqld[6715]: 2020-01-21 13:45:04 139899987421440 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Jan 21 13:45:04 mysqld[6715]: 2020-01-21 13:45:04 139899987421440 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
Jan 21 13:45:04 mysqld[6715]: 2020-01-21 13:45:04 139899987421440 [Note] InnoDB: Compressed tables use zlib 1.2.7
Jan 21 13:45:04 mysqld[6715]: 2020-01-21 13:45:04 139899987421440 [Note] InnoDB: Using Linux native AIO
Jan 21 13:45:04 mysqld[6715]: 2020-01-21 13:45:04 139899987421440 [Note] InnoDB: Using SSE crc32 instructions
Jan 21 13:45:04 mysqld[6715]: 2020-01-21 13:45:04 139899987421440 [Note] InnoDB: Disabling background IO write threads.
Jan 21 13:45:04 mysqld[6715]: 2020-01-21 13:45:04 139899987421440 [Note] InnoDB: Initializing buffer pool, size = 128.0M
Jan 21 13:45:04 mysqld[6715]: 2020-01-21 13:45:04 139899987421440 [Note] InnoDB: Completed initialization of buffer pool
Jan 21 13:45:04 mysqld[6715]: 2020-01-21 13:45:04 139899987421440 [ERROR] InnoDB: auto-extending data file ./ibdata1 is of a different size 0 pages (rounded down to MB) than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-zero) pages!
Jan 21 13:45:04 mysqld[6715]: 2020-01-21 13:45:04 139899987421440 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
Jan 21 13:45:04 mysqld[6715]: 2020-01-21 13:45:04 139899987421440 [ERROR] Plugin 'InnoDB' init function returned error.
Jan 21 13:45:04 mysqld[6715]: 2020-01-21 13:45:04 139899987421440 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Jan 21 13:45:04 mysqld[6715]: 2020-01-21 13:45:04 139899987421440 [Note] Plugin 'FEEDBACK' is disabled.
Jan 21 13:45:04 mysqld[6715]: 2020-01-21 13:45:04 139899987421440 [ERROR] Unknown/unsupported storage engine: InnoDB
Jan 21 13:45:04 mysqld[6715]: 2020-01-21 13:45:04 139899987421440 [ERROR] Aborting
Jan 21 13:45:06 systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
Jan 21 13:45:06 systemd[1]: Failed to start MariaDB 10.1.36 database server.
Jan 21 13:45:06 systemd[1]: Unit mariadb.service entered failed state.
Jan 21 13:45:06 systemd[1]: mariadb.service failed.
Jan 21 13:50:53 systemd[1]: Starting MariaDB 10.1.36 database server...
Jan 21 13:50:53 mysqld[7966]: 2020-01-21 13:50:53 139911771351296 [Note] /usr/sbin/mysqld (mysqld 10.1.36-MariaDB) starting as process 7966 ...
Jan 21 13:50:53 mysqld[7966]: 2020-01-21 13:50:53 139911771351296 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
Jan 21 13:50:54 mysqld[7966]: 2020-01-21 13:50:54 139911771351296 [Note] InnoDB: Using mutexes to ref count buffer pool pages
Jan 21 13:50:54 mysqld[7966]: 2020-01-21 13:50:54 139911771351296 [Note] InnoDB: The InnoDB memory heap is disabled
Jan 21 13:50:54 mysqld[7966]: 2020-01-21 13:50:54 139911771351296 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Jan 21 13:50:54 mysqld[7966]: 2020-01-21 13:50:54 139911771351296 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
Jan 21 13:50:54 mysqld[7966]: 2020-01-21 13:50:54 139911771351296 [Note] InnoDB: Compressed tables use zlib 1.2.7
Jan 21 13:50:54 mysqld[7966]: 2020-01-21 13:50:54 139911771351296 [Note] InnoDB: Using Linux native AIO
Jan 21 13:50:54 mysqld[7966]: 2020-01-21 13:50:54 139911771351296 [Note] InnoDB: Using SSE crc32 instructions
Jan 21 13:50:54 mysqld[7966]: 2020-01-21 13:50:54 139911771351296 [Note] InnoDB: Initializing buffer pool, size = 128.0M
Jan 21 13:50:54 mysqld[7966]: 2020-01-21 13:50:54 139911771351296 [Note] InnoDB: Completed initialization of buffer pool
Jan 21 13:50:54 mysqld[7966]: 2020-01-21 13:50:54 139911771351296 [ERROR] InnoDB: auto-extending data file ./ibdata1 is of a different size 0 pages (rounded down to MB) than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-zero) pages!
Jan 21 13:50:54 mysqld[7966]: 2020-01-21 13:50:54 139911771351296 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
Jan 21 13:50:54 mysqld[7966]: 2020-01-21 13:50:54 139911771351296 [ERROR] Plugin 'InnoDB' init function returned error.
Jan 21 13:50:54 mysqld[7966]: 2020-01-21 13:50:54 139911771351296 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Jan 21 13:50:54 mysqld[7966]: 2020-01-21 13:50:54 139911771351296 [Note] Plugin 'FEEDBACK' is disabled.
Jan 21 13:50:54 mysqld[7966]: 2020-01-21 13:50:54 139911771351296 [ERROR] Unknown/unsupported storage engine: InnoDB
Jan 21 13:50:54 mysqld[7966]: 2020-01-21 13:50:54 139911771351296 [ERROR] Aborting
Jan 21 13:50:54 systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
Jan 21 13:50:54 systemd[1]: Failed to start MariaDB 10.1.36 database server.
Jan 21 13:50:54 systemd[1]: Unit mariadb.service entered failed state.
Jan 21 13:50:54 systemd[1]: mariadb.service failed.
Jan 21 14:00:01 systemd[1]: Starting MariaDB 10.1.36 database server...
Jan 21 14:00:01 systemd[1]: Stopped MariaDB 10.1.36 database server.
Jan 21 14:00:03 systemd[1]: Starting MariaDB 10.1.36 database server...
Jan 21 14:00:03 mysqld[9849]: 2020-01-21 14:00:03 140602217711872 [Note] /usr/sbin/mysqld (mysqld 10.1.36-MariaDB) starting as process 9849 ...
Jan 21 14:00:03 mysqld[9849]: 2020-01-21 14:00:03 140602217711872 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
Jan 21 14:00:03 mysqld[9849]: 2020-01-21 14:00:03 140602217711872 [Note] InnoDB: Using mutexes to ref count buffer pool pages
Jan 21 14:00:03 mysqld[9849]: 2020-01-21 14:00:03 140602217711872 [Note] InnoDB: The InnoDB memory heap is disabled
Jan 21 14:00:03 mysqld[9849]: 2020-01-21 14:00:03 140602217711872 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Jan 21 14:00:03 mysqld[9849]: 2020-01-21 14:00:03 140602217711872 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
Jan 21 14:00:03 mysqld[9849]: 2020-01-21 14:00:03 140602217711872 [Note] InnoDB: Compressed tables use zlib 1.2.7
Jan 21 14:00:03 mysqld[9849]: 2020-01-21 14:00:03 140602217711872 [Note] InnoDB: Using Linux native AIO
Jan 21 14:00:03 mysqld[9849]: 2020-01-21 14:00:03 140602217711872 [Note] InnoDB: Using SSE crc32 instructions
Jan 21 14:00:03 mysqld[9849]: 2020-01-21 14:00:03 140602217711872 [Note] InnoDB: Initializing buffer pool, size = 128.0M
Jan 21 14:00:03 mysqld[9849]: 2020-01-21 14:00:03 140602217711872 [Note] InnoDB: Completed initialization of buffer pool
Jan 21 14:00:03 mysqld[9849]: 2020-01-21 14:00:03 140602217711872 [ERROR] InnoDB: auto-extending data file ./ibdata1 is of a different size 0 pages (rounded down to MB) than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-zero) pages!
Jan 21 14:00:03 mysqld[9849]: 2020-01-21 14:00:03 140602217711872 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
Jan 21 14:00:03 mysqld[9849]: 2020-01-21 14:00:03 140602217711872 [ERROR] Plugin 'InnoDB' init function returned error.
Jan 21 14:00:03 mysqld[9849]: 2020-01-21 14:00:03 140602217711872 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Jan 21 14:00:03 mysqld[9849]: 2020-01-21 14:00:03 140602217711872 [Note] Plugin 'FEEDBACK' is disabled.
Jan 21 14:00:03 mysqld[9849]: 2020-01-21 14:00:03 140602217711872 [Note] Server socket created on IP: '::'.
Jan 21 14:00:03 mysqld[9849]: 2020-01-21 14:00:03 140602217302784 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1286: Unknown storage engine 'InnoDB'
Jan 21 14:00:03 mysqld[9849]: 2020-01-21 14:00:03 140602217711872 [Note] /usr/sbin/mysqld: ready for connections.
Jan 21 14:00:03 mysqld[9849]: Version: '10.1.36-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
Jan 21 14:00:03 systemd[1]: Started MariaDB 10.1.36 database server.
