Posts by CM000n

    I encountered the same problem in OMV 5.2.6-1:

    What could be the cause and how could the problem be solved?
    Adding the KEys manually as suggested by @Wolf2000 back then did not work for me.
    I have installed omv-extras via the commandline with "wget -O -…ckages/raw/master/install | bash" without getting an error message.
    Many thanks in advance

    Today I tried to update to version 5.2.5-1 with the hope that this will fix the problem, and unfortunately I got this:

    When I tried to update my Openmediavault (amd64) to version 5.2.4-1 today, I encountered the following problem:

    Unfortunately, I can't solve it and I'm really starting to get confused. Does anyone else have any ideas?
    Thanks a lot in any case

    Hi @massimog,

    can you please explain how you configured IPv6 Support for Pi-Hole in OMV Docker?
    I tried to specify an IPv6 address as ServerIPv6 environment variable in the container settings.

    But unfortunately this does not seem to work :-(
    The field for the IPv6 address in the Pi-Hole admin area remains empty.

    What's the output if you try to install and update the package via commandline?

    If you on OMV 3.x:

    dpkg -i openmediavault-omvextrasorg_latest_all3.deb
    apt-get update
    apt-get upgrade

    If you on OMV 4.x:

    dpkg -i openmediavault-omvextrasorg_latest_all4.deb
    apt-get update
    apt-get upgrade

    I can confirm this beahaviour!
    But it seems that OMV sends double messages only in some cases. For me it happens for LogIn notifications whe I log in via third party applications like OMV-Remote or in cases of an APT Update.

    When I send test messages I only get one Message.

    When I take a look at the syslog it looks like this for an APT Update:

    Jan 2 07:44:54 Server postfix/pickup[25173]: 3C2022CC08A4: uid=0 from=<root>
    Jan 2 07:44:54 Server postfix/cleanup[26690]: 3C2022CC08A4: message-id=<20170102064454.3C2022CC08A4@Server.Workgroup>
    Jan 2 07:44:54 Server postfix/qmgr[17050]: 3C2022CC08A4: from=<>, size=978, nrcpt=2 (queue active)
    Jan 2 07:44:54 Server postfix/pipe[26708]: 3C2022CC08A4: to=<openmediavault-notification@localhost.localdomain>, relay=omvnotificationfilter, delay=0.18, delays=0.16/0.01/0/0.01, dsn=2.0.0, status=sent (delivered via omvnotificationfilter service)
    Jan 2 07:44:54 Server anacron[25936]: Job `cron.daily' terminated
    Jan 2 07:44:54 Server anacron[25936]: Normal exit (1 job run)
    Jan 2 07:44:55 Server postfix/smtp[26709]: 3C2022CC08A4: replace: header Subject: CRON-APT completed on Server [/etc/cron-apt/config]: Subject: [Server.Workgroup] CRON-APT completed on Server [/etc/cron-apt/config]
    Jan 2 07:44:58 Server postfix/smtp[26709]: 3C2022CC08A4: to=<>,[2a00:1450:400c:c04::6d]:587, delay=4.4, delays=0.16/0.04/0.92/3.2, dsn=2.0.0, status=sent (250 2.0.0 OK 1483339498 cj1sm15512702wjd.46 - gsmtp)
    Jan 2 07:44:58 Server postfix/qmgr[17050]: 3C2022CC08A4: removed

    Jan 2 13:43:42 Server postfix/pickup[11500]: 35A032CC0CD1: uid=0 from=<root>
    Jan 2 13:43:42 Server postfix/cleanup[12007]: 35A032CC0CD1: message-id=<20170102124342.35A032CC0CD1@Server.Workgroup>
    Jan 2 13:43:42 Server postfix/qmgr[3020]: 35A032CC0CD1: from=<>, size=443, nrcpt=2 (queue active)
    Jan 2 13:43:42 Server postfix/pipe[12009]: 35A032CC0CD1: to=<openmediavault-notification@localhost.localdomain>, relay=omvnotificationfilter, delay=0.37, delays=0.25/0.01/0/0.1, dsn=2.0.0, status=sent (delivered via omvnotificationfilter service)
    Jan 2 13:43:42 Server postfix/smtp[12010]: connect to[2a00:1450:400c:c07::6d]:587: Network is unreachable
    Jan 2 13:43:43 Server postfix/smtp[12010]: 35A032CC0CD1: replace: header Subject: Test message from Server: Subject: [Server.Workgroup] Test message from Server
    Jan 2 13:43:44 Server postfix/smtp[12010]: 35A032CC0CD1: to=<>,[]:587, delay=2.3, delays=0.25/0.28/0.59/1.1, dsn=2.0.0, status=sent (250 2.0.0 OK 1483361024 wp2sm49758525wjc.35 - gsmtp)
    Jan 2 13:43:44 Server postfix/qmgr[3020]: 35A032CC0CD1: removed

    Except of the error because of missing IPV6 Adress I can't see any difference between the Test Message and the APT Update Message ?(

    Du must das Testrepo für die "Downloader" aktivieren und nicht das eigentlich Extras Repo.

    Ist leider etwas verwirrend. Finde auch das das Sensor Plugin im "Downloader" Testingrepo eigentlich sinngemäß nix verloren hat.

    Owncloud 9 is running very well on my OMV machine, installed with this guide.
    Great help :thumbsup:

    I often copy files directly to the owncloud data directory via my network and a smb share.
    Because files copied with this method are not shown up in the Owncloud userinterface I tried today a OCC Command that scans for all user for new files:

    sudo -u www-data /media/95c1c8e9-750d-4385-aba7-a97c34cc66a4/www/owncloud/occ files:scan --all

    The command worked very well over the Terminal with putty :)
    So far so good, but did anyone know a mehtod how I can use this command with openmediavaults scheduled tasks?

    If I trie to add it, I get the following error message:

    Um ganz sicher zu gehen:

    sudo apt-get remove mysql-server mysql-client mysql-common

    sudo apt-get purge mysql-server mysql-client mysql-common

    sudo apt-get autoremove

    Danach dann einmal:

    sudo apt-get remove --purge mysql\*

    Dann sollte wirklich alles! gelöscht sein das mit MySQL zu tun hat.
    Dann noch einmal

    sudo updatedb

    Um deine Verzeichnisstruktur zu aktualisieren

    Und dann kannst du nochmal hiermit schauen ob uns ggf ein MySql Paket durch dir Lappen gegangen ist:
    sudo dpkg -l | grep -i mysql

    Falls dir der letze Befehl noch etwas anzeigt kannst du diese Pakete dann auch noch mit Purge Befehl deinstallieren.

    Your Parity Drive has to be as large or larger as the largest Data Drive (Like You already mentioned).
    Since you are using 1 Paritiy Drive you can lose one Data Drive for it (Replace Data Drive with failure for a new one and recover Data from the parity drive).
    It's even easyier if your parity drive fails. Just replace it for a new one and sync your Snapraid again.

    If you need security for two or more diskfailures at the same time you have to use that amount of parity drives.

    Maybe this can help you a bit:…/1677233/thread/5a4ce41c/