OMV-Salt failed to unmask avahi-daemon

TechGuy · 28. Oktober 2022

Hi all,

I'm having some issues with my OMV server when I try to make configuration changes which relate to networking changes. Whenever I try to make changes from the Web UI, committing the pending changes fails because omv-salt is unable to unmask avahi-daemon at the end of the deployment of avahi-daemon. I have made a couple attempts to unmask/mask, enable/disable the avahi-daemon service and socket via systemctl but have not been able to make it work. The avahi-daemon will start successfully when I manually start it, it just fails when salt tries to unmask.

I had been using docker, but have uninstalled it to try troubleshooting, though avahi still starts correctly when docker is installed. So I don't believe it's related to docker as past threads have indicated.

Any help is much appreciated!

The exact message is:

Zitat

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color avahi 2>&1' with exit code '1': debian:

----------

ID: mask_avahi_service

Function: service.masked

Name: avahi-daemon

Result: True

Comment: Service avahi-daemon was masked

Started: 22:59:54.225925

Duration: 268.106 ms

Changes:

----------

masked:

----------

new:

True

old:

False

----------

ID: stop_avahi_socket

Function: service.dead

Name: avahi-daemon.socket

Result: True

Comment: Service avahi-daemon.socket is already disabled, and is dead

Started: 22:59:54.494251

Duration: 69.106 ms

Changes:

----------

avahi-daemon.socket:

False

----------

ID: stop_avahi_service

Function: service.dead

Name: avahi-daemon.service

Result: True

Comment: Service avahi-daemon.service is already disabled, and is dead

Started: 22:59:54.563555

Duration: 66.64 ms

Changes:

----------

avahi-daemon.service:

False

----------

ID: configure_default_avahi_daemon

Function: file.managed

Name: /etc/default/avahi-daemon

Result: True

Comment: File /etc/default/avahi-daemon is in the correct state

Started: 22:59:54.633278

Duration: 28.266 ms

Changes:

----------

ID: divert_default_avahi_daemon

Function: omv_dpkg.divert_add

Name: /etc/default/avahi-daemon

Result: True

Comment: Leaving 'local diversion of /etc/default/avahi-daemon to /etc/default/avahi-daemon.distrib'

Started: 22:59:54.662178

Duration: 29.062 ms

Changes:

----------

ID: configure_avahi_daemon_conf

Function: file.managed

Name: /etc/avahi/avahi-daemon.conf

Result: True

Comment: File /etc/avahi/avahi-daemon.conf updated

Started: 22:59:54.691589

Duration: 57.708 ms

Changes:

----------

diff:

---

+++

@@ -7,7 +7,7 @@

#browse-domains=0pointer.de, zeroconf.org

use-ipv4=yes

use-ipv6=yes

-allow-interfaces=

+allow-interfaces=br0

#deny-interfaces=eth1

#check-response-ttl=no

#use-iff-running=no

----------

ID: divert_avahi_daemon_conf

Function: omv_dpkg.divert_add

Name: /etc/avahi/avahi-daemon.conf

Result: True

Comment: Leaving 'local diversion of /etc/avahi/avahi-daemon.conf to /etc/avahi/avahi-daemon.conf.distrib'

Started: 22:59:54.749461

Duration: 29.322 ms

Changes:

----------

ID: remove_avahi_service_ftp

Function: file.absent

Name: /etc/avahi/services/ftp.service

Result: True

Comment: File /etc/avahi/services/ftp.service is not present

Started: 22:59:54.779219

Duration: 1.303 ms

Changes:

----------

ID: remove_avahi_service_nfs

Function: module.run

Result: True

Comment: file.find: []

Started: 22:59:54.782697

Duration: 2.27 ms

Changes:

----------

file.find:

----------

ID: remove_avahi_service_rsync

Function: file.absent

Name: /etc/avahi/services/rsync.service

Result: True

Comment: File /etc/avahi/services/rsync.service is not present

Started: 22:59:54.785143

