Should be fixed with https://github.com/openmediava…70fa12a91b6b5ab5e6a2eab65.
Beiträge von votdev
-
-
The deployment engine only does what it is told. Your network configuration still contains entries for eth0. Go to the Network page in the UI, deletethe eth0 entry and continue with setting up WiFi.
-
Run dpkg --configure -a as the error message is suggesting.
-
I see no need to change anything. The colors are used by the Angular framework in other cases as well.
-
This error is because a config migration for OMV 6.0.0 was not successful. So this system was migrated from OMV5 to OMV6, right?
Try running the script /usr/share/openmediavault/confdb/migrations.d/conf_6.0.0.sh and report back if it helped.
-
Check out the architecture table at https://github.com/openmediavault/openmediavault-k8s-recipes.
You can also use the Kubernetes plugin to install the filebrowser app.
-
And what do you think is the correct color?
-
In OMV7 it is not possible anymore to disable this notifications because the tool that is used does not support that. It can be on or off; but off means no auto-installation of security updates.
-
The problem is that the shared folder privileges are NOT applied to the file system as mentioned in the info note on that UI page. It is only for service access. Your problem surely relies on the problem thet the user has no FILE SYSTEM PRIVILEGES. Go to the shared folder page, press the ACL button in the action toolbar and apply the necessary user access rights on the file system.
-
votdev is it an idea to add this information in the documentation, maybe under releases?
Not just for this release but also for future releases when the month or day is know.
I've updated the docs.
-
DNS is still not working.
-
But I was wondering whether there's some kind of if ! could be added, so that if Plex is running, this particular alert isn't sent?
To make it short; No
-
-
is it possible to modify the top statement so that it comes out in %MEM order
No, that is not possible.
-
Good news if it does. How do you specify the input in DAEMON_ARGS in the /etc/default/sec file for use with journald?
You can check this here, but i've rejected the feature because rsyslog is required for syslog forwarding. But sending emails when a regex is matching a syslog message is also possible with rsyslog. OMV is using that for looking out for pam_faillock messages.
-
What browser are you using? Can not reproduce that with Firefox and Chrome.Right, on a new test system i can reproduce that. Will fix it asap.
-
Although eliminating rsyslog could make using "sec" for BTRFS notification unviable.
Why, "sec" will monitor systemd journal.
-
So there is no chance to turn off that false nofitication?
No; it's not possible to customize all smartctl calls spread across the source code. Maybe it is possible to teach smartmontools via their database. Check out
- https://github.com/openmediava…9#issuecomment-1788959178
- https://docs.openmediavault.org/en/stable/faq.html
- After update from 6.9.6-1 to -2: SMART stopped working w error
- RE: SMART statuses are not working on omv7, debian 12, raspi4
-
Hi,
I have a similar Error Message in openmediavault-webgui_error.log:
FastCGI sent in stderr: "PHP message: PHP Warning: DOMDocument::load(/etc/openmediavault/config.xml): Failed to open stream: Permission denied in /usr/share/php/openmediavault/config/databasebackend.inc on line 121" while reading response header from upstream client: 192.168.2.222, server: openmediavault-webgui, request: "POST /rpc.php HTTP/1.1", upstream: "fastcgi://unix:/run/php/php8.2-fpm-openmediavault-webgui.sock:", host: "192.168.2.223", referrer: "http://192.168.2.223/"
I am running OMV 7 at Debian 12 (raspberry Pi). I start the Pi via network boot. Installation was going well (no error messages), but I was never able to logon via webgui.
Is the network-boot the problem?
No, it's a file permission problem. Have you modified /etc/openmediavault/config.xml on your own? What is the output of
-
Ok, wrong docs.
In salt.states.file (saltproject.io) it's name instead o path. Now deploy works.
But drive still have Bad health status (with -i or -I parameter):
What you've modified is the configuration for the disk monitoring done by smartmontools. This has no affect on other calls of smartctl.