Attachment 18002 Details for Bug 53371 – Лог mariadb без изменения директорий

Лог mariadb без изменения директорий

mysqld.log (text/x-log), 2.51 KB, created by Руслан Вишталмагомедов on 2025-03-17 13:10:27 MSK

(hide)

Description:

Filename:

MIME Type:

Creator: Руслан Вишталмагомедов

Created: 2025-03-17 13:10:27 MSK

Size: 2.51 KB

patch

obsolete

>2025-03-17 13:00:30 0 [Note] Starting MariaDB 11.4.5-MariaDB-alt1 source revision  server_uid kAJGKubqu5nMn2NKb0/CQx1pVPM= as process 4693
>2025-03-17 13:00:30 0 [Note] Plugin 'InnoDB' is disabled.
>2025-03-17 13:00:30 0 [Note] Plugin 'FEEDBACK' is disabled.
>2025-03-17 13:00:30 0 [Note] Plugin 'wsrep-provider' is disabled.
>2025-03-17 13:00:31 0 [Note] Starting MariaDB 11.4.5-MariaDB-alt1 source revision  server_uid kAJGKubqu5nMn2NKb0/CQx1pVPM= as process 5275
>2025-03-17 13:00:31 0 [Note] InnoDB: The first data file '/var/lib/mysql/ibdata1' did not exist. A new tablespace will be created!
>2025-03-17 13:00:31 0 [Note] InnoDB: Compressed tables use zlib 1.3.1
>2025-03-17 13:00:31 0 [Note] InnoDB: Number of transaction pools: 1
>2025-03-17 13:00:31 0 [Note] InnoDB: Using generic crc32 instructions
>2025-03-17 13:00:31 0 [Note] InnoDB: Using Linux native AIO
>2025-03-17 13:00:31 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
>2025-03-17 13:00:31 0 [Note] InnoDB: Completed initialization of buffer pool
>2025-03-17 13:00:31 0 [ERROR] InnoDB: File /var/lib/mysql/ibdata1 was not found
>2025-03-17 13:00:31 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
>2025-03-17 13:00:31 0 [ERROR] InnoDB: Error number 2 means 'No such file or directory'
>2025-03-17 13:00:31 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
>2025-03-17 13:00:31 0 [ERROR] InnoDB: Cannot open datafile '/var/lib/mysql/ibdata1'
>2025-03-17 13:00:31 0 [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!
>2025-03-17 13:00:31 0 [ERROR] InnoDB: Database creation was aborted with error Cannot open a file. You may need to delete the ibdata1 file before trying to start up again.
>2025-03-17 13:00:31 0 [Note] InnoDB: Starting shutdown...
>2025-03-17 13:00:31 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
>2025-03-17 13:00:31 0 [Note] Plugin 'FEEDBACK' is disabled.
>2025-03-17 13:00:31 0 [Note] Plugin 'wsrep-provider' is disabled.
>2025-03-17 13:00:31 0 [ERROR] Unknown/unsupported storage engine: InnoDB
>2025-03-17 13:00:31 0 [ERROR] Aborting

Actions: View

Attachments on bug 53371: 18002 | 18003