Duration: 0.812 ms

Changes:

----------

ID: configure_avahi_service_smb

Function: file.managed

Name: /etc/avahi/services/smb.service

Result: True

Comment: File /etc/avahi/services/smb.service is in the correct state

Started: 22:59:54.786124

Duration: 17.67 ms

Changes:

----------

ID: configure_avahi_service_ssh

Function: file.managed

Name: /etc/avahi/services/ssh.service

Result: True

Comment: File /etc/avahi/services/ssh.service is in the correct state

Started: 22:59:54.803969

Duration: 8.956 ms

Changes:

----------

ID: configure_avahi_service_webadmin

Function: file.managed

Name: /etc/avahi/services/website.service

Result: True

Comment: File /etc/avahi/services/website.service is in the correct state

Started: 22:59:54.813078

Duration: 8.839 ms

Changes:

----------

ID: unmask_avahi_service

Function: service.unmasked

Name: avahi-daemon

Result: False

Comment: Failed to unmask service 'avahi-daemon'

Started: 22:59:54.822059

Duration: 23.621 ms

Changes:

Summary for debian

-------------

Succeeded: 13 (changed=5)

Failed: 1

-------------

Total states run: 14

Total run time: 611.681 ms

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; export LANGUAGE=; omv-salt deploy run --no-color avahi 2>&1' with exit code '1': debian:

----------

ID: mask_avahi_service

Function: service.masked

Name: avahi-daemon

Result: True

Comment: Service avahi-daemon was masked

Started: 22:59:54.225925

Duration: 268.106 ms

Changes:

----------

masked:

----------

new:

True

old:

False

----------

ID: stop_avahi_socket

Function: service.dead

Name: avahi-daemon.socket

Result: True

Comment: Service avahi-daemon.socket is already disabled, and is dead

Started: 22:59:54.494251

Duration: 69.106 ms

Changes:

----------

avahi-daemon.socket:

False

----------

ID: stop_avahi_service

Function: service.dead

Name: avahi-daemon.service

Result: True

Comment: Service avahi-daemon.service is already disabled, and is dead

Started: 22:59:54.563555

Duration: 66.64 ms

Changes:

----------

avahi-daemon.service:

False

----------

ID: configure_default_avahi_daemon

Function: file.managed

Name: /etc/default/avahi-daemon

Result: True

Comment: File /etc/default/avahi-daemon is in the correct state

Started: 22:59:54.633278

Duration: 28.266 ms

Changes:

----------

ID: divert_default_avahi_daemon

Function: omv_dpkg.divert_add

Name: /etc/default/avahi-daemon

Result: True

Comment: Leaving 'local diversion of /etc/default/avahi-daemon to /etc/default/avahi-daemon.distrib'

Started: 22:59:54.662178

Duration: 29.062 ms

Changes:

----------

ID: configure_avahi_daemon_conf

Function: file.managed

Name: /etc/avahi/avahi-daemon.conf

Result: True

Comment: File /etc/avahi/avahi-daemon.conf updated

Started: 22:59:54.691589

Duration: 57.708 ms

Changes:

----------

diff:

---

+++

@@ -7,7 +7,7 @@

#browse-domains=0pointer.de, zeroconf.org

use-ipv4=yes

use-ipv6=yes

-allow-interfaces=

+allow-interfaces=br0

#deny-interfaces=eth1

#check-response-ttl=no

#use-iff-running=no

----------

ID: divert_avahi_daemon_conf

Function: omv_dpkg.divert_add

Name: /etc/avahi/avahi-daemon.conf

Result: True

Comment: Leaving 'local diversion of /etc/avahi/avahi-daemon.conf to /etc/avahi/avahi-daemon.conf.distrib'

Started: 22:59:54.749461

Duration: 29.322 ms

Changes:

----------

ID: remove_avahi_service_ftp

Function: file.absent

Name: /etc/avahi/services/ftp.service

Result: True

