[BUG] <title> After upgrade container mariadb no longer works

[zedred79]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

After upgrade container mariadb no longer works.
In container log there is this error:

cat: /var/run/mysqld/mysqld.pid: No such file or directory
241028 07:06:53 mysqld_safe Logging to '/config/databases/c72553d4fb53.err'.
241028 07:06:53 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Caught SIGTERM signal!

In c72553d4fb53.err

241017 11:32:15 mysqld_safe Starting mariadbd daemon with databases from /config/databases
2024-10-17 11:32:15 0 [Note] Starting MariaDB 10.11.8-MariaDB-log source revision 3a069644682e336e445039e48baae9693f9a08ee as process 356
2024-10-17 11:32:15 0 [Note] InnoDB: Compressed tables use zlib 1.3.1
2024-10-17 11:32:15 0 [Note] InnoDB: Number of transaction pools: 1
2024-10-17 11:32:15 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2024-10-17 11:32:15 0 [Note] mariadbd: O_TMPFILE is not supported on /var/tmp (disabling future attempts)
2024-10-17 11:32:15 0 [Note] InnoDB: Using Linux native AIO
2024-10-17 11:32:15 0 [Note] InnoDB: Initializing buffer pool, total size = 256.000MiB, chunk size = 4.000MiB
2024-10-17 11:32:15 0 [Note] InnoDB: Completed initialization of buffer pool
2024-10-17 11:32:15 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
2024-10-17 11:32:15 0 [Note] InnoDB: End of log at LSN=486039276162
2024-10-17 11:32:15 0 [Note] InnoDB: 128 rollback segments are active.
2024-10-17 11:32:15 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2024-10-17 11:32:15 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2024-10-17 11:32:15 0 [Note] InnoDB: log sequence number 486039276162; transaction id 509349398
2024-10-17 11:32:15 0 [Note] InnoDB: Loading buffer pool(s) from /config/databases/ib_buffer_pool
2024-10-17 11:32:15 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-10-17 11:32:15 0 [Note] Server socket created on IP: '0.0.0.0'.
2024-10-17 11:32:15 0 [Note] Server socket created on IP: '::'.
2024-10-17 11:32:15 0 [Note] /usr/bin/mariadbd: ready for connections.
Version: '10.11.8-MariaDB-log' socket: '/run/mysqld/mysqld.sock' port: 3306 Alpine Linux
2024-10-17 11:32:15 0 [Note] InnoDB: Buffer pool(s) load completed at 241017 11:32:15
2024-10-17 11:32:16 4 [Warning] Aborted connection 4 to db: 'unconnected' user: 'unauthenticated' host: 'localhost' (This connection closed normally without authentication)
2024-10-17 11:45:59 19 [Warning] Aborted connection 19 to db: 'traccar' user: 'traccar' host: 'traccar.config_default' (Got timeout reading communication packets)
2024-10-17 11:45:59 18 [Warning] Aborted connection 18 to db: 'traccar' user: 'traccar' host: 'traccar.config_default' (Got timeout reading communication packets)
2024-10-17 11:45:59 20 [Warning] Aborted connection 20 to db: 'traccar' user: 'traccar' host: 'traccar.config_default' (Got timeout reading communication packets)
2024-10-17 11:45:59 21 [Warning] Aborted connection 21 to db: 'traccar' user: 'traccar' host: 'traccar.config_default' (Got timeout reading communication packets)
2024-10-17 11:45:59 22 [Warning] Aborted connection 22 to db: 'traccar' user: 'traccar' host: 'traccar.config_default' (Got timeout reading communication packets)
2024-10-17 11:45:59 23 [Warning] Aborted connection 23 to db: 'traccar' user: 'traccar' host: 'traccar.config_default' (Got timeout reading communication packets)
2024-10-17 11:45:59 24 [Warning] Aborted connection 24 to db: 'traccar' user: 'traccar' host: 'traccar.config_default' (Got timeout reading communication packets)
2024-10-17 11:45:59 25 [Warning] Aborted connection 25 to db: 'traccar' user: 'traccar' host: 'traccar.config_default' (Got timeout reading communication packets)
2024-10-17 11:45:59 26 [Warning] Aborted connection 26 to db: 'traccar' user: 'traccar' host: 'traccar.config_default' (Got timeout reading communication packets)
2024-10-17 11:49:52 8 [Warning] Aborted connection 8 to db: 'bitwarden' user: 'bitwarden' host: 'bitwarden.config_default' (Got timeout reading communication packets)
2024-10-17 11:49:54 7 [Warning] Aborted connection 7 to db: 'bitwarden' user: 'bitwarden' host: 'bitwarden.config_default' (Got timeout reading communication packets)
2024-10-17 11:50:52 48 [Warning] Aborted connection 48 to db: 'bitwarden' user: 'bitwarden' host: 'bitwarden.config_default' (Got timeout reading communication packets)
2024-10-17 11:50:54 47 [Warning] Aborted connection 47 to db: 'bitwarden' user: 'bitwarden' host: 'bitwarden.config_default' (Got timeout reading communication packets)
2024-10-17 11:51:20 52 [Warning] Aborted connection 52 to db: 'bitwarden' user: 'bitwarden' host: 'bitwarden.config_default' (Got timeout reading communication packets)
2024-10-17 11:51:20 53 [Warning] Aborted connection 53 to db: 'bitwarden' user: 'bitwarden' host: 'bitwarden.config_default' (Got timeout reading communication packets)
2024-10-17 11:51:52 55 [Warning] Aborted connection 55 to db: 'bitwarden' user: 'bitwarden' host: 'bitwarden.config_default' (Got timeout reading communication packets)
......
2024-10-26 22:21:01 0 [Note] /usr/bin/mariadbd (initiated by: unknown): Normal shutdown
2024-10-26 22:21:01 0 [Note] InnoDB: FTS optimize thread exiting.
2024-10-26 22:21:01 0 [Note] InnoDB: Starting shutdown...
2024-10-26 22:21:01 0 [Note] InnoDB: Dumping buffer pool(s) to /config/databases/ib_buffer_pool
2024-10-26 22:21:01 0 [Note] InnoDB: Restricted to 4048 pages due to innodb_buf_pool_dump_pct=25
2024-10-26 22:21:01 0 [Note] InnoDB: Buffer pool(s) dump completed at 241026 22:21:01
2024-10-26 22:21:01 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
2024-10-26 22:21:01 0 [Note] InnoDB: Shutdown completed; log sequence number 486947364667; transaction id 512048073
2024-10-26 22:21:01 0 [Note] /usr/bin/mariadbd: Shutdown complete

