The Ultimate Guide to High Availability with MariaDB

Error with standard Windows setup

Hi

I'm new to Maria, having issues with installation onto Win 10 machine. I ran mariadb-10.1.22-winx64.msi with standard installation options. I get the following error when i try and run

C:\Program Files\MariaDB 10.1\bin>mysqld.exe --datadir=..\data --console
2017-04-02 22:56:54 6700 [Note] mysqld.exe (mysqld 10.1.22-MariaDB) starting as process 1008 ...
2017-04-02 22:56:54 6700 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-04-02 22:56:54 6700 [Note] InnoDB: The InnoDB memory heap is disabled
2017-04-02 22:56:54 6700 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-04-02 22:56:54 6700 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-04-02 22:56:54 6700 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-04-02 22:56:54 6700 [Note] InnoDB: Using generic crc32 instructions
2017-04-02 22:56:54 6700 [Note] InnoDB: Initializing buffer pool, size = 1006.0M
2017-04-02 22:56:54 6700 [Note] InnoDB: Completed initialization of buffer pool
2017-04-02 22:56:54 6700 [ERROR] InnoDB: .\ibdata1 can't be opened in read-write mode
2017-04-02 22:56:54 6700 [ERROR] InnoDB: The system tablespace must be writable!
2017-04-02 22:56:54 6700 [ERROR] Plugin 'InnoDB' init function returned error.
2017-04-02 22:56:54 6700 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-04-02 22:56:54 6700 [Note] Plugin 'FEEDBACK' is disabled.
2017-04-02 22:56:54 6700 [ERROR] Unknown/unsupported storage engine: innodb
2017-04-02 22:56:54 6700 [ERROR] Aborting

I assume because C:\Program Files\MariaDB 10.1\data\ibdata1 has been created with the wrong permissions?

Seems a basic requirement for the installer to create files with appropriate permissions. I followed installation instructions https://mariadb.com/kb/en/mariadb/installing-mariadb-msi-packages-on-windows/

Google search suggests its a permissions issue under Program Files, but i'm confused why the installer would choose default locations that are problematic

Thanks for any help

Answer Answered by Vladislav Vaintroub in this comment.

You do not have to start the mysqld manually, it is already startedas service after your installation. The files cannot be opened in read-write because they are already opened in read-write mode by the existing running mysqld.exe.

Comments

Comments loading...
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.