Comment: File /etc/avahi/services/ftp.service is not present

Started: 22:59:54.779219

Duration: 1.303 ms

Changes:

----------

ID: remove_avahi_service_nfs

Function: module.run

Result: True

Comment: file.find: []

Started: 22:59:54.782697

Duration: 2.27 ms

Changes:

----------

file.find:

----------

ID: remove_avahi_service_rsync

Function: file.absent

Name: /etc/avahi/services/rsync.service

Result: True

Comment: File /etc/avahi/services/rsync.service is not present

Started: 22:59:54.785143

Duration: 0.812 ms

Changes:

----------

ID: configure_avahi_service_smb

Function: file.managed

Name: /etc/avahi/services/smb.service

Result: True

Comment: File /etc/avahi/services/smb.service is in the correct state

Started: 22:59:54.786124

Duration: 17.67 ms

Changes:

----------

ID: configure_avahi_service_ssh

Function: file.managed

Name: /etc/avahi/services/ssh.service

Result: True

Comment: File /etc/avahi/services/ssh.service is in the correct state

Started: 22:59:54.803969

Duration: 8.956 ms

Changes:

----------

ID: configure_avahi_service_webadmin

Function: file.managed

Name: /etc/avahi/services/website.service

Result: True

Comment: File /etc/avahi/services/website.service is in the correct state

Started: 22:59:54.813078

Duration: 8.839 ms

Changes:

----------

ID: unmask_avahi_service

Function: service.unmasked

Name: avahi-daemon

Result: False

Comment: Failed to unmask service 'avahi-daemon'

Started: 22:59:54.822059

Duration: 23.621 ms

Changes:

Summary for debian

-------------

Succeeded: 13 (changed=5)

Failed: 1

-------------

Total states run: 14

Total run time: 611.681 ms in /usr/share/php/openmediavault/system/process.inc:217

Stack trace:

#0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()

#1 /usr/share/openmediavault/engined/rpc/config.inc(170): 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/bgstatusdy...', '/tmp/bgoutputE2...')

#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))

#7 /usr/share/openmediavault/engined/rpc/config.inc(192): 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

crashtest · 30. Oktober 2022

Try the following:

sudo systemctl unmask avahi

sudo omv-salt deploy run avahi

(If no errors - to clear the yellow banner)

echo "[]" | sudo tee /var/lib/openmediavault/dirtymodules.json

votdev · 30. Oktober 2022

Can you unmask the unit manually? Run systemctl unmask avahi-daemon. Without knowing the reason why systemd can not unmask the unit, we can not make OMV running. It's not a problem of OMV by the way.

TechGuy · 1. November 2022

Thankyou both for your help, I am able to unmask the service manually with systemctl and it unmasks successfully. I can then manually start avahi through systemctl.

However when I attempt to run

omv-salt deploy run avahi

It presents the same result despite avahi being running at the time when this command was issued.

omv-salt output

votdev · 1. November 2022

The problem should be solved in the next version, see https://github.com/openmediava…9fc929c569d65b9e492dfb1e1.

kuchar · 2. November 2022

Hi, i think it is realated to my problem.

Did update after fresh installation OMV6. Can't apply changes

Spoiler anzeigen

votdev · 2. November 2022

Zitat von kuchar

Hi, i think it is realated to my problem.

Did update after fresh installation OMV6. Can't apply changes

Spoiler anzeigen

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color avahi 2>&1' with exit code '1': debian:

----------

ID: stop_avahi_socket

Function: service.dead

Name: avahi-daemon.socket

Result: False

Comment: Service avahi-daemon.socket has been disabled, and is running

Started: 13:10:16.308585

Duration: 939.742 ms

Changes:

----------

avahi-daemon.socket:

True

----------

ID: stop_avahi_service

Function: service.dead

Name: avahi-daemon.service

Result: False

Comment: Service avahi-daemon.service has been disabled, and is running

Started: 13:10:17.249310

Duration: 2206.236 ms

