Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MySQL init process hangs when using image mariadb 10.1.42, 10.2.27, 10.3.18, 10.4.8 #262

Closed
marc-legendre opened this issue Sep 20, 2019 · 36 comments · Fixed by #320
Closed
Labels

Comments

@marc-legendre
Copy link

I am using mariadb:10.3, and there seems to be an issue with the current version (10.3 == 10.3.18 == sha256:17a2a44fb692a7a4b244b104de0f286b51b29083b794ae964e3ed5aab8259358), where the MySQL init process is stuck when running a "fresh" docker (I mean, with no existing database in a volume).

For example, with 10.3.18 the output looks like this:

docker run -e MYSQL_ROOT_PASSWORD=wut mariadb:10.3.18
[...]
MySQL init process in progress...
[...]
Version: '10.3.18-MariaDB-1:10.3.18+maria~bionic'  socket: '/var/run/mysqld/mysqld.sock'  port: 0  mariadb.org binary distribution
# stuck here

Whereas, with 10.3.17, the output looks like this:

docker run -e MYSQL_ROOT_PASSWORD=wut mariadb:10.3.17
[...]
MySQL init process in progress...
[...]
MySQL init process done. Ready for start up.
[...]
# life goes on

Here is the full output when using 10.3.18:

$ docker run -e MYSQL_ROOT_PASSWORD=wut mariadb:10.3.18
Initializing database


PLEASE REMEMBER TO SET A PASSWORD FOR THE MariaDB root USER !
To do so, start the server, then issue the following commands:

'/usr/bin/mysqladmin' -u root password 'new-password'
'/usr/bin/mysqladmin' -u root -h  password 'new-password'

Alternatively you can run:
'/usr/bin/mysql_secure_installation'

which will also give you the option of removing the test
databases and anonymous user created by default.  This is
strongly recommended for production servers.

See the MariaDB Knowledgebase at http://mariadb.com/kb or the
MySQL manual for more instructions.

Please report any problems at http://mariadb.org/jira

The latest information about MariaDB is available at http://mariadb.org/.
You can find additional information about the MySQL part at:
http://dev.mysql.com
Consider joining MariaDB's strong and vibrant community:
https://mariadb.org/get-involved/

Database initialized
MySQL init process in progress...
2019-09-20 14:31:51 0 [Note] mysqld (mysqld 10.3.18-MariaDB-1:10.3.18+maria~bionic) starting as process 109 ...
2019-09-20 14:31:51 0 [Note] InnoDB: Using Linux native AIO
2019-09-20 14:31:51 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-09-20 14:31:51 0 [Note] InnoDB: Uses event mutexes
2019-09-20 14:31:51 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-09-20 14:31:51 0 [Note] InnoDB: Number of pools: 1
2019-09-20 14:31:51 0 [Note] InnoDB: Using SSE2 crc32 instructions
2019-09-20 14:31:51 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
2019-09-20 14:31:51 0 [Note] InnoDB: Completed initialization of buffer pool
2019-09-20 14:31:51 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-09-20 14:31:51 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2019-09-20 14:31:51 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-09-20 14:31:51 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-09-20 14:31:51 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2019-09-20 14:31:51 0 [Note] InnoDB: 10.3.18 started; log sequence number 1630860; transaction id 21
2019-09-20 14:31:51 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2019-09-20 14:31:51 0 [Note] Plugin 'FEEDBACK' is disabled.
2019-09-20 14:31:51 0 [Note] InnoDB: Buffer pool(s) load completed at 190920 14:31:51
2019-09-20 14:31:51 0 [Warning] 'user' entry 'root@bfd3fc90f6f5' ignored in --skip-name-resolve mode.
2019-09-20 14:31:51 0 [Warning] 'user' entry '@bfd3fc90f6f5' ignored in --skip-name-resolve mode.
2019-09-20 14:31:51 0 [Warning] 'proxies_priv' entry '@% root@bfd3fc90f6f5' ignored in --skip-name-resolve mode.
2019-09-20 14:31:51 0 [Note] Reading of all Master_info entries succeeded
2019-09-20 14:31:51 0 [Note] Added new Master_info '' to hash table
2019-09-20 14:31:51 0 [Note] mysqld: ready for connections.
Version: '10.3.18-MariaDB-1:10.3.18+maria~bionic'  socket: '/var/run/mysqld/mysqld.sock'  port: 0  mariadb.org binary distribution
Warning: Unable to load '/usr/share/zoneinfo/leap-seconds.list' as time zone. Skipping it.
@wglambert
Copy link

wglambert commented Sep 20, 2019

I can reproduce it hanging, with the log output missing the line from the entrypoint
https://github.com/docker-library/mariadb/blob/bf675caa56e4a1b462c665d1cded137f13c33753/10.3/docker-entrypoint.sh#L194

Related to or maybe duplicate of #261

$ docker run -d --rm --name mariadb -e MYSQL_ROOT_PASSWORD=pass mariadb:10.3.18                                       
d4a3b782337dd471738e7d6a054d60f6c7f268448f9095785b40288ef810d7b5

$ time grep -iq "ready for connections" <(docker logs -f mariadb 2>&1)                                                
                                                                                                                                                  
real    0m22.382s                                                                                                                                 
user    0m0.000s                                                                                                                                  
sys     0m0.007s
diff -y 10.3.17 10.3.18
$ docker run -d --rm --name mariadb-18 -e MYSQL_ROOT_PASSWORD=pass mariadb:10.3.18        
db458b3f567abb6e70d778bd361e57471af5322ecb57e8f77f17341c38d19cc5

$ docker run -d --rm --name mariadb-17 -e MYSQL_ROOT_PASSWORD=pass mariadb:10.3.17 
10c01a8b60179fb7e017726fc8340691f6ffc4c91eef84deabb216e6b0991c5a

$ diff -y <(docker logs mariadb-17 2>&1) <(docker logs mariadb-18 2>&1)           
Initializing database                                           Initializing database


