OMV5 error while creating network interfaces

Patatorz · 30. August 2020

Hello, i made today the updates of OMV5 to the version 5.5.9-1.

I used to have a PCIe ethernet board i was using the network ports and i wanted to remove it from the PC and use the internal ports. I'm trying to initiate them in the network/interface menu, OMV5 is seeing the interfaces but when i try to close and save an error appears (like below).

Could you give me some hints to solve this issue ?

Best Regards

Zitat

Erreur #0:
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run collectd 2>&1' with exit code '1': debian:
---------- ID: configure_collectd_conf_cpu_plugin Function: file.managed Name: /etc/collectd/collectd.conf.d/cpu.conf Result: True Comment: File /etc/collectd/collectd.conf.d/cpu.conf is in the correct state Started: 17:56:09.756316 Duration: 12.721 ms Changes:
---------- ID: configure_collectd_conf_df_plugin Function: file.managed Name: /etc/collectd/collectd.conf.d/df.conf Result: True Comment: File /etc/collectd/collectd.conf.d/df.conf is in the correct state Started: 17:56:09.769112 Duration: 4.077 ms Changes:
---------- ID: configure_collectd_conf_interface_plugin Function: file.managed Name: /etc/collectd/collectd.conf.d/interface.conf Result: True Comment: File /etc/collectd/collectd.conf.d/interface.conf is in the correct state Started: 17:56:09.773257 Duration: 4.107 ms Changes:
---------- ID: configure_collectd_conf_load_plugin Function: file.managed Name: /etc/collectd/collectd.conf.d/load.conf Result: True Comment: File /etc/collectd/collectd.conf.d/load.conf is in the correct state Started: 17:56:09.777429 Duration: 0.912 ms Changes:
---------- ID: configure_collectd_conf_memory_plugin Function: file.managed Name: /etc/collectd/collectd.conf.d/memory.conf Result: True Comment: File /etc/collectd/collectd.conf.d/memory.conf is in the correct state Started: 17:56:09.778404 Duration: 0.859 ms Changes:
---------- ID: configure_collectd_conf_rrdcached_plugin Function: file.managed Name: /etc/collectd/collectd.conf.d/rrdcached.conf Result: True Comment: File /etc/collectd/collectd.conf.d/rrdcached.conf is in the correct state Started: 17:56:09.779326 Duration: 1.08 ms Changes:
---------- ID: configure_collectd_conf_syslog_plugin Function: file.managed Name: /etc/collectd/collectd.conf.d/syslog.conf Result: True Comment: File /etc/collectd/collectd.conf.d/syslog.conf is in the correct state Started: 17:56:09.780528 Duration: 1.732 ms Changes:
---------- ID: configure_collectd_conf_unixsock_plugin Function: file.managed Name: /etc/collectd/collectd.conf.d/unixsock.conf Result: True Comment: File /etc/collectd/collectd.conf.d/unixsock.conf is in the correct state Started: 17:56:09.782405 Duration: 1.119 ms Changes:
---------- ID: configure_collectd_conf_uptime_plugin Function: file.managed Name: /etc/collectd/collectd.conf.d/uptime.conf Result: True Comment: File /etc/collectd/collectd.conf.d/uptime.conf is in the correct state Started: 17:56:09.783591 Duration: 1.215 ms Changes:
---------- ID: prereq_collectd_service_monit Function: salt.state Result: False Comment: Run failed on minions: debian Started: 17:56:09.785552 Duration: 93.471 ms Changes: debian: Data failed to compile: ---------- Rendering SLS 'base:omv.deploy.monit.default' failed: Jinja error: tls: Invalid value '0', allowed values are 'none, ssl, starttls, auto'. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/salt/utils/templates.py", line 400, in render_jinja_tmpl output = template.render(**decoded_context) File "/usr/lib/python3/dist-packages/jinja2/asyncsupport.py", line 76, in render return original_render(self, *args, **kwargs) File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 1008, in render return self.environment.handle_exception(exc_info, True) File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 780, in handle_exception reraise(exc_type, exc_value, tb) File "/usr/lib/python3/dist-packages/jinja2/_compat.py", line 37, in reraise raise value.with_traceback(tb) File "<template>", line 37, in top-level template code File "/var/cache/salt/minion/extmods/modules/omv_conf.py", line 39, in get objs = db.get(id_, identifier) File "/usr/lib/python3/dist-packages/openmediavault/config/database.py", line 85, in get query.execute() File "/usr/lib/python3/dist-packages/openmediavault/config/database.py", line 724, in execute self._response = self._elements_to_object(elements) File "/usr/lib/python3/dist-packages/openmediavault/config/database.py", line 485, in _elements_to_object result.validate() File "/usr/lib/python3/dist-packages/openmediavault/config/object.py", line 235, in validate self.model.validate(self.get_dict()) File "/usr/lib/python3/dist-packages/openmediavault/config/datamodel.py", line 200, in validate self.schema.validate(data) File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 170, in validate self._validate_type(value, schema, name) File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 224, in _validate_type raise last_exception File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 195, in _validate_type self._validate_object(value, schema, name) File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 300, in _validate_object self._check_properties(value, schema, name) File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 508, in _check_properties self._validate_type(value[propk], propv, path) File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 224, in _validate_type raise last_exception File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 204, in _validate_type self._validate_string(value, schema, name) File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 279, in _validate_string self._check_enum(value, schema, name) File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 468, in _check_enum % (valuev, ", ".join(schema['enum'])), openmediavault.json.schema.SchemaValidationException: tls: Invalid value '0', allowed values are 'none, ssl, starttls, auto'.
; line 37
--- [...] # http://www.debianadmin.com/mon…-servers-using-monit.html # http://www.uibk.ac.at/zid/systeme/linux/monit.html # http://wiki.ubuntuusers.de/Monit # http://viktorpetersson.com/201…-and-postgresql-on-ubuntu
{% set email_config = salt['omv_conf.get']('conf.system.notification.email') %} <======================
configure_default_monit: file.managed: - name: "/etc/default/monit" - contents: [...] ---
---------- ID: configure_collectd_conf Function: file.managed Name: /etc/collectd/collectd.conf Result: True Comment: File /etc/collectd/collectd.conf is in the correct state Started: 17:56:09.879100 Duration: 5.446 ms Changes:
---------- ID: start_collectd_service Function: service.running Name: collectd Result: True Comment: The service collectd is already running Started: 17:56:09.891104 Duration: 20.048 ms Changes:
---------- ID: monitor_collectd_service Function: module.run Name: monit.monitor Result: True Comment: Started: 17:56:09.912566 Duration: 0.612 ms Changes:
---------- ID: install_mkrrdgraph_cron_job Function: file.managed Name: /etc/cron.d/openmediavault-mkrrdgraph Result: True Comment: File /etc/cron.d/openmediavault-mkrrdgraph is in the correct state Started: 17:56:09.913251 Duration: 1.484 ms Changes:
---------- ID: generate_rrd_graphs Function: cmd.run Name: /usr/sbin/omv-mkrrdgraph Result: True Comment: Command "/usr/sbin/omv-mkrrdgraph" run Started: 17:56:09.915289 Duration: 1433.321 ms Changes: ---------- pid: 1661 retcode: 0 stderr: stdout:

Summary for debian
-------------
Succeeded: 14 (changed=1)
Failed: 1
-------------
Total states run: 15
Total run time: 1.582 s in /usr/share/php/openmediavault/system/process.inc:182
Stack trace:
#0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(60): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/config.inc(167): OMV\Engine\Module\ServiceAbstract->deploy()
#2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(588): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatuscW...', '/tmp/bgoutput2q...')
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#7 /usr/share/openmediavault/engined/rpc/config.inc(189): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
#8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array)
#9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
#11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#12 {main}

Alles anzeigen

votdev · 31. August 2020

Could you plese explain how you setup the system? Did you install an older configuration file afterwards? I'm really wondering how users run into this issue because the database is migrated whenever a new package update is installed. All users like you running into this issue seem to install an older backup of the configuration file which does not met the new database schema.

You need to migrate it by running omv-confdbadm migrate conf 5.0.0.

Patatorz · 20. September 2020

Hello votdev , sorry i did not see your answer as notification did not work. How i made the setup :

1/ i instaled a fresh version of OMV5 including the PCIE card with the 2 interfaces and it works like a charm.

2/ i tried to enable the interfaces on the mother boards that never been initiated and problem is appearing.

I'm not sure to understand why you think i migrated as i installed from scratch.

The issue is not resolved.

