Using UNRAID - I was having issues with mariadb not functioning correctly, so I decided to perform a fresh/clean install, and basically I have the same issues -
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.
Could not open required defaults file: /config/custom.cnf
Fatal error in defaults handling. Program aborted
Could not open required defaults file: /config/custom.cnf
Fatal error in defaults handling. Program aborted
actual log file shows the following - which appears to be a permissions issue, but doesn’t the /tmp directory just run in memory, why would we get a permissions issue on that?
250420 22:17:10 mysqld_safe Starting mariadbd daemon with databases from /config/databases
2025-04-20 22:17:10 0 [Note] Starting MariaDB 11.4.5-MariaDB-log source revision 0771110266ff5c04216af4bf1243c65f8c67ccf4 server_uid 2fjwt7IhJv81tIZCnnorHJouv44= as process 450
2025-04-20 22:17:10 0 [Note] InnoDB: Compressed tables use zlib 1.3.1
2025-04-20 22:17:10 0 [Note] InnoDB: Using transactional memory
2025-04-20 22:17:10 0 [Note] InnoDB: Number of transaction pools: 1
2025-04-20 22:17:10 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2025-04-20 22:17:10 0 [ERROR] mariadbd: Can't create/write to file '/tmp/ibXXXXXX' (Errcode: 13 "Permission denied")
2025-04-20 22:17:10 0 [ERROR] InnoDB: Unable to create temporary file; errno: 13
2025-04-20 22:17:10 0 [ERROR] mariadbd: Can't create/write to file '/tmp/ibXXXXXX' (Errcode: 13 "Permission denied")
2025-04-20 22:17:10 0 [ERROR] InnoDB: Unable to create temporary file; errno: 13
2025-04-20 22:17:10 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2025-04-20 22:17:10 0 [Note] InnoDB: Starting shutdown...
2025-04-20 22:17:10 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2025-04-20 22:17:10 0 [Note] Plugin 'FEEDBACK' is disabled.
2025-04-20 22:17:10 0 [Note] Plugin 'wsrep-provider' is disabled.
2025-04-20 22:17:10 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2025-04-20 22:17:10 0 [ERROR] Aborting
250420 22:17:11 mysqld_safe mysqld from pid file /run/mysqld/mysqld.pid ended
250420 22:17:12 mysqld_safe Starting mariadbd daemon with databases from /config/databases
2025-04-20 22:17:12 0 [Note] Starting MariaDB 11.4.5-MariaDB-log source revision 0771110266ff5c04216af4bf1243c65f8c67ccf4 server_uid 2fjwt7IhJv81tIZCnnorHJouv44= as process 728
2025-04-20 22:17:12 0 [Note] InnoDB: Compressed tables use zlib 1.3.1
2025-04-20 22:17:12 0 [Note] InnoDB: Using transactional memory
2025-04-20 22:17:12 0 [Note] InnoDB: Number of transaction pools: 1
2025-04-20 22:17:12 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2025-04-20 22:17:12 0 [ERROR] mariadbd: Can't create/write to file '/tmp/ibXXXXXX' (Errcode: 13 "Permission denied")
2025-04-20 22:17:12 0 [ERROR] InnoDB: Unable to create temporary file; errno: 13
2025-04-20 22:17:12 0 [ERROR] mariadbd: Can't create/write to file '/tmp/ibXXXXXX' (Errcode: 13 "Permission denied")
2025-04-20 22:17:12 0 [ERROR] InnoDB: Unable to create temporary file; errno: 13
2025-04-20 22:17:12 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2025-04-20 22:17:12 0 [Note] InnoDB: Starting shutdown...
2025-04-20 22:17:12 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2025-04-20 22:17:12 0 [Note] Plugin 'FEEDBACK' is disabled.
2025-04-20 22:17:12 0 [Note] Plugin 'wsrep-provider' is disabled.
2025-04-20 22:17:12 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2025-04-20 22:17:12 0 [ERROR] Aborting
provide the docker run and full container logs beginning with out ascii logo; your error sounds like you’re using an invalid umask and have some permissions issues.
User UID: 99
User GID: 100
─────────────────────────────────────── Linuxserver.io version: 11.4.5-r0-ls181
Build-date: 2025-04-15T07:45:53+00:00
───────────────────────────────────────
[custom-init] No custom files found, skipping…
UMASK corrected from 022 to 0640 …
250421 20:09:10 mysqld_safe Logging to ‘/config/log/mysql/mariadb-error.log’.
250421 20:09:10 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Caught SIGTERM signal!
UMASK corrected from 022 to 0640 …
250421 20:09:12 mysqld_safe Logging to ‘/config/log/mysql/mariadb-error.log’.
250421 20:09:12 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Caught SIGTERM signal!
UMASK corrected from 022 to 0640 …
250421 20:09:14 mysqld_safe Logging to ‘/config/log/mysql/mariadb-error.log’.
250421 20:09:14 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Caught SIGTERM signal!
UMASK corrected from 022 to 0640 …
250421 20:09:16 mysqld_safe Logging to ‘/config/log/mysql/mariadb-error.log’.
250421 20:09:16 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Caught SIGTERM signal!
UMASK corrected from 022 to 0640 …
250421 20:09:18 mysqld_safe Logging to ‘/config/log/mysql/mariadb-error.log’.
250421 20:09:18 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Caught SIGTERM signal!
UMASK corrected from 022 to 0640 …
250421 20:09:20 mysqld_safe Logging to ‘/config/log/mysql/mariadb-error.log’.
250421 20:09:20 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 …
250421 20:09:22 mysqld_safe Logging to ‘/config/log/mysql/mariadb-error.log’.
250421 20:09:22 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 …
250421 20:09:24 mysqld_safe Logging to ‘/config/log/mysql/mariadb-error.log’.
250421 20:09:24 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 …
250421 20:09:25 mysqld_safe Logging to ‘/config/log/mysql/mariadb-error.log’.
250421 20:09:26 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 …
250421 20:09:27 mysqld_safe Logging to ‘/config/log/mysql/mariadb-error.log’.
250421 20:09:27 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 …
250421 20:09:29 mysqld_safe Logging to ‘/config/log/mysql/mariadb-error.log’.
250421 20:09:29 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.
I am not sure how to provide the docker run from what I have configured in unraid - I looked at turning on “authoring mode” but its not an available option when I stop the docker service for some reason. I don’t have a lot of time to dig into it right now - if I get additional time in the next couple days here, I will because I am sincerely puzzled.
However, I seem to have “resolved” it by specifying version tag 11.4.4-r1-ls170
on ‘latest’ i was getting those errors and if i chmod 777 the /var/tmp and /var/run directories within the container the sql daemon would finally start.
Now that I’ve got it on the specific version tag, this is my log:
[migrations] started
[migrations] no migrations found
usermod: no changes
───────────────────────────────────────
Brought to you by linuxserver.io
───────────────────────────────────────
To support LSIO projects visit:
REDACTED SO IT WOULD POST -
───────────────────────────────────────
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 corrected from 022 to 0640 …
250421 21:24:52 mysqld_safe Logging to ‘/config/log/mysql/mariadb-error.log’.
250421 21:24:52 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Logrotate is enabled
[ls.io-init] done.
chmod 777 is never a solution for anything, to put it in windows terms, you have basically renamed every single file to end in .exe
you likely had some database corruption and newer versions of mariadb are enforcing a clean db prior to an update, you probably should do a repair and then try the upgrade.
take a look at this link Known Issue: MariaDB Check and Repair | Info :: LinuxServer.io