The config below yields the following error message in the log:
plugin_value_list_clone: Unable to determine interval from context for value list "global/aggregation-num/memory". This indicates a broken plugin. Please report this problem to the collectd mailing list or at <http://collectd.org/bugs/>.
Moreover, when specifying aggregation's LoadPlugin explicitly, one sometimes gets the following:
uc_update: Value too old:
Rerunning sometimes makes it go away, sometimes not. It's quite unpredictable.
Last but not least, the actual value returned by aggregation (should be equal to 4 in theory) is quite unpredictable too: sometimes 0, sometimes 4, sometimes 8. Worse, if the interval of aggregation is N times larger than the interval of memory, the resulting num is 4N.
Am I doing something obvious very wrong?
The text was updated successfully, but these errors were encountered:
I think this should be kept open. #539 is a PR addressing parts of this issue and #297 is a separate issue. Anyway, that said, I've looked further into the "value too old" issue. It turns out that it's a race during setup of the plugin (or rather in utils_vl_lookup). However, that should happen independent on whether the autoloading is enabled (but given that it's a race, different configs may make it more or less likely to happen). I'll send a separate PR in a bit.
This could cause multiple aggregation instances to be created in the
aggregation plugin when first writing data to the plugin. This, in turn, led
to "value too old" warnings because subsequently all data was submitted twice.
Thanks to @faxm0dem for reporting this in GH collectd#535.