You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I did a docker-compose pull and now the database is not starting. Appears to be failing to find a file and upgrade as per the output:
2024-09-24 19:27:22+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.0.39-1.el9 started.
2024-09-24 19:27:22+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2024-09-24 19:27:22+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.0.39-1.el9 started.
'/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock'
2024-09-24T19:27:22.949773Z 0 [Warning] [MY-011068] [Server] The syntax '--skip-host-cache' is deprecated and will be removed in a future release. Please use SET GLOBAL host_cache_size=0 instead.
2024-09-24T19:27:22.951646Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.39) starting as process 1
2024-09-24T19:27:22.960145Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-09-24T19:27:23.180640Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2024-09-24T19:27:23.442696Z 1 [Warning] [MY-012351] [InnoDB] Tablespace 1, name 'sys/sys_config', file './sys/sys_config.ibd' is missing!
2024-09-24T19:27:24.013418Z 4 [System] [MY-013381] [Server] Server upgrade from '80036' to '80039' started.
2024-09-24T19:27:32.821139Z 4 [ERROR] [MY-012592] [InnoDB] Operating system error number 2 in a file operation.
2024-09-24T19:27:32.821185Z 4 [ERROR] [MY-012593] [InnoDB] The error means the system cannot find the path specified.
2024-09-24T19:27:32.821201Z 4 [ERROR] [MY-012216] [InnoDB] Cannot open datafile for read-only: './sys/sys_config.ibd' OS error: 71
2024-09-24T19:27:32.821350Z 4 [Warning] [MY-012049] [InnoDB] Cannot calculate statistics for table `sys`.`sys_config` because the .ibd file is missing. Please refer to http://dev.mysql.com/doc/refman/8.0/en/innodb-troubleshooting.html for how to resolve the issue.
2024-09-24T19:27:32.821445Z 4 [ERROR] [MY-013178] [Server] Execution of server-side SQL statement '-- Copyright (c) 2014, 2024, Oracle and/or its affiliates. -- -- This program is free software; you can redistribute it and/or modify -- it under the terms of the GNU General Public License as published by -- the Free Software Foundation; version 2 of the License. -- -- This program is distributed in the hope that it will be useful, -- but WITHOUT ANY WARRANTY; without even the implied warranty of -- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the -- GNU General Public License for more details. -- -- You should have received a copy of the GNU General Public License -- along with this program; if not, write to the Free Software -- Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA -- -- Table: sys_config -- -- Stores configuration options for sys objects -- CREATE TABLE IF NOT EXISTS sys_config ( variable VARCHAR(128) PRIMARY KEY, value VARCHAR(128), set_time TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, set_by VARCHAR(128) ) ENGINE = InnoDB; ' failed with error code = 1812, error message = 'Tablespace is missing for table `sys`.`sys_config`.'.
2024-09-24T19:27:32.825286Z 0 [ERROR] [MY-013380] [Server] Failed to upgrade server.
2024-09-24T19:27:32.825326Z 0 [ERROR] [MY-010119] [Server] Aborting
2024-09-24T19:27:34.392576Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.39) MySQL Community Server - GPL.
I have nothing custom done to this build - it's pretty much stock with minimal updates (because I'm scared an update will break it as it is sadly frequently experiencing issues after a pull). Any way to fix this without wiping DB and starting all over again? Thank you
EDIT: It would be awesome if there would be a script that can rebuild the database from scratch and apply the latest updates to it .. while exporting all user data and reimporting it after the rebuild. That would likely help resolve many people's DB issues (this is of course assuming running stock setup without any modifications to the DB).
The text was updated successfully, but these errors were encountered:
Hi Acore team,
I did a docker-compose pull and now the database is not starting. Appears to be failing to find a file and upgrade as per the output:
I have nothing custom done to this build - it's pretty much stock with minimal updates (because I'm scared an update will break it as it is sadly frequently experiencing issues after a pull). Any way to fix this without wiping DB and starting all over again? Thank you
EDIT: It would be awesome if there would be a script that can rebuild the database from scratch and apply the latest updates to it .. while exporting all user data and reimporting it after the rebuild. That would likely help resolve many people's DB issues (this is of course assuming running stock setup without any modifications to the DB).
The text was updated successfully, but these errors were encountered: