Posts by henfri

  • The property 'command' does not exist in the model 'conf.service.rsync.job'.

    I notice, that there are entries in the rsync section, that I would expect in a cronjob section:

  • The property 'command' does not exist in the model 'conf.service.rsync.job'.

    Hello,


    I just installed the compose-plugin.

    That triggered an "configuration needs to be updated" info.

    When applying the configuration, I get

    Code
    500 - Internal Server Error
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LC_ALL=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color rsync 2>&1' with exit code '1': debian: Data failed to compile: ---------- Rendering SLS 'base:omv.deploy.rsync.default' failed: Jinja error: The property 'command' does not exist in the model 'conf.service.rsync.job'. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/salt/utils/templates.py", line 477, in render_jinja_tmpl output = template.render(**decoded_context) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 1301, in render self.environment.handle_exception() File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 936, in handle_exception raise rewrite_traceback_stack(source=source) File "<template>", line 25, in top-level template code File "/usr/lib/python3/dist-packages/jinja2/sandbox.py", line 401, in call return __context.call(__obj, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/salt/loader/lazy.py", line 149, in __call__ return self.loader.run(run_func, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/salt/loader/lazy.py", line 1234, in run return self._last_context.run(self._run_as, _func_or_method, *args, **kwargs) ^^^^^^^...


    Code
    The property 'command' does not exist in the model 'conf.service.rsync.job'.


    I am not really using rsync...


    The config.xml does not look wrong wrt. rsync.


    How can I fix this?


    Greetings,

    Hendrik

  • Cannot login to admin panel after upgrade - omv-firstaid does not help

    Hello,


    I have upgraded from omv4 to omv5 and to omv6.

    I cannot reinstall, as the machine is remote :(


    The upgrades did not work smoothly. At some point, I was at an "inbetween" state, where php7.4 was required, but not available in debian 10.


    Now, finally I removed omv (packages), upgraded manually (the debian way) and installed omv again.


    However, I cannot log in to the Admin page.

    even resetting the Password via firstaid does not help - I get 400 Bad user/pass.


    What could be the reason?


    Best regards,

    Hendrik

  • autoshutdown.service: Failed with result 'exit-code'.

    Hello,


    thank you!

    Indeed, this seems to be the problem:

    Code
    Nov  8 12:03:09 homeserveralt autoshutdown[2474]: root: DEBUG: '_get_network_details(): Network interfaces: eth0'
Nov  8 12:03:09 homeserveralt autoshutdown[2474]: root: DEBUG: '_get_network_details(): Network interfaces status: down'
Nov  8 12:03:09 homeserveralt autoshutdown[2474]: root: DEBUG: '_get_network_details(): Network interfaces IPv4 address: N/A'
Nov  8 12:03:09 homeserveralt autoshutdown[2474]: root: DEBUG: '_get_network_details(): Network interfaces IPv4 address valid: false'
Nov  8 12:03:09 homeserveralt autoshutdown[2474]: root: DEBUG: '_get_network_details(): Network interfaces IPv6 address: N/A'
Nov  8 12:03:09 homeserveralt autoshutdown[2474]: root: DEBUG: '_get_network_details(): Network interfaces IPv6 address valid: false'
Nov  8 12:03:09 homeserveralt autoshutdown[2474]: root: INFO: '_get_network_details(): 'eth0' status: down, IPv4 address: N/A, IPv6 address: N/A, retrying in 5s ...'

    After that, the server did not shutdown anymore.


    I now set

    Code
    NET_IFACE_RETRY=120
NET_IFACE_SLEEP=60

    In the expert-settings.

    I hope this helps.


    Greetings,

    Hendrik

  • autoshutdown.service: Failed with result 'exit-code'.

    Hello,


    thanks for your reply.

    Here is the configuration:


    So, nothing really exciting...


    Greetings,

    Hendrik

  • autoshutdown.service: Failed with result 'exit-code'.

    Hello,


    autoshutdown is not working for me... In syslog, I find:

    Code
    Sep 18 12:02:58 homeserveralt systemd[1]: Started openmediavault-autoshutdown plugin service.
Sep 18 12:04:00 homeserveralt systemd[1]: autoshutdown.service: Main process exited, code=exited, status=138/n/a
Sep 18 12:04:00 homeserveralt systemd[1]: autoshutdown.service: Failed with result 'exit-code'.
Sep 18 12:04:00 homeserveralt systemd[1]: autoshutdown.service: Consumed 1.825s CPU time.



    After this, no further shutdowns seem to be tried, so it seems that the plugin is not running anymore - it seems not just a proccess that the plugin tried to start, that crashed.


    What could be the reason for this?



    Best regards,

    Hendrik

  • What does OMV do, when changing network interface settings

    No.


    Let me start again:

    1) for some reason my network looses ipv6 address sporadically

    2) I can detect that in a script, and now would like to fix it in that script as well

    3) re-applying the network settings in the GUI does the trick. Thus, I want to trigger this in from the script

    4) It was pointed out above, that running the complete omv-salt command from above omv-salt deploy run avahi halt hosts issue systemd-networkd would do the trick but potentially more.

    5) Volker pointed out that omv is using netplan

    6) I wonder if netplan apply is sufficient to restart the network with unchanged settings



    Best regards,

    Hendrik

  • What does OMV do, when changing network interface settings

    Thanks, I understand that.


    now, AFTER changing the files through omv-salt, OMV does something to make the system aware of these changes (for instance restart the network or at least let the network know to use these modified files).


    What command is OMV using to re-initiate the network after having changed the files?


    Greetings,

    Hendrik

  • FTP is masked after update vrom 5.x

    Hello,


    I transitioned from 5 to 6. After that, FTP kept working fine.

    But I now changed the Storage and need to update the sharefolder.

    Unfortunately, in the GUI, the FTP is missing under Services.


    I found, that FTP has been moved to a plugin and installed it.


    However, when applying my changes, I get an error-message.

    When running on the CLI to apply the changes, I get:

    Code
    Executing: /lib/systemd/systemd-sysv-install enable proftpd
Failed to enable unit: Unit file /etc/systemd/system/proftpd.service is masked.
[ERROR   ] Command '/bin/systemd-run' failed with return code: 1
[ERROR   ] stderr: Running scope as unit: run-r1774517fa2fc4c9c83b264aea557ca01.scope
Failed to restart proftpd.service: Unit proftpd.service is masked.
[ERROR   ] retcode: 1
[ERROR   ] Failed to restart proftpd.service: Unit proftpd.service is masked.


    (more details here)


    How can I get ftp running again?


    Best regards,

    Hendrik

  • What does OMV do, when changing network interface settings

    Hello,


    my br0 lost its ipv6 adress today.

    In dmesg I see:


    When I try to restart the network, I get:

    Code
    root@homeserver:/etc/openmediavault/scripts# ifdown br0 && ifup br0
ifdown: unknown interface br0
root@homeserver:/etc/openmediavault/scripts# ifdown enp1s0 && ifup enp1s0
ifdown: unknown interface enp1s0

    I was able to fix this, by changing a setting in the Network Interface of br0 in the omv GUI (the search domain, just to trigger an update. That worked.


    Now, it would be great to have a true solution. But I am not so confident..

    If a solution is not possible, a workaround would be a script triggering the same that the omv-gui is doing when applying changes to the network settings.


    What commands do I need to do the same as when applying network setting changes in OMV?


    Best regards,

    Hendrik


  • Samba

    Hello,


    here it is:

    Code
    sudo /usr/bin/salt-call --local saltutil.clear_cache
[sudo] Passwort für henfri:
local:
    True
henfri@homeserver:~$ sudo omv-salt stage run prepare
homeserver.fritz.box:
    Data failed to compile:
----------
    No matching sls found for 'omv.stage.prepare' in env 'base'


    Best regards,

    Hendrik