241026 22:21:01 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
241026 22:23:06 mysqld_safe Starting mariadbd daemon with databases from /config/databases
2024-10-26 22:23:06 0 [Note] Starting MariaDB 10.11.8-MariaDB-log source revision 3a069644682e336e445039e48baae9693f9a08ee as process 353
2024-10-26 22:23:06 0 [Note] InnoDB: Compressed tables use zlib 1.3.1
2024-10-26 22:23:06 0 [Note] InnoDB: Number of transaction pools: 1
2024-10-26 22:23:06 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2024-10-26 22:23:06 0 [Note] mariadbd: O_TMPFILE is not supported on /var/tmp (disabling future attempts)
2024-10-26 22:23:06 0 [Note] InnoDB: Using Linux native AIO
2024-10-26 22:23:06 0 [Note] InnoDB: Initializing buffer pool, total size = 256.000MiB, chunk size = 4.000MiB
2024-10-26 22:23:06 0 [Note] InnoDB: Completed initialization of buffer pool
2024-10-26 22:23:06 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
2024-10-26 22:23:06 0 [Note] InnoDB: End of log at LSN=486947364667
2024-10-26 22:23:06 0 [Note] InnoDB: 128 rollback segments are active.
2024-10-26 22:23:06 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2024-10-26 22:23:06 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2024-10-26 22:23:06 0 [Note] InnoDB: log sequence number 486947364667; transaction id 512048074
2024-10-26 22:23:06 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-10-26 22:23:06 0 [Note] InnoDB: Loading buffer pool(s) from /config/databases/ib_buffer_pool
2024-10-26 22:23:06 0 [Note] Server socket created on IP: '0.0.0.0'.
2024-10-26 22:23:06 0 [Note] Server socket created on IP: '::'.
2024-10-26 22:23:06 0 [Note] /usr/bin/mariadbd: ready for connections.
Version: '10.11.8-MariaDB-log' socket: '/run/mysqld/mysqld.sock' port: 3306 Alpine Linux
2024-10-26 22:23:06 0 [Note] InnoDB: Buffer pool(s) load completed at 241026 22:23:06
2024-10-26 22:23:07 4 [Warning] Aborted connection 4 to db: 'unconnected' user: 'unauthenticated' host: 'localhost' (This connection closed normally without authentication)
2024-10-26 22:25:07 0 [Note] /usr/bin/mariadbd (initiated by: unknown): Normal shutdown
2024-10-26 22:25:08 0 [Note] InnoDB: FTS optimize thread exiting.
2024-10-26 22:25:08 0 [Note] InnoDB: Starting shutdown...
2024-10-26 22:25:08 0 [Note] InnoDB: Dumping buffer pool(s) to /config/databases/ib_buffer_pool
2024-10-26 22:25:08 0 [Note] InnoDB: Restricted to 4048 pages due to innodb_buf_pool_dump_pct=25
2024-10-26 22:25:08 0 [Note] InnoDB: Buffer pool(s) dump completed at 241026 22:25:08
2024-10-26 22:25:08 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
2024-10-26 22:25:08 0 [Note] InnoDB: Shutdown completed; log sequence number 486947364667; transaction id 512048075
2024-10-26 22:25:08 0 [Note] /usr/bin/mariadbd: Shutdown complete

241026 22:25:08 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

Expected Behavior

No response

Steps To Reproduce

I only launch docker-compose pull and docker-compose up -d

Environment

- OS:Ubuntu server 24.04.1 LTS
- How docker service was installed: docker-compose

