Bitwarden Unified with MariaDB leads to "SIGABRT (core dumped); not expected" IPV6

[Cpd879]

Steps To Reproduce

1. Define the docker-compose.yml file as shown - Deploy Unified Beta
2. Define the settings.env file as shown - Deploy Unified Beta
3. Run sudo docker compose up -d
4. Check sudo docker logs <container> sudo docker logs <container-db>

docker-compose.yml

version: "3.8"

services:
  bitwarden:
    depends_on:
      - db
    env_file:
      - settings.env
    image: bitwarden/self-host:beta
    restart: always
    ports:
      - "2012:8080"
      - "879:8443"
    volumes:
      - bitwarden:/etc/bitwarden

  db:
    environment:
      MARIADB_USER: "bitwarden"
      MARIADB_PASSWORD: "OBFUSCATED"
      MARIADB_DATABASE: "bitwarden_vault"
      MARIADB_RANDOM_ROOT_PASSWORD: "false"
      MARIADB_ROOT_PASSWORD: "OBFUSCATED"
    image: mariadb:10
    restart: always
    volumes:
      - data:/var/lib/mysql
      - /etc/bitwarden:/etc/bitwarden
volumes:
  bitwarden:
  data:

settings.env

# Domain
BW_DOMAIN=anarchistsmp.ddns.net
# Key Settings
BW_INSTALLATION_ID=OBFUSCATED
BW_INSTALLATION_KEY=OBFUSCATED
# Database Settings
BW_DB_PROVIDER=mysql
BW_DB_SERVER=db
BW_DB_DATABASE=bitwarden_vault
BW_DB_USERNAME=bitwarden
BW_DB_PASSWORD=Cpd2012$
BW_DB_PORT=3306
# SSL Settings
BW_ENABLE_SSL=true
BW_SSL_CERT=fullchain.pem
BW_SSL_KEY=privkey.pem
BW_ENABLE_SSL_DH=true
BW_SSL_DH_CERT=dh.pem
# SMTP Settings
[email protected]
globalSettings__mail__smtp__host=smtp.gmail.com
globalSettings__mail__smtp__port=465
globalSettings__mail__smtp__ssl=true
[email protected]
globalSettings__mail__smtp__password=OBFUSCATED
# Additional Settings
BW_ENABLE_ADMIN=true
BW_ENABLE_API=true
BW_ENABLE_ICONS=true
BW_ENABLE_EVENTS=false
BW_ENABLE_SSO=false
BW_ENABLE_NOTIFICATIONS=true
[email protected]
globalSettings__disableUserRegistration=false

Expected Result

Objective: Deploy Bitwarden using Docker with a MariaDB backend to manage and store encrypted password data securely.

Expected Sequence of Events:

MariaDB Container Initialization:

The MariaDB container starts successfully, creating a database named bitwarden_vault and a user bitwarden with the specified password OBFUSCATED.
Database Connection:

Bitwarden, upon initialization, connects to the MariaDB container using the credentials provided, allowing it to interact with the bitwarden_vault database for data storage and retrieval.
Data Persistence:

Data from the MariaDB instance persists correctly through the mounted volume (/var/lib/mysql), ensuring that password data remains available even after container restarts.
User Management:

The bitwarden user is granted all necessary permissions on the bitwarden_vault database, allowing for full CRUD operations without restrictions.
Successful Application Launch:

Bitwarden starts successfully, with all components (such as admin, identity, and API) running without errors, enabling users to access the web interface.
Operational Status:

Both the Bitwarden and MariaDB containers remain healthy, with no fatal errors or connection issues, ensuring smooth operation.

Actual Result

Objective: Deploy Bitwarden using Docker with a MariaDB backend to manage and store encrypted password data securely.

Actual Sequence of Events:

MariaDB Container Initialization:

The MariaDB container started but encountered warnings about memory pressure and socket issues.
The database bitwarden_vault was created, but the connection was later denied for the bitwarden user.
Database Connection Issues:

Bitwarden was unable to connect to the MariaDB container, leading to repeated access denied errors for the bitwarden user, indicating potential permission or configuration issues.
Error in User Permissions:

