Samba

    • OMV 5.x (beta)
    • Resolved
    • I'm testing OMV5 on proxmox... when I go to enable Samba I get the following message-error:

      Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run avahi 2>&1' with exit code '1': /usr/lib/python3/dist-packages/salt/modules/file.py:32: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working from collections import Iterable, Mapping /usr/lib/python3/dist-packages/salt/utils/decorators/signature.py:31: DeprecationWarning: `formatargspec` is deprecated since Python 3.5. Use `signature` and the `Signature` object directly *salt.utils.args.get_function_argspec(original_function) /usr/lib/python3/dist-packages/salt/utils/decorators/signature.py:31: DeprecationWarning: `formatargspec` is deprecated since Python 3.5. Use `signature` and the `Signature` object directly *salt.utils.args.get_function_argspec(original_function) debian: Data failed to compile: ---------- Rendering SLS 'base:omv.deploy.avahi.services.nfs' failed: Jinja variable 'salt.utils.templates.AliasedLoader object' has no attribute 'omv_conf.get' ---------- Rendering SLS 'base:omv.deploy.avahi.services.smb' failed: Jinja variable 'salt.utils.templates.AliasedLoader object' has no attribute 'omv_conf.get' ---------- Rendering SLS 'base:omv.deploy.avahi.services.ftp' failed: Jinja variable 'salt.utils.templates.AliasedLoader object' has no attribute 'omv_conf.get' ---------- Rendering SLS 'base:omv.deploy.avahi.services.ssh' failed: Jinja variable 'salt.utils.templates.AliasedLoader object' has no attribute 'omv_conf.get' ---------- Rendering SLS 'base:omv.deploy.avahi.services.rsync' failed: Jinja variable 'salt.utils.templates.AliasedLoader object' has no attribute 'omv_conf.get' ---------- Rendering SLS 'base:omv.deploy.avahi.services.webadmin' failed: Jinja variable 'salt.utils.templates.AliasedLoader object' has no attribute 'omv_conf.get'
    • This is probably caused by the apt clean button clearing the salt cache using:

      salt-call --local saltutil.clear_cache

      I have found the following command fixes the issue but I need to verify with @votdev that it is the proper thing to do:

      sudo salt-call --local --retcode-passthrough --no-color state.orchestrate omv.stage.prepare
      omv 4.1.23 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      This is probably caused by the apt clean button clearing the salt cache using:

      salt-call --local saltutil.clear_cache

      I have found the following command fixes the issue but I need to verify with @votdev that it is the proper thing to do:

      sudo salt-call --local --retcode-passthrough --no-color state.orchestrate omv.stage.prepare
      Don't know what your intention is in clearing the cache, but it seems this will remove the sync'd modules. So you need to run at least


      Shell-Script

      1. # salt-call saltutil.sync_modules

      to fix that. Alternatively use

      Shell-Script

      1. # omv-salt stage run prepare
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • votdev wrote:

      Don't know what your intention is in clearing the cache, but it seems this will remove the sync'd modules
      While porting the plugins, I have noticed numerous times that the salt cache does not update after installing a plugin. This might just be something I see while installing them. So, I will probably just remove the line from omv-extras. Thanks for the tips though.
      omv 4.1.23 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

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