there is no output. Anyways this was just a side error I noticed while the actual problem is the rrd-cached thing, which happens after I restart omv.
It comes out write cache size is a Samba configuration option. Have you added this via Extra Options field? I'm asking because OMV does not add this to smb.conf.
It comes out write cache size is a Samba configuration option. Have you added this via Extra Options field? I'm asking because OMV does not add this to smb.conf.
# Extra options
min receivefile size = 16384
write cache size = 524288
getwd cache = yes
socket options = TCP_NODELAY IPTOS_LOWDELAY
read raw = yes
write raw = yes
seems like so
Any body there? Problem is not resolved in omv 7.3
Hi Folks,
I try to move from Unraid to OMV last week.
Then I have to see the Log (boot in this case) ist filled up and up with these lines:
4.10.2024, 19:42:44
collectd[1211]: rrdcached plugin: rrdc_update (/var/lib/rrdcached/db/localhost/cpu-8/cpu-nice.rrd, [1728063764.609550:0], 1) failed: rrdcached@unix:/run/rrdcached.sock: RRD Error: mmaping file '/var/lib/rrdcached/db/localhost/cpu-8/cpu-nice.rrd': Invalid argument (status=-1)
4.10.2024, 19:42:44
rrdcached[1202]: handle_request_update: Could not read RRD file.
4.10.2024, 19:42:44
collectd[1211]: rrdcached plugin: Successfully reconnected to RRDCacheD at unix:/run/rrdcached.sock
4.10.2024, 19:42:44
collectd[1211]: rrdcached plugin: Successfully reconnected to RRDCacheD at unix:/run/rrdcached.sock
4.10.2024, 19:42:44
rrdcached[1202]: handle_request_update: Could not read RRD file.
4.10.2024, 19:42:44
rrdcached[1202]: handle_request_update: Could not read RRD file.
4.10.2024, 19:42:44
collectd[1211]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1.
4.10.2024, 19:42:44
collectd[1211]: rrdcached plugin: rrdc_update (/var/lib/rrdcached/db/localhost/cpu-5/cpu-nice.rrd, [1728063764.609544:0], 1) failed: rrdcached@unix:/run/rrdcached.sock: RRD Error: mmaping file '/var/lib/rrdcached/db/localhost/cpu-5/cpu-nice.rrd': Invalid argument (status=-1)
4.10.2024, 19:42:44
rrdcached[1202]: handle_request_update: Could not read RRD file.
4.10.2024, 19:42:44
collectd[1211]: rrdcached plugin: Successfully reconnected to RRDCacheD at unix:/run/rrdcached.sock
4.10.2024, 19:42:44
rrdcached[1202]: handle_request_update: Could not read RRD file.
4.10.2024, 19:42:44
collectd[1211]: Filter subsystem: Built-in target `write': Some write plugin is back to normal operation. `write' succeeded.
4.10.2024, 19:42:44
collectd[1211]: rrdcached plugin: Successfully reconnected to RRDCacheD at unix:/run/rrdcached.sock
The logs are getting bigger and bigger with these entries.
I searched for a solution or an Idea to get the problem solved - but nothing really found.
This topic here is from June 2023 and seems to be the same problem with OMV 6.x and 7.x. I am using the actual OMV 7.4.9-1
There are a lot of other questions on OMV System, but this one is the biggest in the moment because i fills up the computer with always the same messages in the logs (more than 100.000 since the last system-restart just 3 hours ago...)
It doesn´t make a good impression when things like this occur, have obviously not been resolved after months and you don´t get any further informations.
So do I have to live with those mistakes in OMV?
Sorry for my bad english.
I searched for a solution or an Idea to get the problem solved - but nothing really found.
This thread contains at least five suggestions. Which one did you try and what was the output of the commands and the result regarding the logs?
Hello Macom,
I am not so good in english therefor I may not understood or having seem the right advice. I saw "This solves it for a while until it happens again!" from #oopenmediavault and saw "Any body there? Problem is not resolved in omv 7.3" from #Invinum.
As I wrote, I am using the actual Vision of OMV (7.4.9-1) and there is still this behavior.
The problem seems to exist since OMV 6.x and is still not really solved at 7.3 as Invinum wrote. My information for you is that it still exists in 7.4.
This thread contains at least five suggestions. Which one did you try and what was the output of the commands and the result regarding the logs?
So, which of the five suggestions should I use with the option really solving the problem?
Why do you think I will get other results than the others before?
May be there is a missunderstanding in this post.
This is not a common issues, otherwise the forum would be full of threads related to this.
Most likely the issue happens only under certain circumstances (e.g. a corrupted file system). So a proposal that did not work for others, but still work for you.
If you provide the output of the commands, they might contain also a hint regarding the underlying problem.
Don’t have an account yet? Register yourself now and be a part of our community!