Changes:

----------

avahi-daemon.service:

True

----------

ID: configure_default_avahi_daemon

Function: file.managed

Name: /etc/default/avahi-daemon

Result: True

Comment: File /etc/default/avahi-daemon is in the correct state

Started: 13:10:19.466063

Duration: 140.007 ms

Changes:

----------

ID: divert_default_avahi_daemon

Function: omv_dpkg.divert_add

Name: /etc/default/avahi-daemon

Result: True

Comment: Leaving 'local diversion of /etc/default/avahi-daemon to /etc/default/avahi-daemon.distrib'

Started: 13:10:19.608172

Duration: 38.8 ms

Changes:

----------

ID: configure_avahi_daemon_conf

Function: file.managed

Name: /etc/avahi/avahi-daemon.conf

Result: True

Comment: File /etc/avahi/avahi-daemon.conf is in the correct state

Started: 13:10:19.648018

Duration: 186.402 ms

Changes:

----------

ID: divert_avahi_daemon_conf

Function: omv_dpkg.divert_add

Name: /etc/avahi/avahi-daemon.conf

Result: True

Comment: Leaving 'local diversion of /etc/avahi/avahi-daemon.conf to /etc/avahi/avahi-daemon.conf.distrib'

Started: 13:10:19.834941

Duration: 39.889 ms

Changes:

----------

ID: remove_avahi_service_ftp

Function: file.absent

Name: /etc/avahi/services/ftp.service

Result: True

Comment: File /etc/avahi/services/ftp.service is not present

Started: 13:10:19.875853

Duration: 2.867 ms

Changes:

----------

ID: remove_avahi_service_nfs

Function: module.run

Result: True

Comment: file.find: []

Started: 13:10:19.883359

Duration: 8.574 ms

Changes:

----------

file.find:

----------

ID: remove_avahi_service_rsync

Function: file.absent

Name: /etc/avahi/services/rsync.service

Result: True

Comment: File /etc/avahi/services/rsync.service is not present

Started: 13:10:19.892386

Duration: 1.955 ms

Changes:

----------

ID: remove_avahi_service_smb

Function: file.absent

Name: /etc/avahi/services/smb.service

Result: True

Comment: File /etc/avahi/services/smb.service is not present

Started: 13:10:19.894712

Duration: 1.602 ms

Changes:

----------

ID: configure_avahi_service_ssh

Function: file.managed

Name: /etc/avahi/services/ssh.service

Result: True

Comment: File /etc/avahi/services/ssh.service is in the correct state

Started: 13:10:19.896746

Duration: 30.418 ms

Changes:

----------

ID: configure_avahi_service_webadmin

Function: file.managed

Name: /etc/avahi/services/website.service

Result: True

Comment: File /etc/avahi/services/website.service is in the correct state

Started: 13:10:19.927626

Duration: 32.148 ms

Changes:

----------

ID: start_avahi_socket

Function: service.running

Name: avahi-daemon.socket

Result: True

Comment: Service avahi-daemon.socket has been enabled, and is in the desired state

Started: 13:10:19.960291

Duration: 781.33 ms

Changes:

----------

avahi-daemon.socket:

True

----------

ID: start_avahi_service

Function: service.running

Name: avahi-daemon.service

Result: True

Comment: Service avahi-daemon.service has been enabled, and is in the desired state

Started: 13:10:20.742588

Duration: 2639.908 ms

Changes:

----------

avahi-daemon.service:

True

Summary for debian

-------------

Succeeded: 12 (changed=5)

Failed: 2

-------------

Total states run: 14

Total run time: 7.050 s

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; export LANGUAGE=; omv-salt deploy run --no-color avahi 2>&1' with exit code '1': debian:

----------

ID: stop_avahi_socket

Function: service.dead

Name: avahi-daemon.socket

Result: False

Comment: Service avahi-daemon.socket has been disabled, and is running

Started: 13:10:16.308585

Duration: 939.742 ms

