Unresponsive Service Processor API service causing command timeout due to hung servprocd
- Views:
- 3,594
- Visibility:
- Public
- Votes:
- 1
- Category:
- fas-systems
- Specialty:
- hw
- Last Updated:
- 2/17/2025, 1:23:00 AM
Applies to
Issue
- Autosupport collection for platform subsystem data times out after 120 seconds
cluster::*> system node autosupport manifest show -status *-limit -fields subsys,status,error,time-collected -subsys !log_files -time-collected >120000
node seq-num prio-num subsys time-collected status error
-------------- ------- -------- -------- -------------- ------------------------------- -----
node-01 812 49 platform 125315 collection-truncated-time-limit
node-01 804 133 platform 125300 collection-truncated-time-limit
node-01 797 49 platform 125197 collection-truncated-time-limit
- Commands like
system node power show
andsystem node environment sensors show
time out after 120 seconds:
::> system node environment sensors show -node node-01
Warning: Unable to list entries on node node-01. The Service Processor on node "node-01" is not reachable. Verify that the SP or BMC is online, verify that api-service is enabled on the SP or BMC, verify that the partner node is running, check if pings from SP or BMC to partner node work, check if hw-assist keep-alives are normal, check that network ports are configured correctly and are functional (up). Then, try the command again.
Warning: Unable to list entries on node node-01. Timeout: Operation "environment_sensors_iterator::next_imp()" took longer than 50 seconds to complete [from mgwd on node "node-01" (VSID: -1) to mgwd at 169.XXX.XX.XXX]
Error: show failed: Timeout: Operation "environment_sensors_iterator::next()" took longer than 50 seconds to complete [from mgwd on node "node-01" (VSID: -1) to mgwd at 169.XXX.XX.XXX]
::> system node power show -node node-01
Error: The Service Processor on node "node-01" is not reachable. Verify
that the SP or BMC is online, verify that api-service is enabled on the
SP or BMC, verify that the partner node is running, check if pings from
SP or BMC to partner node work, check if hw-assist keep-alives are
normal, check that network ports are configured correctly and are
functional (up). Then, try the command again.
Warning: Unable to list entries on node node-01. SP API service is not available on node "node-01".
Check SP firmware version and Data Ontap(R) version.
Error: show failed: SP API service is not available on node
"node-01". Check SP firmware version and Data Ontap(R) version.
- The same error is reported in the
MANIFEST.XML
section of the ASUPplatform-sensors.xml.
The Service Processor on node "***" is not reachable. Verify that the SP or BMC is online, verify that api-service is enabled on the SP or BMC,verify that the partner node is running, check if pings from SP or BMC to partner node work, check if hw-assist keep-alives are normal, check that network ports are configured correctly and are functional (up).
Then, try the command again
- The SP API services certificate was ruled out as an issue, refer to Active IQ Wellness Risk: ONTAP reports error when communicating with SP/BMC