votdev · 21. September 2020

If you have installed OMV from scratch it is not possible that the database error openmediavault.json.schema.SchemaValidationException: tls: Invalid value '0', allowed values are 'none, ssl, starttls, auto'. occurs because this change has been made in 5.2.0 and the latest ISO is 5.3.9. If you've installed OMV using an ARM image, this should also not happen because the latest package is installed. If you've installed an OMV version < 5.2.0 the database is migrated automatically. So, this error should NEVER appear, only if you install an older database file from an OMV < 5.2.0. I've tested the migration by installing 5.1.3 and upgraded to the latest version.

Code

root@omv5box:~# dpkg -l | grep openmediavault
ii  openmediavault                  5.1.3-1                             all          openmediavault - The open network attached storage solution
ii  openmediavault-keyring          1.0                                 all          GnuPG archive keys of the OpenMediaVault archive
root@omv5box:~# cat /etc/openmediavault/config.xml | grep \<tls\>
            <tls>none|ssl|startssl|auto</tls>
      <tls>0</tls>
root@omv5box:~# apt-get install --reinstall openmediavault
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be upgraded:
  openmediavault
1 upgraded, 0 newly installed, 0 to remove and 31 not upgraded.
Need to get 0 B/1707 kB of archives.
After this operation, 337 kB of additional disk space will be used.
Reading changelogs... Done
Preconfiguring packages ...
(Reading database ... 45581 files and directories currently installed.)
Preparing to unpack .../openmediavault_5.5.10-1_all.deb ...
Unpacking openmediavault (5.5.10-1) over (5.1.3-1) ...
Setting up openmediavault (5.5.10-1) ...
Installing new version of config file /etc/apt/post-invoke.d/10install-cleanup ...
Installing new version of config file /etc/bash_completion.d/omv-salt ...
Installing new version of config file /etc/cron.daily/openmediavault-check_locked_users ...
Installing new version of config file /etc/cron.daily/openmediavault-cron-apt ...
Installing new version of config file /etc/cron.daily/openmediavault-flush-mailq ...
Installing new version of config file /etc/cron.daily/openmediavault-mdadm ...
Installing new version of config file /etc/cron.daily/openmediavault-pending_config_changes ...
Installing new version of config file /etc/cron.weekly/openmediavault-update-smart-drivedb ...
Installing new version of config file /etc/default/openmediavault ...
Installing new version of config file /etc/sysctl.d/99-openmediavault.conf ...
Installing new version of config file /etc/udev/rules.d/99-openmediavault-md-raid.rules ...
Installing new version of config file /etc/udev/rules.d/99-openmediavault-nonrot.rules ...
Installing new version of config file /etc/udev/rules.d/99-openmediavault-scheduler.rules ...
Creating configuration database ...
Migrating configuration database ...
  Running migration conf_5.2.0
  Running migration conf_5.5.0
  Running migration conf_5.5.3
WARNING: The node 'clients' already exists at XPath '/config/system/time/ntp'.
Setting up Salt environment ...
Processing system modifications ...
groupadd: group 'openmediavault-admin' already exists
Processing triggers for rsyslog (8.1901.0-1) ...
Processing triggers for openmediavault (5.5.10-1) ...
Restarting engine daemon ...
Updating locale files ...
Updating file permissions ...
Purging internal cache ...
root@omv5box:~# cat /etc/openmediavault/config.xml | grep \<tls\>
            <tls>none|ssl|startssl|auto</tls>
      <tls>none</tls>

Alles anzeigen

Patatorz · 27. September 2020

Hello, all the problems have been solved with the 5.5.11-1. Thanks for your great support.

OMV5 error while creating network interfaces

Patatorz 30. August 2020

votdev 31. August 2020

Patatorz 20. September 2020

Patatorz 27. September 2020

Jetzt mitmachen!

Tags