Changes:

----------

avahi-daemon.socket:

True

----------

ID: stop_avahi_service

Function: service.dead

Name: avahi-daemon.service

Result: False

Comment: Service avahi-daemon.service has been disabled, and is running

Started: 13:10:17.249310

Duration: 2206.236 ms

Changes:

----------

avahi-daemon.service:

True

----------

ID: configure_default_avahi_daemon

Function: file.managed

Name: /etc/default/avahi-daemon

Result: True

Comment: File /etc/default/avahi-daemon is in the correct state

Started: 13:10:19.466063

Duration: 140.007 ms

Changes:

----------

ID: divert_default_avahi_daemon

Function: omv_dpkg.divert_add

Name: /etc/default/avahi-daemon

Result: True

Comment: Leaving 'local diversion of /etc/default/avahi-daemon to /etc/default/avahi-daemon.distrib'

Started: 13:10:19.608172

Duration: 38.8 ms

Changes:

----------

ID: configure_avahi_daemon_conf

Function: file.managed

Name: /etc/avahi/avahi-daemon.conf

Result: True

Comment: File /etc/avahi/avahi-daemon.conf is in the correct state

Started: 13:10:19.648018

Duration: 186.402 ms

Changes:

----------

ID: divert_avahi_daemon_conf

Function: omv_dpkg.divert_add

Name: /etc/avahi/avahi-daemon.conf

Result: True

Comment: Leaving 'local diversion of /etc/avahi/avahi-daemon.conf to /etc/avahi/avahi-daemon.conf.distrib'

Started: 13:10:19.834941

Duration: 39.889 ms

Changes:

----------

ID: remove_avahi_service_ftp

Function: file.absent

Name: /etc/avahi/services/ftp.service

Result: True

Comment: File /etc/avahi/services/ftp.service is not present

Started: 13:10:19.875853

Duration: 2.867 ms

Changes:

----------

ID: remove_avahi_service_nfs

Function: module.run

Result: True

Comment: file.find: []

Started: 13:10:19.883359

Duration: 8.574 ms

Changes:

----------

file.find:

----------

ID: remove_avahi_service_rsync

Function: file.absent

Name: /etc/avahi/services/rsync.service

Result: True

Comment: File /etc/avahi/services/rsync.service is not present

Started: 13:10:19.892386

Duration: 1.955 ms

Changes:

----------

ID: remove_avahi_service_smb

Function: file.absent

Name: /etc/avahi/services/smb.service

Result: True

Comment: File /etc/avahi/services/smb.service is not present

Started: 13:10:19.894712

Duration: 1.602 ms

Changes:

----------

ID: configure_avahi_service_ssh

Function: file.managed

Name: /etc/avahi/services/ssh.service

Result: True

Comment: File /etc/avahi/services/ssh.service is in the correct state

Started: 13:10:19.896746

Duration: 30.418 ms

Changes:

----------

ID: configure_avahi_service_webadmin

Function: file.managed

Name: /etc/avahi/services/website.service

Result: True

Comment: File /etc/avahi/services/website.service is in the correct state

Started: 13:10:19.927626

Duration: 32.148 ms

Changes:

----------

ID: start_avahi_socket

Function: service.running

Name: avahi-daemon.socket

Result: True

Comment: Service avahi-daemon.socket has been enabled, and is in the desired state

Started: 13:10:19.960291

Duration: 781.33 ms

Changes:

----------

avahi-daemon.socket:

True

----------

ID: start_avahi_service

Function: service.running

Name: avahi-daemon.service

Result: True

Comment: Service avahi-daemon.service has been enabled, and is in the desired state

Started: 13:10:20.742588

Duration: 2639.908 ms

Changes:

----------

avahi-daemon.service:

True

Summary for debian

-------------

Succeeded: 12 (changed=5)

Failed: 2

-------------

Total states run: 14

Total run time: 7.050 s in /usr/share/php/openmediavault/system/process.inc:217

