error in syslog regarding rrdcached

Same issue here - same symptoms. It's filling up my rootfs and eventually reaches 100%. At that point OMV UI becomes non-responsive. Yet another issue is that the sd is being written to much more often than necessary cutting down sd life.

System is BeagleBone Black. I'm using an image from another user's BBB as a starting point. Currently without modification. Is it possible the wide time difference is a result of a past time reference variable in the other user's system? If so, how is that past time brought to the current time? Seems like that's what needs to be addressed.

Syslog:

Oct 10 15:44:36 openmediavault monit[1175]: ‘rootfs’ space usage 94.6% matches resource limit [space usage>80.0%]Oct 10 15:45:01 openmediavault /USR/SBIN/CRON[4502]: (root) CMD (/usr/sbin/omv-mkgraph >/dev/null 2>&1)Oct 10 15:45:01 openmediavault rrdcached[1243]: Received FLUSHALLOct 10 15:45:01 openmediavault rrdcached[1243]: queue_thread_main: rrd_update_r (/var/lib/rrdcached/db/localhost/interface-eth0/if_errors.rrd) failed with status -1. (/var/lib/rrdcached/db/localhost/interface-eth0/if_errors.rrd: illegal attempt to update using time 1444512602 when last update time is 1922983631 (minimum one second step))

on RPi you should add an RTC module.........don't know BBB but it could be too

See this Guide for adding a RTC module:

RPi 2(RTC module): from unruly Stepchild to Wunderkind

PS- you should be using the flash memory plugin when you are using a SD card or USB stick as the system drive too.

I'm having the exact same problem: rrdcached is filling up my syslog with:
....
May 10 23:00:01 nas rrdcached[2352]: queue_thread_main: rrd_update_r (/var/lib/rrdcached/db/localhost/rrdcached/queue_length.rrd) failed with status -1. (/var/lib/rrdcached/db/localhost/rrdcached/queue_length.rrd: illegal attempt to update using time 1462913849 when last update time is 1481037057 (minimum one second step))
May 10 23:00:01 nas rrdcached[2352]: queue_thread_main: rrd_update_r (/var/lib/rrdcached/db/localhost/rrdcached/operations-receive-flush.rrd) failed with status -1. (/var/lib/rrdcached/db/localhost/rrdcached/operations-receive-flush.rrd: illegal attempt to update using time 1462913849 when last update time is 1481037057 (minimum one second step))
May 10 23:00:14 nas rrdcached[2352]: queue_thread_main: rrd_update_r (/var/lib/rrdcached/db/localhost/interface-eth0/if_octets.rrd) failed with status -1. (/var/lib/rrdcached/db/localhost/interface-eth0/if_octets.rrd: illegal attempt to update using time 1462914009 when last update time is 1481037057 (minimum one second step))
May 10 23:00:17 nas rrdcached[2352]: queue_thread_main: rrd_update_r (/var/lib/rrdcached/db/localhost/load/load.rrd) failed with status -1. (/var/lib/rrdcached/db/localhost/load/load.rrd: illegal attempt to update using time 1462914009 when last update time is 1481037057 (minimum one second step))
....

What can I do? The above tips are not helping.
It seems rrdcached is having problems accessing my RAID1. I'm using OMV on RPi with two USB-HDDs in a RAID array.

Did you read the link in my post above on adding a RTC module???

Yes, I did - but I think this is not the solution to the problem. I see others were having the same issue too and were able to solve it without a RTC module.
I was able to find a couple of different solution strategies which helped other people but unfortunately not me:

First:
- Turn on "Use NTP server" in Date & Time Settings in OMV web interface
- execute in SSH shell:

service collectd stop
cd /var/lib/collectd/rrd/raspberrypi
rm -rf *
service collectd start

Second:
execute in SSH shell:

echo $(date +"%Y-%m-%d %T") > /etc/fake-hwclock.data

Third:
Add the following to the /etc/collectd/collectd.conf file:

<Plugin df>
    FSType "rootfs"
    IgnoreSelected true
</Plugin>

I tried all solutions but none helped. By the way, here is a link to the full set of log lines that are added to the syslog about every 10 minutes.

That thread is the best way to run OMV on a RPi. RTC modules are not expensive.

Ok, I just did a

find / -type f -newermt 2016-12-01

to find all files that are created after Dec 1 2016 (in the future) because the timestamp in the log is on Dec 6 2016.
This is giving me thousands of files - although I installed OMV on my RPi just two weeks ago. Some files are:

./etc/mailcap
./etc/nginx/sites-available/openmediavault-webgui
./etc/nginx/openmediavault-webgui.d/security.conf
./etc/init.d/f2r-var-lib-monit-tmpfs
./etc/init.d/f2r-var-spool-tmpfs
./etc/init.d/f2r-var-lib-openmediavault-rrd-tmpfs
./etc/init.d/f2r-var-tmp-tmpfs
./etc/init.d/f2r-var-lib-rrdcached--tmpfs
./etc/init.d/f2r-var-log-tmpfs
./etc/init.d/f2r-var-lib-php5-tmpfs

Could it be that the OMV installer is setting incorrect creation dates? Could this be the reason for the error messages?

Ok, I did the following:

service rrdcached stop
rm -rf /var/lib/rrdcached/db/localhost/*
service rrdcached start

no more messages in syslog so far ...

If you want your logs and graphs to be normal the RTC module is what you need to do. If you want to run without a RTC module I would disable the graphs. I am not going to spend a lot of time discussing all the reasons.

How can I disable the graphs?

I think if you disable at System / Monitoring that will turn off the graphs.

Great, thanks
I should have actually found that myself

That should solve your problems for now. If you get a RTC module you will like it. I was not happy with my RPi 2 til I got one.

Actually, I would recommed turning off monitoring on RPi 1 as this frees lots of resources that are badly needed elsewhere on this feeble system

I am saying if you want OMV fully functional. Which I did.