Really? I thought newer generations of CPU were not supported! Thanks for the clarification then.
What about the new 8th generation then? Will it be supported by OMV 4?
omv 4?
-
-
Really? I thought newer generations of CPU were not supported! Thanks for the clarification then.
What about the new 8th generation then? Will it be supported by OMV 4?What wouldn't be supported? The cpu generally isn't the problem. Usually it is something with the motherboard like the network adapter. Hard to say about the 8th generation stuff since bleeding edge hardware and servers generally aren't mixed.
-
What wouldn't be supported? The cpu generally isn't the problem. Usually it is something with the motherboard like the network adapter. Hard to say about the 8th generation stuff since bleeding edge hardware and servers generally aren't mixed.
This is why I was in doubt: New coffee lake processor
-
-
This is why I was in doubt: New coffee lake processor
cpu support really isn't dependent on the OMV version. The kernel is what matters. You can compile your own kernel in OMV 3.x to get support. The 4.9 backports kernel in OMV 3.x supports a lot though. The 4.13 backports kernel in OMV 4.x probably supports 8th gen stuff but I don't have one to try. Why buy such a new cpu for a server?
-
Well as I wrote in that topic, the new i3-8100 seems a good bargain since it has 4 cores and is pretty cheap.
But I could easily be satistfied with a 7th generation processor. -
Well as I wrote in that topic, the new i3-8100 seems a good bargain since it has 4 cores and is pretty cheap.
But I could easily be satistfied with a 7th generation processor.Try it. Then we will all know Or you could search for people using that cpu with Debian Jessie or Stretch. That would tell you if it would work with OMV.
-
-
Try it. Then we will all know Or you could search for people using that cpu with Debian Jessie or Stretch. That would tell you if it would work with OMV.
I probably will, as soon as OMV 4 gets officially released
-
Hello,
Several of these RRDCacheD errors in syslog when booting:
Oct 7 10:03:56 Sirius collectd[983]: rrdcached plugin: Failed to connect to RRDCacheD at unix:/var/run/rrdcached.sock: Unable to connect to rrdcached: No such file or directory (status=2)
Tried, this:
omv-mkconf collectd
omv-mkconf rrdcached
rebootNo luck. Then tried the following:
rm -r /var/lib/rrdcached/db/localhost
rm /var/lib/rrdcached/journal/*
service collectd restart
service rrdcached restart
reboot... no joy either
Did anyone solve this issue?
Greetings,
Hendrik -
Hello,
Did anyone solve this issue?
Greetings,
Hendrikany news?
thanks -
-
I ran into the same problem with rrdcached. The unix domain socket isn't getting created in /var/run it is being created in /tmp. I was able to work around the issue by creating a symlink /var/run/rrdcached.sock ---> /tmp/rrdcached.sock
I was unable to determine why none of the overrides are working. I didn't find anything wrong with /etc/default/rrdcached or /etc/init.d/rrdcached. The only reason I found the socket was I found on the internet that /tmp was the default place. So perhaps rrdcached is not processing its command line options properly.
FYI:
ii collectd 5.7.1-1.1 arm64 statistics collection and monitoring daemon
ii rrdcached1.6.0-1+b2arm64 data caching daemon for RRDtool
Debian GNU/Linux 9 (stretch)
OMV 4.0.19-1
Linux NAS1 4.11.2 #22 SMP Sat May 27 11:14:47 CST 2017 aarch64 GNU/LinuxThis was the error message I was getting in /var/log/syslog
Feb 21 11:03:05 NAS1 collectd[2825]: rrdcached plugin: Failed to connect to RRDCacheD at unix:/var/run/rrdcached.sock: Unable to connect to rrdcached: No such file or directory (status=2) -
I'm running OMV3, and still having this issue.
Is this solution working out for you ?
Code
Alles anzeigenFeb 21 17:00:43 server collectd[1792]: rrdcached plugin: rrdc_update (/var/lib/rrdcached/db/localhost/sensors-coretemp-isa-0000/temperature-temp3.rrd, [1519250443:29.000000], 1) failed with status -1. Feb 21 17:00:43 server collectd[1792]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1. Feb 21 17:00:43 server collectd[1792]: rrdcached plugin: rrdc_update (/var/lib/rrdcached/db/localhost/rrdcached/queue_length.rrd, [1519250443:0.000000], 1) failed with status -1. Feb 21 17:00:43 server collectd[1792]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1. Feb 21 17:00:43 server collectd[1792]: rrdcached plugin: rrdc_update (/var/lib/rrdcached/db/localhost/rrdcached/operations-receive-update.rrd, [1519250443:133988], 1) failed with status -1. Feb 21 17:00:43 server collectd[1792]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1. Feb 21 17:00:43 server collectd[1792]: rrdcached plugin: rrdc_update (/var/lib/rrdcached/db/localhost/rrdcached/operations-receive-flush.rrd, [1519250443:3137], 1) failed with status -1. Feb 21 17:00:43 server collectd[1792]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1. Feb 21 17:00:43 server collectd[1792]: rrdcached plugin: rrdc_update (/var/lib/rrdcached/db/localhost/rrdcached/operations-write-updates.rrd, [1519250443:1682], 1) failed with status -1. Feb 21 17:00:43 server collectd[1792]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1. Feb 21 17:00:43 server collectd[1792]: rrdcached plugin: rrdc_update (/var/lib/rrdcached/db/localhost/rrdcached/operations-write-data_sets.rrd, [1519250443:133916], 1) failed with status -1. Feb 21 17:00:43 server collectd[1792]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1. Feb 21 17:00:43 server collectd[1792]: rrdcached plugin: rrdc_update (/var/lib/rrdcached/db/localhost/rrdcached/gauge-tree_nodes.rrd, [1519250443:5.000000], 1) failed with status -1. Feb 21 17:00:43 server collectd[1792]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1.
-
Hi,
I have broken my new installation. I was getting the erros concerning lines 109 and 117 in "/usr/lib/python3.5/weakref.py".I followed the instructions to edit these lines (discussed much earlier in this thread) but accidently added characters to line 118.
I have reformatted the text so that it looks correct but get this message:
from weakref import WeakKeyDictionary
File "/usr/lib/python3.5/weakref.py", line 118
self._remove = remove
^
IndentationError: unindent does not match any outer indentation levelNow the everything has broken down and I do not know how to replace the file with its original version.
Will I need to reinstall the whole system?
Thanks in advance
-
-
IndentationError: unindent does not match any outer indentation level
Now the everything has broken down and I do not know how to replace the file with its original version.
Will I need to reinstall the whole system?
If you do not have a backup of the file you could try to fix indentation of the lines you edited. It's important to keep that intact.
Have a look here
https://docs.python.org/2.0/ref/indentation.htmlUse spaces and no tabs.
Or install OMV into a VM and copy thats weakref.py over your damaged one.
-
Thanks for your help.
I have checked the spaces and all looks identical.The caret points to the end of the line, not the start. Is that significant?
Can I somehow just reinstall the whole python package?
-
Can I somehow just reinstall the whole python package?
-
-
-
Hi All,
I recently started using OMV. I was googling for a solution to that rrdcached issue and found this thread, posting my solution here in case if anyone is looking for the same.
My Version: 4.1.17-1 (Arrakis)
1. Create a systemd service file ==> /lib/systemd/system/rrdcached.service
Code
Alles anzeigen[Unit] Description=Cache daemon for rrd values After=local-fs.target network.target Requires=local-fs.target network.target Before=collectd.service [Service] Type=notify NotifyAccess=main EnvironmentFile=-/etc/default/rrdcached ExecStart=/usr/bin/rrdcached $BASE_OPTIONS -w $WRITE_TIMEOUT -b $BASE_PATH -j $JOURNAL_PATH -p $PIDFILE -l unix:${SOCKFILE} StandardOutput=journal StandardError=journal RemainAfterExit=yes Restart=always RestartSec=10 [Install] WantedBy=multi-user.target
2. Create a symlink:
Codeln -s /lib/systemd/system/rrdcached.service /etc/systemd/system/multi-user.target.wants/rrdcached.service
3. Reload systemd config4. Stop/enable/start the service.
5. Check out the statusif you see this message in status output -- "Warning: Fake start-stop-daemon called, doing nothing." Run the following followed by by a stop/start process.
In case if anyone is in need of the full command line option for rrdcachedCoderoot@filer1:~# ps -ef | grep rrd root 20912 1 0 14:53 ? 00:00:00 /usr/bin/rrdcached -B -F -f 3600 -w 900 -b /var/lib/rrdcached/db/ -j /var/lib/rrdcached/journal/ -p /var/run/rrdcached.pid -l unix:/var/run/rrdcached.sock root 21134 13198 0 15:00 pts/0 00:00:00 grep rrd
Thanks,
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!