... that was the issue... not sure, how that happened. I did not manually edit the file before.
Beiträge von henfri
-
-
I notice, that there are entries in the rsync section, that I would expect in a cronjob section:
Code
Alles anzeigen<rsync> <server> <enable>1</enable> <port>873</port> <extraoptions></extraoptions> <modules></modules> </server> <jobs> <!-- <job> <uuid>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</uuid> <enable>0|1</enable> <sendemail>0|1<sendemail> <quiet>0</quiet> <comment>xxx</comment> <type>local|remote</type> <src> <sharedfolderref>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</sharedfolderref> <uri>xxx</uri> </src> <dest> <sharedfolderref>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</sharedfolderref> <uri>xxx</uri> </dest> <minute>[00-59|*]</minute> <everynminute>0|1</everynminute> <hour>[00-23|*]</hour> <everynhour>0|1</everynhour> <dayofmonth>[01-31|*]</dayofmonth> <everyndayofmonth>0|1</everyndayofmonth> <month>[01-12|*]</month> <dayofweek>[1-7|*]</dayofweek> <optionrecursive>1</optionrecursive> <optiontimes>1</optiontimes> <optiongroup>1</optiongroup> <optionowner>1</optionowner> <optioncompress>0</optioncompress> <optionarchive>1</optionarchive> <optiondelete>0</optiondelete> <optionperms>1</optionperms> <optionacls>1</optionacls> <optionxattrs>0</optionxattrs> <optiondryrun>0</optiondryrun> <optionpartial>0</optionpartial> <extraoptions></extraoptions> // remote <mode>push|pull</mode> <authentication>password|pubkey</authentication> <password>xxx</password> <sshcertificateref>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</sshcertificateref> <sshport>22</sshport> </job> --> <job> <enable>1</enable> <minute>0</minute> <hour>0</hour> <dayofmonth>*</dayofmonth> <month>*</month> <dayofweek>*</dayofweek> <command>token=x/usr/local/bin/dynv6.sh openmediavault.dynv6.net</command> <user>henfri</user> </job>
-
Hello,
I just installed the compose-plugin.
That triggered an "configuration needs to be updated" info.
When applying the configuration, I get
Code500 - 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) ^^^^^^^...
I am not really using rsync...
The config.xml does not look wrong wrt. rsync.
How can I fix this?
Greetings,
Hendrik
-
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
-
Hello,
thank you!
Indeed, this seems to be the problem:
CodeNov 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
In the expert-settings.
I hope this helps.
Greetings,
Hendrik
-
Hello,
do you have any further Idea?
Best regards,
Hendrik
-
Hello,
thanks for your reply.
Here is the configuration:
Code
Alles anzeigen<autoshutdown> <enable>1</enable> <cycles>6</cycles> <sleep>60</sleep> <ipcheck>0</ipcheck> <range>2..254,0x0..0xFFFF</range> <shutdowncommand>0</shutdowncommand> <checkclockactive>1</checkclockactive> <uphours_begin>12</uphours_begin> <upmins_begin>0</upmins_begin> <uphours_end>12</uphours_end> <upmins_end>30</upmins_end> <wakealarm_set>1</wakealarm_set> <wakealarm_hour>12</wakealarm_hour> <wakealarm_mins>0</wakealarm_mins> <wakealarm_uphours>1</wakealarm_uphours> <checksockets>1</checksockets> <nsocketnumbers>21,22,80</nsocketnumbers> <uldlcheck>1</uldlcheck> <uldlrate>50</uldlrate> <loadaveragecheck>0</loadaveragecheck> <loadaverage>40</loadaverage> <hddiocheck>1</hddiocheck> <hddiorate>401</hddiorate> <smartcheck>0</smartcheck> <checksamba>1</checksamba> <checkcli>1</checkcli> <checkprocnames>1</checkprocnames> <loadprocnames>borg</loadprocnames> <tempprocnames>in.tftpd</tempprocnames> <plugincheck>0</plugincheck> <syslog>1</syslog> <verbose>1</verbose> <fake>0</fake> <extraoptions/> </autoshutdown>
So, nothing really exciting...
Greetings,
Hendrik
-
Hello,
autoshutdown is not working for me... In syslog, I find:
CodeSep 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
-
Thanks, I will try that!
-
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
-
Thanks.
Thus,
netplan apply could do the trick for me, right?
Or would netplan detect that nothing has changed (as I only want to reinitialize with the same settings) and do nothing?
Regards,
Hendrik
-
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
-
chente I think, you mis-understand.
I have a problem, that I can fix by re-applying the network-settings in OMV.
Now, I would like to do the same - without applying any changes- on CLI.
Thus, I wonder what the GUI does to apply settings internally.
Greetings,
Hendrik
-
Thanks, that worked!
-
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:
CodeExecuting: /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
-
-
Hello,
my br0 lost its ipv6 adress today.
In dmesg I see:
Code
Alles anzeigendmesg -T |grep br0 [Fr Aug 18 07:36:10 2023] br0: port 1(enp1s0) entered blocking state [Fr Aug 18 07:36:10 2023] br0: port 1(enp1s0) entered disabled state [Fr Aug 18 07:36:11 2023] br0: port 1(enp1s0) entered blocking state [Fr Aug 18 07:36:11 2023] br0: port 1(enp1s0) entered forwarding state [Fr Aug 18 07:36:11 2023] br0: port 1(enp1s0) entered disabled state [Fr Aug 18 07:36:13 2023] br0: port 1(enp1s0) entered blocking state [Fr Aug 18 07:36:13 2023] br0: port 1(enp1s0) entered forwarding state [Fr Aug 18 07:37:43 2023] br0: port 2(vnet0) entered blocking state [Fr Aug 18 07:37:43 2023] br0: port 2(vnet0) entered disabled state [Fr Aug 18 07:37:43 2023] br0: port 2(vnet0) entered blocking state [Fr Aug 18 07:37:43 2023] br0: port 2(vnet0) entered forwarding state [Fr Aug 25 06:40:34 2023] br0: port 2(vnet0) entered disabled state [Fr Aug 25 06:40:34 2023] br0: port 2(vnet0) entered disabled state
When I try to restart the network, I get:
Coderoot@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
Code
Alles anzeigenroot@homeserver:/etc/openmediavault/scripts# ifconfig br0 br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.177.3 netmask 255.255.255.0 broadcast 192.168.177.255 inet6 fe80::f849:bff:fe8c:138a prefixlen 64 scopeid 0x20<link> ether fa:49:0b:8c:13:8a txqueuelen 1000 (Ethernet) RX packets 18663076 bytes 26625389722 (24.7 GiB) RX errors 0 dropped 642782 overruns 0 frame 0 TX packets 18303371 bytes 6784889802 (6.3 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 root@homeserver:/etc/openmediavault/scripts# ifconfig enp1s0 enp1s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 90:1b:0e:aa:13:a9 txqueuelen 1000 (Ethernet) RX packets 40380847 bytes 30789069373 (28.6 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 26235673 bytes 4845594463 (4.5 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
-
-
Hello,
here it is:
Codesudo /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
-