The expected permissions for the bitwarden user were not properly configured, resulting in access denial when Bitwarden attempted to connect.
Nginx Component Failures:

The Nginx process within the Bitwarden container repeatedly exited unexpectedly, leading to service failures and the Bitwarden application failing to launch completely.
Manual Interventions:

Attempts to manually grant permissions to the bitwarden user on the bitwarden_vault database were made, indicating an ongoing struggle to establish proper access.
Persistent Configuration Issues:

Despite multiple attempts, the database connection and application launch remained problematic, suggesting further troubleshooting is necessary.

Screenshots or Videos

settings.env

docker-compose.yml

Additional Context

Error Log of bitwarden-bitwarden-1

Cpd879@hostrpi:/etc/bitwarden $ docker logs -f bitwarden-bitwarden-1
Adding group `bitwarden' (GID 1000) ...
Done.
Adding user `bitwarden' ...
Adding new user `bitwarden' (1000) with group `bitwarden (1000)' ...
Not creating home directory `/home/bitwarden'.
Adding new user `bitwarden' to supplemental / extra groups `users' ...
Adding user `bitwarden' to group `users' ...
2024-09-28 15:31:01,068 INFO Included extra file "/etc/supervisor.d/admin.ini" during parsing
2024-09-28 15:31:01,068 INFO Included extra file "/etc/supervisor.d/api.ini" during parsing
2024-09-28 15:31:01,068 INFO Included extra file "/etc/supervisor.d/events.ini" during parsing
2024-09-28 15:31:01,068 INFO Included extra file "/etc/supervisor.d/icons.ini" during parsing
2024-09-28 15:31:01,068 INFO Included extra file "/etc/supervisor.d/identity.ini" during parsing
2024-09-28 15:31:01,068 INFO Included extra file "/etc/supervisor.d/nginx.ini" during parsing
2024-09-28 15:31:01,068 INFO Included extra file "/etc/supervisor.d/notifications.ini" during parsing
2024-09-28 15:31:01,068 INFO Included extra file "/etc/supervisor.d/scim.ini" during parsing
2024-09-28 15:31:01,068 INFO Included extra file "/etc/supervisor.d/sso.ini" during parsing
2024-09-28 15:31:01,075 INFO RPC interface 'supervisor' initialized
2024-09-28 15:31:01,075 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2024-09-28 15:31:01,075 INFO supervisord started with pid 1
2024-09-28 15:31:02,078 INFO spawned: 'identity' with pid 66
2024-09-28 15:31:02,081 INFO spawned: 'admin' with pid 67
2024-09-28 15:31:02,083 INFO spawned: 'api' with pid 68
2024-09-28 15:31:02,086 INFO spawned: 'icons' with pid 69
2024-09-28 15:31:02,093 INFO spawned: 'nginx' with pid 70
2024-09-28 15:31:02,100 INFO spawned: 'notifications' with pid 71
2024-09-28 15:31:02,142 WARN exited: nginx (exit status 1; not expected)
2024-09-28 15:31:03,305 INFO spawned: 'nginx' with pid 139
2024-09-28 15:31:03,352 WARN exited: nginx (exit status 1; not expected)
2024-09-28 15:31:05,783 INFO spawned: 'nginx' with pid 164
2024-09-28 15:31:05,833 WARN exited: nginx (exit status 1; not expected)
2024-09-28 15:31:08,835 INFO spawned: 'nginx' with pid 165
2024-09-28 15:31:08,851 WARN exited: nginx (exit status 1; not expected)
2024-09-28 15:31:09,852 INFO gave up: nginx entered FATAL state, too many start retries too quickly
2024-09-28 15:31:17,860 INFO success: identity entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2024-09-28 15:31:17,860 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2024-09-28 15:31:17,860 INFO success: api entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2024-09-28 15:31:17,860 INFO success: icons entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2024-09-28 15:31:17,860 INFO success: notifications entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2024-09-28 15:31:38,671 WARN exited: admin (terminated by SIGABRT (core dumped); not expected)
2024-09-28 15:31:39,673 INFO spawned: 'admin' with pid 177
2024-09-28 15:31:54,690 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2024-09-28 15:32:05,897 WARN exited: admin (terminated by SIGABRT (core dumped); not expected)
2024-09-28 15:32:19,718 INFO spawned: 'admin' with pid 210

