Posts by FredK

    I'm back in business after going back to "image: webhippie/mariadb:latest-arm32v6" and a restore of the last but one backup.

    I had to go this way because I didn't succeed with the latest mariadb image from webhippie which is release 10.6. I found several links where an incompatibility between nextcloud and mariadb 10.6 are described, e.g. https://github.com/nextcloud/docker/issues/1492


    I'll stay for a while with mariadb:latest-arm32v6 until the incompatibility will be resolved, instead of to try the workaround mentioned in the line above.


    EDIT:

    linuxserver/mariadb is at 10.5 → No incompatibility

    Googling brings up this: https://til.codes/how-to-fix-e…ed-storage-engine-innodb/


    Be sure to take backups before changing anything

    Last night I found a similar link. But I had no success (I better should have mention this detail).

    The log says now:

    The nextcloud login screen appears now but after the logon I see the "Internal Server Error" again.

    As on a armfh platform (see signature) I had to migrate from linuxserver/mariadb to webhippie/mariadb according to the guide by Morlan. Applying my weekly "docker-compose pull" I got for the first time a (brand-)new version of webhippie/mariadb. But after the "docker-compose up -d" and trying to connect to my nextcloud I get

    Code
    Internal Server Error
    The server encountered an internal error and was unable to complete your request.
    Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.
    More details can be found in the server log.

    It looks as if the mariadb-container does not start.


    Any clue?


    Not without further information. What does the mariadb-container log say?

    ...

    That's the mariadb-log:

    As on a armfh platform (see signature) I had to migrate from linuxserver/mariadb to webhippie/mariadb according to the guide by Morlan. Applying my weekly "docker-compose pull" I got for the first time a (brand-)new version of webhippie/mariadb. But after the "docker-compose up -d" and trying to connect to my nextcloud I get

    Code
    Internal Server Error
    The server encountered an internal error and was unable to complete your request.
    Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.
    More details can be found in the server log.

    It looks as if the mariadb-container does not start.


    Any clue?

    The problem with the incompatibility arises on 32-bit platforms as my Helios 4. I moved to webhippie and I'm waiting for the alpine based mariadb will be out of its pre-release state.

    Soma  Morlan

    As Soma I already enabled 4-Byte support in the past. For the restore of the database I used the "original" script, i.e. not the enhanced command.

    Emojis are still fine in nextcloud->mail: Subject and content with emojis are represented correctly. A text file containing emojis looks correct but not in the sidebar but i'm not sure whether this effect is a consequence of the former restore command.


    Another topic:

    linuxserver/docker-mariadb is migrating away from mariabionic (with 10.1.47) to alpine-10.5.8 (see https://github.com/linuxserver/docker-mariadb/releases).

    Morlan
    I'm stuck at last step (Disable maintenance mode)

    See my comments inline.

    EDIT:

    After repeating the database command using oc_he instead of oc_admin disabling maintenance mode was successful.

    Nextcloud started, login successful!

    Let me come back to my question in #446.

    In nextcloud now 20.0.7 I get the following warning in Settings->Overview:

    Quote

    MariaDB version "10.1.47-MariaDB-0ubuntu0.18.04.1" is used. Nextcloud 21 will no longer support this version and requires MariaDB 10.2 or higher.

    My hardware (see signature) is an arm32 device.

    Even the newest mariadb image https://github.com/linuxserver…/110.4.17mariabionic-ls10 ("Bump to 10.4 ...") doesn't suppress the warning message.

    Why? "Inside" the nextclouddb (=mariadb) container we have 10.1.47:

    Code
    root@7f6f464c863c:~# apt list --installed | grep maria
    WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
    mariadb-client-10.1/now 1:10.1.47-0ubuntu0.18.04.1 armhf [installed,local]
    mariadb-client-core-10.1/now 1:10.1.47-0ubuntu0.18.04.1 armhf [installed,local]
    mariadb-common/now 1:10.1.47-0ubuntu0.18.04.1 all [installed,local]
    mariadb-server/now 1:10.1.47-0ubuntu0.18.04.1 all [installed,local]
    mariadb-server-10.1/now 1:10.1.47-0ubuntu0.18.04.1 armhf [installed,local]
    mariadb-server-core-10.1/now 1:10.1.47-0ubuntu0.18.04.1 armhf [installed,local]

    What can I do?


    Remark: I also started a corresponding thread in armbian forum:

    https://forum.armbian.com/topi…iadb-docker-version-102ff


    EDIT:

    In https://discourse.linuxserver.io I found two posts which bring some light into the topic.


    1. From Nov 2020: https://discourse.linuxserver.…adb-on-raspberry-pi3/2221

    Mariadb dont push newer binaries for armhf


    2. From Mar 2020: https://discourse.linuxserver.…db-on-arm-still-v10-1/944

    arm one pulls from the ubuntu bionic repo: https://packages.ubuntu.com/bionic-updates/mariadb-server

    either that will be updated, or we’ll update the baseimage to ubuntu focal after it is released


    And the problem is: ubuntu focal doesn't support 32bit. So what to do with nextcloud 21?

    This is a complicated issue. Because MariaDB is not officially compiled for arm32 devices the linuxserver image is stuck on 10.1.*. I don't know if that will change. I tried to find an alternative this morning, but I have not found an easy solution .. Maybe someone else has an idea?

    Thank you for your investigation.

    A missing MariaDB docker version 10.2ff could be a show-stopper if nextcloud v21 will be available for my HW/SW-platform.

    After updating nextcloud to 20.0.5 I get the following warning in Settings->Overview

    Quote

    MariaDB version "10.1.47-MariaDB-0ubuntu0.18.04.1" is used. Nextcloud 21 will no longer support this version and requires MariaDB 10.2 or higher.

    Anybody aware of a MariaDB docker version 10.2ff for the system specified in my signature?

    The two tabs "Disk I/O" + "Disk Usage" in Diagnostics->Performance Statistics are empty, i.e. no graphs are present. This behaviour has been discussed in the past for OMV4 here but without a definitive solution. Today I made an observation which might be a starting point for futher investigations.


    I use four SATA-disks providing a RAID5. There are no graphs present in the two tabs. From time to time I plug-in an external (encrypted) USB-disk for specific backup purposes. After unlocking the device the "Disk I/O" tab is populated and after mounting the device the graphs in the "Disk Usage" tab show up also. For completeness: If the USB-disk is not attached the corresponding file system is mentioned as "missing" in Storage->File Systems.