Change the mariadb docker repository to "linuxserver/mariadb:110.4.21mariabionic-ls31" (without the " of course) and let it run.
Then edit the docker repository again to "linuxserver/mariadb:latest" and it should run fine again.
Edited August 26, 2021 by whitedwarf
- 1
- 3
- Quote
Link to comment
Pava
Posted August 26, 2021
Pava
- Members
- 18
- Author
- Share
Posted August 26, 2021 (edited)
Hello, thank you for help. I change repository to linuxserver/mariadb:110.4.21mariabionic-ls31, click apply, but now can not find Mariadb in Docker Containers. Its missing.
Please where I can find now Mariadb config file to change and start again? Now I find container in orphan image. How I can rebuild again?
- Quote
Link to comment
Rockikone
Posted August 26, 2021
Rockikone
- Members
- 112
- 1
- Share
Posted August 26, 2021
@whitedwarf
Thanks so much. Your instruction works for me.
I always looked for the error in the nextcloud container
Greetings from Bavaria ๐
- Quote
Link to comment
Scoopsy13
Posted August 26, 2021
Scoopsy13
- Members
- 7
- Share
Posted August 26, 2021
Thanks very much @whitedwarf
This fixed my issue as well.
- Quote
Link to comment
daveo132
Posted August 26, 2021
daveo132
- Members
- 73
- Share
Posted August 26, 2021
Thank you @whitedwarf, I just updated my docker containers I couldn't for the life of me figure out what went wrong.
That trick solved if for me right away.
- Quote
Link to comment
Pava
Posted August 26, 2021
Pava
- Members
- 18
- Author
- Share
Posted August 26, 2021
For me also ok. I was backup appdata/mariadb, reinstall image, roll back appdata/mariedb did like what whiredraft wrote, and now all is ok. Thank you so much for help.
- Quote
Link to comment
tomtom77550
Posted August 26, 2021
tomtom77550
- Members
- 14
- Share
Posted August 26, 2021 (edited)
Hello. Folowing mariaDB update hi experienced the same problem.
MariaDB was updated while nextcloud was running. i don't know if this is wyse to do it like this, but i wanted to test and see what happenend.
and of course it crashed with the same problem.
following instructions posted by @whitedwarfi have done the following steps
- shut down docker nextcloud
- shut down docker mariaDB
- edited mariaDB docker and Changed the mariadb docker repository to "linuxserver/mariadb:110.4.21mariabionic-ls31"
- started the mariaDB docker waited 5mins for cpu utilization to idle on the docker
- shut down the mariadb docker
- edited mariaDB docker and Changed the mariadb docker repository to "linuxserver/mariadb:latest"
- started the mariaDB docker waited 5mins for cpu utilization to idle on the docker
- started nextcloud docker.
Webui for nextcloud up and running again.
many thanks to @whitedwarffor the solution. ๐
Edited August 26, 2021 by tomtom77550
- 1
- Quote
Link to comment
ab5g
Posted August 27, 2021
ab5g
- Members
- 78
- Share
Posted August 27, 2021
9 hours ago, tomtom77550 said:
Hello. Folowing mariaDB update hi experienced the same problem.
MariaDB was updated while nextcloud was running. i don't know if this is wyse to do it like this, but i wanted to test and see what happenend.
and of course it crashed with the same problem.
following instructions posted by @whitedwarfi have done the following steps
- shut down docker nextcloud
- shut down docker mariaDB
- edited mariaDB docker and Changed the mariadb docker repository to "linuxserver/mariadb:110.4.21mariabionic-ls31"
- started the mariaDB docker waited 5mins for cpu utilization to idle on the docker
- shut down the mariadb docker
- edited mariaDB docker and Changed the mariadb docker repository to "linuxserver/mariadb:latest"
- started the mariaDB docker waited 5mins for cpu utilization to idle on the docker
- started nextcloud docker.
Webui for nextcloud up and running again.
many thanks to @whitedwarffor the solution. ๐
An alternate way is here
//forums.unraid.net/topic/48383-support-linuxserverio-nextcloud/?do=findComment&comment=1028554
- 1
- Quote
Link to comment
daveo132
Posted August 28, 2021
daveo132
- Members
- 73
- Share
Posted August 28, 2021 (edited)
Well it did work,
Since today I'm now getting "unexpectedly closed the connection" errors
EDIt,
trying the fix again to see if it helps.
I did notice that my Maria DB is constantly logging like this
Spoiler
ErrorWarningSystemArrayLogin
[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:
//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-custom-folders: executing...
[cont-init.d] 90-custom-folders: 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.
210828 11:10:07 mysqld_safe Logging to syslog.
210828 11:10:07 mysqld_safe Starting mysqld daemon with databases from /config/databases
210828 11:10:08 mysqld_safe Logging to syslog.
210828 11:10:08 mysqld_safe Starting mysqld daemon with databases from /config/databases
210828 11:10:09 mysqld_safe Logging to syslog.
210828 11:10:09 mysqld_safe Starting mysqld daemon with databases from /config/databases
210828 11:10:10 mysqld_safe Logging to syslog.
210828 11:10:10 mysqld_safe Starting mysqld daemon with databases from /config/databases
Those last lines just go on and on for the rest of the log
Edited August 28, 2021 by daveo132- Quote
Link to comment
daveo132
Posted August 28, 2021
daveo132
- Members
- 73
- Share
Posted August 28, 2021
Nevermind I think I fixed it now.
My NoIP updated around the same time but something broke with the cached IP address.
Taken me a little while to figure it out but I can log back into my next cloud again now.
- Quote
Link to comment
Batman11
Posted August 28, 2021
Batman11
- Members
- 3
- Share
Posted August 28, 2021
On 8/26/2021 at 1:50 PM, tomtom77550 said:
Hello. Folowing mariaDB update hi experienced the same problem.
MariaDB was updated while nextcloud was running. i don't know if this is wyse to do it like this, but i wanted to test and see what happenend.
and of course it crashed with the same problem.
following instructions posted by @whitedwarfi have done the following steps
- shut down docker nextcloud
- shut down docker mariaDB
- edited mariaDB docker and Changed the mariadb docker repository to "linuxserver/mariadb:110.4.21mariabionic-ls31"
- started the mariaDB docker waited 5mins for cpu utilization to idle on the docker
- shut down the mariadb docker
- edited mariaDB docker and Changed the mariadb docker repository to "linuxserver/mariadb:latest"
- started the mariaDB docker waited 5mins for cpu utilization to idle on the docker
- started nextcloud docker.
Webui for nextcloud up and running again.
many thanks to @whitedwarffor the solution. ๐
This too worked for me. Thank you
- Quote
Link to comment
Dchod
Posted August 30, 2021
Dchod
- Members
- 3
- Share
Posted August 30, 2021 (edited)
@whitedwarf
Thanks so much for the instructions. Solution worked like a charm!
Edited August 30, 2021 by Dchod- Quote
Link to comment
bsimonian
Posted August 30, 2021
bsimonian
- Members
- 14
- Share
Posted August 30, 2021
On 8/26/2021 at 4:18 AM, whitedwarf said:
I have found this fix in another thread:
Change the mariadb docker repository to "linuxserver/mariadb:110.4.21mariabionic-ls31" (without the " of course) and let it run.
Then edit the docker repository again to "linuxserver/mariadb:latest" and it should run fine again.
Awesome, thanks for the share; seems to have fixed it!
- Quote
Link to comment
Martintheshred
Posted August 31, 2021
Martintheshred
- Members
- 41
- Share
Posted August 31, 2021
On 8/26/2021 at 8:50 PM, tomtom77550 said:
Hello. Folowing mariaDB update hi experienced the same problem.
MariaDB was updated while nextcloud was running. i don't know if this is wyse to do it like this, but i wanted to test and see what happenend.
and of course it crashed with the same problem.
following instructions posted by @whitedwarfi have done the following steps
- shut down docker nextcloud
- shut down docker mariaDB
- edited mariaDB docker and Changed the mariadb docker repository to "linuxserver/mariadb:110.4.21mariabionic-ls31"
- started the mariaDB docker waited 5mins for cpu utilization to idle on the docker
- shut down the mariadb docker
- edited mariaDB docker and Changed the mariadb docker repository to "linuxserver/mariadb:latest"
- started the mariaDB docker waited 5mins for cpu utilization to idle on the docker
- started nextcloud docker.
Webui for nextcloud up and running again.
many thanks to @whitedwarffor the solution. ๐
Thanks @Tomtom77550 & @whitedwarf for your info this was foxing me good style
- Quote
Link to comment
1q8448q1
Posted August 31, 2021
1q8448q1
- Members
- 31
- Share
Posted August 31, 2021
On 8/26/2021 at 1:18 PM, whitedwarf said:
I have found this fix in another thread:
Change the mariadb docker repository to "linuxserver/mariadb:110.4.21mariabionic-ls31" (without the " of course) and let it run.
Then edit the docker repository again to "linuxserver/mariadb:latest" and it should run fine again.
Thank you very much! This saved my evening quick! Thank you!!!
- Quote
Link to comment
luizmont
Posted September 1, 2021
luizmont
- Members
- 24
- Share
Posted September 1, 2021
It solved the problem for me as wel!!
Thank you very much!
- Quote
Link to comment
Mogool
Posted September 3, 2021
Mogool
- Members
- 1
- Share
Posted September 3, 2021 (edited)
On 8/26/2021 at 1:18 PM, whitedwarf said:
I have found this fix in another thread:
Change the mariadb docker repository to "linuxserver/mariadb:110.4.21mariabionic-ls31" (without the " of course) and let it run.
Then edit the docker repository again to "linuxserver/mariadb:latest" and it should run fine again.
You're my Hero
Thanks a lot!
Edited September 3, 2021 by Mogool- Quote
Link to comment
starwak3
Posted September 10, 2021
starwak3
- Members
- 19
- Share
Posted September 10, 2021
Got this error last week - the posted solution worked.
Got this error this evening, the posted solution does not work now. Any ideas?
Log for: mariadb
[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-custom-folders: executing... [cont-init.d] 90-custom-folders: exited 0. [cont-init.d] 99-custom-files: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-files: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Warning: World-writable config file '/etc/my.cnf.d/custom.cnf' is ignored Warning: World-writable config file '/etc/my.cnf.d/custom.cnf' is ignored 210909 22:01:41 mysqld_safe Logging to '/config/databases/aae9e9e9ff69.err'. 210909 22:01:41 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Log for: nextcloud
[cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 40-config: executing... [cont-init.d] 40-config: exited 0. [cont-init.d] 50-install: executing... [cont-init.d] 50-install: exited 0. [cont-init.d] 60-memcache: executing... [cont-init.d] 60-memcache: exited 0. [cont-init.d] 70-aliases: executing... [cont-init.d] 70-aliases: exited 0. [cont-init.d] 90-custom-folders: executing... [cont-init.d] 90-custom-folders: exited 0. [cont-init.d] 99-custom-files: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-files: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done.
- Quote
Link to comment
Simplex
Posted September 14, 2021
Simplex
- Members
- 4
- Share
Posted September 14, 2021
On 8/26/2021 at 2:18 PM, whitedwarf said:
I have found this fix in another thread:
Change the mariadb docker repository to "linuxserver/mariadb:110.4.21mariabionic-ls31" (without the " of course) and let it run.
Then edit the docker repository again to "linuxserver/mariadb:latest" and it should run fine again.
Working fine, thanks a lot.
- Quote
Link to comment
Spyderturbo007
Posted September 25, 2021
Spyderturbo007
- Members
- 266
- Share
Posted September 25, 2021
On 8/26/2021 at 7:18 AM, whitedwarf said:
I have found this fix in another thread:
Change the mariadb docker repository to "linuxserver/mariadb:110.4.21mariabionic-ls31" (without the " of course) and let it run.
Then edit the docker repository again to "linuxserver/mariadb:latest" and it should run fine again.
Thanks for the help @whitedwarf that worked perfectly.
- Quote
Link to comment
braydination
Posted October 27, 2021
braydination
- Members
- 27
- Share
Posted October 27, 2021
I had the same issue where I stupidly forgot to stop all dockers that had a db in mariadb, so now the docker has vanished altogether. Is there a way that I can restore just the one docker rather than doing the complete restore for all dockers via the CA Backup/Restore app?
- Quote
Link to comment
smithCanary
Posted November 30, 2021
smithCanary
- Members
- 4
- Share
Posted November 30, 2021
On 8/26/2021 at 9:50 PM, tomtom77550 said:
Hello. Folowing mariaDB update hi experienced the same problem.
MariaDB was updated while nextcloud was running. i don't know if this is wyse to do it like this, but i wanted to test and see what happenend.
and of course it crashed with the same problem.
following instructions posted by @whitedwarfi have done the following steps
- shut down docker nextcloud
- shut down docker mariaDB
- edited mariaDB docker and Changed the mariadb docker repository to "linuxserver/mariadb:110.4.21mariabionic-ls31"
- started the mariaDB docker waited 5mins for cpu utilization to idle on the docker
- shut down the mariadb docker
- edited mariaDB docker and Changed the mariadb docker repository to "linuxserver/mariadb:latest"
- started the mariaDB docker waited 5mins for cpu utilization to idle on the docker
- started nextcloud docker.
Webui for nextcloud up and running again.
many thanks to @whitedwarffor the solution. ๐
Hello everyone.
I have followed the following instructions provided by @tomtom77550 and have not been able to get it to work again....
Accessing the log, I get the following error:
[cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 40-config: executing... [cont-init.d] 40-config: exited 0. [cont-init.d] 50-install: executing... [cont-init.d] 50-install: exited 0. [cont-init.d] 60-memcache: executing... [cont-init.d] 60-memcache: exited 0. [cont-init.d] 70-aliases: executing... [cont-init.d] 70-aliases: exited 0. [cont-init.d] 90-custom-folders: executing... [cont-init.d] 90-custom-folders: exited 0. [cont-init.d] 99-custom-files: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-files: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Doctrine\DBAL\Exception: Failed to connect to the database: An exception occurred in the driver: SQLSTATE[HY000] [2002] Host is unreachable in /config/www/nextcloud/lib/private/DB/Connection.php:87Searching for information about the error I found this post, but I don't quite understand what I should do.
What should I do? Any suggestions?
Thank you very much for your help.
- Quote
Link to comment
Snowman
Posted December 2, 2021
Snowman
- Members
- 62
- Share
Posted December 2, 2021
On 8/26/2021 at 1:50 PM, tomtom77550 said:
Hello. Folowing mariaDB update hi experienced the same problem.
MariaDB was updated while nextcloud was running. i don't know if this is wyse to do it like this, but i wanted to test and see what happenend.
and of course it crashed with the same problem.
following instructions posted by @whitedwarfi have done the following steps
- shut down docker nextcloud
- shut down docker mariaDB
- edited mariaDB docker and Changed the mariadb docker repository to "linuxserver/mariadb:110.4.21mariabionic-ls31"
- started the mariaDB docker waited 5mins for cpu utilization to idle on the docker
- shut down the mariadb docker
- edited mariaDB docker and Changed the mariadb docker repository to "linuxserver/mariadb:latest"
- started the mariaDB docker waited 5mins for cpu utilization to idle on the docker
- started nextcloud docker.
Webui for nextcloud up and running again.
many thanks to @whitedwarffor the solution. ๐
I tried this as well as deleting the the log files mentioned in the alternate way and neither work. It just sits there saying this over and over when switching it to theย linuxserver/mariadb:110.4.21mariabionic-ls31. I let it even run over night and still same result. Is there something I'm missing as stuck with this and nextcloud won't work, still have internal server error?