Just for your information.
Currently trying out the omv5 beta. Found that the rsync server will not run (red dot) after enabling it (green dot).
Enabling the rsync server in the same way on an omv4 machine is successful.
Rsync server not running with OMV5beta
-
- OMV 5.x
- gelöst
- Backupmaster
-
-
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
# 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' -
Can not reproduce this with latest master.
-
-
Can not reproduce this with latest master.
I can confirm that updating to the latest git fixes the issue.
-
I can confirm that updating to the latest git fixes the issue.
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.
-
-
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.
-
I can confirm that updating to the latest git fixes the issue.
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. -
Fixed in openmediavault 5.0.2, see https://github.com/openmediava…2c34d85dd910c84c06c83b786.
-
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!