500 - Internal Server Error Failed to execute command - omv-salt deploy run --no-color postfix

  • Recently during user creation this error popped out, it should not be related to users since it's a postfix but this error is showing every time I change anything in OMV and I want to apply settings:

    Code: error message
    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=; omv-salt deploy run --no-color postfix 2>&1' with exit code '1': xlvmopmv: Data failed to compile: ---------- Cannot extend ID 'start_postfix_service' in 'base:omv.deploy.postfix.90cron'. It is not part of the high state. This is likely due to a missing include statement or an incorrectly typed ID. Ensure that a state with an ID of 'start_postfix_service' is available in environment 'base' and to SLS 'omv.deploy.postfix.90cron' 


    Edited once, last by foklan: added salt version ().

    • Official Post

    Recently during user creation this error popped out, it should not be related to users since it's a postfix but this error is showing every time I change anything in OMV and I want to apply settings:

    Code: error message
    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=; omv-salt deploy run --no-color postfix 2>&1' with exit code '1': xlvmopmv: Data failed to compile: ---------- Cannot extend ID 'start_postfix_service' in 'base:omv.deploy.postfix.90cron'. It is not part of the high state. This is likely due to a missing include statement or an incorrectly typed ID. Ensure that a state with an ID of 'start_postfix_service' is available in environment 'base' and to SLS 'omv.deploy.postfix.90cron' 

    This error only occurs if you are running a Salt version > 3003. See my bug report https://github.com/saltstack/s…21#issuecomment-951782987.


    I assume you've upgraded Salt manually via PIP (which is not supported because it breaks things). You need to undo that to fix the problem.

  • Actually I don't even have pip installed on my system, the only thing I did with salt-minion was that I connected it to my salt-master.
    I really don't know where that version came from, it's actually quite fresh installation of OMV so I assumed that this version came with it.

  • I tried to create new installation from openmediavault_6.0.24-amd64.iso and I can confirm, that this installation contains salt version 3003+ds-1.

    On my previous installation I had 3004.2+ds-1 and I wasn't able to downgrade it (I really don't know where it come from).

    When I tried to downgrade the salt-common package It went really bad as it uninstalled many other packages:

    It looks like I have to do clean installation of OMV.

  • I encountered the same error.

    I confirm that I did not install pip either and had no reason to update salt.


    However:

    Code
    # dpkg -l | grep salt
    ii  salt-common                        3006.0+ds-1+240.1                       all          shared libraries that salt requires for all packages
    ii  salt-minion                        3006.0+ds-1+240.1                       all          client package for salt, the distributed remote execution system




    Is it possible that it was updated through some update procedure such as apt?


    Edit

    it came from: http://packages.openmediavault…ain/binary-amd64/Packages

    found in /etc/apt/sources.list.d/openmediavault.list

    deb [signed-by=/usr/share/keyrings/openmediavault-archive-keyring.gpg] http://packages.openmediavault.org/public/ sandworm main




    Thank you,

    Riccardo

  • Can I ask what is needed to fix this? After trying to install a new hard drive, I'm getting a similar error trying to apply pending changes to the Filesystem and can't get past it.


    Looks like I have salt version 3006.0+ds-1+240.1 installed.

  • Hi, i'm also getting a similar error i suppose, see below:


    In the repo there is no other salt-common packages.

    • Official Post

    Hi, i'm also getting a similar error i suppose, see below:

    If it was after a recent update, check out this thread.

Participate now!

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