FredK

  • Posts

    30
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Applications

Everything posted by FredK

  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 [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 am I doing wrong? EDIT: See the following post in https://forum.openmediavault.org/index.php?thread/28242-nextcloud-with-letsencrypt-using-omv-and-docker-compose-q-a/&postID=265371#post265371 docker-compose.yml
  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,now 0.6.1-2 armhf [installed,automatic] python3-docker/stable,now 3.4.1-4 all [installed,automatic] python3-dockerpty/stable,now 0.4.1-1 all [installed,automatic] python3-dockerpycreds/stable,now 0.3.0-1 all [installed,automatic] "Inside" the MariaDB container mariadb is 10.1.47: root@helios4:~# !494 docker exec -it nextclouddb /bin/bash root@6f5d32139adf:/# 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] The mariadb docker image is from bionic (ubuntu 18.04). build_version Linuxserver.io version:- 110.4.17mariabionic-ls9 Build-date:- 2021-01-30T06:00:22+00:00 Bionic was the last ubuntu release supporting 32bit. An apt-get update takes packages from "http://ports.ubuntu.com/ubuntu-ports bionic". And 10.1.47 is the latest available release.
  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.
  14. Spontaneous reboot with new PSU after 26 hours of operation. EDIT: System now upgraded to 5.8.18-mvebu Buster 20.11 (coming from 5.8.16-mvebu Buster 20.08.22)
  15. I ordered a replacement PSU which was delivered and put in operation this morning. I'll give feedback in any case (spontaneous reboot or continous operation).
  16. @gprovostWhat's about these two replacement PSUs? https://www.amazon.de/dp/B07Q72NBQK https://www.amazon.de/dp/B07RHSX3WR
  17. @gprovost I suspect the PSU is dying, also.
  18. @Magix: Do you also have such a high frequence of reboots? Between 6 hours and 2 days. @gprovost: Can you please if yes or no, the watchdog service is running. During log capturing at the serial console the watchdog service was disabled.
  19. Since two or three weeks I'm experiencing spontaneous reboots, also. My system: Linux helios4 5.8.16-mvebu #20.08.13 Capturing logs at the serial console didn't reveal any useful information. So, I ran out of ideas. "armbianmonitor -u" has been stored at http://ix.io/2EN3
  20. I appreciate the work and support regarding armbian. I'm not an advocate of "Never touch a running system!", rather the opposite. I want to learn and to gain experience. Then it might happen that I get into minor trouble sometimes. But I learn most in such situations. FredK
  21. Hi Heisath, thank you for the clarifications. Sure, I can live with the LED problem. My original post was meant to be used as an indication that something must have gone wrong in the last few updates. Let's wait for 20.11. FredK
  22. Hi Heisath, thank you for your post. There are slightly contradictory informations. The welcome message says "Welcome to Armbian 20.08.17 Buster with Linux 5.8.16-mvebu". "uname -a" says "Linux helios4 5.8.16-mvebu #20.08.13 SMP Mon Oct 19 08:14:25 CEST 2020 armv7l GNU/Linux". i.e. 20.08.17 <-> 20.08.13 Using armbian-config to re-install "linux-image-dev-mvebu=20.08.13 5.8.16-mvebu" resulted in an unbootable system. I had to restore the last backup (SDcard). Now I'm back in business, but as before no LED support. Regards FredK