Hello,
In MariaDB version 10.1.34, the F_DUPFD_CLOEXEC flag is used with FCNTL as part of the operation to create a temporary file during the InnoDB startup process. Kernel versions older than 2.6.24 do not support the F_DUPFD_CLOEXEC flag, and thus InnoDB will fail to start. The following line will appear in the MySQL error log (/var/lib/mysql/$hostname.err) during the MySQL startup process on affected systems:
You can run the following commands to confirm which kernel and MariaDB versions are installed on your system:
The recommended workaround is to update the kernel on the affected system to version 2.6.32 or newer. If you're using a VPS on an environment such as OpenVZ or Virtuozzo and you do not have access to the VPS hardware node, then you'll need to reach out to your VPS hosting provider to see if they can update the kernel at the node level.
Let us know if you have any questions.
Thank you.
In MariaDB version 10.1.34, the F_DUPFD_CLOEXEC flag is used with FCNTL as part of the operation to create a temporary file during the InnoDB startup process. Kernel versions older than 2.6.24 do not support the F_DUPFD_CLOEXEC flag, and thus InnoDB will fail to start. The following line will appear in the MySQL error log (/var/lib/mysql/$hostname.err) during the MySQL startup process on affected systems:
Code:
InnoDB: Error: unable to create temporary file; errno: 22
Code:
mysql --version
uname -r
Let us know if you have any questions.
Thank you.