network creation code in OMV might need a bugfix.
I don’t know the Compose plugin enough but I bet the network creation is done by Docker because it is part of the compose file.
Posts by votdev
-
-
Can I simply copy this directory and file to the /etc directory in the other installation?
No, because the file is generated from the OMV configuration database. You can extract the firewall rules manually from the config.xml file and insert them in the config.xml file of the target system, but this can be tricky and result in a broken database if you do not know what you are doing.
-
You can create shared folders from snapshots.
If you want any other solution, you are on your own.
-
and a problem that has been fixed with a patch I hope that also in omv it will be fixed and solved
If the problem is fixed by the Debian samba package, then it will be available in OMV as well. OMV itself does not maintain any upstream package.
-
Display More
Hi votdev
I executed the commands. They ran without any problems. However, the error still appears when I execute the pending configuration changes.
Error again: 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 samba 2>&1' with exit code '1': dpkg-divert: error: 'local diversion of /etc/default/wsdd to /tmp/_etc_default_wsdd' clashes with 'local diversion of /etc/default/wsdd to /etc/default/wsdd.distrib'
dpkg-divert: error: 'local diversion of /etc/samba/smb.conf to /tmp/_etc_samba_smb.conf' clashes with 'local diversion of /etc/samba/smb.conf to /etc/samba/smb.conf.distrib'
Code
Display Moresudo dpkg-divert --local --no-rename --remove /etc/monit/monitrc [sudo] Passwort für $$$$: »lokale Umleitung von /etc/monit/monitrc zu /etc/monit/monitrc.distrib« wird entfernt $ sudo omv-salt deploy run monit debian: ---------- ID: cleanup_monit_conf_dir Function: module.run Result: True Comment: file.find: ['/etc/monit/conf.d/openmediavault-collectd.conf', '/etc/monit/conf.d/openmediavault-engined.conf', '/etc/monit/conf.d/openmediavault-filesystem.conf', '/etc/monit/conf.d/openmediavault-nginx.conf', '/etc/monit/conf.d/openmediavault-phpfpm.conf', '/etc/monit/conf.d/openmediavault-rrdcached.conf', '/etc/monit/conf.d/openmediavault-system.conf'] Started: 17:31:35.809473 Duration: 0.918 ms Changes: ---------- file.find: - /etc/monit/conf.d/openmediavault-collectd.conf - /etc/monit/conf.d/openmediavault-engined.conf - /etc/monit/conf.d/openmediavault-filesystem.conf - /etc/monit/conf.d/openmediavault-nginx.conf - /etc/monit/conf.d/openmediavault-phpfpm.conf - /etc/monit/conf.d/openmediavault-rrdcached.conf - /etc/monit/conf.d/openmediavault-system.conf ---------- ID: remove_monit_delay_file Function: file.absent Name: /etc/monit/monit_delay Result: True Comment: File /etc/monit/monit_delay is not present Started: 17:31:35.811517 Duration: 0.3 ms Changes: ---------- ID: divert_monit_delay_file Function: omv_dpkg.divert_add Name: /etc/monit/monit_delay Result: True Comment: »lokale Umleitung von /etc/monit/monit_delay zu /tmp/_etc_monit_monit_delay« wird beibehalten Started: 17:31:35.812077 Duration: 6.014 ms Changes: ---------- ID: configure_default_monit Function: file.managed Name: /etc/default/monit Result: True Comment: File /etc/default/monit is in the correct state Started: 17:31:35.818170 Duration: 29.358 ms Changes: ---------- ID: divert_default_monit Function: omv_dpkg.divert_add Name: /etc/default/monit Result: True Comment: »lokale Umleitung von /etc/default/monit zu /tmp/_etc_default_monit« wird beibehalten Started: 17:31:35.847599 Duration: 5.588 ms Changes: ---------- ID: configure_monit_monitrc Function: file.managed Name: /etc/monit/monitrc Result: True Comment: File /etc/monit/monitrc is in the correct state Started: 17:31:35.853275 Duration: 63.893 ms Changes: ---------- ID: divert_monit_monitrc Function: omv_dpkg.divert_add Name: /etc/monit/monitrc Result: True Comment: »lokale Umleitung von /etc/monit/monitrc zu /tmp/_etc_monit_monitrc« wird hinzugefügt Started: 17:31:35.917241 Duration: 11.036 ms Changes: ---------- ID: configure_monit_collectd_service Function: file.managed Name: /etc/monit/conf.d/openmediavault-collectd.conf Result: True Comment: File /etc/monit/conf.d/openmediavault-collectd.conf updated Started: 17:31:35.928406 Duration: 60.977 ms Changes: ---------- diff: New file mode: 0644 ---------- ID: configure_monit_filesystem_service Function: file.managed Name: /etc/monit/conf.d/openmediavault-filesystem.conf Result: True Comment: File /etc/monit/conf.d/openmediavault-filesystem.conf updated Started: 17:31:35.989454 Duration: 62.004 ms Changes: ---------- diff: New file mode: 0644 ---------- ID: configure_monit_nginx_service Function: file.managed Name: /etc/monit/conf.d/openmediavault-nginx.conf Result: True Comment: File /etc/monit/conf.d/openmediavault-nginx.conf updated Started: 17:31:36.051538 Duration: 64.276 ms Changes: ---------- diff: New file mode: 0644 ---------- ID: configure_monit_omv-engined_service Function: file.managed Name: /etc/monit/conf.d/openmediavault-engined.conf Result: True Comment: File /etc/monit/conf.d/openmediavault-engined.conf updated Started: 17:31:36.115880 Duration: 60.271 ms Changes: ---------- diff: New file mode: 0644 ---------- ID: configure_monit_php-fpm_service Function: file.managed Name: /etc/monit/conf.d/openmediavault-phpfpm.conf Result: True Comment: File /etc/monit/conf.d/openmediavault-phpfpm.conf updated Started: 17:31:36.176216 Duration: 60.1 ms Changes: ---------- diff: New file mode: 0644 ---------- ID: configure_monit_rrdcached_service Function: file.managed Name: /etc/monit/conf.d/openmediavault-rrdcached.conf Result: True Comment: File /etc/monit/conf.d/openmediavault-rrdcached.conf updated Started: 17:31:36.236382 Duration: 59.755 ms Changes: ---------- diff: New file mode: 0644 ---------- ID: configure_monit_system_service Function: file.managed Name: /etc/monit/conf.d/openmediavault-system.conf Result: True Comment: File /etc/monit/conf.d/openmediavault-system.conf updated Started: 17:31:36.296199 Duration: 68.326 ms Changes: ---------- diff: New file mode: 0644 ---------- ID: test_monit_config Function: cmd.run Name: monit -t Result: True Comment: Command "monit -t" run Started: 17:31:36.364892 Duration: 5.863 ms Changes: ---------- pid: 423720 retcode: 0 stderr: stdout: Control file syntax OK ---------- ID: reload_monit_service Function: service.running Name: monit Result: True Comment: Service reloaded Started: 17:31:36.844812 Duration: 49.028 ms Changes: ---------- monit: True Summary for debian ------------- Succeeded: 16 (changed=10) Failed: 0 ------------- Total states run: 16 Total run time: 607.707 ms $In that case run
Code# dpkg-divert --local --no-rename --remove /etc/default/wsdd # dpkg-divert --local --no-rename --remove /etc/samba/smb.conf -
shoudl I create these manually?
You can't. These are the RRD databases generated by collectd.
Or where do I get a plugin?
The collectd nut plugin is automatically installed by OMV via the nut Debian package.
-
To generate the NUT RRD graphs, there must be files located at /var/lib/collectd/rrd/<HOSTNAME>/nut-<UPSNAME>. These files are generated by collectd. If they are missing, then no graph images can be generated.
-
I have the feeling that this delays the overall start by the specified time, and not just the monitoring service. The server website is also very delayed.
Are you sure about this option?
Hmmm this sounds strange because all services are started via systemd and NOT monitd on system start. Monit is just monitoring them.
The phenomenon you are observing can only occur if none of the services monitored by monit are started by systemd and monit then starts them after the waiting time. Then the problem is that the services are started too slowly or not at all by systemd for some reason. -
This command should fix it.
Code# dpkg-divert --local --no-rename --remove /etc/monit/monitrc # omv-salt deploy run monit -
The hardware must be supported by the collectd nut plugin. It looks like this is not the case.
-
could it be a docker container that creates these network interfaces? if “yes” how do i find out which one it is?
All veth* interfaces are created by Docker.
-
Exactly, but this makes no sense if it is done after every start of the server. The server goes down at night either way. I didn't have this message before.
When this message is sent during the booting process, then starting the nginx service took longer than monit waits for the first check.
You can modify the delay with the OMV_MONIT_CHECK_START_DELAY environment variable. The value is in seconds and defaults to 30.
Finally, the message indicates that the system startup for some services has changed and now takes longer than before. You will have to find out for yourself why this is the case. -
This email simply informs you that the nginx process does not exist anymore (killed, OOM, ...) and monit has restarted it.
-
The most important prereq that macom menioned in his guide is
Quotethere must be only one partition on the USB drive
-
I've opened a PR that will hide irrelevant config settings in the network interface page. See https://github.com/openmediavault/openmediavault/pull/1947.
-
If I open Network/Interfaces I want current accurate information
This is not how the UI works and I will not change that behaviour for a single page. This will confuse users more than it helps.
-
Alternatively use OMV_BTRFS_SCRUB_PERIOD to switch between weekly and monthly.
-
K3s is simply another lightweight container runtime beside Docker. The k8s plugin does not want to make use of extra features that are available in k8s; this does not make sense on a one node cluster.
But nevertheless you have nice features.
-
I found out by using the command "netplan generate". This gives the according error message.
I am very surprised that it was then possible to press the apply button in the OMV UI because when the configuration is applied then a netplan apply is called which in turn calls netplan generate. Therefore the error message should also be displayed in the UI.
It would be useful to have some additional information to help you. For example, the systemd journal message from netplan or the name of the interface.Solutions I found in the net suggest a renaming of the interface by Netplan before adding the VLAN.
You can customize the config scripts of OMV by injecting your custom SLS files. See https://docs.openmediavault.or…html#the-saltstack-states and https://github.com/openmediava…/systemd-networkd/netplan for more information.
-
If I switch back and forth between dhcp, static and back it contains the ip and mask from the static settings
If you do not remove this static settings parts, then it is part of the config so it is displayed.
Also wrong information is worse than no information and I regard this more as a bug than a feature.
this information is part of the configuration, which is why it is displayed. i don't see this as an error. But I think that's a matter of opinion.
