FreeNAS11 collectd [3311] spams system event

[John Doe]

Code:

Jun 16 13:42:19 freenas collectd[3311]: utils_vl_lookup: The user object callback failed with status 2.
Jun 16 13:46:59 freenas collectd[3311]: aggregation plugin: Unable to read the current rate of "freenas.local/cpu-0/cpu-user".
Jun 16 13:46:59 freenas collectd[3311]: utils_vl_lookup: The user object callback failed with status 2.
Jun 16 14:26:59 freenas collectd[3311]: aggregation plugin: Unable to read the current rate of "freenas.local/cpu-5/cpu-user".
Jun 16 14:26:59 freenas collectd[3311]: utils_vl_lookup: The user object callback failed with status 2.
Jun 16 15:09:39 freenas collectd[3311]: aggregation plugin: Unable to read the current rate of "freenas.local/cpu-2/cpu-user".
Jun 16 15:09:39 freenas collectd[3311]: utils_vl_lookup: The user object callback failed with status 2.
Jun 16 15:28:09 freenas collectd[3311]: aggregation plugin: Unable to read the current rate of "freenas.local/cpu-3/cpu-user".
Jun 16 15:28:09 freenas collectd[3311]: utils_vl_lookup: The user object callback failed with status 2.
Jun 16 15:34:39 freenas collectd[3311]: aggregation plugin: Unable to read the current rate of "freenas.local/cpu-1/cpu-user".
Jun 16 15:34:39 freenas collectd[3311]: utils_vl_lookup: The user object callback failed with status 2.
Jun 16 16:17:19 freenas collectd[3311]: aggregation plugin: Unable to read the current rate of "freenas.local/cpu-3/cpu-user".
Jun 16 16:17:19 freenas collectd[3311]: utils_vl_lookup: The user object callback failed with status 2.
Jun 16 17:08:49 freenas collectd[3311]: aggregation plugin: Unable to read the current rate of "freenas.local/cpu-0/cpu-user".
Jun 16 17:08:49 freenas collectd[3311]: utils_vl_lookup: The user object callback failed with status 2.
Jun 16 17:15:39 freenas collectd[3311]: aggregation plugin: Unable to read the current rate of "freenas.local/cpu-1/cpu-user".
Jun 16 17:15:39 freenas collectd[3311]: utils_vl_lookup: The user object callback failed with status 2.
Jun 16 17:27:09 freenas collectd[3311]: aggregation plugin: Unable to read the current rate of "freenas.local/cpu-1/cpu-user".
Jun 16 17:27:09 freenas collectd[3311]: utils_vl_lookup: The user object callback failed with status 2.
Jun 16 17:34:59 freenas collectd[3311]: aggregation plugin: Unable to read the current rate of "freenas.local/cpu-1/cpu-user".
Jun 16 17:34:59 freenas collectd[3311]: utils_vl_lookup: The user object callback failed with status 2.
Jun 16 19:12:39 freenas collectd[3311]: aggregation plugin: Unable to read the current rate of "freenas.local/cpu-2/cpu-system".

What is this?

 

[dlavigne]

This is currently slated to be fixed for 11.1: https://bugs.freenas.org/issues/23857.

 

[John Doe]

ok thanks

 

[MDKRUSH]

I'm getting same thing but no updates available for stable 11...

 

[NASbox]

Is there a work around for this to shut up the console message?

Is this coming from a script or from something compiled? If it's python or shell script I'd be OK with editing it manually if someone can point me in the right direction.

If it's a script it should be easy to patch until a proper fix is created. Can someone suggest either a manual patch to null out the error call, or instructions to turn off the offending service? (and what are the implications of doing so?)

I don't almost nothing about the system internals, but if I understand the message correctly, it looks like its coming from a module that is collecting performance stats for graphing/logging. I'd rather lose some performance stats short term than put up with these messages.

 

[dlavigne]

The update with the fix is expected on Oct 23.

 

[NASbox]

The update with the fix is expected on Oct 23.

That helps a lot... What is the aggregation plugin? if it's just stats, any easy way to turn it off. I'm doing a lot of testing, and these messages are causing important information to scroll off the screen.

 

[dlavigne]

I don't think so...from the bug referenced above it looks like it required an updated version of collectd.

 

[ajschot]

still keeps on comming... we have to wait till 11.1
I have them a lot too....