CPU architecture

x86-64

Docker creation

mariadb:
    image: lscr.io/linuxserver/mariadb
    container_name: mariadb
    environment:
      - PUID=1000
      - PGID=1000
      - MYSQL_ROOT_PASSWORD=mysecretpass
      - TZ=Europe/Rome
      - MYSQL_DATABASE=mydatabase
      - MYSQL_USER=user
      - MYSQL_PASSWORD=mysecretpass
     #- REMOTE_SQL=http://URL1/your.sql,https://URL2/your.sql #optional
    volumes:
      - /config/mariadb:/config
    ports:
      - 3306:3306
    restart: unless-stopped

Container logs

cat: /var/run/mysqld/mysqld.pid: No such file or directory
241028 07:06:53 mysqld_safe Logging to '/config/databases/c72553d4fb53.err'.
241028 07:06:53 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Caught SIGTERM signal!

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[FlemmingKrarup]

Hi
I have the same error, I have identified two workarounds.

1. Remove and recreate the container: docker compose down && docker compose up -d
2. Connect to the container bash and delete the pid file (/var/run/mysqld/mysqld.pid) and restart the container.

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[FlemmingKrarup]

Temporary Workaround for Orphan mysql.pid Issue

Until a permanent fix is approved, you can use the following workaround:

1. Create a Script
   Create a file named rmpid.sh in your config folder with the following content:

   #!/bin/sh
   echo "Checking for orphan mysql.pid..."
   if [ -f /var/run/mysqld/mysqld.pid ]; then
     rm /var/run/mysqld/mysqld.pid
     echo "File found and deleted: /var/run/mysqld/mysqld.pid"
   else
     echo "File not found: /var/run/mysqld/mysqld.pid"
   fi
   exec /init

2. Set Permissions
   Make the script executable and adjust ownership to match your setup. For example:

   chmod +x /path/to/config/rmpid.sh
   chown <your-user>:<your-group> /path/to/config/rmpid.sh

3. Update Docker Compose
   Add the following entry to your docker-compose.yml file to use the script as the entrypoint:

   entrypoint: ["/bin/sh", "/config/rmpid.sh"]

This script ensures any orphan mysql.pid file is removed before starting the application.

[quietsy]

Hopefully solved in the latest release, feel free to reopen if needed.
CC @thespad

[HamletDuFromage]

I'm having the same issue, just pulled the latest db

docker logs -f mariadb
[migrations] started
[migrations] no migrations found
───────────────────────────────────────

██╗     ███████╗██╗ ██████╗
██║     ██╔════╝██║██╔═══██╗
██║     ███████╗██║██║   ██║
██║     ╚════██║██║██║   ██║
███████╗███████║██║╚██████╔╝
╚══════╝╚══════╝╚═╝ ╚═════╝

Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    1000
User GID:    1000
───────────────────────────────────────
Linuxserver.io version: 11.4.4-r1-ls172
Build-date: 2025-02-04T07:47:11+00:00
───────────────────────────────────────

[custom-init] No custom files found, skipping...
250205 19:38:26 mysqld_safe Logging to '/config/log/mysql/mariadb-error.log'.
250205 19:38:26 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Caught SIGTERM signal!

this is the error logged in /config/log/mysql/mariadb-error.log

250205 19:45:05 mysqld_safe Starting mariadbd daemon with databases from /config/databases
2025-02-05 19:45:05 0 [Note] Starting MariaDB 11.4.4-MariaDB-log source revision e9a502df08bad16aa8a354e854f3c014b1380e32 server_uid 3F2+ETJJP4X/DYe6eBHePHXpFEk= as process 14581
2025-02-05 19:45:05 0 [Note] InnoDB: Compressed tables use zlib 1.3.1
2025-02-05 19:45:05 0 [Note] InnoDB: Number of transaction pools: 1
2025-02-05 19:45:05 0 [Note] InnoDB: Using SSE4.2 crc32 instructions
2025-02-05 19:45:05 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
2025-02-05 19:45:05 0 [Note] InnoDB: Using Linux native AIO
2025-02-05 19:45:05 0 [Note] InnoDB: Initializing buffer pool, total size = 256.000MiB, chunk size = 4.000MiB
2025-02-05 19:45:05 0 [Note] InnoDB: Completed initialization of buffer pool
2025-02-05 19:45:05 0 [ERROR] InnoDB: File ./ib_logfile0 was not found
2025-02-05 19:45:05 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2025-02-05 19:45:05 0 [Note] InnoDB: Starting shutdown...
2025-02-05 19:45:06 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2025-02-05 19:45:06 0 [Note] Plugin 'FEEDBACK' is disabled.
2025-02-05 19:45:06 0 [Note] Plugin 'wsrep-provider' is disabled.
2025-02-05 19:45:06 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2025-02-05 19:45:06 0 [ERROR] Aborting
250205 19:45:06 mysqld_safe mysqld from pid file /run/mysqld/mysqld.pid ended
(END)

EDIT: this might be a different issue actually, and maybe user error. I pulled a backup, updated it and it seems to work fine now