Apply changes in GUI takes a very long time.

Quote from striscio

My system is on a Xeon processor, 32 Gb RAM and a ssd disk.

It's not apt commands or kernel module building that are very slow, but the various salt command at the end of the update process.

To be clearer, it's when I have the "Pending changes" notification in the GUI or, when I use the cli, the various salt passages after the packages are installed.

This morning I had two packages to be installed (openmediavault and openmediavault-nut).

I edited /etc/salt/minion file and I added debug log.

I also added another option that helped when I had the same problem in the past which is

Code

enable_fqdns_grains: False

This time the update took a reasonable amount of time (under a minute).

Code

# time omv-upgrade

real    0m54.915s
user    0m21.385s
sys    0m5.316s

thanks.

Display More

Disabling grains is not a good idea because hostname is used e.g. when postfix is deployed. You should do a omv-salt deploy run systemd-networkd hosts. There were some changes in resolving DNS info, so every getaddr is now much faster which speeds up Salt startup process.

Quote from striscio

I tried your command and my server become unreachable. Luckily I have kvm interface and I connected through that and I see that my network interfaces are down. I tried to reissue your command and I got this (sorry for the jpeg but I couldn't copy and paste from the kvm app).ù

I also tried omv-firstaid to reconfigure at least one of the two network interfaces but I still have the error.

Now I'm stuck...

Just a little update: I rebooted and the first interface I reconfigured with omv-firstaid came up correctly.

I re-run the omv-salt command you suggested and I still get errors (see the second error screenshot)

Another update: the web interface gave me some pending configuration changes.

So I checked the dirtymodules.json

Code

root@omv:~# cat /var/lib/openmediavault/dirtymodules.json 
[
    "nut",
    "avahi",
    "collectd",
    "halt",
    "hosts",
    "issue",
    "systemd-networkd",
    "task"

So I issued a

Code

omv-salt deploy run nut avahi collectd halt issue systemd-networkd hosts 

I had another netplan error and my interface went offline again... I rebooted through KVM and I ran the single modules

I tried and succeded with nut, avahi, collectd, halt, issue, hosts.

I tried with 'task' and I had ERROR: The state 'task' does not exist

I tried finally with systemd-networkd and it took waaaay longer than the other modules. My network interface went down again and I had to reboot through the KVM console to have my server back online.

Last resort: I configured my network interface through the web interface and gave it a static address. Every config update that was pending in the interface ran successfully. I even tried to re-run your omv-salt deploy run hosts systemd-networkd: it succeeded and completed in a short amount of time.

Than I configured my bridge interface on the second network adapter. and it seems ok. Let's wait and see.

Is there a reason why configuring the network adapter through omv-firstaid led to a netplan error?

Sorry for the long post but I really would want to fix this.

Display More

Maybe https://www.openmediavault.org/?p=3492 is the reason.