PLEASE REMEMBER TO SET A PASSWORD FOR THE MariaDB root USER !   PLEASE REMEMBER TO SET A PASSWORD FOR THE MariaDB root USER !
To do so, start the server, then issue the following commands   To do so, start the server, then issue the following commands

'/usr/bin/mysqladmin' -u root password 'new-password'           '/usr/bin/mysqladmin' -u root password 'new-password'
'/usr/bin/mysqladmin' -u root -h  password 'new-password'       '/usr/bin/mysqladmin' -u root -h  password 'new-password'

Alternatively you can run:                                      Alternatively you can run:
'/usr/bin/mysql_secure_installation'                            '/usr/bin/mysql_secure_installation'

which will also give you the option of removing the test        which will also give you the option of removing the test
databases and anonymous user created by default.  This is       databases and anonymous user created by default.  This is
strongly recommended for production servers.                    strongly recommended for production servers.

See the MariaDB Knowledgebase at http://mariadb.com/kb or the   See the MariaDB Knowledgebase at http://mariadb.com/kb or the
MySQL manual for more instructions.                             MySQL manual for more instructions.

Please report any problems at http://mariadb.org/jira           Please report any problems at http://mariadb.org/jira

The latest information about MariaDB is available at http://m   The latest information about MariaDB is available at http://m
You can find additional information about the MySQL part at:    You can find additional information about the MySQL part at:
http://dev.mysql.com                                            http://dev.mysql.com
Consider joining MariaDB's strong and vibrant community:        Consider joining MariaDB's strong and vibrant community:
https://mariadb.org/get-involved/                               https://mariadb.org/get-involved/

