Cannot apply config that was changed by some package upgrade due to Jinja error

  • Hi,

    i'm running OMV 5.5.9-1 and i recently did an omv-update and apparently this caused an internal update of the config file (i didn't change the config by myself). When i try to apply the config, the following error occurs:



    Any idea what may have caused this? openmediavault.local was the default hostname suggested by the installer and it's valid.

    • Offizieller Beitrag

    The hostname is correct, but not your database. The error indicates that the field hostname contains openmediavault.local, but the datamodel wants a openmediavault and the local in the field domainname.


    See also

    * https://github.com/openmediava…/datamodel/schema.py#L128

    * https://github.com/openmediava…vault/json/schema.py#L410


    Go to the WebUI and try to change this, but i assume you'll get an database exception, too. If that's the case, you need to modify the file /etc/openmediavault/config.xml via CLI.


    It must look like

    XML
            <network>
                <dns>
                    <hostname>openmediavault</hostname>
                    <domainname>local</domainname>
                </dns>


    How did you setup the system? Via ISO or an ARM image?


    P.S.: I'm wondering how you could setup this hostname, the UI and the database population script does not allow that.


    * https://github.com/openmediava…/populate.d/20hostname.sh

    * https://github.com/openmediava…em/network/General.js#L40

    * https://github.com/openmediava…/js/ext-overrides.js#L226

  • votdev

    Hat das Label OMV 5.x hinzugefügt.
  • captainkrunch

    Hat das Label gelöst hinzugefügt.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!