FredK

  • Content Count

    30
  • Joined

  • Last visited

About FredK

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @Yolgie I bought this one: https://www.amazon.de/gp/product/B07Q72NBQK
  2. Let me describe the solution of the problem, possibly for help another users of Helios4+OMV5+Nextcloud. The individual steps are mentioned in the OMV forum in the thread https://forum.openmediavault.org/index.php?thread/28242-nextcloud-with-letsencrypt-using-omv-and-docker-compose-q-a. User "Morlan" proposed to exchange linuxserver/mariadb by webhippie/mariadb, he prepared a how-to in post #533, I make minor amendments in #536. Now I'm "back in business", MariaDB version is 10.4.8.
  3. Hm. Using the attached docker-compose.yml the build version "110.4.17mariabionic-ls9" is updated to the fresh "110.4.17mariabionic-ls10". But "inside" the mariadb container the version stayed at 10.1.47. # docker exec -it nextclouddb /bin/bash 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 [inst
  4. I'll ask again in the OMV forum how to proceed, in particular why the mariadb image is bound to ubuntu bionic.
  5. OMV5 on Helios4 is on top of Armbian Buster (see my signature). OMV5 doesn't support nextcloud + MariaDB + swag(letsencrypt) directly. It supports docker plus portainer and yacht for container management. Docker version is: root@helios4:~# apt list --installed | grep docker WARNING: apt does not have a stable CLI interface. Use with caution in scripts. docker-ce-cli/buster,now 5:20.10.3~3-0~debian-buster armhf [installed,automatic] docker-ce/buster,now 5:20.10.3~3-0~debian-buster armhf [installed] docker-compose/stable,now 1.21.0-3 all [installed] golang-docker-credential-helpers/stable
  6. Let me ask a question in a armbian-forum where I found up til now no solution. After updating nextcloud to 20.0.5 (now I use 20.0.7) I get the following warning in OMV5 Settings->Overview: Asking thas question in the OMV-forum I received the following answer from the user "Morlan": A missing MariaDB docker version 10.2ff could be a show-stopper if nextcloud v21 will be available for Helios4.
  7. It's really missing. How to restore it? EDIT: Restored via "apt-get reinstall".
  8. Mail from cron at 00:34: /usr/lib/armbian/armbian-apt-updates: line 39: lsb_release: command not found
  9. New kernel 5.9.14-mvebu available and installed.
  10. @Heisath The reboots took place with 5.8.16-mvebu. After replacement of the PSU I had a reboot after one day, so I excluded the PSU as the root cause, but I left the new one in operation. Next step was the upgrade to 5.8.18-mvebu, five days ago. Since then uninterrupted operation. The usage profile is always the same, a RAID5 serving as media server plus a nextcloud docker installation.
  11. OTOH After the upgrade to 5.8.18, containing the DFS patches, my installation is up and running for 4 days now. Are there any negative implications to be expected after the release of the new kernels without DFS management?
  12. FWIW Although it seems to be evidence that the DFS code is the cause for the spontaneous reboots, I want to inform you that my installation (see https://forum.armbian.com/topic/16038-random-system-reboots/?do=findComment&comment=113510) is running now more than two days after upgrade to 5.8.18-mvebu.
  13. @kratz00 @Mangix @gprovost @Heisath See my post in the parallel thread https://forum.armbian.com/topic/16038-random-system-reboots/?do=findComment&comment=113510 I used a different (newer) Kernel and a new PSU but I got again a spontaneous reboot.