Beiträge von Spirare

  • applying modification on GUI after update

    Hi,

    I have the same problem with a different system.

    Updating has been working fine until today !?

    This is the output of:

    apt-key list

    SOMA suggestion of adding keys did not work on my system.

    Where can't I get the missing key if this is a solution ?

  • Portainer won't start up at restart

    SOLVED!

    Looking at the syslog, the system struggled to mount the drive on which docker is set to run.

    fsck corrected a few problems on that drive and now all my containers are running after booting


    Thank you for nudging me in the right direction :)

  • OMV6 - Docker's containers don't start after boot

    OMV6 is running on a NanopiM4V2

    Had OMV5 running fine for 2 yrs before a total fresh OS and OMV re-install


    Ok, I just tried to re-install docker from OMVextra and rebooted...no change... the same problem.

  • OMV6 - Docker's containers don't start after boot

    OMV6 Fresh install...both Armbian Bullseye (Debian 11) and thereafter OMV6.

    OMV6 installed with armbian-config script.

    Then following this guide "[How to] Prepare OMV to install docker applications was useful to set up Docker & Portainer"


    The Portainer Status of OMV-EXTRA GUI is ''No portainer container found." until Docker is restarted

  • Portainer won't start up at restart

    The output looks like Docker is running fine !


    Nov 19 21:21:32 spirarevault dockerd[2347]: time="2022-11-19T21:21:32.113087601+13:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock <>

    Nov 19 21:21:32 spirarevault dockerd[2347]: time="2022-11-19T21:21:32.113136527+13:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc

    Nov 19 21:21:32 spirarevault dockerd[2347]: time="2022-11-19T21:21:32.141261455+13:00" level=info msg="[graphdriver] using prior storage driver: overlay2"

    Nov 19 21:21:32 spirarevault dockerd[2347]: time="2022-11-19T21:21:32.151776086+13:00" level=info msg="Loading containers: start."

    Nov 19 21:21:32 spirarevault dockerd[2347]: time="2022-11-19T21:21:32.786140844+13:00" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option >

    Nov 19 21:21:32 spirarevault dockerd[2347]: time="2022-11-19T21:21:32.938399808+13:00" level=info msg="Loading containers: done."

  • OMV6 - Docker's containers don't start after boot

    Hi,

    OMV-EXTRA Docker 5:20.10.21~3-0~debian-bullseye

    Fresh install...

    None of my containers (including Portainer) start automatically after booting or rebooting.

    Restart policies is set at "unless stop" for all containers.

    OMV-EXTRA GUI report Docker to be up & running after rebooting.

    In order to get all containers to start automatically, I need to 'restart' Docker via the OMV_EXTRA GUI.


    Am I missing something here?


    Any hints on how to solve this ?


    Thanks

  • Portainer won't start up at restart

    Latest OMV6

    I have the same problem...Portainer nor any container automatically starts after booting up... I need to manually restart Docker.

    Docker is installed on a separate drive and /etc/systemd/system/docker.service.d exist.


    Should I start a new thread for this ??

  • Installing Jellyfin

    I am following this guide: Example of installing an application Jellyfin ([How to] Prepare OMV to install docker applications) but struggle with some simple concepts.


    Question#1: I am not sure how to setup the Portainer Environment setting ?


    Question #2: Customizing the stack - Comment 3...GIVE PERMISSIONS to the userapp on our /DATA/media shared folder

    I have done this by setting 'group' to 'users'... is this OK ?

    I am asking since I can't access jellyfin at 192.168.8.60:8096 after deploying the stack.

    My OMV6 server is at 192.168.8.60 and I have tried adding the PublishedServerUrl line in the stack...but with no avail.

  • Wetty on OMV6

    Is openmediavault-wetty optional or absolutely required?


    I am following the same procedure installing preparing & installing docker on a ARM64 SBC.

  • Can't apply changes in OMV configuration anymore !

    Zitat von Agricola

    I have a first version NanoPi M4 with a SATA hat, but I have never run any drives from the USB. Is there any way you could externally power those 2 HHD’s and see if it’s a power issue?


    BTW: This is an excellent SBC machine. It does become a little pricey when you add the heat sync, 4-port SATA hat, and dedicated 12V. power supply. It is my backup server and has been running continuously for 2 years.

    Great point...Externally powering HDD testing is underway ...I will report back in a few days.


    BTW: I agree, find that little SBC very solid...OMV5 is rock stable on it...running 24/7 as a 8Tb media server with 4x2Tb HDD on the SataHat....personally, I am satisfied (or if you prefer, worth the extra cost). The Sata controller runs a bit warm, so just to be safe, I added a micro fan driven at min low speed by the mainboard... the HDD are also mounded in a way to allow plenty of natural air convection. The HDD on the USB3 ports of the mainboard is used to back up my personal data with Rsyn and repository for OS image backup for other devices running on my network. I am presently experimenting BorgBackup to replace Rsyn. Lastly, this SBC has plenty of capacity left...

  • Can't apply changes in OMV configuration anymore !

    OMV is running on Armbian Buster as per the above instructions.

    Yes, it's on the 'light' Buster without Desktop.

    Again, it has been running for months fine...very stable.

    The NanoPiM4V2 has a Satat Hat on it that can accommodate 4x Sata HDD...additionally the main NanoPiM4V2 board its has 4x USB3 ports...the one I am referring to as when adding more than one USB-HDD on this, I get the problem applying changes.

    The Sata Hat has 12v power connection that powers the HDD but also the NanoPiM4V2... I use a quality 12v / 20Amp regulated power supply to power the whole system so I don't think the problem could be coming from this.


    However, your point prompts me to investigate the NanoPiM4V2 USB3 ports specifications as how much power they can provide...strangely, the 2 USB/HDD 2.5 inches are working fine..the only problem is when I 'apply' OMV changes...which raises the question once again: "What that script is doing that can be linked to the NanoPiM4V2 to restart?