Posts by Zoki

  • Accidentally removed Openmediavault - Need to restore

    systemd tells you your service is masked (marked as not startable):

    Code
    Description: failed to start (exit status 1) -- /bin/systemctl: Failed to start openmediavault-engined.service: Unit openmediavault-engined.service is masked.


    try to verify this with

    Code
    systemctl list-unit-files

    and unmask it with

    Code
    systemctl unmask openmediavault-engined

  • Do Rsync + Rsnapshot have to consume double space on same disk?

    From what you say I understand the following:

    • You are using rsync service to copy files to OMV into Daily-backups and then
    • you are using rsnapshot to copy from Daily-backups to rsnapshot (possibly keeping hard linked history)

    So you have 2 copies of your files one in Daily-backup and a history with hard links in rsnapshot.


    Is this what you wanted? Don`t know

  • weakref.py - name "self" ist not defined

    Here you are:



    Next time keep a backup before editing


    Indentation error or mix of space and tap?


    Python requires strict indentation rules an only spaces

  • omv 4?

    Take a look here

  • Webinterface randomly broken

    Seems like the directory /var/log/nginx doesn not exist on your system.


    Try this:

    Code
    mkdir /var/log/nginx

    chown root.adm /var/log/nginx

    chmod 755 /var/log/nginx

    Next step is to find out, why this directory is missing

  • Missing documentation for rsnapshot

    In the GUI you configure how many hourly, daily, weekly, ... copies should be retained.
    In /etc/cron.d/openmediavault-rsnapshot is defined when to run rsnapshot:
    Mine looks like:



    Code
    # Create cron file

    # This is the cron file for openmediavault-rsnapshot.

    # The file /var/lib/openmediavault/cron.d/rsnapshot will mirror

    # the jobs that are configured in the plugin.

    # m h dom mon dow user command

    5 * * * * root /var/lib/openmediavault/cron.d/rsnapshot hourly

    30 3 * * * root /var/lib/openmediavault/cron.d/rsnapshot daily

    0 3 * * 1 root /var/lib/openmediavault/cron.d/rsnapshot weekly

    30 2 1 * * root /var/lib/openmediavault/cron.d/rsnapshot monthly

    00 2 1 1 * root /var/lib/openmediavault/cron.d/rsnapshot yearly

  • Update does not work - DNS problem

    Ich verstehe den Screenshot nicht:


    DHCP ist ausgeschaltet und trotzdem sind einige Einträge gesetzt. Willst Du, dass OMV IP Adressen an Clients vergibt oder soll das deine Fritzbox tun?
    Die Konfiguration sagt zudem, dass die Rechner, die eine IP-Adresse vom OMV bekommen, die Fritzbox als DNS-Server verwenden sollen.


    Mach mal bitte einen Screenshot von der Konfiguration des Netzwerks in OMV

  • Update does not work - DNS problem

    Jetzt war ich doch neugierig und habe mal das Plugin installiert.
    Bei mir steht dort auf der Seite in dem Abschnitt DNS Settings
    "DNS requests for unknown hosts are forwarded to the OpenMediaVault's DNS servers as configured in System -> Network -> DNS Server."


    Und was steht da, wenn der DNS-Server nicht per DHCP gesetzt wird? Sprich: Was hast Du da eingetragen?

  • Nach Upgrade auf Jessie und OMV 2->3 Neuinstallation nur von OMV

    rc bedeutet :

    • r: das Paket wurde zum entfernen markiert
    • c: die Konfigurationsdateien sind noch auf dem System

    Probier es mal, nur die Konfigurationsdateien zu entfernen


    dpkg –purge openmediavault-nzbget


    Ich tippe aber eher auf einen Fehler in der config.xml, aber das deinstallieren der alten Pakete wird nicht schaden.

  • config.xml - sharedfolderref

    Just for the record. I did the upgrade and had to fix a few of those errors.
    In my case the reason was that there were line breaks and possibly whitespace characters inside the tags. Removing them fixed it.