[BUG] Scrolling error after a few days - Caught SIGTERM

[joshmans]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Constant Scrolling Error every few days, have to delete the container and recreate it.

50921 17:20:42 mysqld_safe Logging to '/config/log/mysql/mariadb-error.log'.
250921 17:20:42 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Caught SIGTERM signal!
cat: /run/mysqld/mysqld.pid: No such file or directory
UMASK must be a 3-digit mode with an additional leading 0 to indicate octal.
The first digit will be corrected to 6, the others may be 0, 2, 4, or 6.
UMASK corrected from 022 to 0640 ...
250921 17:20:43 mysqld_safe Logging to '/config/log/mysql/mariadb-error.log'.
250921 17:20:43 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Caught SIGTERM signal!
cat: /run/mysqld/mysqld.pid: No such file or directory
UMASK must be a 3-digit mode with an additional leading 0 to indicate octal.
The first digit will be corrected to 6, the others may be 0, 2, 4, or 6.
UMASK corrected from 022 to 0640 ...

Expected Behavior

That the container stays started

Steps To Reproduce

1. On Unraid, version doesn't matter, currently on 7.2 beta3, but has also been happening since 6.x was current.
2. MDB version doesn't matter, currently hard coded to 11.4.4-r1-ls170
3. After anywhere from 24 hours up to 96 hours it starts scrolling the referenced error

Environment

- OS: Unraid 7.2 b3
- How docker service was installed: Unraid Community Apps

CPU architecture

x86-64

Docker creation

https://i.postimg.cc/tJNvxjwc/Screenshot-2025-09-21-at-5-25-45-PM.png

Container logs

I deleted the container before being able to capture it - if there isn't a resolution prior to it happening again i'll grab it.

Here it is after re-creating the container and it working:

root@catan:~# docker logs 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:    99
User GID:    100
───────────────────────────────────────
Linuxserver.io version: 11.4.4-r1-ls170
Build-date: 2025-01-21T07:43:05+00:00
───────────────────────────────────────
    
[custom-init] No custom files found, skipping...
UMASK must be a 3-digit mode with an additional leading 0 to indicate octal.
The first digit will be corrected to 6, the others may be 0, 2, 4, or 6.
UMASK corrected from 022 to 0640 ...
250921 17:26:12 mysqld_safe Logging to '/config/log/mysql/mariadb-error.log'.
250921 17:26:12 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Connection to localhost (::1) 3306 port [tcp/mysql] succeeded!
Logrotate is enabled
[ls.io-init] done.

[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.

[joshmans]

Note that I also did reference https://info.linuxserver.io/issues/2023-05-29-mariadb/ and there weren't any unclean DB's, but i cleaned and optimized anyway and we'll see what happens over the next few days.

[j0nnymoe]

Do you have any backup routines setup for mariadb within unraid?
Also, worth noting that the version you're running is a build that's 9 months old.

[joshmans]

backup routines haven't been working for awhile - this is a good reminder to revisit that.

I did also just change my image tag to mariadb:11.4.5-r2-ls192, thus far with no adverse affects.

[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.

[LinuxServer-CI]

This issue is locked due to inactivity