Stack trace:

#0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()

#1 /usr/share/openmediavault/engined/rpc/config.inc(170): 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/bgstatusaR...', '/tmp/bgoutputaf...')

#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))

#7 /usr/share/openmediavault/engined/rpc/config.inc(192): 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

This is a different problem. In your case systemd fails to stop the service. Don't know why. Can you do it manually? systemd stop avahi-daemon.socket

kuchar · 2. November 2022

yes, i can but it didn't help. After stopping it just start

votdev · 2. November 2022

Zitat von kuchar

yes, i can but it didn't help. After stopping it just start

Have you stopped systemd stop avahi-daemon.service or systemd stop avahi-daemon.socket. Both need to be stopped finally.

kuchar · 2. November 2022

I have stopped both. Same result. Both starting after stopping them.

votdev · 2. November 2022

Hmmm, i think this is why i masked the service in the Salt files. I've removed that because of a different error where Salt was not able to unmask the service. See https://github.com/openmediava…9fc929c569d65b9e492dfb1e1. Seems we now have a chicken-egg problem.

votdev · 2. November 2022

What i do not understand is why the service is started again, even if the socket is disabled. What and how is activating the service. I mentioned DBUS in the origin source code, but even this can't enable the service magically. Any ideas?

kuchar · 2. November 2022

Zitat von votdev

Have you stopped systemd stop avahi-daemon.service or systemd stop avahi-daemon.socket. Both need to be stopped finally.

i have used systemctl stop avahi-daemon.socket and systemctl stop avahi-daemon.service.

systemd didn't work - it print Excess arguments.

After checking systemctl status avahi-daemon.socket it was running.

EDIT: It worked after command systemctl disable avah-daemon.service and then appy changes in WebUI. Any ideas?

EDIT2: Maybe is something with upgrade from omv 6.0.24?

after fresh start and then omv-upgrade is something linke

Code

.....

Created symlink /etc/systemd/system/systemd-timesyncd.service -> /dev/null.
Creating configuration database ...
Migrating configuration database ...
  Running migration conf_6.0.31
Setting up Salt environment ...
[ERROR   ] Command '/usr/bin/patch' failed with return code: 1
[ERROR   ] stdout: patching file /tmp/__salt.tmp.hmbwa22j (read from /lib/python3/dist-packages/salt/fileserver/roots.py)
Reversed (or previously applied) patch detected!  Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file /tmp/__salt.tmp.v_eohf50
[ERROR   ] retcode: 1
Processing system modifications ...
Processing triggers for initramfs-tools (0.140) ...

....

Alles anzeigen

votdev · 2. November 2022

Could you please try it again with openmediavault 6.0.46-3 and report if changing the order of disabling the service helped?

Old_Engineer · 2. November 2022

Zitat von kuchar

I have stopped both. Same result. Both starting after stopping them.

Same problem here after upgrading, no configuration changes possible.

kuchar · 2. November 2022

Zitat von votdev

Could you please try it again with openmediavault 6.0.46-3 and report if changing the order of disabling the service helped?

What do you want me to do? Do a fresh install or what? I have backup after fresh install. I can easly restore from backup.

votdev · 2. November 2022

Zitat von kuchar

What do you want me to do? Do a fresh install or what? I have backup after fresh install. I can easly restore from backup.

Simply install the latest update and run omv-salt deploy run avahi or press the apply button in the UI.

kuchar · 2. November 2022

I did a fresh install because i have already solved my problem by typing systemctl disable avahi-daemon.service and then apply changes.

So.... after very fresh install OMV 6.0.24 from iso file and update it via CLI apt update && apt upgrade -y same error occurs.

votdev · 2. November 2022

I know, it fails again in 6.0.46-3. I'll revert everything to the state where no problems arise since years except this initial post here.

kuchar · 2. November 2022

Did fresh install again. Waiting to test from scratch.

OMV-Salt failed to unmask avahi-daemon

Jetzt mitmachen!

Tags