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'm on a freshly installed macOS Sonoma 14.5 with the latest Docker Desktop. Whenever I run lando start or lando rebuild -y the MySQL server never seems to finalize booting. The error that pops up is [InnoDB] Assertion failure: log0recv.cc:1982:!page || (ibool) !!page_is_comp(page) == dict_table_is_comp(index->table) thread 140737052129024 which seems to be a corruption of the database but the database should be empty at that point because no migrations have been run yet. The machine itself doesn't run any kind of databases outside of Lando, so there shouldn't be any conflicts or issues that could arise from that.
Error
⚠ The service "database" failed its healthcheck
Failed with mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 2003 (HY000): Can't connect to MySQL server on 'database' (111)
lando logs -s database
database_1 | 2024-07-12T05:43:12.315706Z 0 [System] [MY-010116] [Server] /opt/bitnami/mysql/bin/mysqld (mysqld 8.0.19) starting as process 155
database_1 | 2024-07-12T05:43:12.326860Z 0 [Warning] [MY-013242] [Server] --character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.
database_1 | 2024-07-12T05:43:12.326968Z 0 [Warning] [MY-013244] [Server] --collation-server: 'utf8_general_ci' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.
database_1 | 2024-07-12T05:43:13.880448Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:1982:!page || (ibool) !!page_is_comp(page) == dict_table_is_comp(index->table) thread 140737052129024
database_1 | InnoDB: We intentionally generate a memory trap.
database_1 | InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
database_1 | InnoDB: If you get repeated assertion failures or crashes, even
database_1 | InnoDB: immediately after the mysqld startup, there may be
database_1 | InnoDB: corruption in the InnoDB tablespace. Please refer to
database_1 | InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
database_1 | InnoDB: about forcing recovery.
database_1 | /opt/bitnami/scripts/libos.sh: line 177: 155 Aborted "$@"
If you've ever started even an incomplete app with the same name, a data volume may already exist that it's trying to use. Try running lando destroy to wipe out the data volumes associated with this app.
Also, try narrowing the scope of the issue by starting with just the laravel recipe with no additional configuration to make sure that you can run that. Then add your additional configurations piece by piece, running lando destroy before each start until you find which part breaks things.
I'm on a freshly installed macOS Sonoma 14.5 with the latest Docker Desktop. Whenever I run
lando start
orlando rebuild -y
the MySQL server never seems to finalize booting. The error that pops up is[InnoDB] Assertion failure: log0recv.cc:1982:!page || (ibool) !!page_is_comp(page) == dict_table_is_comp(index->table) thread 140737052129024
which seems to be a corruption of the database but the database should be empty at that point because no migrations have been run yet. The machine itself doesn't run any kind of databases outside of Lando, so there shouldn't be any conflicts or issues that could arise from that.Error
lando logs -s database
my.cnf
.lando.yml
The text was updated successfully, but these errors were encountered: