Rsync server not running with OMV5beta

    • OMV 5.x (development)
    • Resolved

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • I'm seeing an error in the salt module for rsyncd but I don't see why it is failing. The default.sls file looks fine to me. @votdev

      Display Spoiler

      # omv-salt deploy run rsyncd
      /usr/lib/python3/dist-packages/salt/utils/path.py:265: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working
      if not isinstance(exes, collections.Iterable):
      /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.rsyncd.default' failed: Jinja variable 'salt.utils.templates.AliasedLoader object' has no attribute 'omv_conf.get'

      omv 4.1.22 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!
    • Can not reproduce this with latest master.
      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:

      Can not reproduce this with latest master.
      I can confirm that updating to the latest git fixes the issue.
      omv 4.1.22 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:

      votdev wrote:

      Can not reproduce this with latest master.
      I can confirm that updating to the latest git fixes the issue.

      ryecoaaron wrote:

      I can confirm that updating to the latest git fixes the issue.
      Well, on my PC this problem persists even after having reinstalled the image dated Apr. 19 and immediately updating through "Update management". Rsync can be enabled without any error message, but it does not run - either with modules or without modules. Is there anywhere I might look for a log on rsync? SSH (and CIFS for that matter) work nicely. Enabling FTP gives long error message by the way. See ftp section. Seems a bit more work will be required on OMV5.
    • Debian Buster is not released nor stable, so expect bugs that are not caused by OMV.
      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:

      Debian Buster is not released nor stable, so expect bugs that are not caused by OMV.
      The rsyncd salt module doesn't have anything to enable/disable the service (unit was disabled even after I had a successful enable and apply). As soon as I started the service, everything worked fine.
      omv 4.1.22 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:

      votdev wrote:

      Can not reproduce this with latest master.
      I can confirm that updating to the latest git fixes the issue.

      ryecoaaron wrote:

      I can confirm that updating to the latest git fixes the issue.
      Well, on my PC this problem persists even after having reinstalled the image dated Apr. 19 and immediately updating through "Update management". Rsync can be enabled without any error message, but it does not run - either with modules or without modules. Is there anywhere I might look for a log on rsync? SSH (and CIFS for that matter) work nicely. Enabling FTP gives long error message by the way. See ftp section. Seems a bit more work will be required on OMV5.

      Update:
      Just to make sure the problem is with OMV 5 beta and not with the PC hardware, I installed omv 4 on the same machine with the latest updates. All is well. Same applies to ftp for that matter. So omv 5 beta and/or the underlying Debian Buster need to mature a bit. Anyway I'll stop mucking around (i.e "testing") for the moment and say thank you for all the hard work you put in omv over the years.
    • 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