Error Log of bitwarden-db-1

Cpd879@hostrpi:/etc/bitwarden $ docker logs bitwarden-db-1
2024-09-28 15:28:56+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.11.9+maria~ubu2204 started.
2024-09-28 15:28:57+00:00 [Warn] [Entrypoint]: /sys/fs/cgroup///memory.pressure not writable, functionality unavailable to MariaDB
2024-09-28 15:28:57+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2024-09-28 15:28:57+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.11.9+maria~ubu2204 started.
2024-09-28 15:28:57+00:00 [Note] [Entrypoint]: MariaDB upgrade not required
2024-09-28 15:28:57 0 [Note] Starting MariaDB 10.11.9-MariaDB-ubu2204 source revision 0e8fb977b00983d98c4c35e39bc1f36463095938 server_uid VAS6fteRWveSz6OTMl6mfUMiFww= as process 1
2024-09-28 15:28:57 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2024-09-28 15:28:57 0 [Note] InnoDB: Number of transaction pools: 1
2024-09-28 15:28:57 0 [Note] InnoDB: Using ARMv8 crc32 + pmull instructions
2024-09-28 15:28:57 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
2024-09-28 15:28:57 0 [Note] InnoDB: Using liburing
2024-09-28 15:28:57 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2024-09-28 15:28:57 0 [Note] InnoDB: Completed initialization of buffer pool
2024-09-28 15:28:57 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
2024-09-28 15:28:58 0 [Note] InnoDB: End of log at LSN=46846
2024-09-28 15:28:58 0 [Note] InnoDB: 128 rollback segments are active.
2024-09-28 15:28:58 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2024-09-28 15:28:58 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2024-09-28 15:28:58 0 [Note] InnoDB: log sequence number 46846; transaction id 14
2024-09-28 15:28:58 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2024-09-28 15:28:58 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-09-28 15:28:58 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
2024-09-28 15:28:58 0 [Note] InnoDB: Buffer pool(s) load completed at 240928 15:28:58
2024-09-28 15:28:58 0 [Note] Server socket created on IP: '0.0.0.0'.
2024-09-28 15:28:58 0 [Note] Server socket created on IP: '::'.
2024-09-28 15:28:58 0 [Note] mariadbd: ready for connections.
Version: '10.11.9-MariaDB-ubu2204'  socket: '/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
2024-09-28 15:31:23 3 [Warning] Access denied for user 'bitwarden'@'172.30.0.3' (using password: YES)
2024-09-28 15:32:00 4 [Warning] Access denied for user 'bitwarden'@'172.30.0.3' (using password: YES)

Githash Version

24a548ee180b

Environment Details

-Board = Raspberry Pi 5
-OS = Linux hostrpi 6.6.47+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.47-1+rpt1 (2024-09-02) aarch64 GNU/Linux
CPU: Quad-core ARM Cortex-A76, 64-bit, clocked at 2.4 GHz

RAM:4 GB LPDDR4X-4266 SDRAM

GPU: VideoCore VII (7th generation) graphics

Networking: Gigabit Ethernet, Wi-Fi 6 (802.11ax), Bluetooth 5.0

USB: Two USB 3.0 ports and two USB 2.0 ports

Storage: microSD card slot (support for UHS-I), PCIe 2.0 x1 for additional storage or peripherals

Video Outputs: Dual micro-HDMI ports, supporting up to 4K@60fps

Database Image

Database Image

mariadb:10

Issue-Link

#2480

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[sso-bitwarden]

Hi,

I attempted to reproduce your issue and was unable to do so. I suspect the password is wrong. Let's try a simpler password, possibly without symbols (for testing), and see how it goes.

We use GitHub issues as a place to track bugs and other development related issues. If your issue persists, please write us back using our “Contact support” form located on our Help Center (https://bitwarden.com/help/).