volkovd Any hint how to reproduce this?
Beiträge von votdev
-
-
Thx for the report. The issue will be fixed in openmediavault 7.4.10, see https://github.com/openmediava…481d5afee3d9eb807b1c8f07e.
-
Any idea what has installed the udisk things? I only know about them on a desktop system. On a system that is installed via the OMV ISO it is not included.
-
You should have a look at https://docs.k3s.io/installation/requirements?os=pi. I have not added that to the openmediavault-k8s plugin because i was not sure if this till applies. If you can confirm that it works after applying the changes, then i will implement it in the plugin. A reboot of the system is necessary after changing /boot/cmdline.txt.
-
Sorry but it seems that "apt-get install openmediavault=7.4.8-1" doesn't work because only version 7.4.9-1 is available
Yes, reprepro which is used to build the OMV package repository does not support that. You can manually download older packages, but not install them via APT.
-
-
This may be true, but the values of these tools are not used for the display. As you can see from the code that it is not trivial to make the calculation, it is also not easy to find the error; especially as the code comes from a developer in the community and I am therefore not really familiar with it. It is best if you execute the commands that the code executes step by step yourself and see where the error is in the code. If I know what the problem is, I can fix it. Otherwise there is nothing I can do as it is very unlikely that I can reproduce your setup and status in my developer machine.
-
as i understand you, the collectd config is regenerated by omv at every boot, so no matter what changes i'll add to collectd conf, they will be rewritten by ovm on next boot.
am i right?
It will be regenerated if a filesystem is added or removed via UI.
-
The output of df is not correct for Btrfs because the calculation is much more complicated (see code here).
-
I knew about the UDev attribute of the collectd plugin but that is useless for OMV because e.g. the serial number of disks is not available at the time the plugin configuration is generated and there are massive troubles with serial ids with USB connected disks because manufacturers do not pass through the real serial id and fake them instead; sadly the same ID for all disks connected through that chipset/enclosure.
The finally only the kernel device names can be used.
-
I don't have access to my OVM now to check it, but the time when I configured this and setups time when I want to do backup I choose time between 2am to 3am, the system says the backup will be done between this time (I thought that task should be run once between this time.
If it's working like that, I assume I should specify a minute, or set up this like 2:01 to 2:02 am to run a task, but then is the task will be continued after the 2:02 if there will by active job to do or will be terminated?
The jobs are executed by cron which doesn't take care if there is another job running. But the rsync job exits if there is another job running at the same time (see here).
-
Here is five of them in attachment.
These are rsync cron scripts which are configured by yourself. Maybe you've misconfigured the times they are executed.
-
The answer how to access the app is written at the first line of the recipe.
-
You need to replace everything named <MODIFY> with your custom settings.
-
but instead one mail I'm receiving a 60 (one per minute) e-mail about this single task that is in the process form 2am to 3am.
This is not normal. But without knowing what email you are talking about we can not help to identify the core problem.
-
With the next openmediavault-onedrive 7.1.0 plugin version there is an Extra options field in the UI to configure additional onedrive configuration options.
See https://github.com/openmediavault/openmediavault/pull/1828
-
so, the conslusion - Diskstat plugin can't be used, since the data is not persistent and you never know what disk stats it displays now
am i right?
This might apply to SBC hardware like Raspi where the SATA ports are connected via USB. With AMD64 hardware you should not face the problem because SATA is not connected via crippled USB. At least I have no problems with changing kernel devices in my NAS.
-
Die Meldung kommt dann wenn Du den Browser/Tab schliesst wenn in dem Moment die Ausgabe eines Kommandos in diesem Modalen Dialog ausgegeben wird der wie ein Terminal-Fenster aussieht und Du Dich anschließend wieder an der UI anmeldest.
-
am i right? or it (diskstat) can be someway directed to use persistant symlinks like /dev/dsk1 or whatevere?
No, diskstat only supports kernel device names. Unfortunately this is a bad approach of the plugin, but i can't change that.
-
So what would you recommend?
Rather unistall the plugin and use CLI and install
So it is not under controll of omv?
I mean it can't be that complicated, I just want one folder from OMV synced to on folder in onedrive. Nothing more, nothing less.
The plugin simply does not provide your workflow, so you need to use onedrive from CLI and do the configuration on your own.