Database initialized                                            Database initialized
MySQL init process in progress...                               MySQL init process in progress...
2019-09-20 17:07:09 0 [Note] mysqld (mysqld 10.3.17-MariaDB-1 | 2019-09-20 17:06:54 0 [Note] mysqld (mysqld 10.3.18-MariaDB-1
2019-09-20 17:07:09 0 [Note] InnoDB: Using Linux native AIO   | 2019-09-20 17:06:54 0 [Note] InnoDB: Using Linux native AIO
2019-09-20 17:07:09 0 [Note] InnoDB: Mutexes and rw_locks use | 2019-09-20 17:06:54 0 [Note] InnoDB: Mutexes and rw_locks use
2019-09-20 17:07:09 0 [Note] InnoDB: Uses event mutexes       | 2019-09-20 17:06:54 0 [Note] InnoDB: Uses event mutexes
2019-09-20 17:07:09 0 [Note] InnoDB: Compressed tables use zl | 2019-09-20 17:06:54 0 [Note] InnoDB: Compressed tables use zl
2019-09-20 17:07:09 0 [Note] InnoDB: Number of pools: 1       | 2019-09-20 17:06:54 0 [Note] InnoDB: Number of pools: 1
2019-09-20 17:07:09 0 [Note] InnoDB: Using SSE2 crc32 instruc | 2019-09-20 17:06:54 0 [Note] InnoDB: Using SSE2 crc32 instruc
2019-09-20 17:07:09 0 [Note] InnoDB: Initializing buffer pool | 2019-09-20 17:06:54 0 [Note] InnoDB: Initializing buffer pool
2019-09-20 17:07:09 0 [Note] InnoDB: Completed initialization | 2019-09-20 17:06:54 0 [Note] InnoDB: Completed initialization
2019-09-20 17:07:09 0 [Note] InnoDB: If the mysqld execution  | 2019-09-20 17:06:54 0 [Note] InnoDB: If the mysqld execution 
MySQL init process in progress...                               MySQL init process in progress...
MySQL init process in progress...                               MySQL init process in progress...
2019-09-20 17:07:11 0 [Note] InnoDB: 128 out of 128 rollback  | 2019-09-20 17:06:57 0 [Note] InnoDB: 128 out of 128 rollback 
2019-09-20 17:07:11 0 [Note] InnoDB: Creating shared tablespa | 2019-09-20 17:06:57 0 [Note] InnoDB: Creating shared tablespa
2019-09-20 17:07:11 0 [Note] InnoDB: Setting file './ibtmp1'  | 2019-09-20 17:06:57 0 [Note] InnoDB: Setting file './ibtmp1' 
2019-09-20 17:07:11 0 [Note] InnoDB: File './ibtmp1' size is  | 2019-09-20 17:06:57 0 [Note] InnoDB: File './ibtmp1' size is 
2019-09-20 17:07:11 0 [Note] InnoDB: 10.3.17 started; log seq | 2019-09-20 17:06:57 0 [Note] InnoDB: Waiting for purge to sta
2019-09-20 17:07:11 0 [Note] Plugin 'FEEDBACK' is disabled.   | 2019-09-20 17:06:57 0 [Note] InnoDB: 10.3.18 started; log seq
2019-09-20 17:07:11 0 [Note] InnoDB: Loading buffer pool(s) f | 2019-09-20 17:06:57 0 [Note] InnoDB: Loading buffer pool(s) f
2019-09-20 17:07:12 0 [Warning] 'user' entry 'root@10c01a8b60 | 2019-09-20 17:06:57 0 [Note] Plugin 'FEEDBACK' is disabled.
2019-09-20 17:07:12 0 [Warning] 'user' entry '@10c01a8b6017'  | 2019-09-20 17:06:57 0 [Note] InnoDB: Buffer pool(s) load comp
2019-09-20 17:07:12 0 [Warning] 'proxies_priv' entry '@% root | 2019-09-20 17:06:57 0 [Warning] 'user' entry 'root@db458b3f56
2019-09-20 17:07:12 0 [Note] InnoDB: Buffer pool(s) load comp | 2019-09-20 17:06:57 0 [Warning] 'user' entry '@db458b3f567a' 
2019-09-20 17:07:12 0 [Note] Reading of all Master_info entri | 2019-09-20 17:06:57 0 [Warning] 'proxies_priv' entry '@% root
2019-09-20 17:07:12 0 [Note] Added new Master_info '' to hash | 2019-09-20 17:06:57 0 [Note] Reading of all Master_info entri
2019-09-20 17:07:12 0 [Note] mysqld: ready for connections.   | 2019-09-20 17:06:57 0 [Note] Added new Master_info '' to hash
Version: '10.3.17-MariaDB-1:10.3.17+maria~bionic'  socket: '/ | 2019-09-20 17:06:57 0 [Note] mysqld: ready for connections.
Warning: Unable to load '/usr/share/zoneinfo/leap-seconds.lis | Version: '10.3.18-MariaDB-1:10.3.18+maria~bionic'  socket: '/
2019-09-20 17:07:14 10 [Warning] 'proxies_priv' entry '@% roo <
                                                              <
2019-09-20 17:07:14 0 [Note] mysqld (initiated by: unknown):  <
2019-09-20 17:07:14 0 [Note] Event Scheduler: Purging the que <
2019-09-20 17:07:14 0 [Note] InnoDB: FTS optimize thread exit <
2019-09-20 17:07:14 0 [Note] InnoDB: Starting shutdown...     <
2019-09-20 17:07:14 0 [Note] InnoDB: Dumping buffer pool(s) t <
2019-09-20 17:07:14 0 [Note] InnoDB: Buffer pool(s) dump comp <
2019-09-20 17:07:16 0 [Note] InnoDB: Shutdown completed; log  <
2019-09-20 17:07:16 0 [Note] InnoDB: Removed temporary tables <
2019-09-20 17:07:16 0 [Note] mysqld: Shutdown complete        <
                                                              <
                                                              <
MySQL init process done. Ready for start up.                  <
                                                              <
2019-09-20 17:07:16 0 [Note] mysqld (mysqld 10.3.17-MariaDB-1 <
2019-09-20 17:07:16 0 [Note] InnoDB: Using Linux native AIO   <
2019-09-20 17:07:16 0 [Note] InnoDB: Mutexes and rw_locks use <
2019-09-20 17:07:16 0 [Note] InnoDB: Uses event mutexes       <
2019-09-20 17:07:16 0 [Note] InnoDB: Compressed tables use zl <
2019-09-20 17:07:16 0 [Note] InnoDB: Number of pools: 1       <
2019-09-20 17:07:16 0 [Note] InnoDB: Using SSE2 crc32 instruc <
2019-09-20 17:07:16 0 [Note] InnoDB: Initializing buffer pool <
2019-09-20 17:07:16 0 [Note] InnoDB: Completed initialization <
2019-09-20 17:07:16 0 [Note] InnoDB: If the mysqld execution  <
2019-09-20 17:07:17 0 [Note] InnoDB: 128 out of 128 rollback  <
2019-09-20 17:07:17 0 [Note] InnoDB: Creating shared tablespa <
2019-09-20 17:07:17 0 [Note] InnoDB: Setting file './ibtmp1'  <
2019-09-20 17:07:17 0 [Note] InnoDB: File './ibtmp1' size is  <
2019-09-20 17:07:17 0 [Note] InnoDB: 10.3.17 started; log seq <
2019-09-20 17:07:17 0 [Note] InnoDB: Loading buffer pool(s) f <
2019-09-20 17:07:17 0 [Note] Plugin 'FEEDBACK' is disabled.   <
2019-09-20 17:07:17 0 [Note] InnoDB: Buffer pool(s) load comp <
2019-09-20 17:07:17 0 [Note] Server socket created on IP: ':: <
2019-09-20 17:07:17 0 [Warning] 'proxies_priv' entry '@% root <
2019-09-20 17:07:17 0 [Note] Reading of all Master_info entri <
2019-09-20 17:07:17 0 [Note] Added new Master_info '' to hash <
2019-09-20 17:07:17 0 [Note] mysqld: ready for connections.   <
Version: '10.3.17-MariaDB-1:10.3.17+maria~bionic'  socket: '/ <

@wglambert
Copy link

wglambert commented Sep 20, 2019

Over 25 minutes later it still hasn't initialized

$ docker exec mariadb-18 ps aux
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND                                                                          
mysql        1  0.0  0.0  18508  3216 ?        Ss   17:06   0:00 /bin/bash /usr/local/bin/docker-entrypoint.sh mysqld                             
mysql      109  6.2  0.8 2252904 95980 ?       Sl   17:06   1:35 mysqld --skip-networking --socket=/var/run/mysqld/mysqld.sock                    
mysql      152  0.0  0.0  10324  2496 ?        S    17:06   0:00 mysql_tzinfo_to_sql /usr/share/zoneinfo                                          
mysql      153  0.0  0.0  13560  1116 ?        S    17:06   0:00 sed s/Local time zone must be set--see zic manual page/FCTY/                     
mysql      154  0.0  0.0  41200  8428 ?        S    17:06   0:00 mysql --protocol=socket -uroot -hlocalhost --socket=/var/run/mysqld/mysqld.sock mysql                                                                                                                                              
root       583  0.0  0.0  34400  2780 ?        Rs   17:32   0:00 ps aux

$ docker exec --privileged mariadb-18 netstat -tulpn                                                                  
Active Internet connections (only servers)                                                                                                        
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name

What it looks like on an initialized 10.3.17:

$ docker exec mariadb-17 ps aux                                                                  
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND                                                                          
mysql        1  0.1  0.7 1924884 86576 ?       Ssl  17:06   0:02 mysqld                                                                           
root       577  0.0  0.0  34400  2892 ?        Rs   17:32   0:00 ps aux

$ docker exec --privileged mariadb-17 netstat -tulpn                                                                  
Active Internet connections (only servers)                                                                                                        
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name                                                  
tcp6       0      0 :::3306                 :::*                    LISTEN      1/mysqld

One that I had running in the background just finished after 40 minutes

$ docker logs mariadb
Initializing database
. . .
Database initialized
MySQL init process in progress...
2019-09-20 17:00:22 0 [Note] mysqld (mysqld 10.3.18-MariaDB-1:10.3.18+maria~bionic) starting as process 109 ...
. . .
2019-09-20 17:00:26 0 [Note] mysqld: ready for connections.
Version: '10.3.18-MariaDB-1:10.3.18+maria~bionic'  socket: '/var/run/mysqld/mysqld.sock'  port: 0  mariadb.org binary distribution
Warning: Unable to load '/usr/share/zoneinfo/leap-seconds.list' as time zone. Skipping it.
2019-09-20 17:39:34 10 [Warning] 'proxies_priv' entry '@% root@d4a3b782337d' ignored in --skip-name-resolve mode.
. . .
2019-09-20 17:39:44 0 [Note] mysqld: ready for connections.
Version: '10.3.18-MariaDB-1:10.3.18+maria~bionic'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
2019-09-20 17:39:44 0 [Note] InnoDB: Buffer pool(s) load completed at 190920 17:39:44

@wglambert
Copy link

wglambert commented Sep 20, 2019

Running tests from docker-library/official-images#6627 (comment)

$ git clone --depth 1 https://github.com/docker-library/official-images.git
Cloning into 'official-images'...
remote: Enumerating objects: 1061, done.
remote: Counting objects: 100% (1061/1061), done.
remote: Compressing objects: 100% (878/878), done.
remote: Total 1061 (delta 63), reused 810 (delta 43), pack-reused 0
Receiving objects: 100% (1061/1061), 1.03 MiB | 0 bytes/s, done.
Resolving deltas: 100% (63/63), done.
Checking connectivity... done.

$ cd official-images/

$ git filter-branch --prune-empty --subdirectory-filter test HEAD
Rewrite bf242b5d33c5bda0e0d0d91d04675942bd9eb179 (1/1) (0 seconds passed, remaining 0 predicted)    
Ref 'refs/heads/master' was rewritten

$ ls
clean.sh*  config.sh  README.md  retry.sh*  run.sh*  tests/

$ ./run.sh mariadb:10.3.17
testing mariadb:10.3.17
        'utc' [1/7]...passed
        'cve-2014--shellshock' [2/7]...passed
        'no-hard-coded-passwords' [3/7]...passed
        'override-cmd' [4/7]...passed
        'mysql-basics' [5/7]......passed
        'mysql-initdb' [6/7]......passed
        'mysql-log-bin' [7/7]......passed

$ ./run.sh mariadb:10.3.18
testing mariadb:10.3.18                                                                                                                
        'utc' [1/7]...passed                                                                                                           
        'cve-2014--shellshock' [2/7]...passed                                                                                          
        'no-hard-coded-passwords' [3/7]...passed                                                                                       
        'override-cmd' [4/7]...passed                                                                                                  
        'mysql-basics' [5/7]................................mariadb:10.3.18 failed to accept connections in a reasonable amount of time!                                                                                                                                      
++ docker logs e2e3e52741d5a3df7265e3536e99b397d0d201573f8320375a8ee4bd22742259                                                        
Initializing database                                                                                                                  
                                                                                                                                       
                                                                                                                                       
PLEASE REMEMBER TO SET A PASSWORD FOR THE MariaDB root USER !                                                                          
To do so, start the server, then issue the following commands:                                                                         
                                                                                                                                       
'/usr/bin/mysqladmin' -u root password 'new-password'                                                                                  
'/usr/bin/mysqladmin' -u root -h  password 'new-password'

Alternatively you can run:
'/usr/bin/mysql_secure_installation'

which will also give you the option of removing the test
databases and anonymous user created by default.  This is
strongly recommended for production servers.

See the MariaDB Knowledgebase at http://mariadb.com/kb or the
MySQL manual for more instructions.

Please report any problems at http://mariadb.org/jira

The latest information about MariaDB is available at http://mariadb.org/.
You can find additional information about the MySQL part at:
http://dev.mysql.com
Consider joining MariaDB's strong and vibrant community:
https://mariadb.org/get-involved/

Database initialized
MySQL init process in progress...
2019-09-20 18:11:18 0 [Note] mysqld (mysqld 10.3.18-MariaDB-1:10.3.18+maria~bionic) starting as process 109 ...
2019-09-20 18:11:18 0 [Note] InnoDB: Using Linux native AIO
2019-09-20 18:11:18 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-09-20 18:11:18 0 [Note] InnoDB: Uses event mutexes
2019-09-20 18:11:18 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-09-20 18:11:18 0 [Note] InnoDB: Number of pools: 1
2019-09-20 18:11:18 0 [Note] InnoDB: Using SSE2 crc32 instructions
2019-09-20 18:11:18 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
2019-09-20 18:11:18 0 [Note] InnoDB: Completed initialization of buffer pool
2019-09-20 18:11:18 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
MySQL init process in progress...
2019-09-20 18:11:20 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2019-09-20 18:11:20 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-09-20 18:11:20 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-09-20 18:11:20 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
MySQL init process in progress...
2019-09-20 18:11:20 0 [Note] InnoDB: 10.3.18 started; log sequence number 1631163; transaction id 21
2019-09-20 18:11:20 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2019-09-20 18:11:20 0 [Note] Plugin 'FEEDBACK' is disabled.
2019-09-20 18:11:20 0 [Note] InnoDB: Buffer pool(s) load completed at 190920 18:11:20
2019-09-20 18:11:20 0 [Warning] 'user' entry 'root@e2e3e52741d5' ignored in --skip-name-resolve mode.
2019-09-20 18:11:20 0 [Warning] 'user' entry '@e2e3e52741d5' ignored in --skip-name-resolve mode.
2019-09-20 18:11:20 0 [Warning] 'proxies_priv' entry '@% root@e2e3e52741d5' ignored in --skip-name-resolve mode.
2019-09-20 18:11:21 0 [Note] Reading of all Master_info entries succeeded
2019-09-20 18:11:21 0 [Note] Added new Master_info '' to hash table
2019-09-20 18:11:21 0 [Note] mysqld: ready for connections.
Version: '10.3.18-MariaDB-1:10.3.18+maria~bionic'  socket: '/var/run/mysqld/mysqld.sock'  port: 0  mariadb.org binary distribution
++ eval 'echo '\''SELECT 1'\'' | mysql'
+++ echo 'SELECT 1'
+++ mysql
+++ docker run --rm -i --link mysql-container-19063-24904:mysql --entrypoint mysql -e 'MYSQL_PWD=my cool mysql password' mariadb:10.3.18 -hmysql -u0123456789012345 --silent 'my cool mysql database'
ERROR 2002 (HY000): Can't connect to MySQL server on 'mysql' (115)
failed
        'mysql-initdb' [6/7]................................mariadb:10.3.18 failed to accept connections in a reasonable amount of time!
. . .
        'mysql-log-bin' [7/7]................................mariadb:10.3.18 failed to accept connections in a reasonable amount of time!
. . .

@foolswood
Copy link

I think we're hitting this too, for us it manifests an intermittent issue in the CI, which doesn't happen if we pin to 10.1 (which is what I guess we'll do for a bit).

@lucwillems
Copy link

i'm also hitting this issue. after intial DB initialization, it seems to hang before running the running the /docker-entrypoint-initdb.d/ scripts and root account is not yet configured .

mariadb-cp | 2019-09-30T05:01:54.680535478Z mariadb 42 MySQL init process in progress...
mariadb-cp | 2019-09-30T05:01:54.821192533Z mariadb 42 2019-09-30  5:01:54 0 [Note] mysqld (mysqld 10.3.18-MariaDB-1:10.3.18+maria~bionic) starting as process 173 ...
mariadb-cp | 2019-09-30T05:01:54.8509885Z mariadb 42 2019-09-30  5:01:54 0 [Note] RocksDB: 2 column families found
mariadb-cp | 2019-09-30T05:01:54.851050756Z mariadb 42 2019-09-30  5:01:54 0 [Note] RocksDB: Column Families at start:
mariadb-cp | 2019-09-30T05:01:54.851058644Z mariadb 42 2019-09-30  5:01:54 0 [Note]   cf=default
mariadb-cp | 2019-09-30T05:01:54.851065911Z mariadb 42 2019-09-30  5:01:54 0 [Note]     write_buffer_size=67108864
mariadb-cp | 2019-09-30T05:01:54.851070723Z mariadb 42 2019-09-30  5:01:54 0 [Note]     target_file_size_base=67108864
mariadb-cp | 2019-09-30T05:01:54.851076698Z mariadb 42 2019-09-30  5:01:54 0 [Note]   cf=__system__
mariadb-cp | 2019-09-30T05:01:54.851085395Z mariadb 42 2019-09-30  5:01:54 0 [Note]     write_buffer_size=67108864
mariadb-cp | 2019-09-30T05:01:54.851096444Z mariadb 42 2019-09-30  5:01:54 0 [Note]     target_file_size_base=67108864
mariadb-cp | 2019-09-30T05:01:54.869652415Z mariadb 42 2019-09-30  5:01:54 0 [Note] RocksDB: Table_store: loaded DDL data for 0 tables
mariadb-cp | 2019-09-30T05:01:54.88509981Z mariadb 42 2019-09-30  5:01:54 0 [Note] RocksDB: global statistics using get_sched_indexer_t indexer
mariadb-cp | 2019-09-30T05:01:54.885152525Z mariadb 42 2019-09-30  5:01:54 0 [Note] MyRocks storage engine plugin has been successfully initialized.
mariadb-cp | 2019-09-30T05:01:54.885282479Z mariadb 42 2019-09-30  5:01:54 0 [Note] CONNECT: Version 1.06.0010 June 01, 2019
mariadb-cp | 2019-09-30T05:01:54.901203887Z mariadb 42 2019-09-30  5:01:54 0 [Note] InnoDB: Using Linux native AIO
mariadb-cp | 2019-09-30T05:01:54.901242002Z mariadb 42 2019-09-30  5:01:54 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
mariadb-cp | 2019-09-30T05:01:54.901248925Z mariadb 42 2019-09-30  5:01:54 0 [Note] InnoDB: Uses event mutexes
mariadb-cp | 2019-09-30T05:01:54.901253851Z mariadb 42 2019-09-30  5:01:54 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
mariadb-cp | 2019-09-30T05:01:54.90142919Z mariadb 42 2019-09-30  5:01:54 0 [Note] InnoDB: Number of pools: 1
mariadb-cp | 2019-09-30T05:01:54.901578246Z mariadb 42 2019-09-30  5:01:54 0 [Note] InnoDB: Using SSE2 crc32 instructions
mariadb-cp | 2019-09-30T05:01:54.902676593Z mariadb 42 2019-09-30  5:01:54 0 [Note] InnoDB: Initializing buffer pool, total size = 4G, instances = 4, chunk size = 128M
mariadb-cp | 2019-09-30T05:01:55.063550087Z mariadb 42 2019-09-30  5:01:55 0 [Note] InnoDB: Completed initialization of buffer pool
mariadb-cp | 2019-09-30T05:01:55.064018473Z mariadb 42 2019-09-30  5:01:55 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
mariadb-cp | 2019-09-30T05:01:55.171738991Z mariadb 42 2019-09-30  5:01:55 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
mariadb-cp | 2019-09-30T05:01:55.172426793Z mariadb 42 2019-09-30  5:01:55 0 [Note] InnoDB: Creating shared tablespace for temporary tables
mariadb-cp | 2019-09-30T05:01:55.172523057Z mariadb 42 2019-09-30  5:01:55 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
mariadb-cp | 2019-09-30T05:01:55.172533939Z mariadb 42 2019-09-30  5:01:55 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
mariadb-cp | 2019-09-30T05:01:55.174335619Z mariadb 42 2019-09-30  5:01:55 0 [Note] InnoDB: 10.3.18 started; log sequence number 1630815; transaction id 21
mariadb-cp | 2019-09-30T05:01:55.174484762Z mariadb 42 2019-09-30  5:01:55 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
mariadb-cp | 2019-09-30T05:01:55.174707981Z mariadb 42 2019-09-30  5:01:55 0 [Note] Plugin 'FEEDBACK' is disabled.
mariadb-cp | 2019-09-30T05:01:55.177372465Z mariadb 42 2019-09-30  5:01:55 0 [Warning] 'user' entry 'root@5497cb2b2189' ignored in --skip-name-resolve mode.
mariadb-cp | 2019-09-30T05:01:55.17738354Z mariadb 42 2019-09-30  5:01:55 0 [Warning] 'user' entry '@5497cb2b2189' ignored in --skip-name-resolve mode.
mariadb-cp | 2019-09-30T05:01:55.177387494Z mariadb 42 2019-09-30  5:01:55 0 [Warning] 'proxies_priv' entry '@% root@5497cb2b2189' ignored in --skip-name-resolve mode.
mariadb-cp | 2019-09-30T05:01:55.178132794Z mariadb 42 2019-09-30  5:01:55 0 [Note] InnoDB: Buffer pool(s) load completed at 190930  5:01:55
mariadb-cp | 2019-09-30T05:01:55.179445991Z mariadb 42 2019-09-30  5:01:55 0 [Note] Reading of all Master_info entries succeeded
mariadb-cp | 2019-09-30T05:01:55.17945505Z mariadb 42 2019-09-30  5:01:55 0 [Note] Added new Master_info '' to hash table
mariadb-cp | 2019-09-30T05:01:55.179463886Z mariadb 42 2019-09-30  5:01:55 0 [Note] mysqld: ready for connections.
mariadb-cp | 2019-09-30T05:01:55.179476257Z mariadb 42 Version: '10.3.18-MariaDB-1:10.3.18+maria~bionic'  socket: '/var/run/mysqld/mysqld.sock'  port: 0  mariadb.org binary distribution
mariadb-cp | 2019-09-30T05:01:55.784673084Z mariadb 42 2019-09-30  5:01:55 10 [Warning] Access denied for user 'root'@'localhost' (using password: YES)
mariadb-cp | 2019-09-30T05:01:55.784728988Z 255 ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
mariadb-cp | 2019-09-30T05:01:55.785689063Z check.mariadb exited with error: exit status 1
mariadb-cp | 2019-09-30T05:02:00.791107214Z mariadb 42 2019-09-30  5:02:00 11 [Warning] Access denied for user 'root'@'localhost' (using password: YES)
mariadb-cp | 2019-09-30T05:02:00.791281511Z 259 ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
mariadb-cp | 2019-09-30T05:02:00.793297796Z check.mariadb exited with error: exit status 1
mariadb-cp | 2019-09-30T05:02:05.792145752Z mariadb 42 2019-09-30  5:02:05 12 [Warning] Access denied for user 'root'@'localhost' (using password: YES)
mariadb-cp | 2019-09-30T05:02:05.792305227Z 261 ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
mariadb-cp | 2019-09-30T05:02:05.793920555Z check.mariadb exited with error: exit status 1
mariadb-cp | 2019-09-30T05:02:10.791898474Z mariadb 42 2019-09-30  5:02:10 13 [Warning] Access denied for user 'root'@'localhost' (using password: YES)
mariadb-cp | 2019-09-30T05:02:10.79204545Z 263 ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
mariadb-cp | 2019-09-30T05:02:10.793609751Z check.mariadb exited with error: exit status 1
mariadb-cp | 2019-09-30T05:02:15.791498256Z mariadb 42 2019-09-30  5:02:15 14 [Warning] Access denied for user 'root'@'localhost' (using password: YES)
mariadb-cp | 2019-09-30T05:02:15.791651989Z 265 ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
mariadb-cp | 2019-09-30T05:02:15.793318054Z check.mariadb exited with error: exit status 1
mariadb-cp | 2019-09-30T05:02:20.791050752Z mariadb 42 2019-09-30  5:02:20 15 [Warning] Access denied for user 'root'@'localhost' (using password: YES)
mariadb-cp | 2019-09-30T05:02:20.791233244Z 267 ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
mariadb-cp | 2019-09-30T05:02:20.792776665Z check.mariadb exited with error: exit status 1

while this was running for a few minutes i notice it was handling the tzinfo data.

mysql       42    11  0 05:01 ?        00:00:00 /bin/bash /usr/local/bin/docker-entrypoint.sh mysqld --innodb_buffer_pool_size=4G --innodb-buffer-pool-instances=4
mysql      173    42 33 05:01 ?        00:01:02 mysqld --innodb_buffer_pool_size=4G --innodb-buffer-pool-instances=4 --skip-networking --socket=/var/run/mysqld/mysqld.sock
**mysql      252    42  0 05:01 ?        00:00:00 mysql_tzinfo_to_sql /usr/share/zoneinfo**
mysql      253    42  0 05:01 ?        00:00:00 sed s/Local time zone must be set--see zic manual page/FCTY/
mysql      254    42  0 05:01 ?        00:00:00 mysql --protocol=socket -uroot -hlocalhost --socket=/var/run/mysqld/mysqld.sock mysql
root       275     0  0 05:02 pts/0    00:00:00 bash
root       348   275  0 05:05 pts/0    00:00:00 ps -ef

@lucwillems
Copy link

see #261 (comment), this seems to be related to https://jira.mariadb.org/browse/MDEV-18778

using MYSQL_INITDB_SKIP_TZINFO=1 seems to workaround, but will not have TZINFO data in the database.

@melroy89
Copy link

I think both mariadb devs as well as the mariadb docker devs could prevent this in the future my running CI. And don't label mariadb as 'latest' while it is unstable/not workable. This could be prevented I think.

I hope you all agree. (I do not want to blame.. but just an open discussion regarding prevention).

@yosifkit
Copy link
Contributor

@Danger89, we do run tests that start and connect to the server on every PR here via TravisCI and before it goes to be built for Docker Hub (like docker-library/official-images#6627 (comment)), but this issue was not encountered. The reason the test machine from my build test comment did not see the error is that the hard drive is an NVME SSD and I assume the Travis servers must also be SSD since we have only been able to reproduce the error on a spinning disk.

See the mysql-* tests in official-images test for the details of the tests performed on the MariaDB Docker images.

@melroy89
Copy link

@yosifkit So to conclude you miss test coverage of hard-drives (spinning disks).

@tianon
Copy link
Contributor

tianon commented Oct 23, 2019 via email

@lachnerd
Copy link

hi there, we are experiencing this issue on SSD Storage. (IOPS r 7500/w 5000)
Every mariadb version bigger than 10.3.16 may be stuck on initialisation with first boot of the database.

@yosifkit
Copy link
Contributor

7500/5000 is still very slow compared to a local nvme ssd that is around 680,000/360,000 iops (https://cloud.google.com/compute/docs/disks/performance#type_comparison)

@rdlmda
Copy link

rdlmda commented Nov 6, 2019

#261 is related

@foolswood
Copy link

This is now hitting in the latest 10.1 image too, so we're now using the TZ workaround,

@jgb
Copy link

jgb commented Nov 27, 2019

So what is the story here? Is this a confirmed bug? Will this be fixed in a new version of mariadb? Or will a new docker image be published?

@andryyy
Copy link

andryyy commented Dec 2, 2019

Can someone look into this? Edit: Sad smiley here.

@yosifkit
Copy link
Contributor

yosifkit commented Dec 3, 2019

This is an upstream issue and not something we can fix in the image. The cause is https://jira.mariadb.org/browse/MDEV-18778 and I don't see a new issue linking to it, so it probably still needs to be reported to them.

The multiple workarounds are:

  1. use a faster disk
  2. MYSQL_INITDB_SKIP_TZINFO=1 and add tzdata yourself
  3. use an older version (before 10.1.42, 10.2.27, 10.3.18, 10.4.8)
  4. use an alternative SQL like MySQL or Percona Server for MySQL

@ezawadzki
Copy link

The same with version 1.5.1.

@numericalatina
Copy link

I can confirm that this issue still happens on v. 10.4.12 and not in v. 10.3.22

From the possible workarounds i will choose sticking with a working version.

Is 10.3.22 the recommended working version then? or is it any of 10.2.27, 10.3.18, 10.4.8?

@numericalatina
Copy link

Well 10.4.8 still has this same bug according to #261 so I guess I'll stick with 10.3.18 then

@lingxiankong
Copy link

Adding -e MYSQL_INITDB_SKIP_TZINFO=1 works for me.

openstack-mirroring pushed a commit to openstack/openstack that referenced this issue Jul 18, 2020
* Update trove from branch 'master'
  - Merge "Fix the slow start of mariadb container"
  - Fix the slow start of mariadb container
    
    Adding '-e MYSQL_INITDB_SKIP_TZINFO=1' when starting database
    container.
    
    Ref:
    MariaDB/mariadb-docker#262
    
    Change-Id: I3398557700dd76ec831e441ba074032fd4b67cca
openstack-mirroring pushed a commit to openstack/trove that referenced this issue Jul 18, 2020
Adding '-e MYSQL_INITDB_SKIP_TZINFO=1' when starting database
container.

Ref:
MariaDB/mariadb-docker#262

Change-Id: I3398557700dd76ec831e441ba074032fd4b67cca
@boiddude
Copy link

I wish someone on here could have put where the file is on the docker mariadb or what command to run? If I run mysql_tzinfo_to_sql on the Mariadb Docker container it just complains that the command doens't exist. Can anyone please help with where or what or when or how that command is to be entered to stop the timezone issue?

Adding -e MYSQL_INITDB_SKIP_TZINFO=1 works for me.

Where do you add it to????

@tianon
Copy link
Contributor

tianon commented Jul 20, 2020

That's the syntax for adding an environment variable via docker run -- if you're using Kubernetes or similar, you would just add MYSQL_INITDB_SKIP_TZINFO (set to 1) as an environment variable on your container.

gregorydlogan added a commit to gregorydlogan/opencast-project-infrastructure that referenced this issue Jul 22, 2020
@grooverdan
Copy link
Member

https://jira.mariadb.org/browse/MDEV-23326 created on the 10.3 -> 10.4 performance drop.

grooverdan added a commit to grooverdan/mariadb-docker that referenced this issue Aug 6, 2020
MariaDB-10.4 defaulted to Aria for system tables.

This introduced crash safety under the name of "transactional"
that was not previously in MyISAM.

The Aria implementation of checkpointing incurs significant
penality on fuse-overlayfs that occurs significantly in
container environments, especially those without a
/var/lib/mysql volume.

We work around this penality by disabling the crash
safety of timezone tables for the period of timezone
initialization.

Analysis and timings are in https://jira.mariadb.org/browse/MDEV-23326
and local tests show that 10.4 is only 0.8 seconds slower
than 10.3 on startup (6.8 seconds total).

Version specific comments are used to ensure that ALTER TABLE
statements aren't run on < 10.4 server versions.

closes MariaDB#262
tianon pushed a commit to grooverdan/mariadb-docker that referenced this issue Aug 11, 2020
MariaDB-10.4 defaulted to Aria for system tables.

This introduced crash safety under the name of "transactional"
that was not previously in MyISAM.

The Aria implementation of checkpointing incurs significant
penality on fuse-overlayfs that occurs significantly in
container environments, especially those without a
/var/lib/mysql volume.

We work around this penality by disabling the crash
safety of timezone tables for the period of timezone
initialization.

Analysis and timings are in https://jira.mariadb.org/browse/MDEV-23326
and local tests show that 10.4 is only 0.8 seconds slower
than 10.3 on startup (6.8 seconds total).

Version specific comments are used to ensure that ALTER TABLE
statements aren't run on < 10.4 server versions.

closes MariaDB#262
@grooverdan
Copy link
Member

grooverdan commented Aug 12, 2020

All, to summarise a long issue that you have all endured:

Timezone initialization speed has been corrected in:

MariaDB 10.1.44, 10.2.31, 10.3.22 because of https://jira.mariadb.org/browse/MDEV-21209
MariaDB 10.4.14, 10.5.5 per #320

As you all can understand, having multiple issues at the same time can make it easy to loose sight of what is/isn't fixed. On behalf of the MariaDB Foundation I apologise that this upstream issue lingered so long.

The docker library team of @tianon and @yosifkit have provided you with an excellent expertise in packaging MariaDB containers for you. To grab the attention of MariaDB developers on issues that are beyond the realm of the container initialization please report those to MariaDB directly https://mariadb.com/kb/en/mariadb-community-bug-reporting/.

Retesting the latest versions released yesterday:

Start times (Samsung SSD 970 EVO Plus NVME M.2):

Version With tz Without tz
10.1.46 0m13.543s 0m12.041s
10.2.23 0m5.292s 0m4.539s
10.3.24 0m5.542s 0m4.799s
10.4.14 0m6.042s 0m4.793s
10.5.5 0m5.572s 0m4.315s

Many of you encountered issues under slow disk. So here's the same results on my 5400 rpm Western Digital Green WD40EZRX-00SPEB0:

Version With tz Without tz
10.1.46 0m17.548s 0m16.048s
10.2.23 0m6.796s 0m6.292s
10.3.24 0m6.790s 0m5.285s
10.4.14 0m12.797s 0m8.294s
10.5.5 0m11.297s 0m7.037s

ref: test script

While slower hardware still incurs a relatively high penalty in 10.4+ it is still slow with regard to time zone initialisation, I hope these improvements make it usable if you desire its functionality.

Upstream issues continue to remain open to further improve performance of initialization particularly in the 10.4+

If you are encountering any problems regarding unacceptably slow initialization from the versions above or newer onwards please create a new issue.

note: @w7089 your galera issue might be solved by some variant of #253. If it is still present in a version above or later than, please create a new issue.

grooverdan added a commit to grooverdan/mariadb-server that referenced this issue Aug 13, 2020
Aria's crash safety is its key feature over MyISAM. It
achieves this crash safety by performing a fdatasync
to after each SQL statement.

As non-transactional storage, transactional SQL statements
are typically ignored. We change that in this commit by
only performing the fdataysnc based commit on autocommit
statements. When a SQL statement is in a transaction we
defer the fdatasync to the COMMIT.

The one line that this patches, setting MARIA_HA.autocommit=0
unconditionally, has no external to maria impacts. The impacts
within Aria are:
* _ma_block_get_status where MARIA_HA gains the same flags as concurrent insert
* ha_maria::external_lock, where ma_commit() is skipped if
  autocommit==0, and MARIA_HA is cleared.

An example of the performance gains that can be acheived with
this are explified by mysql_tzinfo_to_sql loading into the
Aria based timezone system tables. With MDEV-23440, 6991
insert are wrapped in a transaction. Aria mysql_tzinfo_to_sql
slowness caused many docker container users to suffer
unaccecptable start up time where they usually disabled
the initialization (MariaDB/mariadb-docker#262).
Currently the work around is to make Aria table TRANSACTIONAL=0
during the load.

Before this patch the time taken to load the timezones
on some fast NVME, SSD is:

  $ time sql/mysql_tzinfo_to_sql   /usr/share/zoneinfo/ |client/mysql -S /tmp/s.sock mysql
  Warning: Unable to load '/usr/share/zoneinfo//leapseconds' as time zone. Skipping it.
  Warning: Unable to load '/usr/share/zoneinfo//tzdata.zi' as time zone. Skipping it.

  real	0m16.850s
  user	0m0.881s
  sys	0m0.592s

With this patch applied:

  $ time sql/mysql_tzinfo_to_sql   /usr/share/zoneinfo/ |client/mysql -S /tmp/s.sock mysql
  Warning: Unable to load '/usr/share/zoneinfo//leapseconds' as time zone. Skipping it.
  Warning: Unable to load '/usr/share/zoneinfo//tzdata.zi' as time zone. Skipping it.

  real	0m1.390s
  user	0m0.171s
  sys	0m0.087s

On slower hardware like Western Digital Green, 5400 rpm,
WDC WD40EZRX-00SPEB0 model the load time is:

  $ time sql/mysql_tzinfo_to_sql   /usr/share/zoneinfo/ |client/mysql -S /tmp/s.sock mysql
  Warning: Unable to load '/usr/share/zoneinfo//leapseconds' as time zone. Skipping it.
  Warning: Unable to load '/usr/share/zoneinfo//tzdata.zi' as time zone. Skipping it.

  real	1m14.200s
  user	0m0.855s
  sys	0m0.623s

With this patch:

  $ time sql/mysql_tzinfo_to_sql   /usr/share/zoneinfo/ |client/mysql -S /tmp/s.sock mysql
  Warning: Unable to load '/usr/share/zoneinfo//leapseconds' as time zone. Skipping it.
  Warning: Unable to load '/usr/share/zoneinfo//tzdata.zi' as time zone. Skipping it.

  real	0m2.826s
  user	0m0.176s
  sys	0m0.091s

Reference, SQL performed by this invokation (without SET statements):
$ sql/mysql_tzinfo_to_sql   /usr/share/zoneinfo/  | grep '^[A-Z]' | grep -v ^SET  |  uniq -c --check-chars=5
      1 IF (select count(*) from information_schema.global_variables where
      4 ALTER TABLE time_zone ENGINE=InnoDB;
      1 END IF|
      4 TRUNCATE TABLE time_zone;
      1 START TRANSACTION;
Warning: Unable to load '/usr/share/zoneinfo//leapseconds' as time zone. Skipping it.
Warning: Unable to load '/usr/share/zoneinfo//tzdata.zi' as time zone. Skipping it.
   6991 INSERT INTO time_zone (Use_leap_seconds) VALUES ('N');
      1 COMMIT;
      2 ALTER TABLE time_zone_transition ORDER BY Time_zone_id, Transition_time;
      1 IF (select count(*) from information_schema.global_variables where
      4 ALTER TABLE time_zone ENGINE=Aria;
      1 END IF|

Row counts:
$ for i in $( client/mysql -S /tmp/s.sock -ABNe "show tables like 'time_%'" mysql); do echo -n "$i: "; client/mysql -S /tmp/s.sock  -ABNe "select count(*) from mysql.$i;";  done
time_zone: 1783
time_zone_leap_second: 0
time_zone_name: 1783
time_zone_transition: 120290
time_zone_transition_type: 9581
bennothommo added a commit to bennothommo/dokku-mariadb that referenced this issue Feb 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging a pull request may close this issue.