Bug#710658: collectd: df plugin causes lots of syslog messages: Illegal attempt to update
Hello, I found a solution to this problem (at least for me) at http://emacstragic.net/collectd-causing-rrd-illegal-attempt-to-update-using-time-errors/ I include the full article bellow in case it disapears: Collectd causing rrd illegal attempt to update using time errors I found collectd was giving me a whole load of errors in my syslog: Aug 20 16:27:12 mythbox collectd[32167]: rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/mythbox/df-root/df_complex-free.rrd) failed: /var/lib/collectd/rrd/mythbox/df-root/df_complex-free.rrd: illegal attempt to update using time 1345444032 when last update time is 1345444032 (minimum one second step) It was adding one message like that every second so my logs were completely full of it. Google didn’t reveal much except that this sort of error is either because there are two instances of RRD trying to write the RRD database at the same time, or that my server’s date and time are way out of sync. Neither of these were true in my case. I asked on #collectd on freenode and a very nice person by the name of tokkee told me that it’s a known issue of sorts. The df plugin for collectd uses /proc/mount to determine which drives to check free space on and if / is in there twice, it tries to update the entry for / twice and causes the problem. The solution is to add the following to the /etc/collectd/collectd.conf file: Plugin df FSType rootfs IgnoreSelected true /Plugin Then I restarted collectd and my logs were peaceful again. The fun part is that the solution was given by tokkee. Is it the same tokkee as Sebastian Harl tok...@debian.org maintainer of this package? :-) Bye -- Dr. Ludovic Rousseau -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710658: collectd: df plugin causes lots of syslog messages: Illegal attempt to update
Am Freitag, 9. August 2013, 11:52:35 schrieb Ludovic Rousseau: Hello, Hi Ludovic, I found a solution to this problem (at least for me) at http://emacstragic.net/collectd-causing-rrd-illegal-attempt-to-update-using- time-errors/ I include the full article bellow in case it disapears: Thanks for adding this information. I think tokkee told me this solution and or I read it elsewhere. Just didn´t update the bug. Thanks, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710658: collectd: df plugin causes lots of syslog messages: Illegal attempt to update
Package: collectd Version: 5.1.0-3 Severity: normal Hi Sebastian! I first thought this to be a duplicate of bug #657122, but I applied the configuration change in there. The df plugin is producing lots of log messages like even after fresh install on two VMware ESX hosted virtual machines: Jun 1 12:17:53 somehost collectd[29921]: Initialization complete, entering read-loop. Jun 1 12:17:53 somehost collectd[29921]: battery plugin: Failed to access `/proc/acpi/battery': No such file or directory Jun 1 12:17:53 somehost collectd[29921]: rrdtool plugin: Adjusting RandomTimeout to 0.000 seconds. Jun 1 12:17:53 somehost collectd[29921]: rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/somehost/df-root/df_complex-free.rrd) failed: /var/lib/collectd/rrd/somehost/df-root/df_complex-free.rrd: illegal attempt to update using time 1370081873 when last update time is 1370081873 (minimum one second step) Jun 1 12:17:53 somehost collectd[29921]: rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/somehost/df-root/df_complex-reserved.rrd) failed: /var/lib/collectd/rrd/somehost/df-root/df_complex-reserved.rrd: illegal attempt to update using time 1370081873 when last update time is 1370081873 (minimum one second step) Jun 1 12:17:53 somehost collectd[29921]: rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/somehost/df-root/df_complex-used.rrd) failed: /var/lib/collectd/rrd/somehost/df-root/df_complex-used.rrd: illegal attempt to update using time 1370081873 when last update time is 1370081873 (minimum one second step) Jun 1 12:18:03 somehost collectd[29921]: rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/somehost/df-root/df_complex-free.rrd) failed: /var/lib/collectd/rrd/somehost/df-root/df_complex-free.rrd: illegal attempt to update using time 1370081883 when last update time is 1370081883 (minimum one second step) Jun 1 12:18:03 somehost collectd[29921]: rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/somehost/df-root/df_complex-reserved.rrd) failed: /var/lib/collectd/rrd/somehost/df-root/df_complex-reserved.rrd: illegal attempt to update using time 1370081883 when last update time is 1370081883 (minimum one second step) Jun 1 12:18:03 somehost collectd[29921]: rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/somehost/df-root/df_complex-used.rrd) failed: /var/lib/collectd/rrd/somehost/df-root/df_complex-used.rrd: illegal attempt to update using time 1370081883 when last update time is 1370081883 (minimum one second step) To do a clear reproducer I have re-installed collectd from scratch with clean configuration. On using reportbug I found bug #657122, but these messages also appear when I apply the suggested configuration change: === modified file 'collectd/collectd.conf' --- collectd/collectd.conf 2013-06-01 10:15:00 + +++ collectd/collectd.conf 2013-06-01 10:16:04 + @@ -290,6 +290,18 @@ # Device 192.168.0.2:/mnt/nfs # MountPoint /home # FSType ext3 + # ignore rootfs; else, the root file-system would appear twice, causing + # one of the updates to fail and spam the log + FSType rootfs + # ignore the usual virtual / temporary file-systems + FSType sysfs + FSType proc + FSType devtmpfs + FSType devpts + FSType tmpfs + FSType fusectl + FSType cgroup + IgnoreSelected true # IgnoreSelected false # ReportByDevice false # ReportReserved false My mounts are: somehost:~ cat /proc/mounts rootfs / rootfs rw 0 0 sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 udev /dev devtmpfs rw,relatime,size=10240k,nr_inodes=30491,mode=755 0 0 devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=25452k,mode=755 0 0 /dev/mapper/somevg-debian / ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0 tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0 tmpfs /run/shm tmpfs rw,nosuid,nodev,noexec,relatime,size=50880k 0 0 /dev/sda1 /boot ext3 rw,relatime,errors=continue,barrier=1,data=ordered 0 0 /dev/mapper/somevg-var /var ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0 /dev/mapper/somevg-varlog /var/log ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0 /dev/mapper/somevg-home /home ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0 /dev/mapper/somevg-srv /srv ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0 ntp is up and running timesync with hypervisor is disabled: somehost: LANG=C vmware-toolbox-cmd timesync status Disabled somehost:~#69 For know I think I just disable the df plugin. Thanks, Martin -- System Information: Debian Release: 7.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Bug#710658: collectd: df plugin causes lots of syslog messages: Illegal attempt to update
Martin Steigerwald mar...@lichtvoll.de wrote: The df plugin is producing lots of log messages like even after fresh install on two VMware ESX hosted virtual machines: Jun 1 12:17:53 somehost collectd[29921]: Initialization complete, entering read-loop. Jun 1 12:17:53 somehost collectd[29921]: battery plugin: Failed to access `/proc/acpi/battery': No such file or directory Jun 1 12:17:53 somehost collectd[29921]: rrdtool plugin: Adjusting RandomTimeout to 0.000 seconds. Jun 1 12:17:53 somehost collectd[29921]: rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/somehost/df-root/df_complex-free.rrd) failed: /var/lib/collectd/rrd/somehost/df-root/df_complex-free.rrd: illegal attempt to update using time 1370081873 when last update time is 1370081873 (minimum one second step) [...] To do a clear reproducer I have re-installed collectd from scratch with clean configuration. On using reportbug I found bug #657122, but these messages also appear when I apply the suggested configuration change: Does this continue to happen after the first iteration? There is/was a bug that caused read callbacks to be executed twice upon startup. On a related note: this message keeps making trouble and should really be turned into a complaint. Cheers, Sebastian Hi Martin, -- Sent from my phone. Please excuse my brevity. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710658: collectd: df plugin causes lots of syslog messages: Illegal attempt to update
Martin Steigerwald mar...@lichtvoll.de wrote: Am Samstag, 1. Juni 2013, 14:46:00 schrieb Sebastian Harl: Martin Steigerwald mar...@lichtvoll.de wrote: The df plugin is producing lots of log messages like even after fresh install on two VMware ESX hosted virtual machines: Jun 1 12:17:53 somehost collectd[29921]: Initialization complete, entering read-loop. Jun 1 12:17:53 somehost collectd[29921]: battery plugin: Failed to access `/proc/acpi/battery': No such file or directory Jun 1 12:17:53 somehost collectd[29921]: rrdtool plugin: Adjusting RandomTimeout to 0.000 seconds. Jun 1 12:17:53 somehost collectd[29921]: rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/somehost/df-root/df_complex-free.rrd) failed: /var/lib/collectd/rrd/somehost/df-root/df_complex-free.rrd: illegal attempt to update using time 1370081873 when last update time is 1370081873 (minimum one second step) [...] To do a clear reproducer I have re-installed collectd from scratch with clean configuration. On using reportbug I found bug #657122, but these messages also appear when I apply the suggested configuration change: Does this continue to happen after the first iteration? There is/was a bug that caused read callbacks to be executed twice upon startup. On a related note: this message keeps making trouble and should really be turned into a complaint. What do you mean by first iteration? I had those happen on one server for long time without really noticing it: somehost:~ zgrep -c illegal attempt /var/log/syslog* /var/log/syslog:6682 /var/log/syslog.1:25920 /var/log/syslog.2.gz:25920 /var/log/syslog.3.gz:25920 /var/log/syslog.4.gz:25920 /var/log/syslog.5.gz:25920 /var/log/syslog.6.gz:26129 /var/log/syslog.7.gz:25926 Earliest message I still have is: somehost:~ zcat /var/log/syslog.7.gz | grep illegal attempt | head -1 May 25 06:25:15 somehost collectd[2188]: rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/somehost/df-root/df_complex-free.rrd) failed: /var/lib/collectd/rrd/somehost/df-root/df_complex-free.rrd: illegal attempt to update using time 1369455915 when last update time is 1369455915 (minimum one second step) And it happens also after restarting collectd. Log messages appear immediately and continue to appear as long as collectd is running, so far as I have observered. Yep, that's what I meant. I'll need to have another look at that, then. Cheers, Sebastian -- Sent from my phone. Please excuse my brevity. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710658: collectd: df plugin causes lots of syslog messages: Illegal attempt to update
Am Samstag, 1. Juni 2013, 14:46:00 schrieb Sebastian Harl: Martin Steigerwald mar...@lichtvoll.de wrote: The df plugin is producing lots of log messages like even after fresh install on two VMware ESX hosted virtual machines: Jun 1 12:17:53 somehost collectd[29921]: Initialization complete, entering read-loop. Jun 1 12:17:53 somehost collectd[29921]: battery plugin: Failed to access `/proc/acpi/battery': No such file or directory Jun 1 12:17:53 somehost collectd[29921]: rrdtool plugin: Adjusting RandomTimeout to 0.000 seconds. Jun 1 12:17:53 somehost collectd[29921]: rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/somehost/df-root/df_complex-free.rrd) failed: /var/lib/collectd/rrd/somehost/df-root/df_complex-free.rrd: illegal attempt to update using time 1370081873 when last update time is 1370081873 (minimum one second step) [...] To do a clear reproducer I have re-installed collectd from scratch with clean configuration. On using reportbug I found bug #657122, but these messages also appear when I apply the suggested configuration change: Does this continue to happen after the first iteration? There is/was a bug that caused read callbacks to be executed twice upon startup. On a related note: this message keeps making trouble and should really be turned into a complaint. What do you mean by first iteration? I had those happen on one server for long time without really noticing it: somehost:~ zgrep -c illegal attempt /var/log/syslog* /var/log/syslog:6682 /var/log/syslog.1:25920 /var/log/syslog.2.gz:25920 /var/log/syslog.3.gz:25920 /var/log/syslog.4.gz:25920 /var/log/syslog.5.gz:25920 /var/log/syslog.6.gz:26129 /var/log/syslog.7.gz:25926 Earliest message I still have is: somehost:~ zcat /var/log/syslog.7.gz | grep illegal attempt | head -1 May 25 06:25:15 somehost collectd[2188]: rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/somehost/df-root/df_complex-free.rrd) failed: /var/lib/collectd/rrd/somehost/df-root/df_complex-free.rrd: illegal attempt to update using time 1369455915 when last update time is 1369455915 (minimum one second step) And it happens also after restarting collectd. Log messages appear immediately and continue to appear as long as collectd is running, so far as I have observered. Thanks, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
