sonic6 Posted August 25, 2021 Share Posted August 25, 2021 @exico here is my workaround, try using this Repository: linuxserver/mariadb:110.4.21mariabionic-ls31 1 5 Quote Link to comment
ich777 Posted August 25, 2021 Share Posted August 25, 2021 How do I migrate to the alpine image: ****************************************************** ****************************************************** * * * * * 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. * * * * * ****************************************************** ****************************************************** 1 Quote Link to comment
goosetrousers Posted August 26, 2021 Share Posted August 26, 2021 7 hours ago, sonic6 said: Repository: linuxserver/mariadb:110.4.21mariabionic-ls31 I did this, everything worked again. Then I updated to linuxserver/mariadb:latest and everything continued to work, but with an Alpine base. Saved me from migrating, I guess I'll sit on my backups and see how this plays out. 8 Quote Link to comment
Simmer Posted August 26, 2021 Share Posted August 26, 2021 2 hours ago, goosetrousers said: I did this, everything worked again. Then I updated to linuxserver/mariadb:latest and everything continued to work, but with an Alpine base. Saved me from migrating, I guess I'll sit on my backups and see how this plays out. This worked for me as well. Quote Link to comment
jademonkee Posted August 26, 2021 Share Posted August 26, 2021 I updated this morning and have this in the logs: Quote 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] 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. 210826 10:05:52 mysqld_safe Logging to '/config/databases/98571c4a56a9.err'. 210826 10:05:52 mysqld_safe Starting mariadbd daemon with databases from /config/databases It's not adding any extra lines (like, they're not repeating), and Swag + NextCloud are working fine (the only things that use it - and I don't even remeber if they both do, or just NC... heh)). Is that safe mode anything to worry about? Or is it all good? Quote Link to comment
jimmy898 Posted August 26, 2021 Share Posted August 26, 2021 8 hours ago, goosetrousers said: I did this, everything worked again. Then I updated to linuxserver/mariadb:latest and everything continued to work, but with an Alpine base. Saved me from migrating, I guess I'll sit on my backups and see how this plays out. This worked for me too. 7 minutes ago, jademonkee said: I updated this morning and have this in the logs: It's not adding any extra lines (like, they're not repeating), and Swag + NextCloud are working fine (the only things that use it - and I don't even remeber if they both do, or just NC... heh)). Is that safe mode anything to worry about? Or is it all good? After the "fix" I have the same logs: [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. 210826 10:27:08 mysqld_safe Logging to '/config/databases/1e9a6a6ee3d8.err'. 210826 10:27:08 mysqld_safe Starting mariadbd daemon with databases from /config/databases Quote Link to comment
j0nnymoe Posted August 26, 2021 Share Posted August 26, 2021 18 hours ago, sonic6 said: @exico here is my workaround, try using this Repository: linuxserver/mariadb:110.4.21mariabionic-ls31 Be aware that this will no longer get updates. Quote Link to comment
j0nnymoe Posted August 26, 2021 Share Posted August 26, 2021 17 hours ago, ich777 said: How do I migrate to the alpine image: ****************************************************** ****************************************************** * * * * * 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. * * * * * ****************************************************** ****************************************************** Upgrading to `:latest` will put you on alpine. Quote Link to comment
j0nnymoe Posted August 26, 2021 Share Posted August 26, 2021 On 8/23/2021 at 5:55 PM, Tucubanito07 said: 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? Less so benefits for unraid users (x86_64) but better for our armhf / aarch64 users as mariadb don't release up to date versions for those platforms on ubuntu base. 1 Quote Link to comment
ich777 Posted August 26, 2021 Share Posted August 26, 2021 45 minutes ago, j0nnymoe said: Upgrading to `:latest` will put you on alpine. Only asking because I got the same issue while upgrading to latest as @sonic6. A downgrade to: 'linuxserver/mariadb:110.4.21mariabionic-ls31' and upgrade after the downgrade solved the issue, everything is now up and running on alpine. Quote Link to comment
fithwum Posted August 26, 2021 Share Posted August 26, 2021 still getting the error after update and fix but at least it works again Quote Link to comment
Tucubanito07 Posted August 26, 2021 Share Posted August 26, 2021 7 hours ago, j0nnymoe said: Less so benefits for unraid users (x86_64) but better for our armhf / aarch64 users as mariadb don't release up to date versions for those platforms on ubuntu base. When we update the container to the latest? Will it break anything on the database? If you know. Any recommendations on updating it so it does not mess up any of the databases we have already working. Quote Link to comment
Froberg Posted August 26, 2021 Share Posted August 26, 2021 "Fix" worked for me, at least I can access the db through phpmyadmin again. Nextcloud is still b0rked though. Have to get some rest, but specifically the fix that worked in my case: And then switching to :latest. Quote Link to comment
nekromantik Posted August 26, 2021 Share Posted August 26, 2021 not really a fix if nextcloud breaks Quote Link to comment
dougiefresh Posted August 26, 2021 Share Posted August 26, 2021 22 hours ago, goosetrousers said: I did this, everything worked again. Then I updated to linuxserver/mariadb:latest and everything continued to work, but with an Alpine base. Saved me from migrating, I guess I'll sit on my backups and see how this plays out. Worked for me. Quote Link to comment
Roxedus Posted August 27, 2021 Share Posted August 27, 2021 This "fix", is needed because the container gets forcefully shut down, before mariadb has successfully shutdown, this is usually isn't a problem, as mariadb is nice, and usually manages to recover from a dirty shutdown. The docker update plugin uses 10s as the default time before killing a container, which does not suffice. 2 Quote Link to comment
Froberg Posted August 27, 2021 Share Posted August 27, 2021 15 hours ago, nekromantik said: not really a fix if nextcloud breaks Agreed.. been unsuccesful thus far in reviving it.. 502 Bad Gateway. The DB is up, as I could upgrade it through console, which I assume required DB connectivity.. so I'm a bit stumped atm. Quote Link to comment
thunderclap Posted August 27, 2021 Share Posted August 27, 2021 16 hours ago, nekromantik said: not really a fix if nextcloud breaks 16 hours ago, Froberg said: "Fix" worked for me, at least I can access the db through phpmyadmin again. Nextcloud is still b0rked though. Have to get some rest, but specifically the fix that worked in my case: And then switching to :latest. 16 hours ago, nekromantik said: not really a fix if nextcloud breaks This fix worked for me. Nextcloud is back up and running without issue. Quote Link to comment
uByte Posted August 27, 2021 Share Posted August 27, 2021 On 8/25/2021 at 1:30 PM, sonic6 said: @exico here is my workaround, try using this Repository: linuxserver/mariadb:110.4.21mariabionic-ls31 I had the same issue and this is what fixed it for me. Thank you @sonic6 1 Quote Link to comment
Bob Junks Posted August 30, 2021 Share Posted August 30, 2021 If you are getting the following error in the logs "Unknown/unsupported storage engine: InnoDB" Then doing this resolved may resolve your issue. It resolved mine. I updated mariadb and then nextcloud. For the future. Before upgrading mariadb, stop the next cloud docker container, then stop mariadb container. Then apply updates. Basically I opened a console on the mariadb docker. ran the following commands > cd /config/databases > rm ib_logfile0 > rm ib_logfile1 (note: You may get "rm : Cannot remove 'ib_logfile1': No such file or directory) on this command Then stop both the containers and restart both the containers This seemed to have resolved my issue. Credit where it's due: https://serverfault.com/questions/379714/unknown-unsupported-storage-engine-innodb-mysql-ubuntu Quote Link to comment
tvd1 Posted August 31, 2021 Share Posted August 31, 2021 On 8/25/2021 at 8:36 PM, goosetrousers said: I did this, everything worked again. Then I updated to linuxserver/mariadb:latest and everything continued to work, but with an Alpine base. Saved me from migrating, I guess I'll sit on my backups and see how this plays out. +1. same exact issue for me and this worked too. Thanks! Quote Link to comment
HaOz Ong Posted August 31, 2021 Share Posted August 31, 2021 On 8/26/2021 at 8:36 AM, goosetrousers said: I did this, everything worked again. Then I updated to linuxserver/mariadb:latest and everything continued to work, but with an Alpine base. Saved me from migrating, I guess I'll sit on my backups and see how this plays out. this worked for me as well. both mariadb service and nextcloud up and running again. thanks !! Quote Link to comment
dellorianes Posted September 1, 2021 Share Posted September 1, 2021 On 8/26/2021 at 2:36 AM, goosetrousers said: I did this, everything worked again. Then I updated to linuxserver/mariadb:latest and everything continued to work, but with an Alpine base. Saved me from migrating, I guess I'll sit on my backups and see how this plays out. It has also worked for me. Thank you very much Quote Link to comment
zoggy Posted September 1, 2021 Share Posted September 1, 2021 (edited) i was on vacation and sadly this mariadb docker auto upgraded (due to CA) and since the change to alpine (and maria 10.5) now my kodi instances randomly become unhappy with the db launching kodi results in it crashing because it cant get data from the db (it connects just errors on things), sample: 2021-09-01 09:58:50.454 T:24263 INFO <general>: Starting Kodi (19.1 (19.1.0) Git:20210508-85e05228b4). Platform: Android ARM 64-bit ... 2021-09-01 09:58:50.504 T:24263 INFO <general>: Contents of special://profile/advancedsettings.xml are... <advancedsettings> <loglevel>0</loglevel> <videodatabase> <type>mysql</type> <host>192.168.0.11</host> <port>3306</port> ... 2021-09-01 09:58:53.110 T:24291 INFO <general>: MYSQL: Connected to version 10.5.12-MariaDB-log 2021-09-01 09:58:53.115 T:24291 INFO <general>: Running database version MyMusic82 2021-09-01 09:58:53.121 T:24291 INFO <general>: Running database version MyVideos119 ... 2021-09-01 09:58:53.555 T:24263 INFO <general>: JSONRPC v12.3.0: Successfully initialized 2021-09-01 09:58:53.574 T:24292 ERROR <general>: SQL: [MyVideos119] An unknown error occurred Query: SELECT * FROM streamdetails WHERE idFile = 16300 2021-09-01 09:58:53.655 T:24292 ERROR <general>: GetStreamDetails(16300) failed ... 2021-09-01 09:58:53.836 T:24291 ERROR <general>: GetArtForItem(1125) failed 2021-09-01 09:58:53.836 T:24291 ERROR <general>: SQL: Missing result set! 2021-09-01 09:58:53.836 T:24291 ERROR <general>: GetArtForItem(181) failed 2021-09-01 09:58:53.841 T:24291 ERROR <general>: SQL: [MyVideos119] Commands were executed in an improper order Query: SELECT * FROM streamdetails WHERE idFile = 733 looking around, i found few different things saying that it may just be mariadb 10.5 itself found this, https://discourse.coreelec.org/t/the-state-of-mariadb-in-the-context-of-coreelec/13025 restarted docker, tried from another box and still no go: 2021-09-01 12:12:49.885 T:24465 INFO <general>: MYSQL: Connected to version 10.5.12-MariaDB-log 2021-09-01 12:12:49.891 T:24465 ERROR <general>: SQL: [MyMusic82] An unknown error occurred Query: SELECT idVersion FROM version 2021-09-01 12:12:50.005 T:24465 ERROR <general>: Process error processing job tried to downgrade mariadb docker to older tag (110.4.21mariabionic-ls31) but then on docker start up it just shows it crashing/starting: 210901 11:49:22 mysqld_safe Logging to syslog. 210901 11:49:22 mysqld_safe Starting mysqld daemon with databases from /config/databases 210901 11:49:23 mysqld_safe Logging to syslog. 210901 11:49:23 mysqld_safe Starting mysqld daemon with databases from /config/databases 210901 11:49:24 mysqld_safe Logging to syslog. 210901 11:49:24 mysqld_safe Starting mysqld daemon with databases from /config/databases 210901 11:49:25 mysqld_safe Logging to syslog. looking at why... # /usr/sbin/mysqld --basedir=/usr --datadir=/config/databases --plugin-dir=/usr/lib/mysql/plugin --pid-file=/var/run/mysqld/mysqld.pid --socket=/var/run/mysqld/mysqld 2021-09-01 12:38:58 0 [Note] /usr/sbin/mysqld (mysqld 10.4.21-MariaDB-1:10.4.21+maria~bionic-log) starting as process 7030 ... 2021-09-01 12:38:58 0 [ERROR] mysqld: Can't lock aria control file '/config/databases/aria_log_control' for exclusive use, error: 11. Will retry for 30 seconds ^C^C^C^C^C 2021-09-01 12:39:29 0 [ERROR] mysqld: Got error 'Could not get an exclusive lock; file is probably in use by another process' when trying to use aria control file '/config/databases/aria_log_control' 2021-09-01 12:39:29 0 [ERROR] Plugin 'Aria' init function returned error. 2021-09-01 12:39:29 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed. 2021-09-01 12:39:29 0 [Note] InnoDB: Using Linux native AIO 2021-09-01 12:39:29 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2021-09-01 12:39:29 0 [Note] InnoDB: Uses event mutexes 2021-09-01 12:39:29 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2021-09-01 12:39:29 0 [Note] InnoDB: Number of pools: 1 2021-09-01 12:39:29 0 [Note] InnoDB: Using SSE2 crc32 instructions 2021-09-01 12:39:29 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts) 2021-09-01 12:39:29 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M 2021-09-01 12:39:29 0 [Note] InnoDB: Completed initialization of buffer pool 2021-09-01 12:39:29 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2021-09-01 12:39:29 0 [ERROR] InnoDB: Unsupported redo log format. The redo log was created with MariaDB 10.5.12. 2021-09-01 12:39:29 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error 2021-09-01 12:39:29 0 [Note] InnoDB: Starting shutdown... 2021-09-01 12:39:30 0 [ERROR] Plugin 'InnoDB' init function returned error. 2021-09-01 12:39:30 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2021-09-01 12:39:30 0 [Note] Plugin 'FEEDBACK' is disabled. 2021-09-01 12:39:30 0 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded 2021-09-01 12:39:30 0 [ERROR] Failed to initialize plugins. 2021-09-01 12:39:30 0 [ERROR] Aborting I got it working on old tag finally. As I had ran "mysql_upgrade -u root -p" when it was on alpine/10.5 to try and get it to fix the problem that the upgrade caused: https://forum.kodi.tv/showthread.php?tid=364255&pid=3057634 So downgraded back to older tag but then in the database folder I had to nuke: aria_log.* / ib_logfile0 / mysql_upgrade_info Now things work like they did before just fine.. Edited September 1, 2021 by zoggy Quote Link to comment
Recommended Posts
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.