:-)
Thanks Andrew,
Yeah, I was aware we could do this. If the warnings really are benign, then
this is OK.
On 18/03/2014, at 14:34:48, "GRAY Andrew G (SPARQ)"
wrote:
> Jesse,
> Here’s a working fix for you, kludgy I know …. Doesn’t answer why, but does
> get you a working system.
>
>
Jesse,
Here's a working fix for you, kludgy I know Doesn't answer why, but does
get you a working system.
/etc/collectd.conf
Change syslog level from info to warning.
LogLevel warning
Regards,
Andrew Gray.
RHCSA, Professional Unix Administration.
From: collectd-boun...
Hi Jesse,
OK, shiny new 1.48 installed ... no change.
What I have tried.
# Explicitly set write target:
Plugin "rrdcached"
No change ... apart from "Dispatching value to all write plugins" changing to
"Dispatching value to 'rrd
Interesting,
I am running rrdtool 1.4.8 (compiled afresh) and collectd 5.4.1 (compiled
afresh also) on Ubuntu Precise 12.04.
Perhaps it's to do with the version of rrdtool. Which version of rrdtool is
your rrdcached using, Andrew?
On 18/03/2014, at 09:57:27, "GRAY Andrew G (SPARQ)"
wrote
I'm seeing this too, I have tried mixing and matching different versions.
5.0.3, 5.1.0, 5.4.1. Recompiled my own collectd rpms. No change.
I'm down to trying another version of rrdtools (the one I'm using is off
rpmfind.net, Rrdtools 1.4.7-1.el6.rfx.x86_64.rpm)
I only seem to get this when I ru
Did you work this out David?
I'm seeing the same thing on a test collectd 5.4.1 server I've just set up.
The server is busy (>500 packets per second arriving on it) and there are heaps
of these errors being logged.
Anyone got any ideas?
Eg:
Mar 17 22:01:31collectd-03 collectd[16278]: uc_u
