Alles anzeigenJust for the Record:
gderf and jofen, you had updated previously from OMV5, correct?
Strange that the issue only showed with the latest update from 6.0.20 to 6.0.21.
Or maybe it was already there and you hadn't spotted it?!?
Nice to see a solution, at least, 👍
I thought the upgrade to 6.0.21 broke it but after looking into it further by running a backup of 6.0.19 it was broken there too but I hadn't noticed it.
The upgrade from 5 to 6 sets the divert on this file.
I upgraded from 5 to 6 quite some time ago and this problem did not happen then. I wonder what triggered it later?
I upgraded from OMV5 to 6.0.27-1 today and had the same problem with the Plugins page not displaying the plugins, despite them being on the system, until I ran as recommended in this thread:
/usr/sbin/omv-mkaptidx
dpkg-divert --remove --rename /usr/sbin/omv-mkaptidx
omv-mkaptidxAll working now 
thank you all
Thank you,
That helped me too to solve my plugins issue.
Alles anzeigenjofen you are still suffering from a unsuccesful upgrade.
Use this script or
try
rm -f /usr/sbin/omv-mkaptidx
dpkg-divert --remove --rename /usr/sbin/omv-mkaptidx
omv-mkaptidx
How do we get this fix made a part of the upgrade process? This killed me for MONTHS after my OMV6 upgrade.
How do we get this fix made a part of the upgrade process?
It doesn't happen on most upgrade and is hard to detect especially in bash.
This killed me for MONTHS after my OMV6 upgrade.
How did it kill you? It would only prevent installing new plugins from the web interface.
It doesn't happen on most upgrade and is hard to detect especially in bash.
How did it kill you? It would only prevent installing new plugins from the web interface.
The upgrade messed with omvextras. I could not reinstall it. I was using LUKS and therefore could not mount the volume once I upgraded. It was a major pain and it would have been helpful for this step to be part of the upgrade process; as it seems non destructive, couldn't it be run regardless of detection?
The upgrade messed with omvextras
The only thing it did is cause plugins to not show up in the web interface. You would have no problem installing omv-extras and omv-extras plugins from the command line. Since omv-extras can only be installed from the command line in OMV 6, this shouldn't have cause months of problems.
it would have been helpful for this step to be part of the upgrade process; as it seems non destructive, couldn't it be run regardless of detection?
Sure but it doesn't always fix the problem. If the upgrade fails before the divert, the file is overwritten by the upgrade process. So, running the divert command won't fix anything. That is why you will see many of my posts telling people to wget the file from the omv source code to fix. Running the wget from the upgrade script would be gross since it doesn't take into account any versioning. The upgrade process is a command line process and if it doesn't go smoothly, it is going to require command line fixes. No way around it.
I really have no idea, the JSON files look all good. Are there any errors reported by the browser when you activate the browser dev tools. In FireFox the relevant tab is called 'Console'.
In my case the console gets almost stuck because it spams over and over again the same error:
TypeError: t.pluginarchitecture is undefined
Alles anzeigenjofen you are still suffering from a unsuccesful upgrade.
Use this script or
try
rm -f /usr/sbin/omv-mkaptidx
dpkg-divert --remove --rename /usr/sbin/omv-mkaptidx
omv-mkaptidx
thanks... it works
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
