BEGIN:VCALENDAR
PRODID:-//vBulletin 6//EN
VERSION:2.0
CALSCALE:GREGORIAN
BEGIN:VEVENT
UID:5cb793ab-452b-44d4-9ef7-0f81c5173542
DTSTAMP:20260523T174108Z
SUMMARY:Cannot open datafile for read-only: 'mysql.ibd' OS error: 71 (docke
 r compose upgrade)
DESCRIPTION:Hi. I`m trying to upgrade my docker compose installation of zab
 bix from version 4.0.4 to 7.2 (mysql form 5.7 to 8.4) and during the start
 up of mysql container I get the following log:\n\n\n2025-02-01 06:30:29+00
 :00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.4.4-1.el9 st
 arted.\n2025-02-01 06:30:31+00:00 [Note] [Entrypoint]: Switching to dedica
 ted user 'mysql'\n2025-02-01 06:30:31+00:00 [Note] [Entrypoint]: Entrypoin
 t script for MySQL Server 8.4.4-1.el9 started.\n'/var/lib/mysql/mysql.sock
 ' -> '/var/run/mysqld/mysqld.sock'\n2025-02-01T06:30:31.731664Z 0 [System]
  [MY-015015] [Server] MySQL Server - start.\n2025-02-01T06:30:31.918223Z 0
  [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.4.4) starting as
  process 1\n2025-02-01T06:30:31.991898Z 1 [System] [MY-013576] [InnoDB] In
 noDB initialization has started.\n2025-02-01T06:30:34.920488Z 1 [ERROR] [M
 Y-012592] [InnoDB] Operating system error number 2 in a file operation.\n2
 025-02-01T06:30:34.920554Z 1 [ERROR] [MY-012593] [InnoDB] The error means 
 the system cannot find the path specified.\n2025-02-01T06:30:34.920571Z 1 
 [ERROR] [MY-012216] [InnoDB] Cannot open datafile for read-only: 'mysql.ib
 d' OS error: 71\nmysqld: Can't open file: 'mysql.ibd' (errno: 0 - )\n2025-
 02-01T06:30:35.408233Z 1 [ERROR] [MY-010334] [Server] Failed to initialize
  DD Storage Engine\n2025-02-01T06:30:35.408431Z 0 [ERROR] [MY-010020] [Ser
 ver] Data Dictionary initialization failed.\n2025-02-01T06:30:35.408479Z 0
  [ERROR] [MY-010119] [Server] Aborting\n2025-02-01T06:30:35.409390Z 0 [Sys
 tem] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.4.
 4)  MySQL Community Server - GPL.\n2025-02-01T06:30:35.409462Z 0 [System] 
 [MY-015016] [Server] MySQL Server - end.\n\n\nI`m fairly sure that data di
 rectory for mysql is set properly as mysql is creating new some new files 
 during startup process:\n\n\n\n-rw-r----- 1 999 docker 56 Jan 30 2019 auto
 .cnf\n-rw-r----- 1 999 systemd-journal 0 Feb 1 07:30 binlog.index\n-rw----
 --- 1 999 docker 1679 Jan 30 2019 ca-key.pem\n-rw-r--r-- 1 999 docker 1107
  Jan 30 2019 ca.pem\n-rw-r--r-- 1 999 docker 1107 Jan 30 2019 client-cert.
 pem\n-rw------- 1 999 docker 1675 Jan 30 2019 client-key.pem\n-rw-r----- 1
  999 systemd-journal 6291456 Feb 1 11:18 '#ib_16384_0.dblwr'\n-rw-r----- 1
  999 systemd-journal 14680064 Feb 1 07:30 '#ib_16384_1.dblwr'\n-rw-r----- 
 1 999 systemd-journal 15566 Feb 1 06:37 ib_buffer_pool\n-rw-r----- 1 999 d
 ocker 79691776 Feb 1 11:18 ibdata1\ndrwxr-x--- 2 999 systemd-journal 4096 
 Feb 1 11:18 '#innodb_redo'\ndrwxr-x--- 2 999 systemd-journal 4096 Feb 1 11
 :18 '#innodb_temp'\ndrwxr-x--- 2 999 docker 4096 Jan 30 2019 mysql\nlrwxrw
 xrwx 1 999 systemd-journal 27 Feb 1 11:18 mysql.sock -> /var/run/mysqld/my
 sqld.sock\ndrwxr-x--- 2 999 docker 4096 Jan 30 2019 performance_schema\n-r
 w------- 1 999 docker 1675 Jan 30 2019 private_key.pem\n-rw-r--r-- 1 999 d
 ocker 451 Jan 30 2019 public_key.pem\n-rw-r--r-- 1 999 docker 1107 Jan 30 
 2019 server-cert.pem\n-rw------- 1 999 docker 1679 Jan 30 2019 server-key.
 pem\ndrwxr-x--- 2 999 docker 12288 Jan 30 2019 sys\n-rw-r----- 1 999 syste
 md-journal 16777216 Feb 1 07:30 undo_001\n-rw-r----- 1 999 systemd-journal
  16777216 Feb 1 07:30 undo_002\ndrwxr-x--- 2 999 docker 16384 Jan 30 2019 
 zabbix\n\nbut there is in fact no "mysql.ibd" file. How should I propoery 
 upgrade that database in this case?
URL:https://www.zabbix.com/forum/node/498321
DTSTART;VALUE=DATE:20250201
DTEND;VALUE=DATE:20250301
END:VEVENT
END:VCALENDAR