Downgraded from 6.12.1 to 6.11.5 - now none of my MariaDB containers will start

[BurntOC]

So 6.12.x was giving me fits.  I downgraded back to 6.11.5, but I also had to use mover and dynamix file manager to move my files off cache and reformat back to xfs, then put the files back on (since 6.11 didn't natively support zfs).  My other containers are starting fine, but I have 3 Mariadb dockers that are throwing errors like this:

 

Caught SIGTERM signal!
UMASK corrected from 022 to 0640 ...
230628 16:41:31 mysqld_safe Logging to '/config/databases/c6cc2824f233.err'.
230628 16:41:31 mysqld_safe Starting mariadbd daemon with databases from /config/databases

 

I tried changing the UMASK to 0640 in the template but it seems to revert.  I tried copying the directory from an extracted backup and it fails with a different error.  Thought maybe permissions needed to be reset to nobody:users and 744 like the others, but the error remains the same:

 

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

User UID:    99
User GID:    100
───────────────────────────────────────

Setting Up Initial Databases
Couldn't set an owner to '/auth_pam_tool_dir/auth_pam_tool'.
It must be root, the PAM authentication plugin doesn't work otherwise..

Cannot change ownership of the '/auth_pam_tool_dir' directory
to the 'abc' user. Check that you have the necessary permissions and try again.

Installing MariaDB/MySQL system tables in '/config/databases' ...

Installation of system tables failed!  Examine the logs in
/config/databases for more information.

 

I also have one PostgreSQL database that is erroring with this type of message, but it seems it might be continuing to launch properly after that and chmod and chowning as above didn't seem to help here either.

 

2023-06-27 22:54:22.998 PDT [30] WARNING:  could not open statistics file "pg_stat_tmp/global.stat": Permission denied
2023-06-27 22:54:23.008 PDT [30] LOG:  using stale statistics instead of current ones because stats collector is not responding
2023-06-27 22:54:23.008 PDT [30] WARNING:  could not open statistics file "pg_stat_tmp/global.stat": Permission denied
2023-06-27 22:54:40.470 PDT [243] FATAL:  could not open file "global/pg_filenode.map": Permission denied
2023-06-27 22:55:10.539 PDT [1] LOG:  received fast shutdown request
2023-06-27 22:55:10.539 PDT [1] LOG:  could not open file "postmaster.pid": Permission denied
2023-06-27 22:55:10.540 PDT [1] LOG:  aborting any active transactions
2023-06-27 22:55:10.541 PDT [1] LOG:  background worker "logical replication launcher" (PID 32) exited with exit code 1
2023-06-27 22:55:10.541 PDT [27] LOG:  shutting down
2023-06-27 22:55:10.542 PDT [27] PANIC:  could not open file "/var/lib/postgresql/data/global/pg_control": Permission denied
2023-06-27 22:55:10.542 PDT [1] LOG:  checkpointer process (PID 27) was terminated by signal 6: Aborted
2023-06-27 22:55:10.542 PDT [1] LOG:  terminating any other active server processes
2023-06-27 22:55:10.542 PDT [31] LOG:  could not open temporary statistics file "pg_stat/global.tmp": Permission denied

 

Any ideas why just my databases seem to be jacked and how to fix them?

 

UPDATE - yes, the PostgreSQL db seems to be working okay for Immich.  This just seems to be a problem with my MariaDB containers.

Edited June 28, 2023 by BurntOC

[BurntOC]

I've tried downgrading the MariaDB release to several of the prior versions.  It shows successful on install, but they all fail with this same error.

[metalchad]

Were you able to find a resolution to your issue with your MariaDB containers? I'm experiencing the same issue on 6.11.5 but was not previously upgraded to 6.12.1

 

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 ...
230707 14:09:14 mysqld_safe Logging to '/config/databases/608d93154c87.err'.
230707 14:09:14 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Caught SIGTERM signal!
cat: /var/run/mysqld/mysqld.pid: No such file or directory

 

EDIT:

Looking into the referenced log I found

[ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.5.12. You must start up and shut down MariaDB 10.7 or earlier.

So, I changed the tag in the repository field to  :10.5.12

Chances are you have a similar log entry

Edited July 7, 2023 by metalchad
new information

[BurntOC]

On 7/7/2023 at 12:11 PM, metalchad said:

Were you able to find a resolution to your issue with your MariaDB containers? I'm experiencing the same issue on 6.11.5 but was not previously upgraded to 6.12.1

 

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 ...
230707 14:09:14 mysqld_safe Logging to '/config/databases/608d93154c87.err'.
230707 14:09:14 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Caught SIGTERM signal!
cat: /var/run/mysqld/mysqld.pid: No such file or directory

 

EDIT:

Looking into the referenced log I found

[ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.5.12. You must start up and shut down MariaDB 10.7 or earlier.

So, I changed the tag in the repository field to  :10.5.12

Chances are you have a similar log entry

 

Sorry for the delay - I'm not getting notifications on this.  Been a crazy month so my memory is shot, honestly, but IIRC I just restored via my appdata backups.