search

lando / drupal

The Official Drupal Lando plugin
https://docs.lando.dev/drupal
GNU General Public License v3.0
15 stars 16 forks source link

Problem with database. I can't start the app #102

Closed drale1 closed 5 months ago

drale1 commented 5 months ago

I'm working with Lando v3.21.0-beta.12. And I think issue started after update to this version.

After lando start on my Drupal app I'm getting this message

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)"

After lando logs -s database I get this:

➜ d10-minimal lando logs -s database database_1 | database_1 | database_1 | database_1 | STARTING UP
database_1 | database_1 | ██  █████  ███  ██ ██████  ██████ 
database_1 | ██  ██   ██ ████  ██ ██   ██ ██    ██ 
database_1 | ██  ███████ ██ ██  ██ ██  ██ ██  ██ 
database_1 | ██  ██   ██ ██  ██ ██ ██  ██ ██  ██ 
database_1 | ███████ ██  ██ ██   ████ ██████   ██████  
database_1 | database_1 | The best local development tool in the galaxy!
database_1 | database_1 | database_1 | =============================================================== database_1 | database_1 | database_1 | userperms 06:27:23.78 WARN ==> Only the root user can reset permissions! This is probably ok though... database_1 | loadkeys 06:27:23.79 WARN ==> Only the root user can load ssh keys! This is probably ok though... database_1 | lando 06:27:23.80 INFO ==> Lando handing off to: /launch.sh database_1 | lando 06:27:23.80 DEBUG ==> Running command with exec... database_1 | mysql 06:27:23.90 database_1 | mysql 06:27:23.91 Welcome to the Bitnami mysql container database_1 | mysql 06:27:23.91 Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-mysql database_1 | mysql 06:27:23.91 Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-mysql/issues database_1 | mysql 06:27:23.91 Send us your feedback at containers@bitnami.com database_1 | mysql 06:27:23.91 database_1 | mysql 06:27:23.91 INFO ==> Starting MySQL setup database1 | mysql 06:27:23.98 INFO ==> Validating settings in MYSQL/MARIADB_ env vars database_1 | mysql 06:27:23.99 WARN ==> You set the environment variable ALLOW_EMPTY_PASSWORD=yes. For safety reasons, do not use this flag in a production environment. database_1 | mysql 06:27:24.00 INFO ==> Initializing mysql database database_1 | mysql 06:27:24.01 DEBUG ==> Injecting custom configuration from my_custom.conf database_1 | mysql 06:27:24.02 DEBUG ==> Ensuring expected directories/files exist database_1 | mysql 06:27:24.03 DEBUG ==> Creating main configuration file database_1 | mysql 06:27:24.03 INFO ==> Using persisted data database_1 | mysql 06:27:24.05 INFO ==> Running mysql_upgrade database_1 | mysql 06:27:24.06 INFO ==> Starting mysql in background database_1 | 2024-04-02T06:27:24.267989Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled database_1 | 2024-04-02T06:27:24.268056Z 0 [Note] /opt/bitnami/mysql/bin/mysqld (mysqld 5.7.29) starting as process 157 ... database_1 | 2024-04-02T06:27:24.338693Z 0 [Note] InnoDB: PUNCH HOLE support available database_1 | 2024-04-02T06:27:24.338742Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins database_1 | 2024-04-02T06:27:24.338747Z 0 [Note] InnoDB: Uses event mutexes database_1 | 2024-04-02T06:27:24.338748Z 0 [Note] InnoDB: GCC builtin atomic_thread_fence() is used for memory barrier database_1 | 2024-04-02T06:27:24.338750Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 database_1 | 2024-04-02T06:27:24.338752Z 0 [Note] InnoDB: Using Linux native AIO database_1 | 2024-04-02T06:27:24.338936Z 0 [Note] InnoDB: Number of pools: 1 database_1 | 2024-04-02T06:27:24.339066Z 0 [Note] InnoDB: Using CPU crc32 instructions database_1 | 2024-04-02T06:27:24.341458Z 0 [Note] InnoDB: Initializing buffer pool, total size = 384M, instances = 1, chunk size = 128M database_1 | 2024-04-02T06:27:24.366578Z 0 [Note] InnoDB: Completed initialization of buffer pool database_1 | 2024-04-02T06:27:24.372986Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). database_1 | 2024-04-02T06:27:24.390603Z 0 [Note] InnoDB: Highest supported file format is Barracuda. database_1 | 2024-04-02T06:27:24.422358Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 66453270 database_1 | 2024-04-02T06:27:24.422398Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 66453279 database_1 | 2024-04-02T06:27:24.422404Z 0 [Note] InnoDB: Database was not shutdown normally! database_1 | 2024-04-02T06:27:24.422406Z 0 [Note] InnoDB: Starting crash recovery. database_1 | 2024-04-02T06:27:24.646182Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables database_1 | 2024-04-02T06:27:24.646449Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... database_1 | 2024-04-02T06:27:24.646627Z 0 [Warning] InnoDB: Retry attempts for writing partial data failed. database_1 | 2024-04-02T06:27:24.646706Z 0 [ERROR] InnoDB: Write to file ./ibtmp1failed at offset 0, 1048576 bytes should have been written, only 0 were written. Operating system error number 28. Check that your OS and file system support files of this size. Check also that the disk is not full or a disk quota exceeded. database_1 | 2024-04-02T06:27:24.646752Z 0 [ERROR] InnoDB: Error number 28 means 'No space left on device' database_1 | 2024-04-02T06:27:24.646758Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html database_1 | 2024-04-02T06:27:24.646762Z 0 [ERROR] InnoDB: Could not set the file size of './ibtmp1'. Probably out of disk space database_1 | 2024-04-02T06:27:24.646764Z 0 [ERROR] InnoDB: Unable to create the shared innodb_temporary database_1 | 2024-04-02T06:27:24.646766Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error database_1 | 2024-04-02T06:27:25.147831Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" database_1 | 2024-04-02T06:27:25.147917Z 0 [ERROR] Plugin 'InnoDB' init function returned error. database_1 | 2024-04-02T06:27:25.147923Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. database_1 | 2024-04-02T06:27:25.147927Z 0 [ERROR] Failed to initialize builtin plugins. database_1 | 2024-04-02T06:27:25.147928Z 0 [ERROR] Aborting database_1 | database_1 | 2024-04-02T06:27:25.147931Z 0 [Note] Binlog end database_1 | 2024-04-02T06:27:25.147969Z 0 [Note] Shutting down plugin 'CSV' database_1 | 2024-04-02T06:27:25.153716Z 0 [Note] /opt/bitnami/mysql/bin/mysqld: Shutdown complete database_1 | database_1 | userperms 06:31:40.29 WARN ==> Only the root user can reset permissions! This is probably ok though... database_1 | loadkeys 06:31:40.32 WARN ==> Only the root user can load ssh keys! This is probably ok though... database_1 | lando 06:31:40.32 INFO ==> Lando handing off to: /launch.sh database_1 | lando 06:31:40.33 DEBUG ==> Running command with exec... database_1 | mysql 06:31:40.43 database_1 | mysql 06:31:40.43 Welcome to the Bitnami mysql container database_1 | mysql 06:31:40.43 Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-mysql database_1 | mysql 06:31:40.43 Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-mysql/issues database_1 | mysql 06:31:40.43 Send us your feedback at containers@bitnami.com database_1 | mysql 06:31:40.43 database_1 | mysql 06:31:40.44 INFO ==> Starting MySQL setup database1 | mysql 06:31:40.53 INFO ==> Validating settings in MYSQL/MARIADB_ env vars database_1 | mysql 06:31:40.53 WARN ==> You set the environment variable ALLOW_EMPTY_PASSWORD=yes. For safety reasons, do not use this flag in a production environment. database_1 | mysql 06:31:40.54 INFO ==> Initializing mysql database database_1 | mysql 06:31:40.54 DEBUG ==> Injecting custom configuration from my_custom.conf database_1 | mysql 06:31:40.55 DEBUG ==> Custom configuration my.cnf detected database_1 | mysql 06:31:40.55 DEBUG ==> Ensuring expected directories/files exist database_1 | mysql 06:31:40.57 INFO ==> Using persisted data database_1 | mysql 06:31:40.61 INFO ==> Running mysql_upgrade database_1 | mysql 06:31:40.61 INFO ==> Starting mysql in background database_1 | 2024-04-02T06:31:40.978495Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled database_1 | 2024-04-02T06:31:40.979381Z 0 [Note] /opt/bitnami/mysql/bin/mysqld (mysqld 5.7.29) starting as process 155 ... database_1 | 2024-04-02T06:31:41.128367Z 0 [Note] InnoDB: PUNCH HOLE support available database_1 | 2024-04-02T06:31:41.128389Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins database_1 | 2024-04-02T06:31:41.128391Z 0 [Note] InnoDB: Uses event mutexes database_1 | 2024-04-02T06:31:41.128393Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier database_1 | 2024-04-02T06:31:41.128395Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 database_1 | 2024-04-02T06:31:41.128397Z 0 [Note] InnoDB: Using Linux native AIO database_1 | 2024-04-02T06:31:41.129872Z 0 [Note] InnoDB: Number of pools: 1 database_1 | 2024-04-02T06:31:41.131720Z 0 [Note] InnoDB: Using CPU crc32 instructions database_1 | 2024-04-02T06:31:41.136840Z 0 [Note] InnoDB: Initializing buffer pool, total size = 384M, instances = 1, chunk size = 128M database_1 | 2024-04-02T06:31:41.200043Z 0 [Note] InnoDB: Completed initialization of buffer pool database_1 | 2024-04-02T06:31:41.216736Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). database_1 | 2024-04-02T06:31:41.236533Z 0 [Note] InnoDB: Highest supported file format is Barracuda. database_1 | 2024-04-02T06:31:41.241489Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 66453270 database_1 | 2024-04-02T06:31:41.241580Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 66453279 database_1 | 2024-04-02T06:31:41.241614Z 0 [Note] InnoDB: Database was not shutdown normally! database_1 | 2024-04-02T06:31:41.241632Z 0 [Note] InnoDB: Starting crash recovery. database_1 | 2024-04-02T06:31:41.479711Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables database_1 | 2024-04-02T06:31:41.479764Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... database_1 | 2024-04-02T06:31:41.481099Z 0 [Warning] InnoDB: Retry attempts for writing partial data failed. database_1 | 2024-04-02T06:31:41.481131Z 0 [ERROR] InnoDB: Write to file ./ibtmp1failed at offset 0, 1048576 bytes should have been written, only 0 were written. Operating system error number 28. Check that your OS and file system support files of this size. Check also that the disk is not full or a disk quota exceeded. database_1 | 2024-04-02T06:31:41.481147Z 0 [ERROR] InnoDB: Error number 28 means 'No space left on device' database_1 | 2024-04-02T06:31:41.481193Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html database_1 | 2024-04-02T06:31:41.481201Z 0 [ERROR] InnoDB: Could not set the file size of './ibtmp1'. Probably out of disk space database_1 | 2024-04-02T06:31:41.481205Z 0 [ERROR] InnoDB: Unable to create the shared innodb_temporary database_1 | 2024-04-02T06:31:41.481208Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error database_1 | 2024-04-02T06:31:41.881920Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" database_1 | 2024-04-02T06:31:41.882034Z 0 [ERROR] Plugin 'InnoDB' init function returned error. database_1 | 2024-04-02T06:31:41.882041Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. database_1 | 2024-04-02T06:31:41.882046Z 0 [ERROR] Failed to initialize builtin plugins. database_1 | 2024-04-02T06:31:41.882048Z 0 [ERROR] Aborting database_1 | database_1 | 2024-04-02T06:31:41.882059Z 0 [Note] Binlog end database_1 | 2024-04-02T06:31:41.882395Z 0 [Note] Shutting down plugin 'CSV' database_1 | 2024-04-02T06:31:41.889624Z 0 [Note] /opt/bitnami/mysql/bin/mysqld: Shutdown complete database_1 | database_1 | userperms 08:37:29.60 WARN ==> Only the root user can reset permissions! This is probably ok though... database_1 | loadkeys 08:37:29.62 WARN ==> Only the root user can load ssh keys! This is probably ok though... database_1 | lando 08:37:29.62 INFO ==> Lando handing off to: /launch.sh database_1 | lando 08:37:29.62 DEBUG ==> Running command with exec... database_1 | mysql 08:37:29.71 database_1 | mysql 08:37:29.71 Welcome to the Bitnami mysql container database_1 | mysql 08:37:29.71 Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-mysql database_1 | mysql 08:37:29.72 Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-mysql/issues database_1 | mysql 08:37:29.72 Send us your feedback at containers@bitnami.com database_1 | mysql 08:37:29.72 database_1 | mysql 08:37:29.73 INFO ==> Starting MySQL setup database1 | mysql 08:37:29.82 INFO ==> Validating settings in MYSQL/MARIADB_ env vars database_1 | mysql 08:37:29.82 WARN ==> You set the environment variable ALLOW_EMPTY_PASSWORD=yes. For safety reasons, do not use this flag in a production environment. database_1 | mysql 08:37:29.83 INFO ==> Initializing mysql database database_1 | mysql 08:37:29.83 DEBUG ==> Injecting custom configuration from my_custom.conf database_1 | mysql 08:37:29.84 DEBUG ==> Custom configuration my.cnf detected database_1 | mysql 08:37:29.85 DEBUG ==> Ensuring expected directories/files exist database_1 | mysql 08:37:29.87 INFO ==> Using persisted data database_1 | mysql 08:37:29.92 INFO ==> Running mysql_upgrade database_1 | mysql 08:37:29.93 INFO ==> Starting mysql in background database_1 | 2024-04-02T08:37:30.292445Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled database_1 | 2024-04-02T08:37:30.293917Z 0 [Note] /opt/bitnami/mysql/bin/mysqld (mysqld 5.7.29) starting as process 154 ... database_1 | 2024-04-02T08:37:30.438852Z 0 [Note] InnoDB: PUNCH HOLE support available database_1 | 2024-04-02T08:37:30.438904Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins database_1 | 2024-04-02T08:37:30.438909Z 0 [Note] InnoDB: Uses event mutexes database_1 | 2024-04-02T08:37:30.438911Z 0 [Note] InnoDB: GCC builtin atomic_thread_fence() is used for memory barrier database_1 | 2024-04-02T08:37:30.438913Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 database_1 | 2024-04-02T08:37:30.438915Z 0 [Note] InnoDB: Using Linux native AIO database_1 | 2024-04-02T08:37:30.441037Z 0 [Note] InnoDB: Number of pools: 1 database_1 | 2024-04-02T08:37:30.443799Z 0 [Note] InnoDB: Using CPU crc32 instructions database_1 | 2024-04-02T08:37:30.450203Z 0 [Note] InnoDB: Initializing buffer pool, total size = 384M, instances = 1, chunk size = 128M database_1 | 2024-04-02T08:37:30.518720Z 0 [Note] InnoDB: Completed initialization of buffer pool database_1 | 2024-04-02T08:37:30.540219Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). database_1 | 2024-04-02T08:37:30.559242Z 0 [Note] InnoDB: Highest supported file format is Barracuda. database_1 | 2024-04-02T08:37:30.566343Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 66453270 database_1 | 2024-04-02T08:37:30.566542Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 66453279 database_1 | 2024-04-02T08:37:30.566586Z 0 [Note] InnoDB: Database was not shutdown normally! database_1 | 2024-04-02T08:37:30.566590Z 0 [Note] InnoDB: Starting crash recovery. database_1 | 2024-04-02T08:37:30.898564Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables database_1 | 2024-04-02T08:37:30.898880Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... database_1 | 2024-04-02T08:37:30.920911Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. database_1 | 2024-04-02T08:37:30.921931Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active. database_1 | 2024-04-02T08:37:30.921941Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active. database_1 | 2024-04-02T08:37:30.924138Z 0 [Note] InnoDB: 5.7.29 started; log sequence number 66453279 database_1 | 2024-04-02T08:37:30.926222Z 0 [Note] InnoDB: Loading buffer pool(s) from /bitnami/mysql/data/ib_buffer_pool database_1 | 2024-04-02T08:37:30.929445Z 0 [Note] Plugin 'FEDERATED' is disabled. database_1 | 2024-04-02T08:37:30.957289Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them. database_1 | 2024-04-02T08:37:30.957363Z 0 [Note] Skipping generation of SSL certificates as certificate files are present in data directory. database_1 | 2024-04-02T08:37:30.961284Z 0 [Warning] CA certificate ca.pem is self signed. database_1 | 2024-04-02T08:37:30.961361Z 0 [Note] Skipping generation of RSA key pair as key files are present in data directory. database_1 | 2024-04-02T08:37:30.962340Z 0 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306 database_1 | 2024-04-02T08:37:30.962731Z 0 [Note] - '127.0.0.1' resolves to '127.0.0.1'; database_1 | 2024-04-02T08:37:30.962835Z 0 [Note] Server socket created on IP: '127.0.0.1'. database_1 | 2024-04-02T08:37:30.969069Z 0 [Note] InnoDB: Buffer pool(s) load completed at 240402 8:37:30 database_1 | 2024-04-02T08:37:31.038238Z 0 [Note] Event Scheduler: Loaded 0 events database_1 | 2024-04-02T08:37:31.039328Z 0 [Note] /opt/bitnami/mysql/bin/mysqld: ready for connections. database_1 | Version: '5.7.29' socket: '/opt/bitnami/mysql/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL) database_1 | Checking server version. database_1 | Running queries to upgrade MySQL server. database_1 | Checking system database. database_1 | mysql.columns_priv OK database_1 | mysql.db OK database_1 | mysql.engine_cost OK database_1 | mysql.event OK database_1 | mysql.func OK database_1 | mysql.general_log OK database_1 | mysql.gtid_executed OK database_1 | mysql.help_category OK database_1 | mysql.help_keyword OK database_1 | mysql.help_relation OK database_1 | mysql.help_topic OK database_1 | mysql.innodb_index_stats OK database_1 | mysql.innodb_table_stats OK database_1 | mysql.ndb_binlog_index OK database_1 | mysql.plugin OK database_1 | mysql.proc OK database_1 | mysql.procs_priv OK database_1 | mysql.proxies_priv OK database_1 | mysql.server_cost OK database_1 | mysql.servers OK database_1 | mysql.slave_master_info OK database_1 | mysql.slave_relay_log_info OK database_1 | mysql.slave_worker_info OK database_1 | mysql.slow_log OK database_1 | mysql.tables_priv OK database_1 | mysql.time_zone OK database_1 | mysql.time_zone_leap_second OK database_1 | mysql.time_zone_name OK database_1 | mysql.time_zone_transition OK database_1 | mysql.time_zone_transition_type OK database_1 | mysql.user OK database_1 | The sys schema is already up to date (version 1.5.2). database_1 | Checking databases. database_1 | drupal10.batch OK database_1 | drupal10.cache_bootstrap OK database_1 | drupal10.cache_config OK database_1 | drupal10.cache_container OK database_1 | drupal10.cache_data OK database_1 | drupal10.cache_default OK database_1 | drupal10.cache_discovery OK database_1 | drupal10.cache_dynamic_page_cache OK database_1 | drupal10.cache_entity OK database_1 | drupal10.cache_menu OK database_1 | drupal10.cache_render OK database_1 | drupal10.cachetags OK database_1 | drupal10.comment OK database_1 | drupal10.commentcomment_body OK database_1 | drupal10.commentfield_stick_comment_on_top_boole OK database_1 | drupal10.commentstick_on_top_by_likes OK database_1 | drupal10.comment_entity_statistics OK database_1 | drupal10.comment_field_data OK database_1 | drupal10.config OK database_1 | drupal10.help_search_items OK database_1 | drupal10.key_value OK database_1 | drupal10.key_value_expire OK database_1 | drupal10.menu_tree OK database_1 | drupal10.node OK database_1 | drupal10.nodebody OK database_1 | drupal10.node_access OK database_1 | drupal10.node_field_data OK database_1 | drupal10.node_field_revision OK database_1 | drupal10.node_revision OK database_1 | drupal10.node_revisionbody OK database_1 | drupal10.path_alias OK database_1 | drupal10.path_alias_revision OK database_1 | drupal10.queue OK database_1 | drupal10.router OK database_1 | drupal10.semaphore OK database_1 | drupal10.sequences OK database_1 | drupal10.sessions OK database_1 | drupal10.userroles OK database_1 | drupal10.users OK database_1 | drupal10.users_data OK database_1 | drupal10.users_field_data OK database_1 | drupal10.watchdog OK database_1 | sys.sys_config OK database_1 | Upgrade process completed successfully. database_1 | Checking if update is needed. database_1 | mysql 08:37:33.17 INFO ==> Stopping mysql database_1 | 2024-04-02T08:37:33.176906Z 0 [Note] Giving 0 client threads a chance to die gracefully database_1 | 2024-04-02T08:37:33.176965Z 0 [Note] Shutting down slave threads database_1 | 2024-04-02T08:37:33.176979Z 0 [Note] Forcefully disconnecting 0 remaining clients database_1 | 2024-04-02T08:37:33.176984Z 0 [Note] Event Scheduler: Purging the queue. 0 events database_1 | 2024-04-02T08:37:33.177397Z 0 [Note] Binlog end database_1 | 2024-04-02T08:37:33.177875Z 0 [Note] Shutting down plugin 'ngram' database_1 | 2024-04-02T08:37:33.177929Z 0 [Note] Shutting down plugin 'partition' database_1 | 2024-04-02T08:37:33.177935Z 0 [Note] Shutting down plugin 'BLACKHOLE' database_1 | 2024-04-02T08:37:33.177937Z 0 [Note] Shutting down plugin 'ARCHIVE' database_1 | 2024-04-02T08:37:33.177939Z 0 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA' database_1 | 2024-04-02T08:37:33.177953Z 0 [Note] Shutting down plugin 'MRG_MYISAM' database_1 | 2024-04-02T08:37:33.177954Z 0 [Note] Shutting down plugin 'MyISAM' database_1 | 2024-04-02T08:37:33.177960Z 0 [Note] Shutting down plugin 'INNODB_SYS_VIRTUAL' database_1 | 2024-04-02T08:37:33.177961Z 0 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES' database_1 | 2024-04-02T08:37:33.177962Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES' database_1 | 2024-04-02T08:37:33.177964Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS' database_1 | 2024-04-02T08:37:33.177965Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN' database_1 | 2024-04-02T08:37:33.177966Z 0 [Note] Shutting down plugin 'INNODB_SYS_FIELDS' database_1 | 2024-04-02T08:37:33.177967Z 0 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS' database_1 | 2024-04-02T08:37:33.177968Z 0 [Note] Shutting down plugin 'INNODB_SYS_INDEXES' database_1 | 2024-04-02T08:37:33.177969Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS' database_1 | 2024-04-02T08:37:33.177970Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLES' database_1 | 2024-04-02T08:37:33.177971Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE' database_1 | 2024-04-02T08:37:33.177972Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE' database_1 | 2024-04-02T08:37:33.177973Z 0 [Note] Shutting down plugin 'INNODB_FT_CONFIG' database_1 | 2024-04-02T08:37:33.177974Z 0 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED' database_1 | 2024-04-02T08:37:33.177975Z 0 [Note] Shutting down plugin 'INNODB_FT_DELETED' database_1 | 2024-04-02T08:37:33.177976Z 0 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD' database_1 | 2024-04-02T08:37:33.177977Z 0 [Note] Shutting down plugin 'INNODB_METRICS' database_1 | 2024-04-02T08:37:33.177978Z 0 [Note] Shutting down plugin 'INNODB_TEMP_TABLE_INFO' database_1 | 2024-04-02T08:37:33.177979Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS' database_1 | 2024-04-02T08:37:33.177980Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU' database_1 | 2024-04-02T08:37:33.177981Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE' database_1 | 2024-04-02T08:37:33.177982Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET' database_1 | 2024-04-02T08:37:33.177983Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX' database_1 | 2024-04-02T08:37:33.177984Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET' database_1 | 2024-04-02T08:37:33.177985Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM' database_1 | 2024-04-02T08:37:33.177986Z 0 [Note] Shutting down plugin 'INNODB_CMP_RESET' database_1 | 2024-04-02T08:37:33.177987Z 0 [Note] Shutting down plugin 'INNODB_CMP' database_1 | 2024-04-02T08:37:33.177988Z 0 [Note] Shutting down plugin 'INNODB_LOCK_WAITS' database_1 | 2024-04-02T08:37:33.177988Z 0 [Note] Shutting down plugin 'INNODB_LOCKS' database_1 | 2024-04-02T08:37:33.177990Z 0 [Note] Shutting down plugin 'INNODB_TRX' database_1 | 2024-04-02T08:37:33.177991Z 0 [Note] Shutting down plugin 'InnoDB' database_1 | 2024-04-02T08:37:33.178254Z 0 [Note] InnoDB: FTS optimize thread exiting. database_1 | 2024-04-02T08:37:33.178569Z 0 [Note] InnoDB: Starting shutdown... database_1 | 2024-04-02T08:37:33.279053Z 0 [Note] InnoDB: Dumping buffer pool(s) to /bitnami/mysql/data/ib_buffer_pool database_1 | 2024-04-02T08:37:33.279318Z 0 [Note] InnoDB: Buffer pool(s) dump completed at 240402 8:37:33 database_1 | 2024-04-02T08:37:34.791673Z 0 [Note] InnoDB: Shutdown completed; log sequence number 66539172 database_1 | 2024-04-02T08:37:34.791796Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" database_1 | 2024-04-02T08:37:34.791808Z 0 [Note] Shutting down plugin 'MEMORY' database_1 | 2024-04-02T08:37:34.791812Z 0 [Note] Shutting down plugin 'CSV' database_1 | 2024-04-02T08:37:34.791814Z 0 [Note] Shutting down plugin 'sha256_password' database_1 | 2024-04-02T08:37:34.791816Z 0 [Note] Shutting down plugin 'mysql_native_password' database_1 | 2024-04-02T08:37:34.791898Z 0 [Note] Shutting down plugin 'binlog' database_1 | 2024-04-02T08:37:34.796656Z 0 [Note] /opt/bitnami/mysql/bin/mysqld: Shutdown complete database_1 | database_1 | database_1 | mysql 08:37:35.18 INFO ==> MySQL setup finished! database_1 | mysql 08:37:35.25 INFO ==> Starting MySQL database_1 | 2024-04-02T08:37:35.422730Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled database_1 | 2024-04-02T08:37:35.422790Z 0 [Note] /opt/bitnami/mysql/bin/mysqld (mysqld 5.7.29) starting as process 16 ... database_1 | 2024-04-02T08:37:35.455983Z 0 [Note] InnoDB: PUNCH HOLE support available database_1 | 2024-04-02T08:37:35.456028Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins database_1 | 2024-04-02T08:37:35.456033Z 0 [Note] InnoDB: Uses event mutexes database_1 | 2024-04-02T08:37:35.456035Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier database_1 | 2024-04-02T08:37:35.456037Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 database_1 | 2024-04-02T08:37:35.456039Z 0 [Note] InnoDB: Using Linux native AIO database_1 | 2024-04-02T08:37:35.456344Z 0 [Note] InnoDB: Number of pools: 1 database_1 | 2024-04-02T08:37:35.456488Z 0 [Note] InnoDB: Using CPU crc32 instructions database_1 | 2024-04-02T08:37:35.458006Z 0 [Note] InnoDB: Initializing buffer pool, total size = 384M, instances = 1, chunk size = 128M database_1 | 2024-04-02T08:37:35.480037Z 0 [Note] InnoDB: Completed initialization of buffer pool database_1 | 2024-04-02T08:37:35.484644Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). database_1 | 2024-04-02T08:37:35.497766Z 0 [Note] InnoDB: Highest supported file format is Barracuda. database_1 | 2024-04-02T08:37:35.540782Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables database_1 | 2024-04-02T08:37:35.540886Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... database_1 | 2024-04-02T08:37:35.552540Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. database_1 | 2024-04-02T08:37:35.553181Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active. database_1 | 2024-04-02T08:37:35.553214Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active. database_1 | 2024-04-02T08:37:35.554011Z 0 [Note] InnoDB: 5.7.29 started; log sequence number 66539172 database_1 | 2024-04-02T08:37:35.554417Z 0 [Note] InnoDB: Loading buffer pool(s) from /bitnami/mysql/data/ib_buffer_pool database_1 | 2024-04-02T08:37:35.554605Z 0 [Note] Plugin 'FEDERATED' is disabled. database_1 | 2024-04-02T08:37:35.559002Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them. database_1 | 2024-04-02T08:37:35.559035Z 0 [Note] Skipping generation of SSL certificates as certificate files are present in data directory. database_1 | 2024-04-02T08:37:35.559516Z 0 [Warning] CA certificate ca.pem is self signed. database_1 | 2024-04-02T08:37:35.559579Z 0 [Note] Skipping generation of RSA key pair as key files are present in data directory. database_1 | 2024-04-02T08:37:35.559651Z 0 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306 database_1 | 2024-04-02T08:37:35.559684Z 0 [Note] - '127.0.0.1' resolves to '127.0.0.1'; database_1 | 2024-04-02T08:37:35.559712Z 0 [Note] Server socket created on IP: '127.0.0.1'. database_1 | 2024-04-02T08:37:35.570197Z 0 [Note] Event Scheduler: Loaded 0 events database_1 | 2024-04-02T08:37:35.570813Z 0 [Note] /opt/bitnami/mysql/bin/mysqld: ready for connections. database_1 | Version: '5.7.29' socket: '/opt/bitnami/mysql/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL) database_1 | 2024-04-02T08:37:35.573356Z 0 [Note] InnoDB: Buffer pool(s) load completed at 240402 8:37:35

It is not problem with disk space I have more than 500 GB

reynoldsalec commented 5 months ago

@drale1 what's your Landofile look like?

Also, are you saying you have 500GB dedicated to Docker Desktop, or 500GB free on your hard drive? Want to make sure that your Docker Desktop instance has space dedicated to it; you can see how much is available at the bottom of the Docker Desktop dashboard.

rubenvarela commented 5 months ago

Yeah, looks like space.

If on docker desktop, this is where to see the space used and allocated,

image

and this is how to increase it,

image
drale1 commented 5 months ago

@reynoldsalec @rubenvarela you are right. It was a Docker space. But one thing was strange, on v3.21.0-beta.11 and below there was no problem, but on v3.21.0-beta.12 I had a problem. So when I downgraded, there were no issues again. Now when I increased the space on Docker it works on v3.21.0-beta.12.

reynoldsalec commented 5 months ago

Excellent, thanks @rubenvarela for the help, glad that solved your issue @drale1.