Posts by daschmidt1994

    What is the output of

    after change to port 80:


    EDIT:


    I saw that apache2 is listen on port 80 when i systemcl stop apache.service and then start nginx it work till the next reboot.

    Good morning,



    after a power failur the web Gui only show the Apache2 Debian Default Page. When I change the port to 81 it work but when change it back to 80 I get this errors:


    Code
    Total run time:    6.318 s
    [ERROR   ] Command '/bin/systemd-run' failed with return code: 1
    [ERROR   ] stderr: Running as unit: run-p2260-i2560.scope; invocation ID: 333e1eccc1394c168a9d00cb3db4e738
    Job for nginx.service failed because the control process exited with error code.
    See "systemctl status nginx.service" and "journalctl -xeu nginx.service" for details.
    [ERROR   ] retcode: 1
    [ERROR   ] Running as unit: run-p2260-i2560.scope; invocation ID: 333e1eccc1394c168a9d00cb3db4e738
    Job for nginx.service failed because the control process exited with error code.
    See "systemctl status nginx.service" and "journalctl -xeu nginx.service" for details.

    how I can fix this?

    That works, today I created some dataset and child dataset but in the shared folder I can only use the dataset and not the child one is this normal?


    EDIT: Solution is Discover in the ZFS section

    Good evening,


    I just installed OpenMediaVault on a Pironman. Now I wanted to install ZFS via a plugin, but I get the following error message:



    I installed the packages manually and then installed ZFS via the GUI. Is this a problem, or did I do something wrong?

    Good evening,


    short question.


    Is it possible to encrypt a mergerfs? Have for a backup 2 HDD stripped with mergerfs and look for encryption.


    With luks there I can't see a device(mergerfs) in the dropdownlist.

    oh sorry that was my fault, in the document standt only changes between the # and I added it on the bottom.




    I don't understand why the sda2 have a mountpoint with /export/frigate

    I'm back with the same problem and still have no solution, but now I need the nfs for my frigate.


    Have nobody the same problem?

    The nfs share writte often to my root directory after a rebot from my openmediavault.


    Code
    root@openmediavault:/export/frigate# df -h /
    Dateisystem    Größe Benutzt Verf. Verw% Eingehängt auf
    /dev/sda2       218G     40G  167G   20% /


    the export:


    Code
    # This file is auto-generated by openmediavault (https://www.openmediavault.org)# WARNING: Do not edit this file, your changes will get lost.
    # /etc/exports: the access control list for filesystems which may be exported
    #               to NFS clients.  See exports(5).
    /export/frigate 192.168.178.220(fsid=02063ded-ecfe-429d-b651-4d1866067c58,rw,subtree_check,insecure,no_root_squash,crossmnt)
    /export 192.168.178.220(ro,fsid=0,root_squash,subtree_check)


    the mount om the client:


    Code
    root@debianswag:~/docker/frigate# mount | grep nfs
    192.168.178.199:/frigate on /mnt/frigate type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.178.220,local_lock=none,addr=192.168.178.199,_netdev)