Beiträge von votdev

sec seems to be cool tool. Maybe i can use it too vanish rsyslog completely. rsyslog is only used to monitor syslog and send emails if necessary.

Please open a issue at GitHub. I've often told that i do not process feature request coming from the forum because this is not meant to be a feature/issue tracker,

This sounds strange because all systems are based on Samba. At the end you have to compare the smb.conf of all systems to find out what the reason for this different behaviour is.

You can add custom Salt states that can be used to manipulate the config files auto-generated by OMV. This way you are safe that your customization is applied when OMV redeploys a service. But you have to get familar with the OMV deployment system.

Zitat von Teschbert

Hmmmm - not on my system. On my side it stopped working after an update of 6.9.??? and its still not working after upgrading yesterday to OMV 7

Edit: in SMART Devices in the GUI my 3 SSD are shown

Please check the changelog.

You can do that in the Network | Interfaces page in the UI or run omv-firstaid from CLI to reconfigure the network.

What is the output of

omv-confdbadm read --prettify conf.system.network.interface

I assume there is a configuration for eth0. Delete it and recreate a new config for end0.

Zitat von InTheNoon

Do you think this might be an option, too as replacement for recipes or are you afraid that the complexity will get higher when incorporating Helm?

Recipes are using Helm charts. I don’t want to create Helm charts, I want to consume them and that is very simple with k3s. Check out the FileBrowser recipe, it is based on a Helm chart. As you can see, the recipe uses only three resources to get this app running behind a reverse proxy with SSL certificate and subpath. The user only needs to file the shared folder path. Voila, that’s near to a one-click installation.

Recipes are building on Helm charts if possible plus adding everything else that the chart does not provide to give the user a more or less one-click solution.

I got the same message today while buying an iTunes gift card. Seems to be a general problem with PayPal atm.

The message comes from Salt. OMV7 has updated the version, so there might be changes in Salt that might cause this output. But Salt does not exit with an error, so everything is OK and you can ignore the output.

Zitat von olduser

Following that, Kubernetes brings nothing new to OMV users, it simply asks to redo what has already been done with Docker.

IMO Kubernetes is the future and much more powerful than Docker Compose. TrueNAS Scale is based on SUSE K3s for a reason.

Zitat von olduser

I find the current plugin system too limiting as it seems you can't even add your Javascript.

This is a unique selling point and a feature of OMV. The UI can be implemented in a declarative way via YAML which is much simpler than doing that in Javascript. This allows users to contribute without having the knowledge of Javascript, Typescript, Angular and aIl the other things that would be necessary. IMO the UI already provides everything that is necessary for this type of UI.

The watchdog package was a hard dependency long time ago. I'm sorry i do not remember everything what i've done in the last 15 years, but it seems that it is a soft dependency now. Nevertheless, with the commands mentioned above you can configure OMV so that the watchdog config is purged.

But the core problem persists, the Raspi kernel does not ship the required modules to get the watchdog working.

Zitat von Barqu

you wrote "This is a useful feature for headless servers. But it is not a service that is really required to run the NAS." Is this still valid for V7 and RPI? If so, I do not really understand the benefit of disabling watchdog.
Please excuse if I misunderstand something, my knowledge is a bit low, but I'm trying to understand what is going on.

Using a watchdog makes absolute sense on a headless NAS, but it seems Raspi OS does not contain the necessary kernel modules. So it is better to disable the OMV feature.

Maybe it makes sense to raise a ticket for the Raspi OS that the project is aware of the problem.

It's a PayPal thing. Where are you lcated Grogster?

I think you shoudl raise the issue in the Raspi forum because OMV is using their OS but does not maintain it. If there is a problem, only the Raspi project can fix it. To me it looks like their kernel is missing some modules.

You need to disable watchdog the OMV way, so the softdog module will not be configured. Set the OMV_WATCHDOG_ENABLED env var to false according to the docs. Instead of deploying everything as mentioned in the docs simply run

omv-salt stage run prepare
omv-salt deploy run watchdog

I think storage management in OMV is good, but there is room for getting better. Keep in mind that OMV is done by myself and omv-extras.org by Aaron and other contributors. It is unfair to compare it with companies that have employees that work on it full-time. We do it in our spare time as a hobby.

OMV7 has now a Kubernetes plugin to run containers in a K8s environment without the need of Docker or Podman. I've also started a repository for it to collect recipes to easily install container apps from Helm Charts or K8s API resources. Standalone plugins require much much much time and maintenance. Therefore container based apps are much easier to maintain. The sad thing is that they need to be managed via Yaml and are not integrated very well in the UI. But i'm thinking about how to provide a UI for that because the whole OMV UI is done in a declarative manner, so it should be easy to provide that for container based plugins as well.

To populate and increase this Kubernetes recipes it requires active participation of the community. When it comes to plugins/apps, i think this is the way to go because it reduces the implementation and maintenance time of apps/plugins.

Users have to choose then between Kubernetes and Docker. I'm in favor of K8s because it is much easier when it comes to network config. I hate the Docker approach. But thats my personal point of view.

Finally, a ecosystem like OMV can only increase when the community is contributing. This is something that is sadly going lim x->0.

Zitat von Barqu

I entered your code in the terminal but no outcome at all from the terminal. So.... what does that mean? No watchdog available in the kernel?

Looks like. What hardware and distro are you using? is it a SBC?

You can simply disable watchdog via systemctl disable --now watchdog.

Zitat von Stepinsky

Or do I need to set a log size limit on my own?

Yes

Zitat von Stepinsky

Why are there still old fashioned log entries written? Why is there still a syslog file when syslogd journal is active? Is this a bug on my system?

rsyslog is still installed because of features that are not available and possible with systemd. But afaik there shouldn't be written anything to the filesystem. This only applies to a fresh OMV7/Debian12, if it is migrated from OMV6/Debian11, then the rsyslog config is not touched and everything is duplicated.

This is not possible via UI because filesystem labels are not used in OMV. You need to use the CLI, check out tune2fs if you are using a EXT file system.

Google for vacuum syslogd journal