April 5, 20215 yr MariaDB seems to be crashing or something because cheesemarathon's Ghost container is crapping the bed saying that the connection is refused for some reason. Any reason why the database is restarting itself randomly or crashing and then recovering? I've literally only got the one table on it for Ghost. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-envfile: executing... [cont-init.d] 01-envfile: exited 0. [cont-init.d] 10-adduser: executing... ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io ------------------------------------- To support LSIO projects visit: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-config: executing... [cont-init.d] 30-config: exited 0. [cont-init.d] 40-initialise-db: executing... [cont-init.d] 40-initialise-db: exited 0. [cont-init.d] 90-warning: executing... ****************************************************** ****************************************************** * * * * * This image will soon be rebased * * from ubuntu to alpine. * * Please be aware, this may cause issues * * It is strongly recommended to make backups * * of your config and databases before * * updating your image to the alpine base. * * * * * ****************************************************** ****************************************************** [cont-init.d] 90-warning: exited 0. [cont-init.d] 99-custom-scripts: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-scripts: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. 210404 01:01:05 mysqld_safe Logging to syslog. 210404 01:01:05 mysqld_safe Starting mysqld daemon with databases from /config/databases Caught SIGTERM signal! [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-envfile: executing... [cont-init.d] 01-envfile: exited 0. [cont-init.d] 10-adduser: executing... usermod: no changes ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io ------------------------------------- To support LSIO projects visit: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-config: executing... [cont-init.d] 30-config: exited 0. [cont-init.d] 40-initialise-db: executing... [cont-init.d] 40-initialise-db: exited 0. [cont-init.d] 90-warning: executing... ****************************************************** ****************************************************** * * * * * This image will soon be rebased * * from ubuntu to alpine. * * Please be aware, this may cause issues * * It is strongly recommended to make backups * * of your config and databases before * * updating your image to the alpine base. * * * * * ****************************************************** ****************************************************** [cont-init.d] 90-warning: exited 0. [cont-init.d] 99-custom-scripts: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-scripts: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. 210405 03:04:51 mysqld_safe Logging to syslog. 210405 03:04:51 mysqld_safe Starting mysqld daemon with databases from /config/databases The log isn't verbose enough for me to understand why the container keeps rebooting.
April 19, 20215 yr Anyone? This container is literally crashing daily... [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-envfile: executing... [cont-init.d] 01-envfile: exited 0. [cont-init.d] 10-adduser: executing... ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io ------------------------------------- To support LSIO projects visit: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-config: executing... [cont-init.d] 30-config: exited 0. [cont-init.d] 40-initialise-db: executing... [cont-init.d] 40-initialise-db: exited 0. [cont-init.d] 90-warning: executing... ****************************************************** ****************************************************** * * * * * This image will soon be rebased * * from ubuntu to alpine. * * Please be aware, this may cause issues * * It is strongly recommended to make backups * * of your config and databases before * * updating your image to the alpine base. * * * * * ****************************************************** ****************************************************** [cont-init.d] 90-warning: exited 0. [cont-init.d] 99-custom-scripts: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-scripts: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. 210418 01:01:47 mysqld_safe Logging to syslog. 210418 01:01:47 mysqld_safe Starting mysqld daemon with databases from /config/databases Caught SIGTERM signal! [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-envfile: executing... [cont-init.d] 01-envfile: exited 0. [cont-init.d] 10-adduser: executing... usermod: no changes ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io ------------------------------------- To support LSIO projects visit: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-config: executing... [cont-init.d] 30-config: exited 0. [cont-init.d] 40-initialise-db: executing... [cont-init.d] 40-initialise-db: exited 0. [cont-init.d] 90-warning: executing... ****************************************************** ****************************************************** * * * * * This image will soon be rebased * * from ubuntu to alpine. * * Please be aware, this may cause issues * * It is strongly recommended to make backups * * of your config and databases before * * updating your image to the alpine base. * * * * * ****************************************************** ****************************************************** [cont-init.d] 90-warning: exited 0. [cont-init.d] 99-custom-scripts: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-scripts: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. 210419 03:05:31 mysqld_safe Logging to syslog. 210419 03:05:31 mysqld_safe Starting mysqld daemon with databases from /config/databases Edited April 19, 20215 yr by plantsandbinary
April 19, 20215 yr I just realised these guys haven't been here since Feb 23rd. So I think I am going to give all their containers a miss for now... https://forums.unraid.net/profile/66820-linuxserverio/
April 20, 20215 yr 15 hours ago, plantsandbinary said: I just realised these guys haven't been here since Feb 23rd. So I think I am going to give all their containers a miss for now... https://forums.unraid.net/profile/66820-linuxserverio/ When have you seen us post anything support related with that account? It's only used to start the support thread, which we now stopped doing and will not do anymore as we want support to happen on our platforms. There are nobody else reporting any chrashes using our container, so it's a local issue. The container is receiving a signal to stop, so you will have to figure out what does that.
April 30, 20215 yr On 4/20/2021 at 1:21 AM, saarg said: When have you seen us post anything support related with that account? It's only used to start the support thread, which we now stopped doing and will not do anymore as we want support to happen on our platforms. There are nobody else reporting any chrashes using our container, so it's a local issue. The container is receiving a signal to stop, so you will have to figure out what does that. Hey Saarg! So uh.. I may be encountering a similar error as well I'm using Mariadb for my nextcloud only and am trying to figure it out as I'm not 100% familiar with this topic. Thank you for releasing this Docker Container though! I suspected my issue with nextcloud was related to a password expiring or something but I haven't figured out how to reset or access the database as I'm getting "ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)" when I entered my password using "mysql -uroot -p". EDIT: Would you happen to have any advise on how I can fix/get pass this error? cat: /var/run/mysqld/mysqld.pid: No such file or directory [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-envfile: executing... [cont-init.d] 01-envfile: exited 0. [cont-init.d] 10-adduser: executing... usermod: no changes ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io ------------------------------------- To support LSIO projects visit: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-config: executing... [cont-init.d] 30-config: exited 0. [cont-init.d] 40-initialise-db: executing... [cont-init.d] 40-initialise-db: exited 0. [cont-init.d] 90-warning: executing... ****************************************************** ****************************************************** * * * * * This image will soon be rebased * * from ubuntu to alpine. * * Please be aware, this may cause issues * * It is strongly recommended to make backups * * of your config and databases before * * updating your image to the alpine base. * * * * * ****************************************************** ****************************************************** [cont-init.d] 90-warning: exited 0. [cont-init.d] 99-custom-scripts: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-scripts: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. 210430 15:51:31 mysqld_safe Logging to syslog. 210430 15:51:31 mysqld_safe Starting mysqld daemon with databases from /config/databases 210430 15:51:33 mysqld_safe Logging to syslog. 210430 15:51:33 mysqld_safe Starting mysqld daemon with databases from /config/databases 210430 15:51:35 mysqld_safe Logging to syslog. 210430 15:51:35 mysqld_safe Starting mysqld daemon with databases from /config/databases 210430 15:51:37 mysqld_safe Logging to syslog. Edited April 30, 20215 yr by coresplinter Added an extra sentence
April 30, 20215 yr 38 minutes ago, coresplinter said: Hey Saarg! So uh.. I may be encountering a similar error as well I'm using Mariadb for my nextcloud only and am trying to figure it out as I'm not 100% familiar with this topic. Thank you for releasing this Docker Container though! I suspected my issue with nextcloud was related to a password expiring or something but I haven't figured out how to reset or access the database as I'm getting "ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)" when I entered my password using "mysql -uroot -p". EDIT: Would you happen to have any advise on how I can fix/get pass this error? cat: /var/run/mysqld/mysqld.pid: No such file or directory [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-envfile: executing... [cont-init.d] 01-envfile: exited 0. [cont-init.d] 10-adduser: executing... usermod: no changes ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io ------------------------------------- To support LSIO projects visit: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-config: executing... [cont-init.d] 30-config: exited 0. [cont-init.d] 40-initialise-db: executing... [cont-init.d] 40-initialise-db: exited 0. [cont-init.d] 90-warning: executing... ****************************************************** ****************************************************** * * * * * This image will soon be rebased * * from ubuntu to alpine. * * Please be aware, this may cause issues * * It is strongly recommended to make backups * * of your config and databases before * * updating your image to the alpine base. * * * * * ****************************************************** ****************************************************** [cont-init.d] 90-warning: exited 0. [cont-init.d] 99-custom-scripts: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-scripts: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. 210430 15:51:31 mysqld_safe Logging to syslog. 210430 15:51:31 mysqld_safe Starting mysqld daemon with databases from /config/databases 210430 15:51:33 mysqld_safe Logging to syslog. 210430 15:51:33 mysqld_safe Starting mysqld daemon with databases from /config/databases 210430 15:51:35 mysqld_safe Logging to syslog. 210430 15:51:35 mysqld_safe Starting mysqld daemon with databases from /config/databases 210430 15:51:37 mysqld_safe Logging to syslog. Sorry, I don't know how to fix that problem. You are inside the mariadb container when executing the command?
April 30, 20215 yr 39 minutes ago, saarg said: Sorry, I don't know how to fix that problem. You are inside the mariadb container when executing the command? Yep! I'm running it in the mariadb container via the unraid GUI which is why I am confused. (I believe I followed the Spaceinvader video) (Clicking on the MariaDB docker icon and clicking console). My Nextcloud instance was working fine the past month so I'm 99% certain the command should have been accessible back then. But all of a sudden I'm getting an error now. Do you happen to know if I would lose everything in my NextCloud if I uninstall and reinstall the container? (I'm leaning towards it would screw everything up because it would be basically deleting the NextCloud file database..)
May 1, 20215 yr 15 hours ago, coresplinter said: Yep! I'm running it in the mariadb container via the unraid GUI which is why I am confused. (I believe I followed the Spaceinvader video) (Clicking on the MariaDB docker icon and clicking console). My Nextcloud instance was working fine the past month so I'm 99% certain the command should have been accessible back then. But all of a sudden I'm getting an error now. Do you happen to know if I would lose everything in my NextCloud if I uninstall and reinstall the container? (I'm leaning towards it would screw everything up because it would be basically deleting the NextCloud file database..) You haven't said what the problem is, just that it's similar and you get the error message when you try to connect. You can't access nextxloud? If you remove and install the container you will still have the database as the appdata folder is not deleted when removing a container. If you want to set up a new database using the same settings you did for the current one, just stop mariadb and delete the appdata folder for mariadb and start the container again. That will get you a clean database. If you do this, you will have to set up nextxloud again also as the settings and users are stored in the database. The files are still in /data, so you will still have them, but you need to add the users again and then scan for new files manually.
May 1, 20215 yr 8 hours ago, saarg said: You haven't said what the problem is, just that it's similar and you get the error message when you try to connect. You can't access nextxloud? If you remove and install the container you will still have the database as the appdata folder is not deleted when removing a container. If you want to set up a new database using the same settings you did for the current one, just stop mariadb and delete the appdata folder for mariadb and start the container again. That will get you a clean database. If you do this, you will have to set up nextxloud again also as the settings and users are stored in the database. The files are still in /data, so you will still have them, but you need to add the users again and then scan for new files manually. Hi Saarg, sorry for the delay! Yeah, I'm unable to access NextCloud and the Web UI of that just says Internal Server Error. I am trying your suggestion and it seems I'm unable to remake/add users with the same username. As I'm unfamiliar with how to get around that, I've just opted to wipe both containers & the share then re-install and resync everything again! Since I'm doing a (nearly) fresh install, everything should work properly! Thank you for looking into this for me.
May 22, 20215 yr I'm also having no luck with this docker right from the start. I created the docker and added a password: mypassword Open the console, type: mysql -u root -p Enter the password and I get: ERROR 1045 (28000): Access denied for user ‘root’@’localhost’ (using password: YES) Same result on another unraid machine.
May 22, 20215 yr 5 hours ago, RichardU said: I'm also having no luck with this docker right from the start. I created the docker and added a password: mypassword Open the console, type: mysql -u root -p Enter the password and I get: ERROR 1045 (28000): Access denied for user ‘root’@’localhost’ (using password: YES) Same result on another unraid machine. Docker run command and container log is needed for others to help.
May 25, 20215 yr On 5/22/2021 at 3:57 PM, RichardU said: I'm also having no luck with this docker right from the start. I created the docker and added a password: mypassword Open the console, type: mysql -u root -p Enter the password and I get: ERROR 1045 (28000): Access denied for user ‘root’@’localhost’ (using password: YES) Same result on another unraid machine. Hello Richard, I just had the same problem.. I dont know where it came from but my hypothethis is that the first password i picked during first install was not filling requirement somehow and made mariadb bug. Unfortunatly no way to change it cleanly , I had to remove the container , remove the directory and files for my maria db in my appdata share then clean reinstall using fresh from the start "password" as password. [RESOLVED] Afterward i still get error when i try the modification of the password through mysql console that i dont have permission of updating my password. Really weird. Ok i found how just a synthax error ( i was using 'root'@localhost') : command to change root password: MariaDB [(none)]> ALTER USER 'root' IDENTIFIED BY 'new_password'; Edited May 25, 20215 yr by Nikogar
May 31, 20215 yr On 3/1/2021 at 9:20 PM, allanp81 said: I've done it, it's fairly straight forward to migrate the DB from mysql to mariadb, you can use mysqldump to backup from mysql and then import into mariadb. It's slightly more complicated to edit the nextcloud config though if you're using different DB credentials. In theory if the credentials are the same then nextcloud will just work when you restart the docker. Care to share steps with us? In my case it is my main nextcloud database. Mysql support is going away, so I want to get it right. Or I will guess. 1/ Backup mysql database 2/ Load mariadb docker and point to nextcloud store 3/ Import mysql database into mariadb. Couldn't be that simple could it? Are there any other steps needed. If it fell apart, could I simply turn the mysql docker back on and back to square 1? Help appreciated...
June 7, 20215 yr How does one change the root or user password? I have a lot of problems with setting and changing the password. I don't know if it is because I have used special charaters? Seems like it should be allowed: https://kb.iu.edu/d/aphg I have tried using: 1. mysqladmin -u root -p password newpass 2. mysql_secure_installation I can login using mysql -uroot -p # mysql -uroot -p Enter password: Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 38 Server version: 10.4.19-MariaDB-1:10.4.19+maria~bionic-log mariadb.org binary distribution Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [(none)]> EDIT: I now changed the password with mysqladmin -u root -p password newpass and used a password with special characters, however I copied the password I used to login and it will not recognize it. Is there a way to recover/reset the password? EDIT nr.2: I figured out how to change it even when you can't login to mariadb root user based on this link: https://gist.github.com/rordi/ab55c92848fd06884172ed22ae88d7df Resetting mariadb root password even when you can't login - first change mariadb Container settings below - select advanced view - add entrypoint below to "Post Arguments:" mysqld_safe --skip-grant-tables --user=mysql - now use server terminal (not container terminal) - get into the container $> docker exec -it mariadb bash - login to root with no password $> mysql -u root -p - check the hostname for root Mysql> SELECT user,host FROM mysql.user; - now change root password and insert hostname for root 1. mysql> FLUSH PRIVILEGES; 2. mysql> ALTER USER 'root'@'INSERT_HOST' IDENTIFIED BY 'your_secret'; 2. mysql> ALTER USER 'root'@'%' IDENTIFIED BY 'your_secret'; <- my setup 3. mysql> FLUSH PRIVILEGES; - logout and remove the entrypoint and restart the container Edited June 7, 20215 yr by JustAnotherGuy1324
June 8, 20215 yr I've noticed in this version of MariaDB it seems the following are set to Swedish: collation_databaselatin1_swedish_ci collation_serverlatin1_swedish_ci Is it possible to either switch this to something unicode or manually change the defaults ourselves, as this is causing some issues with some of my other containers trying to use databases. I presume those devs can also hard-code their collation choice, but it'd be nice to change it at this level, too..
June 11, 20215 yr On 6/8/2021 at 8:48 PM, polishprocessors said: I've noticed in this version of MariaDB it seems the following are set to Swedish: collation_databaselatin1_swedish_ci collation_serverlatin1_swedish_ci Is it possible to either switch this to something unicode or manually change the defaults ourselves, as this is causing some issues with some of my other containers trying to use databases. I presume those devs can also hard-code their collation choice, but it'd be nice to change it at this level, too.. That's not something we set, so if you haven't set it yourself, then it's in the upstream package it gets set. In which config file is it set?
June 14, 20215 yr Hey Guys, one of my databases got lost within the last couple of days. Unfortunately I don't know why and how, but this is not the biggest issue, I just deleted the old mariadb folder in appdate (while the container was stoped), copied an old backup into it and then started the container again. But somehow I get the error mentioned in this post, I can't get it fixed with solution #2, so is there any way to get back the data from my old database? Error: ...... 210614 11:10:30 mysqld_safe Logging to syslog. 210614 11:10:30 mysqld_safe Starting mysqld daemon with databases from /config/databases 210614 11:10:31 mysqld_safe Logging to syslog. 210614 11:10:31 mysqld_safe Starting mysqld daemon with databases from /config/databases 210614 11:10:32 mysqld_safe Logging to syslog. 210614 11:10:32 mysqld_safe Starting mysqld daemon with databases from /config/databases ..... Thank you in advance, Autchi
June 14, 20215 yr On 6/3/2021 at 3:02 AM, allanp81 said: I think I just followed the guide here: https://mariadb.com/kb/en/mysqldump/ Thanks. I'll have a look.
July 2, 20215 yr A few months back I ran into an issue with Ghost and Maria due to a Ghost update. I was advised on the ghost forum to do this... https://ghost.org/docs/faq/misconfigured-mysql-database/ Does anyone know what the actual commands are to turn off ANSI_QUOTES?
August 8, 20214 yr For some reason I can't run the mysql_secure_installation command in the linuxserver/mariadb container. It works fine in the official mariadb container and is in the mariadb documentation recommended for a "productive" system. But mine ist only throwing the following error when I enter my password that I chose at container creation: Enter current password for root (enter for none): ERROR 1133 (28000) at line 1: Can't find any matching row in the user table My mariadb will only be for a private nextcloud, so it's not directly a productive system. But nextcloud will be accessible from the internet (behind reverse proxy) so I am concerned about security. So is it intended that the mysql_secure_installation can't be executed or is it already been done by linuxserver? Or should I pick the official mariadb container for my usecase?
August 23, 20214 yr When ever the tag gets update to ALPINE = LATEST, what will happen to the application if we update it then? Will it corrupt the database or would we have to do something before we update to make sure it does not corrupt the databases or mess up anything when updating? Also, why are you guys going to Alpine? What's the benefits?
August 25, 20214 yr So,... i updated the container a few minutes ago... and now i got this: Some ideas, how i can solve this? *edit* my workaround in Post #1028110 Edited August 25, 20214 yr by sonic6
August 25, 20214 yr 21 minutes ago, sonic6 said: So,... i updated the container a few minutes ago... and now i got this: Some ideas, how i can solve this? Yeah. mine too. I was wondering why one of the services just died and i checked the db connection... Not sure why it worked but i changed the repo from linuxserver/mariadb to linuxserver/mariadb:alpine-version-10.5.12-r0 (an older version) and then changed it to linuxserver/mariadb:latest and works. Not ideal i know but works. Logs for the error points to a fail in innodb 210825 18:56:18 mysqld_safe Starting mariadbd daemon with databases from /config/databases Warning: World-writable config file '/etc/my.cnf.d/custom.cnf' is ignored 2021-08-25 18:56:18 0 [Note] /usr/bin/mariadbd (mysqld 10.5.12-MariaDB) starting as process 4703 ... 2021-08-25 18:56:18 0 [Note] InnoDB: Uses event mutexes 2021-08-25 18:56:18 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2021-08-25 18:56:18 0 [Note] InnoDB: Number of pools: 1 2021-08-25 18:56:18 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2021-08-25 18:56:18 0 [Note] mariadbd: O_TMPFILE is not supported on /var/tmp (disabling future attempts) 2021-08-25 18:56:18 0 [Note] InnoDB: Using Linux native AIO 2021-08-25 18:56:18 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728 2021-08-25 18:56:18 0 [Note] InnoDB: Completed initialization of buffer pool 2021-08-25 18:56:18 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.4.21. 2021-08-25 18:56:18 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error 2021-08-25 18:56:18 0 [Note] InnoDB: Starting shutdown... 2021-08-25 18:56:18 0 [ERROR] Plugin 'InnoDB' init function returned error. 2021-08-25 18:56:18 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2021-08-25 18:56:18 0 [Note] Plugin 'FEEDBACK' is disabled. 2021-08-25 18:56:18 0 [ERROR] Unknown/unsupported storage engine: InnoDB 2021-08-25 18:56:18 0 [ERROR] Aborting 210825 18:56:18 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended Edited August 25, 20214 yr by exico
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.