update of openmediavault-compose complains about omv-compose-term.service not found

  • Hello,

    today I installed a pending update of openmediavault-compose. Later in the GUI I was asked to apply the changes, but I got an error.

    The mentioned file is not there. Locate has that file still listed under /usr/lib/systemd/system/omv-compose-term.service.

    I am also not able to remove the package manually as a pre-removal-Skript is failing too.

    Edited once, last by bermuda ().

  • I was able to solve my issue, by manually altering the pre-removal-Skript, so it would not give an error.

    Since the service file was not there anymore, this would not brake anything anyway.

    • Official Post

    Did you have the test version installed prior? There is nothing in the pre-removal script about the unit file that should cause a failure. What did you remove? The older versions of the plugin used to install the service from the debian package. The newer versions create and remove it from saltstack. It seems like you had the older version.

    omv 8.0.10-2 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.6 | compose 8.1.3 | cterm 8.0 | borgbackup 8.1.5 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    Edited once, last by ryecoaaron ().

  • Yes, I tried the test version, because I often have to attach to my containers. And since it was removed from testing I had no way back to remove it. During update today morning there was no error. I decided to manually override the script and do a reinstall.

    • Official Post

    And since it was removed from testing I had no way back to remove it.

    I don't know why that has anything to do with removing it. You don't need the .deb file to remove the package.


    During update today morning there was no error. I decided to manually override the script and do a reinstall.

    I don't think this will be a problem going forward. You just had an old testing version in a weird state. I've upgraded 5 systems that never had the testing version installed and had no issues.

    omv 8.0.10-2 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.6 | compose 8.1.3 | cterm 8.0 | borgbackup 8.1.5 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • I just wanted to go to the previous state with the service-file, do a clean uninstall (probably purge too) and a reinstall with the newer version.

    But as I said, by tweaking the script I was able to uninstall the package and do a clean reinstall and the error was gone.

  • I was running the last test version and updated this more with no errors.

    OMV Version 8.latest | AMD Ryzen 5600G with 64GB | JBOD EXT4 & BRTFS

    Various Unifi router & switches | Only Linux laptops and PC's

  • I was running the last test version and updated this more with no errors.

    My update went also with no errors. But when I logged in and had to apply the changes, it gave me an error.

    Can't tell anyone more than that. But all is working now, since I was finally able to purge the package and reinstall.

    • Official Post

    But when I logged in and had to apply the changes, it gave me an error.

    Can't tell anyone more than that.

    There really is no need to worry about. Only a handful of people had the test version installed. They would've had to still had the version installed that let the debian package create the unit file. So, no one else should have the problem.

    omv 8.0.10-2 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.6 | compose 8.1.3 | cterm 8.0 | borgbackup 8.1.5 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Oh, by the way ... syntax highlighting in Dockerfile doesn't work anymore. It highlights only the first comment but that's it. This has been broken for some time. I know it was working under OMV6.

    • Official Post

    syntax highlighting in Dockerfile doesn't work anymore. It highlights only the first comment but that's it. This has been broken for some time. I know it was working under OMV6.

    Really, you were just lucky that it ever worked. The code editor component that OMV supplies only has the following code types:
    'json' | 'python' | 'shell' | 'xml' | 'yaml' | 'none'


    It is set to shell. https://github.com/OpenMediaVa…rfiles-form-page.yaml#L37


    So, there is nothing I can do to "fix" it.

    omv 8.0.10-2 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.6 | compose 8.1.3 | cterm 8.0 | borgbackup 8.1.5 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Thanks, I see.

    Just figured out by accident that an indent by a blank space makes it work again. So it's not a total loss :)

Participate now!

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