[MDEV-31486] mariadb crash after startup on bitnami redmine Containers Created: 2023-06-16  Updated: 2023-06-27  Resolved: 2023-06-25

Status: Closed
Project: MariaDB Server
Component/s: Docker
Affects Version/s: 10.6.14
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Masato Nagao Assignee: Daniel Black
Resolution: Duplicate Votes: 0
Labels: crash
Environment:

Attachments: Text File bitnami_mariadb_log.txt    
Issue Links:
Duplicate
duplicates MDEV-28580 Server crash when creating an index a... Closed

 Description   

i did below operation

  1. curl -sSL https://raw.githubusercontent.com/bitnami/containers/main/bitnami/redmine/docker-compose.yml > docker-compose.yml
  2. docker-compose up -d
  3. marinadb and redmine containers were started
  4. but, after few seconds mariadb container was crashed and stop all containers. attach log file


 Comments   
Comment by Daniel Black [ 2023-06-17 ]

Appears to be a duplicate of MDEV-31347

Comment by Daniel Black [ 2023-06-17 ]

Not sure how repeatable it was, but testing with the latest build of 10.6 appears to be successful a few time I tested.

compose modified

version: '2'
services:
  mariadb:
    image: quay.io/mariadb-foundation/mariadb-devel:10.6
    volumes:
      - 'mariadb_data:/var/lib/mysql'
    environment:
      - MARIADB_ALLOW_EMPTY_ROOT_PASSWORD=yes
      - MARIADB_USER=bn_redmine
      - MARIADB_PASSWORD=rm
      - MARIADB_DATABASE=bitnami_redmine
  redmine:
    image: docker.io/bitnami/redmine:5
    ports:
      - '8080:3000'
    volumes:
      - 'redmine_data:/bitnami/redmine'
    depends_on:
      - mariadb
    environment:
      # ALLOW_EMPTY_PASSWORD is recommended only for development.
      - ALLOW_EMPTY_PASSWORD=yes
      - REDMINE_DATABASE_HOST=mariadb
      - REDMINE_DATABASE_PORT_NUMBER=3306
      - REDMINE_DATABASE_USER=bn_redmine
      - REDMINE_DATABASE_PASSWORD=rm
      - REDMINE_DATABASE_NAME=bitnami_redmine
volumes:
  mariadb_data:
    driver: local
  redmine_data:
    driver: local

Note: this was assuming a MDEV-31347 bug fix, and wasn't tested under WSL.

Comment by Daniel Black [ 2023-06-18 ]

Being WSL - it seems it would be MDEV-28580 / https://github.com/microsoft/WSL/issues/8443 (particularly if this occurs every time)

Comment by Daniel Black [ 2023-06-25 ]

Sorry ma3107gao, its a WSL bug that writing a work around for would be a large code restructure that I don't want to attempt on a stable version.

Comment by Masato Nagao [ 2023-06-27 ]

Thank you for your inquiry.
I changed db to postresql and avoid this problem.

Generated at Thu Feb 08 10:24:14 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.