Search

Error starting a collector for asset=mnode_hostname
https://kb.netapp.com/on-prem/solidfire/hardware_Kbs/Error_starting_a_collector_for_asset_mnode_hostname
mNode is stil able to forward the second storage cluster data to Active IQ May 02 2022 02:25:09.491 INFO Starting collector for SF-xxxx storage_id=1054c4d2-xxxx-xxxx-xxxx-xxxxxxxxxxxx May 02 2022 02:2...mNode is stil able to forward the second storage cluster data to Active IQ May 02 2022 02:25:09.491 INFO Starting collector for SF-xxxx storage_id=1054c4d2-xxxx-xxxx-xxxx-xxxxxxxxxxxx May 02 2022 02:25:09.510 INFO Starting collector for SF-xxxx storage_id=577a07f5- xxxx-xxxx-xxxx-xxxxxxxxxxxx May 02 2022 02:25:09.516 ERROR Error starting a collector for asset=SF-xxxx - continuing on to allow other collectors to start if present: ('Connection aborted.', error(104, 'Connection reset by peer'))
Repeating 'Service sfvasa is not running' error on several nodes
https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/Repeating_Service_sfvasa_is_not_running_error_on_several_nodes
Applies to NetApp Element Software 12.X NetApp SF-series NetApp H-series Issue The following alert repeats in NetApp SolidFire Active IQ and in the Cluster UI: Service sfvasa is not running