Error started getting after put Intel 520X 10gb NIC in FreeNAS server

[Ray Milyard]

Nov 10 12:10:03 freenas collectd[3957]: aggregation plugin: Unable to read the current rate of "freenas.local/cpu-3/cpu-user".
Nov 10 12:10:03 freenas collectd[3957]: utils_vl_lookup: The user object callback failed with status 2.
Nov 10 12:27:43 freenas collectd[3957]: aggregation plugin: Unable to read the current rate of "freenas.local/cpu-3/cpu-user".
Nov 10 12:27:43 freenas collectd[3957]: utils_vl_lookup: The user object callback failed with status 2.
Nov 10 13:30:33 freenas collectd[3957]: aggregation plugin: Unable to read the current rate of "freenas.local/cpu-3/cpu-user".
Nov 10 13:30:33 freenas collectd[3957]: utils_vl_lookup: The user object callback failed with status 2.

After installing this Intel 520X NIC I am now getting this error all the time. Any ideas why or how to fix this?

 

[Chris Moore]

Is that a supported NIC?

Currently, Chelsio 10GbE NICs are the preferred choice for use with FreeNAS, and are the models
shipped with iXsystems hardware.

https://www.ebay.com/itm/110-1107-3...NGLE-PORT-10GB-SFP-PCIE-ADAPTER-/282590499118

 

[Chris Moore]

https://forums.freenas.org/index.php?resources/hardware-recommendations-guide.12/

 

[dlavigne]

Nov 10 12:10:03 freenas collectd[3957]: aggregation plugin: Unable to read the current rate of "freenas.local/cpu-3/cpu-user".
Nov 10 12:10:03 freenas collectd[3957]: utils_vl_lookup: The user object callback failed with status 2.
Nov 10 12:27:43 freenas collectd[3957]: aggregation plugin: Unable to read the current rate of "freenas.local/cpu-3/cpu-user".
Nov 10 12:27:43 freenas collectd[3957]: utils_vl_lookup: The user object callback failed with status 2.
Nov 10 13:30:33 freenas collectd[3957]: aggregation plugin: Unable to read the current rate of "freenas.local/cpu-3/cpu-user".
Nov 10 13:30:33 freenas collectd[3957]: utils_vl_lookup: The user object callback failed with status 2.

After installing this Intel 520X NIC I am now getting this error all the time. Any ideas why or how to fix this?

That was a bug that will be fixed in 11.1 (already in RC1).

 

[Ray Milyard]

That was a bug that will be fixed in 11.1 (already in RC1).

Thanks. So guess I don't need worry about it.