ExecException when applying changes since OMV5 upgrade

jfromeo · 27. Januar 2020

Hello all.

I just upgraded to OMV5 and I am facing this error whenever I try to apply any change thorugh the webUI (rsync changes in this example):

Code

Error #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 rsync 2>&1' with exit code '1': Traceback (most recent call last):
File "/usr/sbin/omv-salt", line 136, in <module>
sys.exit(main())
File "/usr/sbin/omv-salt", line 132, in main
cli()
File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__
return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 717, in main
rv = self.invoke(ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 1137, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/lib/python3/dist-packages/click/core.py", line 1137, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke
return callback(*args, **kwargs)
File "/usr/sbin/omv-salt", line 120, in deploy_run
caller = salt.client.Caller(mopts=mopts)
File "/usr/lib/python3/dist-packages/salt/client/__init__.py", line 1995, in __init__
self.sminion = salt.minion.SMinion(self.opts)
File "/usr/lib/python3/dist-packages/salt/minion.py", line 842, in __init__
opts['grains'] = salt.loader.grains(opts)
File "/usr/lib/python3/dist-packages/salt/loader.py", line 784, in grains
ret = funcs[key]()
File "/usr/lib/python3/dist-packages/salt/grains/core.py", line 2379, in dns
resolv = salt.utils.dns.parse_resolv()
File "/usr/lib/python3/dist-packages/salt/utils/dns.py", line 1143, in parse_resolv
for line in src_file:
File "/usr/lib/python3.7/codecs.py", line 322, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xa0 in position 10: invalid start byte 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/bgstatusz3...', '/tmp/bgoutputdE...')
#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

Has it something to do with python module? Should I try to reinstall it?. What is omv-salt exactly? It looks like a new OMV5 thing.

I did:

Code

apt-get update
apt-get upgrade

And I have no packets to be updated at the moment.

I tried browser cache cleaning and locale changing to English/Spanish.

PD: Done some research. It seems there is another user on the same situation: https://forum.openmediavault.o…26061-Salt-Stack-in-OMV5/

Zitat

"Every time you apply a configuration change OMV5 checks against its salt states and will fail if they aren't there.
I then have to enable the custom OMV Salt Configuration, apply the change and then disable the config again."

Thanks in advance.

PD: Nevermind, got fixed after a reboot.

votdev · 28. Januar 2020

Can you please post the content of /etc/resolv.conf?

Zitat von jfromeo

What is omv-salt exactly?

This is the new tool to deploy the configurations.

jfromeo · 28. Januar 2020

Zitat von votdev

Can you please post the content of /etc/resolv.conf?

This is the new tool to deploy the configurations.

Thank you for the quick response. After a reboot, everything worked fine.

Code

# cat /etc/resolv.conf
nameserver 8.8.8.8
nameserver 8.8.4.4

Talking about nameservers, which is the difference between:

/etc/resolv.conf
/etc/resolvconf/run/resolv.conf

And the edit option at Interfaces which let you fill in nameservers for each NIC/bond connections? (and how did you fill 2 different ones, separated with coma maybe?)

votdev · 28. Januar 2020

Zitat von jfromeo

Talking about nameservers, which is the difference between:

/etc/resolv.conf
/etc/resolvconf/run/resolv.conf

I think to remember that systemd creates a symlink between both.

Zitat von jfromeo

And the edit option at Interfaces which let you fill in nameservers for each NIC/bond connections? (and how did you fill 2 different ones, separated with coma maybe?)

I think comma or blank.

jfromeo · 28. Januar 2020

Zitat von votdev

I think to remember that systemd creates a symlink between both.

I think comma or blank.

Thank you. Comma worked.

wombat · 29. Januar 2020

OMV 5.2.x(6)

I found out, that:

1) If I set /etc/resolv.conf everything works fine until next OMV update (eg now 5.2.4 > 5.2.6)
2) After the update, the /etc/resolv.conf file is deleted and must be manually set/created again.
3) DNS servers settings in OMV GUI (Network> Interfaces ...) are ignored.

Code

openmediavault systemd-networkd[18665]: /etc/systemd/network/10-openmediavault-enp3s0.network:8: Unknown lvalue 'UseDNS' in section 'Network', ignoring

Code

[Match]
Name=enp3s0


[Network]
Address=10.7.1.254/24
Gateway=10.7.1.1
IPv6AcceptRA=no
LinkLocalAddressing=no
UseDNS=yes
DNS=1.1.1.1 1.0.0.1


[Link]


[IPv6Prefix]

Alles anzeigen

votdev · 29. Januar 2020

The UseDNS issue has been fixed in openmediavault 5.2.7: https://github.com/openmediava…2df1a37f97c706b56d0ecd968

votdev · 29. Januar 2020

Is systemd-resolved running? This daemon is responsible for creating the /etc/resolv.conf file.

Bash

# systemctl status systemd-resolved.service

wombat · 29. Januar 2020

Yes, it is.

Finally, it seems that /run/systemd/resolve/resolv.conf via symlinks works fine, so at the moment it works correctly. I will follow the next update.

Code

systemctl status systemd-resolved.service
 systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/lib/systemd/system/systemd-resolved.service; disabled; vendor preset: enabled)
  Drop-In: /lib/systemd/system/systemd-resolved.service.d
           └─resolvconf.conf
   Active: active (running) since Wed 2020-01-29 20:16:31 CET; 51min ago
     Docs: man:systemd-resolved.service(8)
           https://www.freedesktop.org/wiki/Software/systemd/resolved
           https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
           https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
  Process: 23960 ExecStartPost=/bin/sh -c [ ! -e /run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved (code=exited, status=0/SUCCESS)
 Main PID: 23954 (systemd-resolve)
   Status: "Processing requests..."
    Tasks: 1 (limit: 4915)
   Memory: 2.6M
   CGroup: /system.slice/systemd-resolved.service
           └─23954 /lib/systemd/systemd-resolved


Jan 29 20:16:30 openmediavault.local systemd[1]: Starting Network Name Resolution...
Jan 29 20:16:30 openmediavault.local systemd-resolved[23954]: Positive Trust Anchors:
Jan 29 20:16:30 openmediavault.local systemd-resolved[23954]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Jan 29 20:16:30 openmediavault.local systemd-resolved[23954]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Jan 29 20:16:30 openmediavault.local systemd-resolved[23954]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr
.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in
-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test
Jan 29 20:16:30 openmediavault.local systemd-resolved[23954]: Using system hostname 'openmediavault.local'.
Jan 29 20:16:31 openmediavault.local systemd[1]: Started Network Name Resolution.

Alles anzeigen

Jetzt mitmachen!