No way to detect full initialization of the database, healthcheck.sh always returns code 0

[olivierboudet]

Name and Version

bitnami/mariadb:10.11

What architecture are you using?

None

What steps will reproduce the bug?

1. Run mariadb with a lot of sql files which slow down initialization with a compose file like this :

  db:
    image: bitnami/mariadb:10.11
    environment:
      BITNAMI_DEBUG: true
      ALLOW_EMPTY_PASSWORD: "true"
      MARIADB_SKIP_TEST_DB: "yes"
      MARIADB_USER: root
      MARIADB_PASSWORD: password
      MARIADB_DATABASE: bitnami
      MARIADB_ROOT_PASSWORD: password
    ports:
      - 3306:3306
    healthcheck:
      test: [ "CMD", "/opt/bitnami/scripts/mariadb/healthcheck.sh", "--connect", "--innodb_initialized" ]
      start_period: 10s
      interval: 10s
      timeout: 5s
      retries: 10
    volumes:
      - ./sql/:/docker-entrypoint-initdb.d/

2. we expect the container to be ready only when initialization is completed. In the official mariadb image, initialization of the db is executed with the server running with --skip-networking flag. In this case, healthcheck.sh --connect fails and the container is not in a ready state.
   With the bitnami image, the --skip-networking flag is not used, which prevents to detect the full initialization of the database

What is the expected behavior?

healthcheck.sh --connect should allow to detect the full initialization of the database

What do you see instead?

There is no way to detect the real ready state of the database

Additional information

If this bug is valid and the proposal to use --skip-networking during setup is accepted, I am willing to contribute to this, please tell me.

[alvneiayu]

hi @olivierboudet

I think that I am reproducing the error. Could you send me logs reproducing the problem, please? Just to be aligned.

Thanks a lot

Álvaro

[olivierboudet]

hello @alvneiayu
I am not sure of what kind of logs you need, but here it is the startup logs when executing custom scripts :

db  | mariadb 10:03:15.87 INFO  ==> Running mysql_upgrade
db  | mariadb 10:03:15.89 INFO  ==> Loading user's custom files from /docker-entrypoint-initdb.d
db  | find: '/docker-entrypoint-startdb.d/': No such file or directory
db  | mariadb 10:04:34.21 INFO  ==> Stopping mariadb
db  | 2025-01-25 10:04:34 0 [Note] /opt/bitnami/mariadb/sbin/mysqld (initiated by: unknown): Normal shutdown

you can see that my script took more than 1 minute.

During this minute, I ran healthcheck.sh regularly :

I have no name!@5607c18d2932:/$ /opt/bitnami/scripts/mariadb/healthcheck.sh 
mysqld is alive
Uptime: 73  Threads: 7  Questions: 1012  Slow queries: 0  Opens: 762  Flush tables: 1  Open tables: 88  Queries per second avg: 13.863
I have no name!@5607c18d2932:/$ /opt/bitnami/scripts/mariadb/healthcheck.sh 
mysqld is alive
Uptime: 75  Threads: 7  Questions: 1091  Slow queries: 0  Opens: 776  Flush tables: 1  Open tables: 97  Queries per second avg: 14.546
I have no name!@5607c18d2932:/$ /opt/bitnami/scripts/mariadb/healthcheck.sh 
mysqld is alive
Uptime: 75  Threads: 7  Questions: 1212  Slow queries: 0  Opens: 787  Flush tables: 1  Open tables: 108  Queries per second avg: 16.160
I have no name!@5607c18d2932:/$ /opt/bitnami/scripts/mariadb/healthcheck.sh 
mysqld is alive
Uptime: 76  Threads: 7  Questions: 1343  Slow queries: 0  Opens: 790  Flush tables: 1  Open tables: 111  Queries per second avg: 17.671
I have no name!@5607c18d2932:/$ /opt/bitnami/scripts/mariadb/healthcheck.sh 
mysqld is alive
Uptime: 76  Threads: 7  Questions: 1451  Slow queries: 0  Opens: 796  Flush tables: 1  Open tables: 117  Queries per second avg: 19.092
I have no name!@5607c18d2932:/$ /opt/bitnami/scripts/mariadb/healthcheck.sh 
mysqld is alive
Uptime: 77  Threads: 7  Questions: 1560  Slow queries: 0  Opens: 800  Flush tables: 1  Open tables: 121  Queries per second avg: 20.259
I have no name!@5607c18d2932:/$ /opt/bitnami/scripts/mariadb/healthcheck.sh 
mysqld is alive
Uptime: 78  Threads: 7  Questions: 1691  Slow queries: 0  Opens: 814  Flush tables: 1  Open tables: 135  Queries per second avg: 21.679
I have no name!@5607c18d2932:/$ /opt/bitnami/scripts/mariadb/healthcheck.sh 
mysqld is alive
Uptime: 78  Threads: 7  Questions: 1701  Slow queries: 0  Opens: 818  Flush tables: 1  Open tables: 135  Queries per second avg: 21.807
I have no name!@5607c18d2932:/$ /opt/bitnami/scripts/mariadb/healthcheck.sh 
mysqld is alive
Uptime: 79  Threads: 7  Questions: 1769  Slow queries: 0  Opens: 831  Flush tables: 1  Open tables: 140  Queries per second avg: 22.392
I have no name!@5607c18d2932:/$ /opt/bitnami/scripts/mariadb/healthcheck.sh 
mysqld is alive
Uptime: 80  Threads: 7  Questions: 1823  Slow queries: 0  Opens: 840  Flush tables: 1  Open tables: 143  Queries per second avg: 22.787
I have no name!@5607c18d2932:/$ /opt/bitnami/scripts/mariadb/healthcheck.sh 

you can see that the number of tables increases as the scripts are executed, but the healthcheck is always returning a success.

[alvneiayu]

hi @olivierboudet

thanks a lot for your response. I created an internal issue to investigate and fix the problem if it is possible.

we will come back as soon as we have a solution for this. PRs are welcome. If you find a solution from your side, I will be really happy to review it.

Thanks a lot again

Álvaro

[olivierboudet]

hello @alvneiayu I sent a PR which works for my use case, I let you check it.

[carrodher]

Thank you for opening this issue and submitting the associated Pull Request. Our team will review and provide feedback. Once the PR is merged, the issue will automatically close.

Your contribution is greatly appreciated!