Tell me how to fix it
In OMV6 web ui, System, omv-extras, Setting, click apt clean.
Then go to System, Plugins, search for kvm, select openmediavault-kvm 6.1.23, click Install to re-installed KVM plugin.
This worked for me.
Posts by RonO
-
-
Did an apt clean in omv-extras, then re-installed KVM with no issues. VMs are back up and running.
Same here.
Thanks ryecoaaron
-
have a working system
omv6 is working at present, as for updates, none are showing to know if updating works, should there be any updates available?
The Save and Apply changes in the web ui issue is not happening at present.
I have all of the usual containers up and running at present, without issue.
The only thing that is not configured yet is the Adguardhome instance is not being used as the dns server.
All appears working ok.
Today I'll do the testing of the Adguardhome instance being used as the dns server.
-
I don't think a container would cause a problem unless it was blocking a port of something in OMV. What containers are you running?
Your output looks like backports are disabled. Shouldn't be hard to fix.I'm only going on anecdotal evidence, it's all I got at present. The list of containers, of what was running during the "Apply changes" issue is below;
media servers, plex, jellyfin (plex still running now with no problems, jellyfin is not starting for some reason, another thing to fix!)
netdata, server monitoring dashboard (still running now with no problems)
guacamole, made up of guacamole/guacamole, guacamole/guacd & guaca-mysql (still running now with no problems)
dozzle, real time docker container log file viewer (still running now with no problems)
various rclone browser containers being tested (none were running during the issue) (shutdown at present)
speedtest, hourly internet speed test (shutdown at present)
adguardhome, running a macvlan, used as the dns server for lan (running during issue, shutdown at present)
nagios, server log viewer (not running during the issue, shutdown at present)
watchyourlan, compiles a list of devices on lan (may have been running during issue, shutdown at present)
I think the most likely container is adguardhome (and this is my most important one, dns blocking/filtering and device blocking)
omv, System, omv-extras, Settings, Testing repo disabled, Backports enabled
omv, System, Update Management, Settings, Pre-release updates disabled, Community-maintained updates enabled
The Debian backports repos had some packages removed. That is causing this problem. hopefully they are replaced.
Is this a wait and see what happens thing? No kvm plugin until this is resolved?
Want to do the zerotier thing again?
-
No idea what is causing this.
I think I've isolated the problem to being a docker container.
Tried the old "Get back to basics", stopped all docker containers and rebooted omv, and Apply changes completes in just several seconds now.
Now it's trial and error method to start each container one at a time to see which container causes the omv Apply changes issue.
But
18 updates appeared in omv, so I thought do the updates, get that out of the way (a kvm plugin update was amongst the list of updates).
Rebooted, just to make sure all was running ok in the server.
Noticed the kvm plugin missing from omv Services list, hmm, try installing the plugin again.
When selecting openmediavault-kvm 6.1.23 in System, Plugins and install, I now get an error ending in "you have held broken packages".
Full error message in attached kvm-plugin-install-error.txt
Where do I go from here?
Might I have endd up with a rogue process from a docker container?
Nearly at the end of the line for omv and me...
-
What is the output of: time sudo /usr/bin/salt-call -l debug --local saltutil.sync_grains
See attached time.txt
Ran the above, run time = 1:25 minutes, same as real in text file.
I hope there are some clues.
-
This is still unreleased, right?
Correct. Still on 6.0.40-2 here. Haven't seen any update from this version.
A bit of useless trivia for you, sorry I'm no help!
PS. Sorry I've cluttered your thread with my sh$%!
-
/usr/bin/salt-call --local saltutil.clear_cache
Ran the above, run time = 1:23 minutes, output below
local:
True
Next I done a test of a "Disable Rsync task, Save, Apply changes", run time = 3:00 minutes then got runtime error, (sorry missed copying displayed error, think it was run time error 500).
omv-salt stage run prepare
Ran the above, run time = 9:00 minutes, output in attached omv-salt stage run prepare.txt
I was going to abort this test at 10 minutes, it just made it in ha.
cat /var/lib/openmediavault/dirtymodules.json output = none still.
Rebooted omv6
Next I done a test of a "Disable Rsync task, Save, Apply changes", run time = 2:32 minutes to Apply changes
Open WeTTY as root
Next /usr/bin/salt-call --local saltutil.clear_cache, run time = 1:20 minutes to complete, output local: True
Next omv-salt stage run prepare, run time = 7:44 minutes to complete, output see attached omv-salt stage run prepare 2.txt
Next cat /var/lib/openmediavault/dirtymodules.json output = none still.
Next Enable Rsync task, Save
Next cat /var/lib/openmediavault/dirtymodules.json output = "rsync"
Next Apply changes, run time = 2:31 minutes to Apply changes completion.
Next cat /var/lib/openmediavault/dirtymodules.json output = none
-
That was fast. How about this:
sudo omv-salt deploy run nginx phpfpmI timed this run, 3:03 minutes in total, but omv-salt deploy run nginx phpfpm output total time = 2.401 s, huh!
Previous omv-salt deploy run hostname run was about 3 minutes also.
These are run from the WeTTY plugin cli, logged in as root.
See attached omv-salt deploy run nginx phpfpm.txt
I have to go out, catch u tomorrow Aaron, thanks for all this help, very very much appreciated.
-
What about:
omv6 was at a state of no changes made/saved and Apply bar not showing
sudo omv-salt deploy run hostname
debian:
----------
ID: configure_hostname
Function: cmd.run
Name: hostnamectl set-hostname "naso"
Result: True
Comment: unless condition is true
Started: 09:58:50.552618
Duration: 828.226 ms
Changes:
Summary for debian
------------
Succeeded: 1
Failed: 0
------------
Total states run: 1
Total run time: 828.226 ms
-
oops, we crossed timing of your reply and my post #69 edit, my bad, sorry
Make change.
Save Change. Don't click Apply
cat /var/lib/openmediavault/dirtymodules.json
Apply Change
This was the sequence I used, correct me if I'm wrong here (brain is very foggy, had flu for 2 weeks).
-
I need to see the output before you click apply
I'm not exactly sure what you mean ryecoaaron
I used cat /var/lib/openmediavault/dirtymodules.json command 3 times,
1. before any change (no apply bar showing), output of cat none
2. after a change is saved, ie rsync task, disable, save (apply bar showing), output of cat "rsync"
3. after Apply changes finished (no apply bar showing), output of cat none.
Is there another sequence I should do this ?
-
output of: cat /var/lib/openmediavault/dirtymodules.json
Output before any change: empty
Output after disabling Rsync task: "rsync"
Apply changes duration = 2:30 minutes
Output after Apply changes: empty
That's not normal is it?
-
My install of omv 6.0.40-2 takes 3 minutes to Apply changes, is that normal?
This is even for a single change like enable/disable Rysync task.
-
What is the error?
In a red message box (bottom center of web ui) is displayed the following
500 - Internal Server Error
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=; systemctl restart srv-mergerfs-mfsp.mount' with exit code '1':
I had lan connected pc's with file managers viewing parts of the shares, and highly probable that there were open files also.
create sharedfolders in the OMV web interface
Yes, shares were created via web ui
What you do outside of OMV will never be known to the plugin.
I'll keep that in mind.
-
Q1. In omv6, Storage, mergerfs, when a mergerfs pool is marked as shared, can the Restart pool be used? It produces an error for me.
Q2. Is mergerfs a pool marked as Shared if there are defined shares within the pool? I have not shared the pool itself, just made shares on dirs within the mergerfs pool.
-
remove systemd-networkd from /var/lib/openmediavault/dirtymodules.json
That fixed it, thank you Aaron.
Just recalled there was also another error message being displayed on the server monitor when the "Apply Pending configuration changes" first appeared.
It was about a duplicate entry in the fstab, the boot drive uuid was entered twice, I edited the fstab by removing the duplicate in the "openmediavualt section", server stopped displaying the error then, and the network would stay up continuously.
OMV 6 seems fragile compared to OMV 5, or am I just having a bad run with it while ironing out the bugs!
-
Were you changing a network setting?
No network changes made since installing omv6 a few weeks ago, (sometime later I will create a br0 for kvm, but not yet).
The only thing I recall doing prior to noticing the "Apply Pending configuration changes", was a cli apt update && apt upgrade and trialing some rclonebrowser/rclonewebui containers in portainer.
-
Hi, not sure where to start with this issue, any help would be greatly appreciated.
I'm having a similar issue with "Apply Pending configuration changes". When Apply is clicked the whole server losses the network and goes off line. A reboot gets the server back on the lan, but "Apply Pending configuration changes" is still there.
Hopefully the attached files may help.
-
So there won't be any logs outside of the VM. What distro is it?
vm Distro = LinuxMint 20.3
Desktop = XFCE
Been looking through the journal log with journal -b -r
But no nothing about kvm exiting hardware virtualization
After several forced shutdowns the vm can now shutdown correctly, don't know what changed to fix that.
But Restart / Reboot still hangs. It''l just have to stay like that.
