Please wait ... Apply configuration changes

  • If you are using OMV 5.x, it does take considerably longer to apply changes especially on slower systems. Refreshing the page doesn't mean the config change is done.

    omv 5.5.17-3 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.4.2
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • I am using 4.1.27-1 according to the system information page. My system shouldn't be too slow.

    If you have a large amount of filesystems, it can take a long time too.


    On another note, should I be upgrading to 5.x?

    Depends. If your Linux skills are solid, I think it is a good upgrade but I would install fresh over upgrading. There is no OMV provided upgrade path. So, you will have to manually upgrade OMV stuff.

    omv 5.5.17-3 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.4.2
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • If you have a large amount of filesystems, it can take a long time too.

    That would make sense I guess since I'm using about 26 disks now. Thanks for letting me know!




    Depends. If your Linux skills are solid, I think it is a good upgrade but I would install fresh over upgrading. There is no OMV provided upgrade path. So, you will have to manually upgrade OMV stuff.

    Is there an improvements or additions changelog in 5? Everything is working quite nicely for me right now, but I'm always interested in newer/better things. If there's not too much different, I'll probably stay as is for a while :D. Thank you for the information.

  • Looks like the problem is related to this script:


    /usr/lib/python3/dist-packages/salt/utils/decorators/__init__.py


    that calls to a function that has a bug in "salt" automation tool (using strace you can see lots of errors when applying changes).


    I have edited that file and I have added this:


    return function


    in line 101.


    So now it looks like this:


    return function

    frame = inspect.stack()[1][0]


    In this way the function "__call__(self, function)" does not execute the "inspect.stack" function, that has some kind of bug and it takes too much time to finish.


    I know that in this way the module and function name are not stored in the class wide dependency_dict but I am not noticing a big problem with that and now I can "Apply" changes faster than before without apparently major problems.


    Hope it helps (until someone could find a better fix).

    Regards

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!