According to the log message a python script tries to log in via localhost.
Beiträge von votdev
-
-
You can check the source code to find out why your device is not listed. See https://github.com/openmediava…ned/rpc/usbbackup.inc#L65
-
The file can be emptied when the system is shut down during writing this file or the process that is responsible for that is killed somehow.
-
I wish OMV would allow more user control over Postfix, at least enough for it to act as a mail server for the localdomain and its users. I used to have a main.cf file that allowed for this but got tired of having to restore it everytime OMV decided to overwrite it.
you can hook into the service deployment according to this:
-
This error is thrown when a internal status file was generated by a different user than the user that wants to read the file content. This is done for security reasons. The question now is which user has created the file.
Run ls -alh /tmp/bgstatusJ4* and post the output.
What plugins have you installed?
-
The problem is your host system, you need to restart avahi there. The same happens to me on Ubuntu 22.04 LTS since some weeks. I assume there is a bug in Avahi.
-
Glad to hear it is working for you.
This project, which is mentioned in auanasgheps guide, seems to be active
The problem with this is that it is not packaged for every platform that is supported by Debian and therefor OMV.
-
Yes that is sad. Maybe it will take some time to get some reactions. For myself I will stay on k8s and will add some recipes from time to time for apps i am using myself.
-
No, you can’t
-
The install is trying not to change them. Armbian puts the settings in /etc/default/cpufrequtils (as you said) but this is not what OMV's saltstack code uses for a source of truth. So, the script tries to read /etc/default/cpufrequtils on all Armbian installs and write them to OMV's default overrides allowing saltstack to rewrite /etc/default/cpufrequtils to the original values.
If the script doesn't do this, OMV will change them to the values you saw. I'm not sure where things went wrong on your install. I will have to try an armbian install.
I see Aaron has already explained the behaviour in detail.
-
We (Helios64 owners) are currently experiencing significant problems when we try to use the script from...
https://github.com/OpenMediaVa…Script/raw/master/install
... to install the current OMV 7 on a Armbian Bookworm system.
At the following point...
Code/usr/lib/python3/dist-packages/salt/grains/core.py:2711: DeprecationWarning: Use setlocale(), getencoding() and getlocale() instead ) = locale.getdefaultlocale() /usr/lib/python3/dist-packages/salt/grains/core.py:2711: DeprecationWarning: Use setlocale(), getencoding() and getlocale() instead ) = locale.getdefaultlocale() /usr/lib/python3/dist-packages/salt/utils/pycrypto.py:26: DeprecationWarning: 'crypt' is deprecated and slated for removal in Python 3.13 import crypt /usr/lib/python3/dist-packages/salt/modules/linux_shadow.py:21: DeprecationWarning: 'spwd' is deprecated and slated for removal in Python 3.13 import spwd Deploying service configurations ... <<<<< here !? Processing system modifications ... <<<<< or here !?
... the cpu frequency from the following value...
Code# cat /etc/default/cpufrequtils ENABLE="true" GOVERNOR="ondemand" MAX_SPEED="1200000" MIN_SPEED="408000"
... is changed to this value...
the cpu frequency is then written back at the following point...
Code
Alles anzeigen---------- ID: sync_modules Function: saltutil.sync_modules Result: True Comment: Updated modules. Started: 23:12:40.830096 Duration: 1119.591 ms Changes: ---------- modules: - modules.omv_conf - modules.omv_utils Summary for helios64 ------------ Succeeded: 4 (changed=4) Failed: 0 ------------ Total states run: 4 Total run time: 3.700 s Summary for helios64 ------------ Succeeded: 6 (changed=5) Failed: 0 ------------ Total states run: 6 Total run time: 22.648 s
... and then the Helios64 automatically reboots and the installation is faulty.
The question remains with us...
Why is the cpu frequency changed at all during the OMV installation?
Is this really necessary or can it be left to the user's settings so that these changes do not occur?
The file is modified because it is under the control of OMV. If you want to use custom settings, then you need to set the environment variables that you can find here: https://github.com/openmediava…/files/cpufrequtils.j2#L1
-
is just a thought when the wrong "0" values are written or who is responsible for the output at that time...
Code/usr/lib/python3/dist-packages/salt/utils/pycrypto.py:26: DeprecationWarning: 'crypt' is deprecated and slated for removal in Python 3.13 import crypt /usr/lib/python3/dist-packages/salt/modules/linux_shadow.py:21: DeprecationWarning: 'spwd' is deprecated and slated for removal in Python 3.13 import spwd Deploying service configurations ... <<<<< here !? Processing system modifications ... <<<<< or here !?
These lines are written by the postinst script of the openmediavault package.
-
I have replaced hdparm with smartctl because the later one is in active development, whereas hdparm and hdidle seem to be dead as projects. I also assume that the smartmontools project has high knowledge about everything that has to do with harddisks.
-
I don't understand that answer.
If someone has prepared a ready plugin for installing PhotoPrism, it should simply work after installing it. Otherwise, this plugin should be removed from the plugin list and no one will use it.
The plugin is working. I always get it running when I install it. I can not reproduce the errors that some users have.
If there are problems and I can not reproduce it, then the community should provide a fix because this is how open source works. Nobody is paying me to fix your problems in my spare time.
-
I assume the config is for the network device eth0, but with Debian 12 and the new kernel the device is named end0 on RPIs. Use omv-firstaid to reconfigure the network.
-
The ID of the user is random and may be different on Debian and its (ARM) derivates depending on what other users and groups have been installed previously.
-
You need to install the openmediavault-md plugin.
-
Please have a look at the openmediavault-k8s Kubernetes plugin and use the PhotoPrism recipe to install this app. The standalone plugin based on Podman makes more troubles than it helps. Debugging problems is not trivial.
-
It may be that only unformatted media can be used.
This is correct, a filesystem must exist; preferably a Linux POSIX filesystem like EXT4, XFS, JFS, BTRFS.
-
Sure, but the community is responsible for contributing the recipes; it is not my job to do everything on my own. Otherwise I have to think about making OMV commercial to have all the time that is necessary for that.